SchemaShield

OFFLINE SNAPSHOT

Explore three interactive schema-change cases without touching a catalog. Every hosted result comes from a committed synthetic fixture and links its decision to the supporting evidence.

The hosted demo makes no live DataHub connection, never writes back, and never uses production data.

A protected data catalog connected to schema, analytics, and lineage consumers — Hosted cases stay read-only. The verified roundtrip ran separately against a local DataHub OSS catalog.

VERIFIED LOCAL ROUNDTRIP

A real catalog check behind the demo.

A separate replay against DataHub OSS v1.6.0 read the catalog, followed two lineage hops, wrote a risk tag and decision document, and then read both back to verify the result.

Observed fields: 3
Downstreams: 2
Verified tag: SchemaShieldRiskHigh
Decision document: Verified

Agent Context Kitlist_schema_fieldsadd_tagssave_documentget_entities

DataHub SDK2-hop lineage

Verification evidence is reported here; the hosted interactive cases remain OFFLINE SNAPSHOT and cannot mutate any catalog.

01 / INPUT

Choose a replay case.

These fixtures are synthetic catalog snapshots modeled for DataHub 1.6.0. They demonstrate three narrow, reproducible rules.

OFFLINE SNAPSHOT / NO LIVE DATAHUB

02 / DECISION

Inspect the proof, not a promise.

Risk, evidence references, and generated artifacts come from the deterministic offline core. Nothing shown here was written to DataHub.

AWAITING REPLAY

Select a case and run the preflight to reveal its evidence-backed decision.