Proof of Recovery
Proof of Recovery is evidence that, after a failure, a system returned to its proven state and function within a declared recovery objective, shown by an independent fingerprint capture and passing good canaries. An operator's declaration that service is restored is not evidence.
What it means
Proof of Recovery answers one question: After a failure, was the system restored?
Proof of Recovery is the claim that a system returned to its proven state and function within a recovery objective declared in advance, after a failure: an induced fault, a black hole, or a Missed bad canary whose effect landed. Restoration is established by an independent capture showing the pre-failure fingerprint and by good canaries passing again, never by the operator’s declaration that service is restored.
Resilience is not the absence of failure. It is the proven return from it.
How it is determined
A Claim Declaration is registered and anchored before the evidence it is measured against is produced. The claim is then determined mechanically, from registered Proof Protocol records only, as exactly one of proven, refuted or insufficient. Every determination is published, whatever the result.
What it does not show
- It is not Proof of Efficacy. Recovery says the system came back; it does not say the failure was stopped.
- It is not a backup or disaster-recovery plan, or a record that one exists.
Where it sits
Proof of Recovery is one member of the Proof of X family. Only Proof of Efficacy answers whether a control worked; Proof of Recovery answers one other question a buyer, insurer or regulator needs answered before relying on it. Defined in PP-SPEC-099 of the Proof Protocol.