Create your first Shutdown Gate
Complete the local-live quickstart first. You need a ready DataHub scenario, PostgreSQL, the worker, and a verified inference provider.
- Run
pnpm db:seedand open the printed/accords/<gate-id>route. The seed creates a draft; it does not analyze or approve retirement. - Start analysis. Payne records the capability snapshot, evidence boundary, downstream consumers, exact lineage path where available, schemas, query context, consumer contract, and deterministic blocker.
- Inspect the evidence and reasoning summary. Model interpretation is bounded to cited evidence; deterministic rules own the gate result.
- Prepare the supported PostgreSQL compatibility artifact. Prepared for review means generated and validated, not accepted or applied.
- Review the exact checksum-bound artifact. The accountable owner may accept it. Accepted still does not mean applied.
- Apply it through the official sandbox. Payne verifies baseline and artifact integrity, runs the fixture, updates the scenario lineage, and re-ingests it.
- Wait for a fresh DataHub read. A mutation response alone is provisional.
- Preview and authorize the allowlisted write-back. Each write is reread before it is verified.
- Confirm Open under current evidence, Monitoring active, and a recent Last verified time. A human still retains shutdown authority.
Day 2 evidence change
pnpm local:day2After the monitoring cadence runs, refresh the gate and confirm Previous approval invalidated, the new consumer evidence, impact, and required action.
Last updated on