Understanding Governance and Sovereignty
Of Africa’s DPI-Ed
#14 in a series of 29 on Africa’s EdTech Breakthrough System & Project.
Executive Summary
Africa’s Digital Public Infrastructure for Education (DPI-Ed) must solve two problems simultaneously: how to govern a shared, continent-scale digital system, and how to preserve national sovereignty over education policy, data, and delivery. This essay explains how Africa’s DPI-Ed does both.
The answer lies in strict layer separation. Africa’s DPI-Ed consists of a GovStack-compatible specification layer, governed initially by the African Union, and one or more implementation layers, of which RESPECT is a reference implementation stewarded by the Spix Foundation. Sovereignty is preserved because the specification governs interoperability—not control—while implementations compete, evolve, and are governed separately.
This essay clarifies who holds authority at each layer, why trademarks and certification marks confer real governance power at the implementation layer, how EMIS authority remains fully national, and how Africa’s DPI-Ed can evolve from AU stewardship into the global GovStack ecosystem without surrendering national control. Governance and sovereignty are not opposing goals; they are co-designed features of a modern DPI.
1. Why Governance and Sovereignty Are Inseparable
Every continent-scale digital system raises the same inevitable questions:
- Who sets the rules?
- Who can change them?
- Who controls data?
- Who decides what is mandatory—and what remains optional?
In education, these questions are especially sensitive. Education is constitutionally national in most countries, culturally embedded, and politically charged. Any architecture that weakens national sovereignty will fail, regardless of technical merit.
For that reason, governance and sovereignty must be designed together. Governance defines how shared decisions are made. Sovereignty defines what cannot be taken away. Africa’s DPI-Ed succeeds only because it draws this boundary clearly.
2. Two Layers, Two Kinds of Authority
Africa’s DPI-Ed is intentionally divided into two logically separate layers:
- The DPI-Ed Specification Layer
- The DPI-Ed Implementation Layer
Each layer has different purposes, different authorities, and different governance models.
2.1 The Specification Layer: Governing Interoperability
The specification layer defines what interoperable educational systems must be able to do and how they communicate—not who provides them, how they are funded, or which pedagogies they use.
This layer:
- Is GovStack-compatible by design
- Defines interfaces, data models, and compliance requirements
- Enables vendor neutrality and cross-border interoperability
- Cannot mandate any economic model, commercial structure, or operational practice
Because the African Union cannot—and should not—mandate how education systems are financed or delivered, the specification layer is deliberately limited to what must be shared for interoperability to work.
Initial stewardship of Africa’s DPI-Ed specification layer properly sits with the African Union and AUDA-NEPAD. That authority derives from political legitimacy, continental coordination mandates, and policy harmonization—not from operational control.
2.2 The Implementation Layer: Governing Real Systems
Implementations turn specifications into working systems. They carry operational risk, brand risk, and user trust. Governance at this layer must therefore be firm, enforceable, and continuous.
RESPECT is one such implementation. Others may follow.
Implementation governance includes:
- Code stewardship and release control
- Security practices and quality assurance
- Ecosystem participation rules
- Certification criteria and enforcement
- Economic model design and evolution
These responsibilities cannot be exercised by a multilateral political body. They require a dedicated steward with operational continuity.
3. Trademarks, Certification, and Real Authority
In the case of RESPECT, the Spix Foundation holds full authority permitted by law and market forces over its implementation. This authority is not symbolic.
Trademarks and certification marks confer real, enforceable power:
- Only compliant products may use the RESPECT™ and RESPECT Compatible™ marks
- Certification standards can be tightened or revised over time
- Non-compliant or harmful forks cannot present themselves as part of the ecosystem
- Trust signals remain consistent for Ministries, educators, and partners
This model is standard practice in mature FOSS ecosystems. Linux®, Python®, Apache®, and others all rely on strong trademark control to protect integrity while keeping code open.
Open source governs use of code. Trademarks govern use of identity. Together, they enable scale without chaos.
4. Sovereignty at the National Level: What Never Moves
A central concern for Ministries of Education is whether DPI-Ed replaces or subsumes existing national systems. It does not.
In particular:
- EMIS systems remain fully national
- DPI-Ed interoperates with EMISs; it does not replace them
- Data sovereignty remains with national authorities
- Pedagogy, curriculum, assessment, and policy authority remain national
DPI-Ed defines shared rails. EMIS systems remain systems of record.
This distinction is fundamental. Without it, no Ministry could responsibly participate.
5. From African Stewardship to Global GovStack Convergence
Africa’s DPI-Ed is designed not as a regional dead end, but as a contributor to global DPI convergence.
Over time, two evolutions are expected:
- GovStack Absorption As Africa’s DPI-Ed specification matures and proves itself, it is expected to be incorporated into GovStack’s global specification set. At that point, governance shifts from AU-led stewardship to multi-stakeholder GovStack governance, in which the African Union remains a major—but not sole—voice.
- Specification Broadening As non-African jurisdictions adopt country-scale digital education infrastructures, Africa’s DPI-Ed specifications will need to broaden to accommodate additional legal, pedagogical, and institutional contexts—without compromising interoperability.
In both cases, what changes is who governs the shared specification. What does not change is national sovereignty over education systems or implementation-layer autonomy.
Africa governs what must be shared, and keeps sovereign what must remain national.
6. Implementation Sovereignty Is Not a Bug
Just as nations retain sovereignty over education, implementation stewards retain sovereignty over their implementations.
For RESPECT, this includes:
- Governance of the codebase
- Control of trademarks and certification marks
- Enforcement of ecosystem rules
- Evolution of the economic model
This is not a contradiction. It is what makes long-term stewardship possible.
Multiple implementations can coexist beneath a single specification. They may compete, specialize, or collaborate. DPI-Ed enables that plurality by design.
7. Conclusion: Governance That Scales Without Centralizing Power
Africa’s DPI-Ed demonstrates that governance and sovereignty need not be traded off against scale.
By separating specification from implementation, interoperability from control, and shared rails from national authority, the system achieves something rare: continent-scale coordination without political overreach.
The African Union governs the interfaces that must be shared. Nations govern education. Implementation stewards govern their platforms. GovStack governs global convergence.
That layered governance is not complexity for its own sake. It is the minimum structure required for trust, legitimacy, and durable scale in education.
This layered sovereignty architecture also governs the continent-scale education data that AI will require. Learning data generated through Africa’s DPI-Ed remains under African governance at every layer, positioning Africa to train sovereign AI models tuned to African curricula, languages, and learners (see AI in Africa’s DPI-Ed, Essay 12).
This is how Africa’s DPI-Ed can grow from continental coordination to global infrastructure—without losing the sovereignty that makes adoption possible in the first place.
The next essay in this series is 15. Legitimacy, Trust, and Safety (LeTS).
