PROOF · ARTEFACTS FROM REAL RUNS
Evidence first. Claims second.
Determinism is a security property, not a feature. Below are artefacts from actual runs — the kind of evidence you can hand to an auditor, not a list of promises.
Determinism
Two independent passes of 500 iterations produced a byte-identical event stream.
- Iterations
- 500 × 2 passes
- Digest, pass A
- sha256:12fc9fee…
- Digest, pass B
- sha256:12fc9fee…
- Divergences
- 0
Replay is driven by recorded cassettes, so model calls are part of the determinism guarantee — not an exception to it.
Algebraic invariants
Every algebraic law is checked in CI. A broken law fails the build — it does not file a warning.
- Invariants passing
- 20 / 20
- Digest
- sha256:988c490f…
- Families
- P01–P03 · Q01–Q07 · A01–A10
- Gate
- blocking
Internal notes previously claimed 23 invariants; the actual run reports 20. We publish the number the run reports.
Java parity
Our compiler's stdout is byte-identical to JDK 17 on the parity suite.
- Cases
- 4 / 4
- Reference
- JDK 17 javac
- Comparison
- byte-for-byte stdout
- Divergences
- 0
“Close enough” was never accepted as a passing result.
Constitutional defence
Dangerous operations are rejected by rule, not by prompt-time politeness.
- Patterns blocked
- 20 / 20
- Categories
- 8
- Example rule
- E_NO_CLONING
- Escapes
- 0
E_NO_CLONING rejects operator clone : Qubit → (Qubit, Qubit) at compile time, because physics says so.
Why this matters
Anyone can demonstrate that software works. Demonstrating that it works identically every time — and handing over the proof — only matters in regulated work. But there, nothing else will do. A bank cannot point a guessing tool at its COBOL core. It can point a tool that leaves a receipt for every transformation.