Continuity summary
Infra should say what is live, what is staged, and what still needs a transaction, proof receipt, or explicit refusal before users rely on it.
Continuity gate
checking
What continuity proves
A refresh is not a clean slate by implication. It must point to source truth, current chain state, endpoint posture, and the first receipt or explicit pending state.
RuntimeShow the chain that actually booted.
Public status should expose chain identity, height, freshness, and snapshot posture.
Status path ProofBind continuity to evidence.Hashes, receipts, and first-proof labels keep service refreshes from becoming narrative resets.
Proof path RefuseName fixture and replay failures.Bad local fixtures and stale routes should fail visibly instead of becoming public state.
Failure path ExposePublish the bounded labels.The data feed provides the machine-readable version of what the status pages show.
Data pathRequired continuity proofRows that separate an actual-chain runtime from a convenient local harness.
Continuity requirements
checking
Policy inputsWallet metadata, minting, reserve, routes, providers, pricing, and public stats.
Policy inputs
checking
Fixture refusalsPublic route state must come from live handshakes, acknowledgements, hashes, receipts, and source-truth evidence.
Fixture refusals
checking
Continuity report fieldsWhat actually booted and what remains pending before endpoint exposure.
Continuity report fields
checking