Proof of Persistence
Proof of Persistence is evidence that a control's efficacy held over a declared span, every epoch within declared tolerances and with no Silent Drift. A change to the control's fingerprint ends the claim at the change.
What it means
Proof of Persistence answers one question: Does the efficacy still hold over time?
Proof of Persistence is the claim that a control’s measured efficacy held over a declared span: across every epoch of a PP-SPEC-077 Production Stream Mode run, or a declared series of Bounded Mode runs, its Efficacy Rate and False Block Rate stayed within tolerances declared in advance, and no Silent Drift event occurred. Every DUT Fingerprint change inside the span is recorded and ends the claim at that change.
A proof from one day is a proof about that day.
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 a guarantee about the future. It covers the declared span, and nothing after it.
- It does not carry across a DUT Fingerprint change. A changed control is a new control.
Where it sits
Proof of Persistence is one member of the Proof of X family. Only Proof of Efficacy answers whether a control worked; Proof of Persistence answers one other question a buyer, insurer or regulator needs answered before relying on it. Defined in PP-SPEC-091 of the Proof Protocol.