Correspondence proof format
The parts of a proof, the three verdicts, staged conditions and the signature.
A draft (0.x): read it, build to it and comment on it; it may change without notice. Drawn from the Correspondence Prover page. Changelog · Comment on this specification
Relies on: Continuity Invariant · Relied on by: Ledger entry format, CTU metering method, Audit method, Staged rollout
This is a draft for Systems Engineering to correct, not a final specification.
A.1 Purpose
A correspondence proof records whether a candidate version of a system matches reality at least as well as the version it would replace, tested on evidence the system has never seen. Every candidate change produces one proof, whatever the verdict, and every proof is written to the Knowledge Ledger.
A.2 Parts of a proof
| Part | Required | Meaning |
|---|---|---|
| Candidate and baseline | Yes | Identifiers of the proposed version and the live version |
| Evidence set | Yes | Identifiers of the held-out evidence used, never the evidence itself |
| Domains | Yes | The result in each domain the change could affect |
| Contradictions | Yes (may be empty) | Each place model and evidence disagree, with the evidence source |
| Verdict | Yes | One of pass, staged, fail |
| Conditions | Only if staged | The limits and monitoring a staged trial must keep |
| Signature | Yes | The Prover’s signature and time, so tampering is detectable |
A.3 Rules
- Both versions face exactly the same evidence.
- A loss in any domain fails the proof, unless a board-approved tolerance allows a staged trial.
- For domains where evidence is uncertain, a proof may be probabilistic, with a stated confidence; thresholds are set by the board, never by the Prover.
- A proof is never edited. A correction is a new proof that refers to the old one.
A.4 Verdicts
| Verdict | Condition | Next step |
|---|---|---|
| Pass | At least as faithful in every domain | The candidate goes to the C-Gate |
| Staged | A small loss within a tolerance the board has approved | A limited, monitored trial; proved again before promotion |
| Fail | Less faithful in any domain, beyond tolerance | Not promoted; recorded; sent back with the contradictions |
A.5 Illustrative example
{
"proofFormat": "0.1.0",
"candidate": "example-system@2",
"baseline": "example-system@1",
"evidenceSet": ["held-out-set-A"],
"domains": [
{ "domain": "domain-1", "baseline": 0.91, "candidate": 0.93, "result": "no-loss" },
{ "domain": "domain-2", "baseline": 0.88, "candidate": 0.88, "result": "no-loss" }
],
"contradictions": [],
"verdict": "pass",
"conditions": null,
"signature": { "key": "example-key", "time": "2027-01-01T00:00:00Z", "value": "..." }
}To validate it, check that every required part in A.2 is present, that the verdict is one of the three, that conditions are null unless the verdict is staged, and that no domain shows a loss under a pass.
A.6 Changelog
- 0.1.0 · 11 November 2026 · minor · First draft, from the Correspondence Prover page.
Printed from the developer hub changelog, the one record of every version.
