Governance

Continuity Audit Suite

Tools for anyone who needs to check our work.

Approved by the Board for implementation · 20 November 2026

In one paragraph

The Continuity Audit Suite is how anyone can check CRIS's work. It samples the proofs that test every change, the decisions that promote or reject new versions, and the permanent record of what was learned. It re-runs a share of those proofs independently, and checks every claim in our public benefit report against its evidence. Its findings go to our board and, once it is appointed, to an independent Audit Council, and a summary is published. It is our answer to the oldest question in governance: who checks the checkers?

It does not improve the loop; it checks that the loop did what it says. Every other promise on this site, that changes are tested, that purpose is kept, that nothing is deleted, that participants are paid fairly, rests on someone outside the team being able to check it.

Where it sits

The Audit Suite does not carry one stage of the loop: it checks the work of every stage, and it runs beside every layer of the CRIS stack.

The Audit Suite
checks every stage
  1. Observe

    Observe the world as it is, and record where each observation came from.

    Learn more about observe →

  2. Verify

    Verify every observation, and every change a system makes to itself, against evidence it has not seen.

    Learn more about verify →

  3. Reason

    Reason only from what has been verified, in steps someone else can trace.

    Learn more about reason →

  4. Accumulate

    Accumulate what was verified, so knowledge adds up instead of being overwritten.

    Learn more about accumulate →

  5. Benefit

    Benefit people and the environment: participants share in the value they create, and every change is weighed against our public benefit purpose.

    Learn more about benefit →

  6. Continue

    Continue, changing anything except correspondence with reality and continuity of purpose.

    Learn more about continue →

Select a tile to see what it does. Every tile links to its page.

One continuity loop runs beneath every CRIS product: ten core systems and four applied programmes, as described in Recursion Without Rupture.

Our approach treats safety as continuity: the risk is drift, not intelligence (book Chapter 16.2). Every safeguard checks whether correspondence with reality and purpose survived a change, and the Audit Suite is the layer that checks all the other safeguards. It sits at the independent end of the five layers of assurance.

  1. Automated checksProofs and drift tests
  2. Human reviewC-Gate board, every release
  3. Independent auditAudit Council, major versions
  4. External standardThird-party certification
  5. Public reportBenefit report, every year
Five layers of assurance around the engine, from machine speed to public view.

Rules for this system are proposed in the AI Constitution, Article 22: audit and assurance. They are approved by the Board for implementation.

What it checks

The Audit Suite checks four things, each produced by a different part of CRIS.

The four things the Audit Suite checks, and the question it asks of each.
What is checkedProduced byThe questionEvidence
Correspondence proofsCorrespondence ProverDoes the proof hold if re-run independently?Held-out evidence; signed proofs
C-Gate decisionsC-GateWere purpose tests, drift checks and rollback done as the rules require?C-Gate reports; review board minutes
The ledgerKnowledge LedgerIs history complete and unaltered?Entry links; signatures; consolidation records
Benefit claimsPublic benefit reportIs every published result backed by evidence?Scorecard sources; payout data; programme results

How it works

Audits happen on a published calendar, before or after every major version, and whenever someone complains. Each audit follows four steps.

Three triggers

  1. Scheduled auditOn a published calendar
  2. Major versionBefore or after release
  3. ComplaintFrom anyone, inside or outside CRIS
  1. 1SampleProofs, gate decisions and ledger entries
  2. 2Re-runA subset of proofs, independently
  3. 3CheckBenefit claims against their evidence
  4. 4ReportFindings to the board; a summary published
The Audit Suite workflow (CRIS document, Section 9). The plan proposes Audit Council summaries twice a year and an audited benefit report every year.
  1. Sample proofs, gate decisions and ledger entries.
  2. Re-run a subset of proofs independently.
  3. Check benefit claims against their evidence.
  4. Report findings to the board and publish a summary.

The CRIS plan proposes Audit Council summaries twice a year and an audited benefit report every year.

Sampling and re-runs

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 rest are drawn at random, and the sample is recorded before work starts, so management cannot change it.

Always included
  • Major versions
  • Decisions held for people
  • Complaints
  • Large payouts
Then at randomFrom everything in the period, using a seed the auditor sets
Recorded before work startsThe sample cannot be changed by management
Sampling: risk first, then at random. The auditor chooses the sample, not the people audited. Sample sizes will be published with the audit method.

The strongest check is a re-run. 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.

  • The candidate
  • The baseline
  • The held-out evidence set
  • The tolerances
Published procedureRun by the auditor on separate infrastructure
  • Match, within toleranceThe proof is confirmed
  • MismatchA finding; the promotion it supported is reviewed
Re-running a proof independently: the strongest check the Audit Suite performs.

Benefit claims and standards

As a public benefit corporation, CRIS reports on the public benefit it creates. Our charter ties that benefit to a third-party standard, and we publish a report every year. The Audit Suite traces every number in that report to its source and recomputes it, because our risk register names the danger: benefit claims overstated (book Chapter 13.4).

  1. Published resultA number in the public benefit report
  2. Trace to sourceScorecard sources, payout data, programme results
  3. RecomputeThe auditor recalculates it
  4. Confirmed or a findingOverstated claims are corrected
Candidate standardsISO/IEC 42001 (management of AI systems) and B Lab’s assessment (overall benefit), with the Audit Suite mapped to both. Candidates only, until the board records its choice in the bylaws.
Checking benefit claims: every number traced to its source and recomputed.

Two standards are under consideration: ISO/IEC 42001 for the management of AI systems, and B Lab's assessment for overall benefit, with the Audit Suite as our own method mapped to both. These are candidates; the board will record its choice in our bylaws. Results are tracked on our scorecard.

Who audits the auditors

A verifier that answers to the people it checks is not independent. Our plan is an independent Audit Council of three to five members, drawn from academics, standards experts and community representatives, that reviews the results and reports to our board, not to management. An external assessor checks us against a recognised standard. The team that runs the audit tools cannot change the findings.

  • BoardReceives findings, requires fixes, publishes the reportReports to: Stockholders, under the public benefit duty
  • Audit Council (to be appointed)Three to five independent members; inspects proofs, gate decisions and the ledger; reviews major versions and the benefit reportReports to: The board, not management
  • External assessorChecks CRIS against the chosen third-party standardReports to: The board
  • Trust and SafetyRuns the tools, the calendar and the toolkit; cannot edit findingsReports to: Management, with a direct line to the Audit Council
Who audits the auditors. The answer to “verifier captured by management” (book Chapter 8.5): the Audit Council reports to the board, with an external standard on top.
Note. The Audit Council has not yet been appointed. Until it is, the board reviews audit results directly, and this page will name the council and its chair once the board appoints them.
RoleDoesReports toCannot
Audit Council (to be appointed)Inspects proofs, C-Gate decisions and the ledger; reviews major versions and the benefit reportThe boardBe managed by the teams it audits
Trust and SafetyRuns the tools, the audit calendar and the toolkitManagement, with a direct line to the Audit CouncilEdit findings
External assessorChecks CRIS against the chosen third-party standardThe boardRely only on CRIS's own reports
BoardReceives findings, requires fixes and publishes the reportStockholders, under the public benefit dutyDelegate the decision to publish

Findings and disclosure

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.

  1. CriticalA promoted version whose proof does not re-run
    FixPromotions frozen at once; fixed before any further release
    DisclosureIncident note on the Trust page; in the next benefit report
  2. MajorA C-Gate decision made without a required rollback test
    FixWithin one release cycle
    DisclosureIn the next Audit Council summary
  3. MinorA ledger entry missing a field, with no effect on decisions
    FixWithin the next audit period
    DisclosureIn the summary, in aggregate
What happens to a finding (proposed): rated, fixed, checked again and disclosed.
Awaiting counsel. Severity levels, fix deadlines and disclosure wording are proposals for counsel and the board to approve.

A critical finding follows our incident response: detect, contain, record, investigate, fix the loop, and disclose.

The public toolkit

You will be able to read our audit method, look at summary views of the record, re-run a published proof with our kit, read a sample report, ask for an audit or make a complaint. Requesting an audit and making a complaint are open now; the rest are linked here as they are published.

  • Audit methodThe public form of the book’s continuity audit frameworkDraft 0.1
  • Ledger viewsSummaries for the public; full read-only views for accredited auditorsTo be published
  • Re-run kitRe-run a published proof yourselfTo be published
  • Sample audit reportWhat a report looks likeTo be published
  • Request an auditAsk for an audit of something we have doneAvailable now
  • Make a complaintA complaint can start an auditAvailable now
The public audit toolkit: “tools for anyone who needs to check our work”. Items link here as they are published.

Status and read more

This status is set by the CRIS team and links to the evidence behind it. The CRIS plan calls for the first public benefit report to be audited against the chosen standard in 2028.

Current status: Status to be confirmed

LevelEvidence requiredWho sets it
ResearchConcept page; draft audit method (book Appendix D) publishedCEO
PrototypeA test audit of a CRL test cycle: sample drawn, proofs re-run, findings reportedCEO, on the Labs and Systems leads’ advice
PilotAudit Council appointed; first audit summary published; first benefit report auditedCEO
LiveRegular audits on the published calendar; external assessment against the chosen standard passedCEO, with notice to the board

For developers: the Verify path and the audit method, draft 0.1.

Next steps

Owner: Trust and SafetyNext review: 2027-03-01