Impact

Sovereign AI

Intelligence infrastructure that a country, a community or a person can own and control.

Approved by the Board for implementation · 20 November 2026

Awaiting counsel. Data residency, licence terms and the related-party lines are drafts for counsel to approve.

In one paragraph

Status

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.

LayerWho controls itWhat CRIS doesUseministries, universities, schools, small enterprisesThe local institutionSupports and trains; neveroperatesThe Sovereign Continuity Stackthe whole loop, observation to the C-GateRun locally, underlicenceSoftware, updates; meterscost in CTUHostingnational or partner hardware; hosts are optionsChosen locallyWorks with any host; noneis requiredData and modelsstay in the local jurisdictionThe owner, under locallawNone leave without consentand local lawFrom the ecosystem page’s sovereign deployment table. Designed; no deployment has taken place.
Sovereign AI in four layers: control stays local.
LayerWho controls itWhat CRIS does
Use: ministries, universities, schools, small enterprisesThe local institutionSupports and trains; never operates them
The Sovereign Continuity Stack, running the loopRun locally, under licenceSupplies and updates the software; meters energy and cost in metered CTU
HostingChosen locally: national or partner hardware, or a hosting provider, under a written agreementWorks with any of them; none is required
Data and modelsLocal jurisdictionNone 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.

1 Assessresidency, law,readiness2 Deployon chosen localhosting3 First cycleson testnet nodes4 Hand overaudit tools,trained operators5 ReportCTU cost withcapabilityThe staging every new country follows (steps 2 and 3)SandboxCRIS lab; synthetic dataTestnet nodesany capable testnet, undera written agreementLimited partner uselocal observation sources;named usersPartner operationlocal operators; rollbacktestedEach move needs the previous stage’s proofs, a C-Gate decision and a tested rollback; a failure goes back one stage.Designed, not deployed. From the Stack page.
Five steps, four stages: how the Stack would reach a country.

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.

From CRISsoftware, updatesThe partner’s jurisdictionLocal dataModels trained on itLedger recordsOperators and keysCommunity knowledgecommunity’s consent; Tier 4; its chosen jurisdictionNone leaves without the owner’sconsent and local lawMay go outonly as theagreement allowsWhat may cross a border is stated only in counsel-approved wording; each agreement sets it under local law.
What stays inside, what comes in, what may go out.
PrincipleSource
Data and models stay in the local jurisdiction; none leave without the owner’s consent and local lawEcosystem: sovereign deployment
CRIS supplies software and updates; it does not operate the system for the people who use itEcosystem
Local operators hold operational keys and can pause and roll backStack: local control
Community knowledge from Africa and the Global South is stored and processed under the community’s chosen jurisdiction where practicable, through sovereign deploymentProposed Contributor Rights Charter 13.4
Each partner agreement sets the details under local lawStack: 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.

1 Talk to usbriefing,interest2 Readinesslaw, data,infrastructure3 Agreementwritten, thenpublication ok4 Stagedfour stages,each gated5 Handoverlocal keys,trained staff6 Auditindependent;aim 2029(proposed)named after thisWhat a partner can do before an agreement (proposed)Request a briefingon the Stack and the readinessassessmentTrain stafffor example through the Academy(related party, under a writtenagreement)Prepare data and lawresidency rules, local observationsourcesThe 2029 aim and every date here are proposals from the Stack page, not commitments.
How a country or institution would take part.
StepWhat happensWho decides
1 Talk to usA briefing on the Stack and on what a readiness assessment covers—
2 ReadinessData residency, law, infrastructure and peopleAssessment shared with the partner
3 AgreementA written agreement covering licence, hosting, data, audit and publicationBoth parties; for CRIS, the decision rule under related organisations
4 Staged deploymentSandbox, testnet, limited use, partner operation; each move gatedA C-Gate decision at each stage
5 HandoverLocal operators hold keys; staff trainedThe partner
6 Independent auditBefore and after handoverThe Audit Council (once appointed) or an external auditor

Three organisations our Founder also leads could play a part in a sovereign deployment, each as one option among several.

RoleOptions (any, under a written agreement)HostingNational hardwarePartner’s own data centreLOGOS-C *Testnet cyclesAny capable testnetBGTI nodes *TrainingLocal universitiesResearch partnersThe Academy ** An organisation also led by our Founder. Any work with CRIS is under a separate written agreementon arm’s-length terms. None is recorded yet. Choosing one needs approval by people without that interest.Options from the ecosystem and Stack pages; none is required. The approval rule is a proposal (Q4).
Related organisations: one option among several, always marked.
OrganisationRole it could playWhat we say
LOGOS-CHosting optionLOGOS-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 InitiativeTestnet nodesThe 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-EngineeringTrainingThe 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 (Bylaws 3A.11, proposed)Measured byTodayAffordable or concessional licencesB4 concessional licencesNo licence issuedSovereign deploymentB4 deployments; B2 usefulcompute per CTUNone deployedLocal capabilityB1 people reached, by regionNot yet reportedA share of surplus to the regionValue allocation (3A.6)None setA yearly reportPublic-benefit statementFirst due by 22 Dec 2027Status line: Sovereign Continuity Stack, status from data. Designed, not deployed.Commitments from the proposed bylaws and indicators from benefit.json; the Today column is generated from data.
Five commitments, their measures, and where each stands.
CommitmentWhat carries itIndicatorToday
Affordable or concessional licencesThe licence for the Stack and the programmesB4 (concessional licences and sovereign deployments)No licence issued
Sovereign deploymentThe Sovereign Continuity Stack; local hostingB4; B2 (useful compute per unit of energy, in metered CTU)None deployed
Local capabilityTraining through partners (such as the Academy, under agreement); local hiringB1 (people reached), with Africa and the Global South shown separatelyNot yet reported
A share of surplus to the regionThe Continuity Value Allocation PolicyValue allocation in the statementNone set
A yearly reportThe 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

Status

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

  1. The subject is CRIS’s work. The page explains sovereign AI as CRIS designs and commits to it; related organisations appear only as options.
  2. Related-party line every time BGTI, LOGOS-C, SCVX or the Academy is named, with the agreement’s status from data.
  3. Could, not does. No host, testbed or partner is described as used, chosen or required until a written agreement is recorded.
  4. No country, ministry, university or partner named as a deployment or pilot until a written agreement exists and publication is approved.
  5. Status from data. Designed, not deployed until it changes.
  6. Proposed until adopted. The bylaws’ Africa and Global South commitments are proposed.
  7. Data residency in counsel’s words. Each agreement sets the details under local law.
  8. No results without evidence. Any testnet or deployment result is shown only with a link to its evidence and who checked it.
  9. No earnings or investment language about compute, CTU or hosting.
  10. One owner. This page and the Stack page share one owning role.

What the page will never say

May sayMust not sayThe testnet initiative could provide nodes, undera written agreementOur testbed is BGTI, built on LOGOS-CDesigned; no deployment yetRunning in BotswanaAny capable host; none requiredHosted on LOGOS-CData stays under local lawYour data never leaves the countryNo country is named before an agreementPartnering with [ministry]We propose to offer concessional termsAffordable AI for Africa, todayEach right-hand line fails a build check.
Six pairs: what the page may say, and what it must not.
LimitSay on the page
No deploymentDesigned, not deployed, from data
No agreementsNone is recorded yet, beside every related organisation
Commitments proposedThe bylaws’ Africa and Global South commitments are proposed
Data residencyPrinciples 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
DatesThe Stack page’s 2027 and 2029 aims are proposals
CTUMeasures energy and cost; not a token, a currency or an investment

Readers

Ministry or regulatorweighs a deploymentWho controls the system,the data and the updates?University, research labwants to host or studyCan we run it on our ownhardware, and audit it?Community representativeguards local knowledgeDoes our knowledge stayours, under our law?Journalist, analystchecks independenceHow is the Founder’s otherwork kept separate?Funder, development bankconsiders supportWhat exists today, andwhat is only proposed?Old-site visitorfrom the old testnet routeWhere did the Botswanatestnet page go?The first three decide the design; the fourth decides the wording.
Six readers, six first questions.
ReaderOne-line answerLinked out to
Ministry or regulatorYou run it, on infrastructure you choose, with your data under your law; CRIS supplies software, updates and audit tools.Stack; ecosystem
University or labAny capable hardware can host it, under a written agreement; none is required.How a deployment works
Community representativeCommunity 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 analystThe 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 bankDesigned, not deployed. Status from data; commitments proposed in the bylaws.Benefit report; Africa commitment
Old-site visitorThe testnet initiative has its own site. This page is about CRIS’s sovereign AI work.Related organisations

The road

12 NovReview20 NovShort line,related-party,could, status4 DecQ1 to Q4 decided18 DecPage rebuilt;Stack wordingfixed15 JanCounsel:residency, relatedparties1 MarPage reviewPhase P4Earlier testnetmaterial placedAll dates are proposals; not to scale. The 20 Nov step matters most: it removes an unsupported claim about related parties.
Correct it first, then rebuild it (proposed dates).
Date (proposed)StepToday
12 Nov 2026This reviewDone
20 Nov 2026Quick fixes: short description; related-party line; could, under a written agreement; status line; openingDone on this preview
4 Dec 2026Q1 (where the testnet’s story lives), Q2 (Stack wording), Q3 (owner), Q4 (decision rule) decidedOpen; recommendations applied on this preview for Q1 and Q2
18 Dec 2026Page rebuilt; Stack page opening and staging label fixed; redirect updatedDone on this preview
15 Jan 2027Counsel reviews residency principles and related-party linesOpen
1 Mar 2027Page review date—
Phase P4Earlier-site testnet material placed per Q1, rewritten, checked, with nothing unverifiableOpen

How the page is built

/research/botswana-global-testnet/impact/sovereign-ai/#in-one-paragraph#layers#how-it-reaches#data#take-part#related#commitments#statusSovereign Stack pageAfrica and sovereignRelated organisationsBenefit reportredirect now goes to the testnet’s entry on the related-organisations page (Q1, Option A)Eleven links landed on the page top; the anchors are all new.
Eight anchors, four neighbours, one redirect moved.
OrderAnchorSection
1#in-one-paragraphThree opening sentences; status line
2#layersFour layers, who controls each
3#how-it-reachesFive steps, four stages
4#dataData, jurisdiction, community knowledge
5#take-partThe partner path
6#relatedRelated organisations as options
7#commitmentsFive commitments and measures
8#statusStatus from data; read more
ecosystem.json: relationshipsstatus.json: sovereign-stackbenefit.json: B1, B2, B4sovereign.json (new)deployments, licences,agreements: all emptyChecksSovereign AI pageSovereign Stack pageAfrica and sovereign pageRelated organisationsWhile a list is empty, pages say none; when an entry is added with evidence, every page updates together.
What exists is recorded once; every page reads it.
S1 In one paragraphThree sentences; designed, not deployedS2 Four layersWho controls each layer; what CRIS doesS3 How it reachesFive steps and four stages, hosts genericS4 DataPrinciples; counsel’s wording for the restS5 Take partSix steps; nothing named before agreementS6 RelatedOptions, marked, none recorded, none requiredS7 CommitmentsFive commitments, indicators, today from dataS8 StatusStatus line; read more; briefingGreen: status. Blue: how it works. Red: related parties.
Eight blocks, top to bottom.
1Quick fixes20 Nov2sovereign.json4 Dec3Checks11 Dec4Rebuilt page18 Dec5Counsel15 Jan6Approvals12 Feb7Testnet materialPhase P4Steps 1 to 4 in 2026 (built on this preview); steps 5 to 7 in 2027. All dates are proposals.
Seven build steps (proposed dates).
CheckFails when
sv-relatedBGTI, 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-namedA 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-aimsA 2027 or 2029 aim appears without “proposed”
sv-shortThe page’s short description names a related organisation
sv-ctuCTU 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

Title, promise, short: the testnetinitiativeTopic shown as one related organisation (K1); ownerdiffers from the Stack (K4)Link: Africa and sovereign deploymentKeep; move below the opening (K12)“A testbed for sovereign AI … built onLOGOS-C”Stated as fact; data says could, under a writtenagreement (K3); no related-party line (K2)Africa and Global South commitment (link)Keep; show the five commitments here (K10)Plan: programme, partners, results, in P4Partners and results only once agreed and verified(K7)Green: keep. Red: fix. Not on the page: what sovereign AI is (K5), status (K6), measures (K11).
The page before this update: five blocks, about 120 words.
#FindingFixed by
K1The topic was one related organisationShort description and opening about CRIS’s work
K2No related-party lineA line for each, from data
K3Stronger than the data (“a testbed … built on LOGOS-C”)“Could, under a written agreement; none recorded”
K4Two owners for one topicOpen (Q3)
K5Said little about sovereign AIEight blocks
K6No statusStatus line from data
K7The P4 plan promised partners and resultsPlan note rewritten
K8The old testnet route landed hereRedirect moved to the related-organisations entry (Q1, Option A)
K9Stack page said it tests first on the testnet’s nodesStack opening, steps and staging label reworded (Q2)
K10Commitments only linkedFive commitments with measures
K11No measuresB1, B2 and B4
K12Opened with a cross-linkCross-link moved below the opening

Owner: InfrastructureNext review: 2027-03-01