Sovereign AI
Intelligence infrastructure that a country, a community or a person can own and control.
In one paragraph
Sovereign Continuity Stack: Status to be confirmed No sovereign deployment has taken place.
Sovereign AI means the whole CRIS loop runs inside a country or institution, on infrastructure it controls, with its own data. CRIS supplies the software, updates, a licence on fair terms, training through partners and tools to audit it; it never operates the system for the people who use it. It is designed, not deployed: no sovereign deployment has taken place yet.
How it would work technically is set out on the Sovereign Continuity Stack page; how it fits the whole CRIS ecosystem, on Africa and sovereign deployment. This page explains why it matters and how its effect will be measured.
Four layers
Sovereignty means control stays local at every layer. CRIS supplies the software and the tools to check it; the people who use it decide.
| Layer | Who controls it | What CRIS does |
|---|---|---|
| Use: ministries, universities, schools, small enterprises | The local institution | Supports and trains; never operates them |
| The Sovereign Continuity Stack, running the loop | Run locally, under licence | Supplies and updates the software; meters energy and cost in metered CTU |
| Hosting | Chosen locally: national or partner hardware, or a hosting provider, under a written agreement | Works with any of them; none is required |
| Data and models | Local jurisdiction | None leave without the owner’s consent and local law |
The same table as Africa and sovereign deployment, with hosts left generic.
How it would reach a country
Every deployment would follow the same five steps, and every new country the same four stages. Assessment protects local law. Staging protects people from a version that has not passed its checks. Handover means local operators, not CRIS, hold the keys. Success would be a deployment passing an independent audit, and the measures below.
Aims on the Stack page, all proposals: testnet cycles open to partners, 2027 (proposed); first sovereign deployment passing an independent audit, 2029 (proposed).
Data, jurisdiction and community knowledge
Data and models stay in the local jurisdiction, and none leave without the owner's consent and local law. Local operators hold the keys and can pause or roll back the system. Knowledge held by a community is stored and processed under the community's chosen jurisdiction where practicable. Exactly what may cross a border is set in each agreement, in wording our counsel approves; until then, see the Stack page's data residency section.
| Principle | Source |
|---|---|
| Data and models stay in the local jurisdiction; none leave without the owner’s consent and local law | Ecosystem: sovereign deployment |
| CRIS supplies software and updates; it does not operate the system for the people who use it | Ecosystem |
| Local operators hold operational keys and can pause and roll back | Stack: local control |
| Community knowledge from Africa and the Global South is stored and processed under the community’s chosen jurisdiction where practicable, through sovereign deployment | Proposed Contributor Rights Charter 13.4 |
| Each partner agreement sets the details under local law | Stack: data residency |
Still with counsel: exactly what may cross a border, and on what terms; how updates are delivered without moving local data out; and the licence terms, including concessional terms.
How a country or institution would take part
If you represent a government, a university or an institution, you can request a briefing on the Sovereign Continuity Stack and on what a readiness assessment covers. We name no country, ministry, university or partner until a written agreement exists and they have approved publication.
| Step | What happens | Who decides |
|---|---|---|
| 1 Talk to us | A briefing on the Stack and on what a readiness assessment covers | — |
| 2 Readiness | Data residency, law, infrastructure and people | Assessment shared with the partner |
| 3 Agreement | A written agreement covering licence, hosting, data, audit and publication | Both parties; for CRIS, the decision rule under related organisations |
| 4 Staged deployment | Sandbox, testnet, limited use, partner operation; each move gated | A C-Gate decision at each stage |
| 5 Handover | Local operators hold keys; staff trained | The partner |
| 6 Independent audit | Before and after handover | The Audit Council (once appointed) or an external auditor |
Related organisations
Three organisations our Founder also leads could play a part in a sovereign deployment, each as one option among several.
| Organisation | Role it could play | What we say |
|---|---|---|
| LOGOS-C | Hosting option | LOGOS-C, sovereign AI-native compute infrastructure, is an organisation also led by our Founder. It could host the Sovereign Continuity Stack, as one hosting option, under a separate written agreement on arm’s-length terms. None is recorded yet. |
| Botswana Global Testnet Initiative | Testnet nodes | The Botswana Global Testnet Initiative, a testnet for sovereign AI and continuity infrastructure, is an organisation also led by our Founder. It could provide testnet nodes for staged rollouts, under a separate written agreement on arm’s-length terms. None is recorded yet. See botswanaglobaltestnet.africa. |
| The Academy of Philosophy-Engineering | Training | The Academy of Philosophy-Engineering, which teaches the Fourth Law of Logic and the engineering methods CRIS builds on, is an organisation also led by our Founder. It could train local staff, under a separate written agreement on arm’s-length terms. None is recorded yet. See philosophyengineering.academy. |
None of them is required: any capable host, testnet or trainer could take part on the same terms. Deploying in a new country is the Chief Executive’s decision under the Stack’s rules, and our Founder is Chief Executive and also leads these three organisations. So when a deployment would use one of them, we propose that the choice is approved by people without that interest: the Board’s disinterested members once they exist, or meanwhile an independent reviewer the Board names, and the decision record says so.
Commitments and measures
| Commitment | What carries it | Indicator | Today |
|---|---|---|---|
| Affordable or concessional licences | The licence for the Stack and the programmes | B4 (concessional licences and sovereign deployments) | No licence issued |
| Sovereign deployment | The Sovereign Continuity Stack; local hosting | B4; B2 (useful compute per unit of energy, in metered CTU) | None deployed |
| Local capability | Training through partners (such as the Academy, under agreement); local hiring | B1 (people reached), with Africa and the Global South shown separately | Not yet reported |
| A share of surplus to the region | The Continuity Value Allocation Policy | Value allocation in the statement | None set |
| A yearly report | The public-benefit statement, with the Africa Continuity Council’s opinion | — | First due by 22 December 2027 |
These commitments are in our proposed bylaws (Section 3A.11). They are not yet adopted.
Status and next steps
Sovereign Continuity Stack: Status to be confirmed No sovereign deployment has taken place.
Read how it works on the Sovereign Continuity Stack page, how it fits our ecosystem in Africa and sovereign deployment, and how we will report on it in our benefit report. Request a briefing.
About this page
- The subject is CRIS’s work. The page explains sovereign AI as CRIS designs and commits to it; related organisations appear only as options.
- Related-party line every time BGTI, LOGOS-C, SCVX or the Academy is named, with the agreement’s status from data.
- Could, not does. No host, testbed or partner is described as used, chosen or required until a written agreement is recorded.
- No country, ministry, university or partner named as a deployment or pilot until a written agreement exists and publication is approved.
- Status from data. Designed, not deployed until it changes.
- Proposed until adopted. The bylaws’ Africa and Global South commitments are proposed.
- Data residency in counsel’s words. Each agreement sets the details under local law.
- No results without evidence. Any testnet or deployment result is shown only with a link to its evidence and who checked it.
- No earnings or investment language about compute, CTU or hosting.
- One owner. This page and the Stack page share one owning role.
What the page will never say
| Limit | Say on the page |
|---|---|
| No deployment | Designed, not deployed, from data |
| No agreements | None is recorded yet, beside every related organisation |
| Commitments proposed | The bylaws’ Africa and Global South commitments are proposed |
| Data residency | Principles only; details in counsel-approved wording and each agreement. Updates, audits and agreed reports may cross borders, so the page never makes an absolute promise about data |
| Dates | The Stack page’s 2027 and 2029 aims are proposals |
| CTU | Measures energy and cost; not a token, a currency or an investment |
Readers
| Reader | One-line answer | Linked out to |
|---|---|---|
| Ministry or regulator | You run it, on infrastructure you choose, with your data under your law; CRIS supplies software, updates and audit tools. | Stack; ecosystem |
| University or lab | Any capable hardware can host it, under a written agreement; none is required. | How a deployment works |
| Community representative | Community knowledge needs your community’s own consent and a written benefit-sharing agreement, stored under your chosen jurisdiction where practicable. | Charter Art. 13 |
| Journalist or analyst | The related organisations are led by our Founder; any work with CRIS is under a separate written agreement on arm’s-length terms. None is recorded yet. | Related organisations |
| Funder or development bank | Designed, not deployed. Status from data; commitments proposed in the bylaws. | Benefit report; Africa commitment |
| Old-site visitor | The testnet initiative has its own site. This page is about CRIS’s sovereign AI work. | Related organisations |
The road
| Date (proposed) | Step | Today |
|---|---|---|
| 12 Nov 2026 | This review | Done |
| 20 Nov 2026 | Quick fixes: short description; related-party line; could, under a written agreement; status line; opening | Done on this preview |
| 4 Dec 2026 | Q1 (where the testnet’s story lives), Q2 (Stack wording), Q3 (owner), Q4 (decision rule) decided | Open; recommendations applied on this preview for Q1 and Q2 |
| 18 Dec 2026 | Page rebuilt; Stack page opening and staging label fixed; redirect updated | Done on this preview |
| 15 Jan 2027 | Counsel reviews residency principles and related-party lines | Open |
| 1 Mar 2027 | Page review date | — |
| Phase P4 | Earlier-site testnet material placed per Q1, rewritten, checked, with nothing unverifiable | Open |
How the page is built
| Order | Anchor | Section |
|---|---|---|
| 1 | #in-one-paragraph | Three opening sentences; status line |
| 2 | #layers | Four layers, who controls each |
| 3 | #how-it-reaches | Five steps, four stages |
| 4 | #data | Data, jurisdiction, community knowledge |
| 5 | #take-part | The partner path |
| 6 | #related | Related organisations as options |
| 7 | #commitments | Five commitments and measures |
| 8 | #status | Status from data; read more |
| Check | Fails when |
|---|---|
sv-related | BGTI, LOGOS-C, SCVX or the Academy is named without the related-party line |
sv-could | “is built on”, “runs on”, “hosted on”, “our testbed” or “tests first on” [a related organisation] appears while its agreement is none recorded |
sv-named | A country, ministry, university or partner is named as a deployment, pilot or partner without an entry in sovereign.json |
sv-status | “deployed”, “running” or “live” appears while the Stack’s status is unset or research |
sv-never | “never leaves the country” (or a similar absolute) appears |
sv-aims | A 2027 or 2029 aim appears without “proposed” |
sv-short | The page’s short description names a related organisation |
sv-ctu | CTU is described as a token, currency, asset or investment |
All eight run in every build, on this page, the Stack page and the two ecosystem pages.
What changed
| # | Finding | Fixed by |
|---|---|---|
| K1 | The topic was one related organisation | Short description and opening about CRIS’s work |
| K2 | No related-party line | A line for each, from data |
| K3 | Stronger than the data (“a testbed … built on LOGOS-C”) | “Could, under a written agreement; none recorded” |
| K4 | Two owners for one topic | Open (Q3) |
| K5 | Said little about sovereign AI | Eight blocks |
| K6 | No status | Status line from data |
| K7 | The P4 plan promised partners and results | Plan note rewritten |
| K8 | The old testnet route landed here | Redirect moved to the related-organisations entry (Q1, Option A) |
| K9 | Stack page said it tests first on the testnet’s nodes | Stack opening, steps and staging label reworded (Q2) |
| K10 | Commitments only linked | Five commitments with measures |
| K11 | No measures | B1, B2 and B4 |
| K12 | Opened with a cross-link | Cross-link moved below the opening |
