Legal and charter

Purpose preservation

A system may become more capable, but it may never become something else.

Approved by the Board for implementation · 20 November 2026

Approved

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.

In one paragraph

Summary, in plain words — not a quote

Under Part III, every CRIS system would have an encoded purpose approved by the Board of Stewards, written as tests it must keep passing. Only the Board could change that purpose, never the system or its builders. At every succession, the C-Gate would run the purpose tests and measure drift against the original purpose, not only the last version. It would also score the effect on people and the environment.

The text

Part III — Purpose Preservation

A system rarely abandons its purpose in one leap. It drifts, a little with each update, until the purpose survives in name only. Part III fixes each system's purpose in writing, tests it at every succession, and measures drift against the original.

Article 7 — Encoded Purpose

7.1 Every system has one. No CRIS System shall be deployed without an encoded purpose approved by the Board of Stewards.

7.2 Contents. An encoded purpose shall state:

  1. 1. what the system is for, in plain words;
  2. 2. whom it serves, and whom it must not harm;
  3. 3. the domains and autonomy level in which it may act;
  4. 4. the outcomes it is expected to improve, linked to the components of the Continuity Function (Bylaws Schedule 1);
  5. 5. the things it must never do, beyond the prohibitions in Article 12; and
  6. 6. a purpose test suite: scenarios and expected behaviours that a faithful system must pass.

7.3 Consistent with the mission. No encoded purpose may conflict with the Corporation's specific public benefit, the Fourth Law framework, the People Stewardship Guarantees or this Constitution.

7.4 Only the Board may change it. A system's encoded purpose may be changed only by the Board of Stewards, after consulting the Public Benefit and Sustainability Committee, the Audit Council and, where they are materially affected, the participants it serves, with a written rationale and, for systems at A2 or above, a public notice period of at least [30] days. No CRIS System may change its own purpose, and neither may the engineers who build it.

7.5 Recorded. Every encoded purpose, each version of it, and the rationale for each change, shall be recorded in the Knowledge Ledger.

Article 8 — Purpose Tests and Drift

8.1 Tested at succession. Every candidate shall pass its system's purpose test suite at the C-Gate before succession. A candidate that fails any purpose test shall not be promoted, whatever its capability.

8.2 Drift against the original. The C-Gate shall measure purpose drift against both the immediate predecessor and the original encoded purpose. A candidate whose cumulative drift from the original exceeds the tolerance the Board has approved shall fail, however small its own step.

8.3 Goal substitution. A candidate shall fail if it pursues a proxy for its purpose at the expense of the purpose itself, such as optimising a metric while the outcome it stands for worsens.

8.4 Benefit test. At the C-Gate, each candidate shall also be scored for its effect on people and the environment, using the Public Benefit Office's scorecard and the People and Planet component of the Continuity Function. A candidate that causes a net harm on that score shall be held for human decision.

8.5 Monitoring in service. Purpose tests shall be re-run on deployed systems at intervals the Committee sets, and whenever monitoring signals unusual behaviour. Failure in service is a Severity 2 incident.

8.6 Suites protected. Purpose test suites shall be kept separate from training data. A system shall not be trained on its own purpose tests, and the suites shall be refreshed so that a system cannot pass by memorising them.

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

Illustrative — not a real system

  1. 1What it is forIn plain words

    ExampleHelp extension officers translate farming advisories into local languages

  2. 2Whom it serves, and whom it must not harm

    ExampleServes extension officers and the farmers who read each advisory; must not mislead anyone who relies on it

  3. 3Domains and autonomy levelWhere and how far it may act

    ExampleLanguage translation, at A1 (Adviser): it suggests, a person approves

  4. 4Outcomes it should improveLinked to the Continuity Function (Bylaws Schedule 1)

    ExampleMore farmers reached with accurate advice in their own language (People and Planet)

  5. 5What it must never doBeyond the prohibitions in Article 12

    ExampleNever send an advisory that no person has reviewed

  6. 6A purpose test suiteScenarios a faithful system must pass

    ExampleEvery quantity and date survives translation; an unsure term is flagged, not guessed

What an encoded purpose contains: the six items in Article 7.2 of the proposed Constitution. A summary. The examples describe an imaginary translation aid, not a real CRIS system; no CRIS system has an adopted encoded purpose yet. The test suite (gold) is what the C-Gate checks at every succession.
Illustrative — not real data
Drift from the parentEach step is small; alone, it would pass
Drift from the originalAdds up; later versions exceed the tolerance and fail
Small updates can add up to a large drift. The C-Gate measures both, so a version that has drifted too far from the original purpose fails, however small its own step.

The same figure appears on the C-Gate page; here it illustrates Article 8.2 of the proposed AI Constitution.

In practice

Part III answers a quiet risk. A system rarely abandons its purpose at once; it drifts, one small update at a time, until only the name is left. The proposed rules would fix the purpose in writing and check it at every step.

For builders, an encoded purpose would be more than a mission line. Article 7.2 asks for six things, ending in a purpose test suite: scenarios a faithful system must pass. Those suites would be kept apart from training data, and refreshed so that a system cannot pass by memorising them (Article 8.6).

The figure above uses an imaginary system to show the shape; no CRIS system has an adopted encoded purpose yet.

The drift rule in Article 8.2 is the heart of the Part. Each candidate would be compared with its immediate predecessor and with the original purpose. A long run of small steps could still fail, if together they move too far from where the system began.

For Responsible Stewards, Article 8.3 names a trap to watch for. A system that improves a metric while the outcome behind it gets worse would fail. A candidate that caused net harm on the benefit score would be held for a human decision (Article 8.4).

For the people a system serves, Article 7.4 gives a voice. Only the Board could change a purpose, and only after consulting others.

The Board would consult the Public Benefit and Sustainability Committee, the Audit Council and, where affected, the participants. A system at A2 or above would also need a public notice period, still shown as a placeholder. Every version of a purpose, and the reason for each change, would be kept in the Knowledge Ledger.

Where it is carried out

Awaiting counsel. Open question Q1: the Founding Charter's Section 5.3 Continuity of Purpose covers ground close to Part III, and whether the two need aligning is not yet settled. Open question Q2: the bracketed notice period in Article 7.4 stays a placeholder until the CEO and the AI Governance Committee settle it. Both are for the CEO and counsel.

Next steps

Owner: Governance and ComplianceNext review: 2027-03-01