comgu

DataHub Core

Open the catalog

This is our own DataHub Core instance — the same stack anyone gets from datahub docker quickstart, holding 1,267 entities across eight platforms. Everything Comgu claims about lineage, ownership and authority is readable here, in the source rather than in a screenshot.

Sign in with

Usernamejudge
Passwordnorthstar-2026

Open context.comgu.site →

Your browser will show its own sign-in box. That dialog is drawn by the browser, not by us, so we cannot put these credentials inside it — which is why this page exists.

Why there is a login at all. DataHub's own account on a fresh install is datahub/datahub, which is a well-known default and not something to leave facing the internet. The basic-auth layer in front of it exists so that default is never reachable. It is not hiding anything from you.

What to look at

Four things, in the order Comgu reads them. Each one changes what a run does.

1 · The authoritative asset

Search for NH-BREW-PRO and open the Shopify catalog dataset. Its structured property comgu.authority is set to authoritative. That marker is what makes it the source of truth — Comgu does not assume it.

2 · The lineage

Open the Lineage tab. Five downstream surfaces project from that asset, some three hops out. This graph is the blast radius — Comgu walks it with get_lineage rather than holding its own list of what to check.

3 · Criticality and ownership

Each downstream asset carries comgu.criticality and comgu.customer_facing, which set finding severity. Note that the AI shopping manifest has no owner — Comgu turns that absence into a finding instead of guessing a recipient.

4 · What a run wrote back

After you approve a remediation in the demo, the affected assets carry comgu.last_run, comgu.pull_request_url, comgu.incident_status and a comgu:remediated tag, plus a Decision document. Every write is read back before it is reported.

Try breaking it. Delete the lineage edges from the Shopify catalog asset, trigger a run, and the blast radius comes back empty — every rule skips. Clear comgu.authority and the engine halts rather than choosing a value. Restore either and the six findings return. Two tests in the repository assert exactly this.

How Comgu uses DataHub, in detail →

Simulated assets are labelled

The downstream commerce platforms are simulated — there is no live Merchant Center account behind this. Every simulated asset is tagged comgu:simulated-downstream in the catalog you are about to open, so you can tell them apart without taking our word for it.