4 min read - The Sovereign AI Stack: Data, Compute, Models, Skills and Governance

In June 2026, the Morocco at UN Open Source Week 2026 supplied the dated context for assessing data control. The announcement sets the external boundary. Your own evidence must establish whether the idea fits your organisation.

Decide how to handle data control

Proceed only after verifying Data control, Compute capacity, Model choice, Operating skills before selecting a design or provider.

Architecture should make constraints visible before implementation. Map data movement, trust boundaries, failure modes and reversibility before selecting a platform or model. Apply that rule to data control and compute capacity.

Start with data control. That check determines which evidence will be useful for the other dimensions.

What the Morocco at UN Open Source Week 2026 source contributes to data control

Morocco at UN Open Source Week 2026 was reviewed on 27 August 2026 for its treatment of data control. Check the current source before a procurement, architecture or compliance decision. An announcement describes the offer or initiative. Your internal evidence determines whether it meets the need. This operational framework is not legal advice.

Examine data control, compute capacity, model choice, operating skills

1. Data control

For data control, record the current state, the owner and the decision that depends on this dimension. Keep the inventory limited to verifiable facts.

2. Compute capacity

For compute capacity, map the dependencies, data and affected people. Test any assumption that could invalidate the initiative before investing further.

3. Model choice

For model choice, choose observable evidence and a minimum threshold. The test should tell you whether to proceed; an impressive demonstration is not enough.

4. Operating skills

For operating skills, set the boundary, escalation path and exit condition. The team must be able to stop, replace or return the solution to manual operation.

Decision matrix for data control

Leadership, business, technology and security teams should assess the same evidence on data control and compute capacity before deciding.

Test data control in five steps

1. Scope data control. Write down the question, owner and date by which an answer is required.
2. Establish the compute capacity baseline. Measure the current process, including quality, incidents and review effort.
3. Test model choice. Limit data, users, permissions and duration so the change remains reversible.
4. Review operating skills. Examine errors, manual rework, escalations and effects on affected people.
5. Answer the original question. Record proceed, change or stop, together with the evidence supporting that choice.

Evidence to retain for compute capacity

The evidence pack keeps the findings on data control with the other material needed for the decision:

• the decision, its owner and consulted stakeholders;
• the inventory associated with data control;
• the baseline and test results for compute capacity;
• the access, risks and approvals connected to model choice;
• the rollout, monitoring and exit plan for operating skills.

If this initiative stops, retain its findings on data control and operating skills so the next review does not repeat the same assumptions.

Mistakes that weaken model choice

Avoid:

• selecting a platform before mapping data and trust boundaries
• assuming a successful demo proves production feasibility
• ignoring reversibility, portability and failure containment

A 30-day plan for operating skills

• Days 1 to 5. Name the owner of data control, define the boundary and collect available sources.
• Days 6 to 12. Map compute capacity, including its data, access, dependencies and failure scenarios.
• Days 13 to 20. Test model choice against a baseline and pre-agreed stop criteria.
• Days 21 to 26. Ask the responsible functions to review the findings on operating skills.
• Days 27 to 30. Compare the four findings with the decision above and define the next required proof.

Record the decision on data control

Keep a short record with the owner, evidence reviewed and decision. Add the condition that would trigger another review of data control or operating skills.