Build to the Invariant
Build a system that keeps the Continuity Invariant.
Specifications are drafts (0.x) and may change. Comment on them.
For builders and researchers.
In one paragraph
Every CRIS system keeps one rule: it may change anything about itself except its correspondence with reality and its continuity of purpose. You can build your own systems to the same rule today, using our draft specifications. Six steps take you from the idea to a system you can check, and none of them needs an account or a CRIS system.
Six steps
- Learn the loop. Read Concepts: six stages, two gates and five records.
- Write the Invariant as a test, before you build any feature. The Continuity Invariant specification shows how. This is our first design principle: the test comes first.
- Run the checklist below. If any answer is no, stop and fix it before going further.
- Read the formats for the correspondence proof and the ledger entry. Your system should be able to produce a proof for every change and a ledger entry for every action.
- Validate an example. Check our illustrative proof against the parts and rules of the proof format, then try the same with a proof from your own system.
- Tell us what is unclear or wrong, on the specification’s page. Every comment is read, and accepted changes are credited in the changelog.
| Step | Material | State at launch |
|---|---|---|
| 1 Learn the loop | Concepts guide | Draft |
| 2 Write the Invariant | Continuity Invariant specification | Draft 0.1 |
| 3 Run the checklist | Builder’s checklist | Published |
| 4 Read the formats | Proof and ledger entry specifications | Draft 0.1 |
| 5 Validate an example | Illustrative proof | Draft, illustrative |
| 6 Tell us | Support and the contribution flow | Opens with the hub |
The seven tests
The seven design principles every CRIS system is built to are also the first seven tests a builder should run. They are printed from the same source as the Systems page, so the wording never drifts.
- 1Invariant firstIs the Continuity Invariant written as a test before any feature is built?See: Research: the Continuity Invariant →
- 2Evidence by defaultDoes every action leave a ledger entry an auditor can read?See: Knowledge Ledger →
- 3Human observation is a required inputIs human observation a required input, not an optional feedback widget?See: CIX →
- 4Reversible by constructionDoes every promotion record its lineage and a tested rollback path?See: C-Gate →
- 5Measured costAre compute and energy reported in metered CTU?See: Sovereign Continuity Stack →
- 6Sovereign-readyCan the system run without depending on a single foreign cloud?See: Sovereign Continuity Stack; Sovereign AI →
- 7Open specificationsAre the interfaces, the Invariant and the audit method published, with weights and participant data protected?See: Specifications →
If the answer to any of them is no, the system is not ready. The fuller checklist of ten conditions before any system improves itself joins this path when workflow W8 publishes it.
Measure what it costs
Test 5 asks whether compute and energy are reported in Compute Thermodynamic Units. The CTU metering method is a draft 0.1 that shows what to record for each cycle, so that gains in capability can be weighed against their cost.
Later on this path
Reference implementations and software development kits will join this path when they exist. Kits are planned for when at least two interfaces are stable; see Status. Specifications are drafts (0.x) and may change; every change is listed in the changelog.
