Status
Whether each interface works, and what it promises.
Updated 11 November 2026 by Systems Engineering (draft, awaiting the Founder’s sign-off).
Every interface
| 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.
Six states
A developer must always know three things about anything in the hub: whether it works, whether it will change, and what changed last. One lifecycle, one version scheme and one changelog answer them.
| State | What it promises | Described as working? | Shown as |
|---|---|---|---|
| Planned | Nothing yet; states its opening condition | No | Grey, with the condition |
| Draft (0.x) | Content to read and comment on; may change without notice | No: we write “will” or “is proposed to” | Amber |
| Preview | It works, for accredited users; changes are announced in advance | Yes | Blue, marked preview |
| Stable (1.x and above) | No breaking change within the major version | Yes | Green |
| Deprecated | Still works; a successor and a retirement date are named | Yes, with the notice | Amber, with the date |
| Retired | Switched off; its documentation stays in the record | No | Grey, archived |
Bounded by the system
An interface’s state is separate from its system’s status (research, prototype, pilot or live), but bounded by it. An interface cannot be preview while its system is below prototype, or stable while its system is below pilot. The build checks this against our status file, so the hub can never claim a working interface on a system that does not yet run. Today every system’s status is to be confirmed, so no interface can be above draft.
Notice periods
| Change | Notice |
|---|---|
| Breaking change to a preview interface | [30] days (proposal) |
| Deprecation of a stable interface | [12] months before retirement (proposal) |
| Security fix | As fast as needed, with a note afterwards |
The numbers in square brackets are proposals for Systems Engineering. Once set, they are published here and the build enforces them against the changelog dates.
When an interface opens
When an interface reaches preview, its page will follow one template: what it does, who may use it, authentication, the consent rule for any personal data, rate limits, the records it reads or writes, errors, a real example, the changelog and the support route. No part of that template is published early.
