Emergency-state boundary
This documentation does not establish a live emergency_state_watch, recovery_status, automatic halt, key rotation, slashing, route pause, or Foundation ratification contract. Prototype MCP names and historical event samples are not operational APIs.
For a real incident, preserve evidence, verify the exact network and runtime, stop ambiguous writes, and follow authenticated instructions shipped through the current release’s designated incident channel. Do not rotate keys, submit attestations, or execute agent-generated remediation from this page.
There is no in-tree bridge to pause and no supported SLH-DSA emergency-rotation path. A future coordination surface requires a versioned threat model, authority and authentication design, replay protection, quorum and expiry rules, human confirmation, rehearsals, rollback, audit logging, and an independent security review.