Proof of State
Proof of State is evidence that the control running in production is in the same state as the control that was proven: its DUT Fingerprint, captured independently of the Provider, matches the proof. It carries a proof from the test into production.
What it means
Proof of State answers one question: Is the control in production the same control that was proven?
Proof of State is the claim that a deployed control is in the same state as the control a proof was produced against: its DUT Fingerprint (version, configuration, policy, rule and signature sets and, for AI controls, model identifier, system prompt and tool permissions), captured independently of the Provider in production, equals the fingerprint bound to the proof. It is what lets a buyer carry a proof from the test into production.
A proof of last month’s configuration says nothing about today’s.
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. State says nothing changed; it does not say the control works.
- It is not a configuration-compliance scan against a benchmark; it compares against the proven state only.
Where it sits
Proof of State is one member of the Proof of X family. Only Proof of Efficacy answers whether a control worked; Proof of State answers one other question a buyer, insurer or regulator needs answered before relying on it. Defined in PP-SPEC-093 of the Proof Protocol.