Resources

Developer hub

Specifications, methods and tools for building on, checking and deploying CRIS systems.

Approved by the Board for implementation · 20 November 2026

Status

Developer preview. CRIS systems are in research; this hub publishes our specifications and methods first.

In one paragraph

CRIS systems are in research. Before they run, we are publishing what you would need to build to them, check them and deploy them: our specifications, our audit method and our deployment guide. They are drafts, and we want your comments. Interfaces and tools will open one by one, each when the system behind it is ready. This page shows what you can use today, what is coming and what has to happen first.

What you can use today

None of it needs an account, a key or a running CRIS system.

Start here

The hub is written for five kinds of developer. Find yours, then follow its first link.

BuildersEngineers designing continuity systems, inside or outside CRIS

Today: The Invariant as a test, the builder’s checklist, the draft proof and ledger formats

Later: Reference implementations; SDKs

Start with Concepts, then Build. →
AuditorsIndependent reviewers, the Audit Council, academic checkers

Today: The audit method (draft), the re-run procedure, a sample proof

Later: The audit kit; read access to the ledger

Read the audit method, then the sample proof, then the re-run procedure. →
Sovereign deployersTechnical teams in governments, universities and institutions

Today: The deployment guide, the readiness checklist (draft), the CTU metering method

Later: Sandbox; deployment tooling

Read the deployment guide, then the readiness checklist, then the staged rollout. →
IntegratorsTeams that want to connect their apps or data to CIX or CES

Today: What is planned, the consent rules any integration must follow, an interest list

Later: The CIX contribution API

Read what is planned and the consent rules, then join the interest list. →
ResearchersAcademics working on the Fourth Law, verification or self-improving systems

Today: Formal specifications (0.x), open questions, how to contribute

Later: Datasets and benchmarks, if published

Start with the Continuity Invariant specification, then the open questions. →

The hub at a glance

The hub is organised by what you are trying to do, not by which CRIS system you are touching. Four paths sit under this page, and a shared reference serves all of them.

Developer hub: start herewhat exists · what is planned · which pathBuildfor buildersInvariant as a testBuilder’s checklistConcepts guideCTU meteringVerifyfor auditorsAudit methodRe-run a proofSample proofReport a findingDeployfor sovereign teamsDeployment guideReadiness checklistStaged rolloutHosting optionsIntegrateplanned · integratorsCIX contribution APIConsent rulesInterest listopens on conditionsShared reference, used by every pathSpecifications (versioned) →Status of every interface →Changelog →Licensing →Security and disclosure →Support and community →Dashed: planned, not yet open. Researchers use the Build path and the specifications.
The hub at a glance: one start page, four paths by task, and a shared reference. Select a path or a reference page to open it.

What opens, and when

Every interface carries one of six states: planned, draft, preview, stable, deprecated or retired. Only preview and stable interfaces are described as working. A planned interface states the condition for opening it, not a date; a date appears only when Systems Engineering commits to one.

InterfaceWhat it will let you doStateOpening condition (proposed)Owner
SpecificationsRead and build to the published formats and rulesDraft 0.xOpen at launch, as draftsSystems Engineering
Audit kit
System: status to be confirmed
Re-run a published correspondence proof on separate systems and compare the resultPlannedThe Correspondence Prover issues its first real proofsTrust and Safety
Ledger read API
System: status to be confirmed
Read Knowledge Ledger entries, with their level and provenance: summary views for the public, full read for auditorsPlannedThe Knowledge Ledger reaches prototype statusSystems Engineering
Deployment tooling
System: status to be confirmed
Install and run the Sovereign Continuity Stack in a sandbox, then on local infrastructurePlannedThe Sovereign Continuity Stack reaches prototype statusSovereign Deployment
CIX contribution API
System: status to be confirmed
Offer people in another app a way to contribute observations to CIX, with their consent taken by CIXPlannedCIX is in pilot, and the Contributor Rights Charter and Participant Charter are adopted
Personal data: yes. Consent rule: Participant Charter and Contributor Rights Charter: CIX takes consent on its own screen, records it, and the person can withdraw it
CIX Product
SDKsUse the APIs from common programming languagesPlannedAt least two APIs are stableSystems Engineering

From data/devhub.json, set by a person only. Each state is bounded by its system’s status in data/status.json, so this table cannot show a working interface on a system that does not yet run.

Specificationsdraft 0.x · openat launchDraftAudit kitwhen the firstreal proofsexistPlannedLedger readAPIwhen the LedgerreachesprototypePlannedDeploymenttoolingwhen the StackreachesprototypePlannedCIXcontributionAPIwhen CIX is inpilot and thecharters areadoptedPlannedSDKswhen two APIsare stablePlannedexpected order of opening, left to right · order, not datesConditions are proposals for Systems Engineering to confirm (Q2). Model weights andparticipant data are never on this staircase.
Interfaces open one by one, each when its condition is met. Solid: open at launch. Dashed: planned. States come from data/devhub.json.

Each interface opens when its condition is met, not on a fixed date. Follow the changelog to hear when something moves. An interface can never move ahead of the system behind it: it cannot reach preview while its system is below prototype, or stable while its system is below pilot. See Status for what each state promises.

What is not here, and why

There is no public interface yet, because no CRIS system is running yet. And some things will never be here: model weights, participant data and anything that would identify a person are protected, as our seventh design principle says. The hub does not serve people who want to build consumer apps on CES today, or to embed CRIS models: neither is on our current plan.

If you build on CRIS systems, or to our specifications, the rules of our proposed AI Constitution are the ones to build to, including the fifteen actions no CRIS system may take. A human stays accountable for any automated decision that materially affects a person.

Get help or comment

Support and community sends each kind of need to the right place. To report a security issue, use the security page, never a public thread.

Owner: Systems Engineering, with the Website and Content Lead for this start pageNext review: 2027-05-11