Resources

Status

Whether each interface works, and what it promises.

Approved by the Board for implementation · 20 November 2026

Status

Updated 11 November 2026 by Systems Engineering (draft, awaiting the Founder’s sign-off).

Every interface

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.

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.

Planneda condition,not a dateDraft 0.xmay changewithout noticePreviewworks; changeswith noticeStable 1.xno breaking changewithin 1.xDeprecatedstill works; asuccessor namedRetiredswitched off;kept in the recordVersion numbers: major.minor.patchmajora breaking change (a field removed, or its meaning changed)minorsomething added that old readers can ignorepatchwording, or a correction that changes no behaviourNotice: [30] days for a breaking change to a preview interface; [12] months before a stable one retires (proposals, Q8).
Interface lifecycle: six states, each a different promise to developers, and the versioning rule.
StateWhat it promisesDescribed as working?Shown as
PlannedNothing yet; states its opening conditionNoGrey, with the condition
Draft (0.x)Content to read and comment on; may change without noticeNo: we write “will” or “is proposed to”Amber
PreviewIt works, for accredited users; changes are announced in advanceYesBlue, marked preview
Stable (1.x and above)No breaking change within the major versionYesGreen
DeprecatedStill works; a successor and a retirement date are namedYes, with the noticeAmber, with the date
RetiredSwitched off; its documentation stays in the recordNoGrey, 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

ChangeNotice
Breaking change to a preview interface[30] days (proposal)
Deprecation of a stable interface[12] months before retirement (proposal)
Security fixAs 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.

Owner: Systems EngineeringNext review: 2027-05-11