Specifications
Every specification we have drafted, versioned, with where to start.
Every specification here is a draft (version below 1.0). Build to them and comment on them, knowing they may change. No licence is granted yet.
In one paragraph
A specification is a versioned description of a format, rule or method. These six are the first, published as drafts with the developer hub because our system pages already describe most of their content. Each has a version, a date, an owner, a state and a changelog entry. Versions below 1.0 are drafts: read them, build to them and comment on them, knowing they may change.
Where to start
Read the Continuity Invariant first: it is the rule every other specification serves. Then the correspondence proof format and the C-Gate decision format (planned), which test its two halves. Then the ledger entry, which records every result, and CTU metering, which records the cost of each cycle. Then the audit method and staged rollout, which check and release the work.
The specifications
| Specification | Version | State | Relies on | Owner | Licence | On the template |
|---|---|---|---|---|---|---|
| Continuity Invariant The Invariant stated precisely, with how to write it as a test. | 0.1.0 | Draft | — | Head of Continuity Labs (role being recruited; interim owner to be named, Q4) | [to be confirmed] | Not yet |
| Correspondence proof format The parts of a proof, the three verdicts, staged conditions and the signature. | 0.1.0 | Draft | Continuity Invariant | Head of Continuity Labs (role being recruited; interim owner to be named, Q4) | [to be confirmed] | Not yet |
| Ledger entry format Entry fields, the three levels, append-only rules and chaining to the previous entry. | 0.1.0 | Draft | Correspondence proof format, C-Gate decision format | Systems Engineering (role being recruited; interim owner to be named, Q4) | [to be confirmed] | Not yet |
| CTU metering method What is metered, at which boundary, in what record, how it is checked and how it is reported. | 0.2.0 | Draft | Correspondence proof format, Ledger entry format | Systems Engineering (role being recruited; interim owner to be named, Q4) | [to be confirmed] | Not yet |
| Audit method Sample, re-run, check claims, report. Severity levels join after counsel approves them. | 0.1.0 | Draft | Correspondence proof format, Ledger entry format, CTU metering method | Trust and Safety | [to be confirmed] | Not yet |
| Staged rollout Readiness, sandbox, testnet nodes, limited partners, live: what each stage needs. | 0.1.0 | Draft | Correspondence proof format, C-Gate decision format, Audit method | Sovereign Deployment (role being recruited; interim owner to be named, Q4) | [to be confirmed] | Not yet |
| C-Gate decision format The purpose half of the Invariant needs a recorded decision. | — | Planned | Continuity Invariant | [to assign, Q4] | — | — |
| Sovereign Stack runtime interface What the Sovereign Stack needs from any host. | — | Planned | Staged rollout | [to assign, Q4] | — | — |
The C-Gate decision format and the Sovereign Stack runtime interface are planned: named so you know they are coming, with nothing yet to build to. Every owner role listed is being recruited; the Founder will name an interim owner who answers comments for each (Q4).
What each state means
| State | Version | Licence | What it means for a builder |
|---|---|---|---|
| Planned | none | — | Named so you know it is coming; nothing to build to yet |
| Draft | 0.x | may be to be confirmed | Build to it and comment; it may change without notice |
| Candidate | 1.0.0-rc.n | required | Frozen for public review; only fixes |
| Stable | 1.x and above | required | Changes follow the versioning rules |
| Retired | last version kept | as published | Kept for reference; its successor is named |
Take part
Every specification has a comment link. A comment that asks for a change becomes a proposal, reviewed in public on the proposals page and decided with reasons. See how we write specifications and conformance. Contributors are credited, not paid; paid contribution happens on CIX, under its own rules.
The library in pictures
Sixteen pictures set out how the library works: what changed, who reads it, where to start, how complete each specification is, the shape every one follows, how they move from draft to stable, how changes are proposed, what is published and what never is, how conformance is tested, who owns what, and what comes next.
What changed on this page.
Who reads the library.
How complete each specification is today. Measured against the ten-section template.
| Specification | Strongest part | Biggest gap | Next version adds |
|---|---|---|---|
| Continuity Invariant 0.1.0 | A clear two-part statement; six rules; weakening goes to the board | No test vectors; no is / is not section | 0.2: test vectors for the illustrative test; the C-Gate half linked |
| Correspondence proof format 0.1.0 | The parts table, three verdicts and a validation rule | No open questions; A.1–A.6 numbering; an internal note at the top | 0.2: renumber; define the gain; vectors for each verdict |
| Ledger entry format 0.1.0 | Fields, three levels and five rules | No evidence types for gate decisions or metering records | 0.2: evidence types; a chaining example; vectors |
| CTU metering method 0.2.0 | A full method, tables from data, conformance levels | No definition of one CTU, by design | 0.3: the unit and the first conversion |
| Audit method 0.1.0 | Four steps; the auditor chooses the sample | No rules list, no example, no report format | 0.2: a finding format; a sample report; rules |
| Staged rollout 0.1.0 | Five stages and exit needs; no partner named before signature | No example; depends on a gate format that does not exist yet | 0.2: a stage-exit checklist; link to the gate format |
One shape for every specification.
Lifecycle.
Versioning and the changelog.
Comments and proposals.
Licence and the protected line.
Conformance across the library.
Ownership.
The road ahead.
How the library is built. The section map, the data files, the rebuilt index and the build pipeline.
Deferred values
Values left to Continuity Labs, the board or counsel, each with its owner.
| Specification | Deferred value | Owner |
|---|---|---|
| Continuity Invariant | Tolerances and confidence thresholds | Board |
| Continuity Invariant | How continuity of purpose is encoded and measured (the C-Gate decision format) | [owner to assign, Q4] |
| Correspondence proof format | Tolerances for a staged verdict | Board |
| Correspondence proof format | How correspondence gain is stated (needed by CTU metering) | Head of Continuity Labs |
| Ledger entry format | Thresholds for each level of knowledge | Continuity Labs |
| CTU metering method | The definition of one CTU | Continuity Labs |
| CTU metering method | The benefit indicator (B2) | Founder |
| Audit method | Severity levels, fix deadlines and disclosure wording | Counsel and the board |
| Staged rollout | The external audit standard before live | Board |
Runtime
The Sovereign Stack runtime interface, what the Stack needs from any host, is planned. Any host that meets it can run the Stack, each under a written agreement. It is described on the Deploy path.
Licence
The licence for specifications is not yet chosen; counsel chooses it. Until it is published on Licensing, no licence is granted by these pages. No specification moves above draft without one. Names and marks are reserved and not licensed by any of the above.
What is never here
Model weights, participant data and anything that would identify a person are protected, as our seventh design principle says. A specification describes a format or a method; it never carries the data.
