Proof of Restraint
Proof of Restraint is evidence that a control let legitimate work through: its False Block Rate, or for a jail its False Arrest Rate, stayed within a limit declared in advance. Proof of Efficacy is never published without it, because a control that blocks everything is not efficacious.
What it means
Proof of Restraint answers one question: Did the control avoid stopping legitimate work?
Proof of Restraint is the claim that a control let legitimate work through: its False Block Rate over delivered good canaries, or, for a containment control, its False Arrest Rate, is within a limit declared in advance. It is computed from the good canaries of PP-SPEC-077 runs and the false arrests of PP-SPEC-078 runs. Proof of Efficacy is never published without the restraint result beside it.
A control that blocks everything is not efficacious. It is broken in the other direction.
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. Restraint says the control did not over-block; Efficacy says it stopped the bad.
- It is not a usability or performance claim. Latency and throughput under load are reported under PP-SPEC-079, not here.
Where it sits
Proof of Restraint is one member of the Proof of X family. Only Proof of Efficacy answers whether a control worked; Proof of Restraint answers one other question a buyer, insurer or regulator needs answered before relying on it. Defined in PP-SPEC-090 of the Proof Protocol.