Build 230 • 43 gates • Test, correct, prove, retest

Startup Readiness Cockpit

Work through every launch gate in order, assign an owner and due date, save proof, correct failures using the gate-specific procedure, and reopen an item when production evidence changes. The database is the status authority; STARTUP_GO_LIVE_GUIDE.md is the detailed human-readable operating guide. Missing, broken, fallback, placeholder, or unproved launch imagery remains its own Critical gate.

Open detailed Startup GuideOpen visual image manifestOpen Process MapOpen Smoke Tests

How to use this page

  1. The initial view shows All statuses, preventing completed D1 records from producing a confusing empty screen. Switch to Open only when actively closing gates.
  2. Open the exact internal page and follow Preparation, every numbered test step, Correction if failed, Evidence, Retest, and Pass condition.
  3. Record the owner, due date, factual result, and a safe evidence link or reference.
  4. Use Blocked only with a clear reason. Use Complete only after the pass condition is proven.
  5. Reopen a completed gate after a related deployment, credential rotation, provider version, schema, policy, or material data change.

When D1 or the network is unavailable, changes are stored only in this browser and visibly marked Unsynced. They are not treated as server evidence until synchronization succeeds.

Loading startup readiness…