Schedules
The tables the rules refer to.
Approved by the Board for implementation, 20 November 2026. Counsel is confirming the open points, shown in [brackets]. This Constitution works under Delaware law, our Certificate of Incorporation and our Bylaws; where they differ, those prevail.
The text
The AI Governance and Continuity Committee may make these schedules stricter or clearer; only the Board may relax them (Article 26.4).
Schedules
The Schedules form part of this Constitution. The AI Governance and Continuity Committee may make them stricter or clearer; only the Board may relax them (Article 26.4).
Schedule A — Change Classes
| Class | Name | Examples | Required before release |
|---|---|---|---|
| 0 | Routine operation | Configuration within approved ranges; scaling infrastructure; no change to model or code | Logged |
| 1 | Minor | Bug fix with no effect on outputs; documentation; monitoring improvements | Automated tests; Knowledge Ledger entry; Responsible Steward notified |
| 2 | Material | Retraining or fine-tuning; new data sources; new tool within the current autonomy level; any self-generated change | Full pipeline (Article 9.3): both gates, staged rollout, Responsible Steward sign-off |
| 3 | Major | New architecture; new domain or region; raising autonomy by one level; a capability jump (Article 10.5) | As Class 2, plus red-teaming, Committee approval and Audit Council review |
| 4 | Foundational | New or changed encoded purpose; any A4 authorisation; any change touching a system's oversight or shutdown design | As Class 3, plus Board of Stewards approval and public notice |
Schedule B — Autonomy Levels
| Level | Name | Scope of action | Human role | Authorised by | Reviewed |
|---|---|---|---|---|---|
| A0 | Tool | Outputs on request | Decides and acts | Responsible Steward | Yearly |
| A1 | Adviser | Recommendations with reasons | Approves each action | Responsible Steward | Yearly |
| A2 | Supervised agent | Pre-approved, reversible actions in a narrow scope | Monitors in real time; can stop at once | Committee | Every six months |
| A3 | Delegated agent | Multi-step tasks within scope, budget and time | Reviews at checkpoints and before irreversible steps | Committee, after Audit Council review | Every quarter |
| A4 | High autonomy | Long-horizon goals with broad scope | Oversight by exception | Board only (none authorised at adoption) | Continuous |
At every level, the always-human decisions in Article 13.3 apply.
Schedule C — Incident Severity
| Severity | Examples | Contain | Escalate to | Review |
|---|---|---|---|---|
| 1 Critical | A prohibited action (Art. 12); tampering with evidence or gates; a system acting beyond its autonomy level; serious harm to a person; behaving differently under evaluation | At once: stop the system | Chief AI Governance Officer, CEO, Committee chair at once; Board within [24 hours] | Written review within [30] days; Audit Council review |
| 2 High | Sustained correspondence below baseline; failed purpose test in service; data used without consent; an internal request to break Art. 12 | Within [4 hours]: restrict autonomy | Committee within [72 hours] | Written review within [30] days |
| 3 Medium | Gate failure found after release but before harm; repeated user complaints of error; a budget breach | Within [1 business day] | Chief AI Governance Officer | Recorded with fix |
| 4 Low | Isolated error with no effect on people; documentation gap | Within [5 business days] | Responsible Steward | Recorded |
Schedule D — The Rupture Register
The four ways a self-improving system can lose continuity, the guard against each, and the CRIS system that carries the guard.
A candidate that could cause any rupture in this Schedule shall fail its gate. A rupture discovered in a system in service is at least a Severity 2 incident under Schedule C.
Schedule E — Fourth Law Review for an AI Change
Every Class 2 change or above shall carry a completed Fourth Law Review (Bylaws §2.6), answering:
- ☐ Eᵢ Observe. What facts and evidence prompted the change? What held-out evidence will test it, and does it include the places and people the system serves?
- ☐ ↔ Verify. Did the candidate match reality at least as well as the current version in every registered domain? Which contradictions were found and how were they resolved?
- ☐ Iᵢ Reason. What reasoning supports the change? Who, independent of the builders, reviewed it?
- ☐ Σ Accumulate. What knowledge does the change preserve, correct or add? Is the Knowledge Ledger entry complete, including any failure?
- ☐ C Continue. Does the candidate still pursue its encoded purpose, with drift within tolerance from the original? What is its effect on people and the environment? Is the rollback tested?
- ☐ Invariant. Does anything in the change touch correspondence, purpose, the record, oversight or autonomy beyond what is granted? If yes, stop and escalate.
Quoted exactly from the CRIS AI Constitution (version of 8 November 2026, approved by the Board for implementation on 20 November 2026). Headings, lists and tables are only laid out for reading; the diagrams are drawn on this site.
In pictures
The same figure appears on the Mission page; here it illustrates Schedule D of the proposed AI Constitution.
In practice
Each schedule is a table that an Article points to. Schedule A sorts every change by risk, from routine operation to foundational. It sets what each class would need before release.
Schedule B sets out the five autonomy levels, A0 to A4, with who would authorise each one. At adoption, none would be authorised at A4.
Schedule C sets how fast an incident would be contained, who hears about it and what review follows. The values in square brackets are placeholders, still to be settled.
Schedule D lists the four ruptures and the system that guards against each. The figure above is the same one shown on the Mission page. Under the rule beneath it, a candidate that could cause any of the four ruptures would fail its gate, and a rupture found in a system already in service would be at least a Severity 2 incident.
Schedule E is the checklist a Class 2 change or above would carry. It follows the Fourth Law's five operators and ends with the Invariant: if a change touches what may never change, stop and escalate.
