EVIDENCE-FIRST SCHEMA CHANGE PREFLIGHT

Know the blast radius before merge.

SchemaShield turns catalog context into a reproducible risk decision, compatibility artifacts, and an approval-gated writeback plan.

Run an offline replay Inspect verified evidence

This browser experience uses synthetic OFFLINE SNAPSHOT fixtures. It does not connect to, read from, or mutate a live DataHub instance.

A protected data catalog connected to schema, analytics, and lineage consumers — HOSTED MODEOFFLINE SNAPSHOT

01 / READ CONTEXT02 / TRACE IMPACT03 / GENERATE GUARDRAILS04 / REQUIRE APPROVAL

SEPARATELY VERIFIED LOCAL ROUNDTRIP

The live integration was tested. The browser stays safe.

A controlled run against local DataHub OSS v1.6.0 seeded three synthetic DEV datasets, inspected schema and two-hop lineage, then applied and read back a risk tag and decision document.

Schema fields observed: 3
Downstream hops verified: 2
Risk tag: VERIFIED
Decision document: VERIFIED

Agent Context Kit / readlist_schema_fields

Observed order_id, customer_id, and order_total.

DataHub SDK / lineagelineage.get_lineage

Verified one-hop and two-hop downstream dependencies.

Agent Context Kit / writebackadd_tags · save_document · get_entities

Applied approved synthetic writebacks and read them back.

01 / OFFLINE INPUT

Choose a replay case.

Each case is a committed synthetic catalog snapshot. The same deterministic core used by the command-line replay evaluates it here.

OFFLINE SNAPSHOT / ZERO LIVE WRITEBACKS

02 / EVIDENCE-BACKED DECISION

Inspect the proof, not a promise.

Risk, evidence references, and generated SQL come from the offline core. Nothing shown in this section was read from or written to DataHub.

AWAITING OFFLINE REPLAY

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