Resources
Staged rollout
Readiness, sandbox, testnet nodes, limited partners, live: what each stage needs.
DraftVersion 0.1.0Drafted 11 November 2026Owner: Sovereign Deployment (role being recruited; interim owner to be named, Q4)Licence: [to be confirmed]Side of the line: published
A draft (0.x): read it, build to it and comment on it; it may change without notice. Drawn from the Sovereign Continuity Stack page. Changelog · Comment on this specification
Relies on: Correspondence proof format, C-Gate decision format (planned), Audit method · Relied on by: Sovereign Stack runtime interface (planned)
1 Purpose
Every CRIS release, and every sovereign deployment, moves forward one stage at a time. This specification sets out the stages and what each gate between them needs.
2 The stages
| Stage | What happens | Exit needs |
|---|---|---|
| 1 Readiness | The readiness checklist is completed and agreements are signed | A local accountable person named |
| 2 Sandbox | The loop runs in isolation, with no real people or data | The sandbox’s correspondence proofs, a C-Gate decision and a tested rollback |
| 3 Testnet nodes | The loop runs on testnet infrastructure under a written agreement, still without live personal data | As above, plus the local partner’s approval |
| 4 Limited partners | A small number of named institutions use it, monitored, under their own agreements | As above |
| 5 Live | General use, under local control | An independent audit first |
3 Rules
- Each move forward needs the previous stage’s correspondence proofs, a C-Gate decision, a tested rollback and the local partner’s approval.
- A failure sends the deployment back one stage.
- No partner receives a stack that has not passed an external audit.
- No stage names a country, ministry or partner in public until an agreement is signed and publication is approved.
See the Deploy path for the documents each stage uses and the hosting options.
4 Changelog
- 0.1.0 · 11 November 2026 · minor · First draft, from the Sovereign Continuity Stack page.
Printed from the developer hub changelog, the one record of every version.
