Recovery — quarantine

Locked

Quarantine is the design requirement that a node stop participating or serving potentially incorrect state after a serious integrity failure. The public docs do not certify trigger codes, on-disk markers, commands, or a procedure for clearing that condition.

A future release must fail closed, preserve evidence, authenticate the operator, require explicit review before rejoining, prevent stale or conflicting state from being served, and document escalation and recovery against the exact runtime version. Clearing isolation must never be inferred from a historical command.

The current Foundation-operated development testnet is value-less and resettable. See Operate for the public boundary.