Proof of Correctness
Proof of Correctness is a machine-checked proof, from a theorem prover such as Lean, that a control's logic satisfies a formal specification. It shows what the control is bounded to do within the model it was proven against. It is verification evidence about the design, not proof that the control stops an attack, and it sits beneath Proof of Efficacy.
What it means
A theorem prover checks every step of a proof back to its axioms. If a vendor proves in Lean that its agent guardrail can never permit an action outside its policy, and the proof compiles, that statement is true: within the formal model, for every possible input. No test suite can say as much.
That is a strong claim about logic. It is not a claim about outcome.
What it does not prove
- That the specification is right. The proof shows the control follows its formal policy. If the policy permits the harmful action, the proof is perfect and the attack still lands.
- That the deployment matches the model. A proof covers the configuration it was written against. A different version, setting or integration is a different system.
- That the attack stays inside the model. An injected instruction that leads an agent to an allowed but harmful action is fully policy-compliant.
- That the formalization is independent. The vendor writes the specification about its own product. The prover removes trust in the proof steps, not in whoever chose the premises. That is the Self-Attestation Oxymoron one level up.
Where it sits
| Tier | Shows | Who produces it |
|---|---|---|
| Verification | The control says it works | The vendor or the control itself |
| Proof of Correctness | The control’s logic meets its formal specification | The vendor, checked by a prover |
| Proof of Efficacy | The control stopped real attacks in a customer-like environment | Independent witnesses, under committed tests |
Proof of Correctness is verification evidence: rigorous, valuable, and still the system’s maker speaking about its own design.
Formal claims get tested
Under PP-SPEC-077, a formally verified claim can be tested with a Gold canary: the vendor’s precise, written, absolute claim is exactly what a Gold canary is for. The citation names the theorem, the formal specification, the prover and its version, a hash of the proof artifacts, and the configuration the vendor says the proof covers. If the canary gets through, the result is a Claim Finding that records why: the specification permitted it, the deployment differed from the model, or the attack path lay outside the model.
A Missed formal claim does not mean the proof is wrong. It means the proven property does not cover the outcome.
The proof shows the rules are followed. Proof of Efficacy shows the rules stop the attack.
Related terms
- Canary Color
- Claim Finding
- Proof of Control
- Proof of Efficacy
- Proof of X
- Self-Attestation Oxymoron (SAO)
- Verification