Quiesce — Shutdown assurance

Shutdown assuranceSystem 01<br>Prove your agents<br>truly stop.<br>A stopped parent is not proof that everything it created stopped with it.<br>Run shutdown test→<br>Deterministic simulation · No real infrastructure

00Scenario library

Cloud cleanupThe nine-second deletionThe offboarded tokenThe unrevocable token<br>Run full test suite<br>06Reconstruct — bring your own incident

Paste an incident description, upload a .txt/.md file, or start from a bundled reference. Review the compiled scenario and accept it into the library. The AI authors, the deterministic engine decides. — additions are session-only in the hosted demo.<br>Paste incident textCompile pasted textUpload .txt / .md<br>URL import is available in self-hosted deployments.

Or start from a reference:<br>The nine-second deletion (reference)The offboarded token (reference)The integration that never logged out (reference)PocketOS incident-library entry (verbatim reference)

01Quiescence Trace<br>Recorded activity will appear here when a test begins.

02Logical-time ruler<br>Awaiting the post-STOP clock advance.

03Authority topology

Authority graph awaiting a deterministic run.<br>No topology is inferred before evidence exists.

04Test state

StatusSTANDBY<br>Event count—<br>Logical time—<br>Residual authority—<br>Pending work—<br>Escaped effects—<br>Time to quiescence—<br>Result metrics remain unset until derived from shutdown events.

05Evidence ledger

No events recorded. Start a shutdown test to create an append-only evidence trail.