Resources

Specifications

Every specification we have drafted, versioned, with where to start.

Approved by the Board for implementation · 20 November 2026

Status

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.

Continuity Invariant0.1.0 · draftCorrespondence proof format0.1.0 · draftC-Gate decision formatplannedLedger entry format0.1.0 · draftCTU metering method0.2.0 · draftAudit method0.1.0 · draftStaged rollout0.1.0 · draftSovereign Stack runtime interfaceplannedRead top to bottom. Lines show what each specification relies on; dashed boxes are planned and not yet written.
Where to start: how the specifications depend on each other, read top to bottom. Select one to open it.

The specifications

SpecificationVersionStateRelies onOwnerLicenceOn the template
Continuity Invariant
The Invariant stated precisely, with how to write it as a test.
0.1.0Draft—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.0DraftContinuity InvariantHead 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.0DraftCorrespondence proof format, C-Gate decision formatSystems 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.0DraftCorrespondence proof format, Ledger entry formatSystems 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.0DraftCorrespondence proof format, Ledger entry format, CTU metering methodTrust and Safety[to be confirmed]Not yet
Staged rollout
Readiness, sandbox, testnet nodes, limited partners, live: what each stage needs.
0.1.0DraftCorrespondence proof format, C-Gate decision format, Audit methodSovereign 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.
—PlannedContinuity Invariant[to assign, Q4]——
Sovereign Stack runtime interface
What the Sovereign Stack needs from any host.
—PlannedStaged 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

StateVersionLicenceWhat it means for a builder
Plannednone—Named so you know it is coming; nothing to build to yet
Draft0.xmay be to be confirmedBuild to it and comment; it may change without notice
Candidate1.0.0-rc.nrequiredFrozen for public review; only fixes
Stable1.x and aboverequiredChanges follow the versioning rules
Retiredlast version keptas publishedKept 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.

The index: seven blocks, and what this update did to eachStatus linenow says every specification is a draft, no licence grantedIn one paragraphkeptThe tableK7 · relies on, owner, template; planned rowsHow to commentK8 · the proposals pageRuntimeK10 · a planned rowLicenceK5 · kept; the gate to candidateWhat is never herekeptNewK1–K4, K9, K11, K12 · where to start, states, rules, figureschanged in this updatekept as it was
The index before this update: seven blocks, and where the twelve findings sat.

Who reads the library.

BuilderArrives fromBuild pathStarts withthe Invariant,then theformatsAuditorArrives fromVerify pathStarts withthe auditmethodSovereignteamArrives fromDeploy pathStarts withstaged rolloutand CTUmeteringResearcherArrives fromthe booksStarts withthe Invariantand openquestionsCounsel andBoardArrives fromLicensingStarts withlicence and theboard limitCuriousreaderArrives fromany system pageStarts withwhat aspecificationis
Who reads the library: six readers, and where each starts.

How complete each specification is today. Measured against the ten-section template.

PurposeIs/notTermsFormatRulesExampleConf.SecurityOpen q.LogContinuity Invariant✓——✓✓✓——✓✓Proof format✓——✓✓✓———✓Ledger entry format✓——✓✓✓—✓—✓CTU metering✓✓—✓✓✓✓✓✓✓Audit✓——✓—————✓Staged rollout✓——✓✓————✓Green: the part is there today. Each specification moves to the full template in its next version.
Coverage: the ten template parts across the six specifications.
SpecificationStrongest partBiggest gapNext version adds
Continuity Invariant 0.1.0A clear two-part statement; six rules; weakening goes to the boardNo test vectors; no is / is not section0.2: test vectors for the illustrative test; the C-Gate half linked
Correspondence proof format 0.1.0The parts table, three verdicts and a validation ruleNo open questions; A.1–A.6 numbering; an internal note at the top0.2: renumber; define the gain; vectors for each verdict
Ledger entry format 0.1.0Fields, three levels and five rulesNo evidence types for gate decisions or metering records0.2: evidence types; a chaining example; vectors
CTU metering method 0.2.0A full method, tables from data, conformance levelsNo definition of one CTU, by design0.3: the unit and the first conversion
Audit method 0.1.0Four steps; the auditor chooses the sampleNo rules list, no example, no report format0.2: a finding format; a sample report; rules
Staged rollout 0.1.0Five stages and exit needs; no partner named before signatureNo example; depends on a gate format that does not exist yet0.2: a stage-exit checklist; link to the gate format

One shape for every specification.

Header, from data: state, version, date, owner, licence, side of the line, relies on, comment link1 Purpose2 What it is, and is not3 Terms4 The format, rule or method5 Rules6 Illustrative example7 Conformance8 Security, privacy, protected line9 Open questions and deferred values10 ChangelogThe same names and numbering, in the same order, on every specification. Old anchors are kept as aliases.
One shape for every specification: a header from data and ten numbered sections.

Lifecycle.

PlannednoneDraft0.xCandidate1.0.0-rc.nStable1.x and aboveRetiredlast version keptowner and template;a changelog entrylicence published;vectors; 30-day reviewonly fixes; owner andFounder signa successor named,or the system withdrawna substantive problem in review reopens as the next 0.xToday: all six are drafts; two are planned. Nothing leaves draft without a published licence.
Lifecycle: five states, and what each move needs.

Versioning and the changelog.

1 . 2 . 3majorminorpatchmay breakaddsfixesOne changelog entryin dataThe specification pageThe hub changelog and feedVersion history
Versioning: three numbers, and one changelog entry printed everywhere.

Comments and proposals.

1 Commentfrom the spec’s link2 Proposalthe change and reasons3 Triageacknowledged; [10] days4 Public reviewon the proposals page5 Decisionwith reasons, publicWeakens the Invariant or a gate → the boardCredit, not pay: contributors are credited by name if they wish. Names appear only with consent.
Comments and proposals: from a comment to a public decision.

Licence and the protected line.

Publishedspecification text: an open documentationlicence (to be chosen by counsel)schemas and samples: a permissive codelicence (to be chosen)names and marks: reservedNever heremodel weightsparticipant dataanything that would identify a personformats reference data,never carry itUntil counsel publishes a licence with a date and the version it applies from, no licence is granted by these pages.
Licence and the protected line: what is published, under which licence, and what never is.

Conformance across the library.

One vector formatid · spec · level · case · input · expect · sinceContinuityInvariant3 proposedProof format4 proposedLedger entryformat3 proposedCTU metering8 publishedAudit2 proposedStagedrollout3 proposedA builder’s report of which vectors their work passes is their own statement; it becomes a CRIS statement only after an audit.
Conformance across the library: one vector format for all six.

Ownership.

Founder and Chief Architectsigns candidate → stableSystems Engineeringlibrary editorCounsellicence; severity wordingBoardchanges that weaken a gateContinuity InvariantContinuity LabsProof formatContinuity LabsLedger entry formatSystems EngineeringCTU metering methodSystems EngineeringAudit methodTrust and SafetyStaged rolloutSovereign DeploymentC-Gate decision formatto assignRuntime interfaceto assignMost owner roles here are being recruited; interim owners are to be named by the Founder (Q4).
Ownership: one editor, one owner per specification.

The road ahead.

Dec 2026Q1 2027Q2 2027H2 2027Continuity Invariant0.2Proof format0.2C-Gate decision format0.1Ledger entry format0.2CTU metering method0.3Audit method0.2Staged rollout0.2any candidateEarliest candidate: licence published, 30-day reviewDates are proposals. No specification becomes stable before the system it describes has been tested against it.
The road ahead: proposed versions by specification. Dates are proposals.

How the library is built. The section map, the data files, the rebuilt index and the build pipeline.

Specifications index/resources/specifications/ContinuityInvariantProof formatLedger entryformatCTU meteringmethodAudit methodStaged rolloutNew shared pagesProposals →How we write specifications →Conformance →Planned rows: the C-Gate decision format and the runtime interface. Versioned archives (Q7) and more vector pages follow.
Section map: the index, the six, and three new shared pages. Select one to open it.
specs.jsonspecifications,planned rows, owners,relies ondevhub-changelog.jsonevery version;breaking; proposalvectors.jsontest vectors, oneformatproposals.jsonpublic review, withconsentIndex, headers, figures, checksreliedOnBy is computed, never stored. A planned row has no version and no page.
Data: four files feed every page and figure.
Status lineIn one paragraphWhere to startThe tableWhat each state meansTake partPicturesRuntime, licence, never hereevery specification is a draft; no licencewhat a specification isthe chain, read top to bottomrelies on, owner, licence, template; planned rowsplanned to retiredcomment, propose, see decisionssixteen figureskept
The index rebuilt: where to start comes before the list.
1 Changedrafted by the owner2 Templateten sections, in order3 Dataversion; changelog4 Build checksall pass5 Sign-offowner; Foundera failed check goes back to the change
Build pipeline: five steps for every change.

Deferred values

Values left to Continuity Labs, the board or counsel, each with its owner.

SpecificationDeferred valueOwner
Continuity InvariantTolerances and confidence thresholdsBoard
Continuity InvariantHow continuity of purpose is encoded and measured (the C-Gate decision format)[owner to assign, Q4]
Correspondence proof formatTolerances for a staged verdictBoard
Correspondence proof formatHow correspondence gain is stated (needed by CTU metering)Head of Continuity Labs
Ledger entry formatThresholds for each level of knowledgeContinuity Labs
CTU metering methodThe definition of one CTUContinuity Labs
CTU metering methodThe benefit indicator (B2)Founder
Audit methodSeverity levels, fix deadlines and disclosure wordingCounsel and the board
Staged rolloutThe external audit standard before liveBoard

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.

Owner: Systems EngineeringNext review: 2027-05-11