02 / EXPLORE / RECOVERY
A fault is a candidate
for rejection.
Use a disposable workspace. Corrupt it, inspect the failure, then restore from a retained verified baseline.
The repair sequence
DETECT → ISOLATE → OBSERVE → COMPARE → REWRITE → RE-ROLL → VERIFY
Only an independently checked candidate returns to the admitted state. Otherwise it is rejected or quarantined. The affected layer is not its sole repair authority.
The security boundary has to be built
This is a browser reference model of rejection and restoration. The baseline is retained inside the demonstration. An enforced germline/mind boundary needs readonly storage, separate volatile execution, capabilities and attempted-write tests.
Hash checking detects a mismatch against a trusted baseline. It does not stop an adversary who can replace both data and its unauthenticated reference.
READ THE RECOVERY EVIDENCE →