PLATFORM / IMMUNE-RESPONSE
Recovery needs its own authority.
A failed proof cannot authorise replacement of the legitimate key.
PROTOCOL EXPLAINER
The design and its boundary.
Reject invalid protected requests. Apply explicit containment policy, then establish a successor only through an authorised recovery path.
Concurrency controls and rate limits must prevent arbitrary invalid requests from creating repeated recovery churn. Preserve lineage and distinguish pending from finalised evidence.
START WITH THE SESSION
See the session lifecycle under test.
Explore the boundary. Inspect the decision. Trace the recovery.