Developer hub
Specifications, methods and tools for building on, checking and deploying CRIS systems.
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
- Draft specifications for the Continuity Invariant, the correspondence proof, the ledger entry, CTU metering, the audit method and staged rollout.
- The builder’s checklist: seven tests every continuity system should pass before it ships.
- The audit method and how to re-run a proof, with an illustrative example.
- The deployment guide and readiness checklist for running the loop on your own infrastructure.
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.
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. →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. →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. →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. →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.
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.
| Interface | What it will let you do | State | Opening condition (proposed) | Owner |
|---|---|---|---|---|
| Specifications | Read and build to the published formats and rules | Draft 0.x | Open at launch, as drafts | Systems Engineering |
| Audit kit System: status to be confirmed | Re-run a published correspondence proof on separate systems and compare the result | Planned | The Correspondence Prover issues its first real proofs | Trust 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 auditors | Planned | The Knowledge Ledger reaches prototype status | Systems Engineering |
| Deployment tooling System: status to be confirmed | Install and run the Sovereign Continuity Stack in a sandbox, then on local infrastructure | Planned | The Sovereign Continuity Stack reaches prototype status | Sovereign 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 CIX | Planned | CIX is in pilot, and the Contributor Rights Charter and Participant Charter are adopted | CIX Product |
| SDKs | Use the APIs from common programming languages | Planned | At least two APIs are stable | Systems 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.
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.
