Audit method
Sample, re-run, check claims, report. Severity levels join after counsel approves them.
A draft (0.x): read it, build to it and comment on it; it may change without notice. Drawn from the Continuity Audit Suite page. Changelog · Comment on this specification
Relies on: Correspondence proof format, Ledger entry format, CTU metering method · Relied on by: Staged rollout
1 Purpose
The audit method is how an independent auditor checks CRIS’s work. It is published so that anyone can see how the checking is done. Severity levels, fix deadlines and disclosure wording are proposals for counsel and our board; they join this specification once approved.
2 Four steps
- Sample proofs, gate decisions and ledger entries.
- Re-run a subset of proofs independently.
- Check benefit claims against their evidence.
- Report findings to the board and publish a summary.
Audits happen on a published calendar, before or after every major version, and whenever someone complains.
3 Sampling
The auditor, not the team being audited, chooses what to check: every high-risk item, and a random share of everything else. High-risk items are always included: major versions, decisions held for people, complaints and large payouts. The sample is recorded before work starts, so management cannot change it.
4 Re-runs
The auditor takes the same inputs (the candidate, the baseline, the held-out evidence and the tolerances) and runs the published procedure again on separate systems. A match within the stated tolerance confirms the proof; a mismatch is a finding, and the promotion it supported is reviewed. See Verify for the procedure and who may see what.
5 Findings
Every finding is rated, fixed and checked again. A critical finding freezes releases until it is fixed and is disclosed on our Trust page. Every finding appears, at least in summary, in the next public benefit report. A critical finding follows the incident path: detect, contain, record, investigate, fix the loop and disclose.
6 Changelog
- 0.1.0 · 11 November 2026 · minor · First draft, from the Continuity Audit Suite page. Severity levels not included until counsel approves them.
Printed from the developer hub changelog, the one record of every version.
