Measuring Ecosystem-Wide Adoption of Africa's EdTech Breakthrough System
This document defines a comprehensive Momentum Points (MP) Framework for measuring the adoption of Africa's EdTech Breakthrough System across all stakeholder categories. The framework replaces and extends the scoring matrix in the original Momentum Proof document, which focused on pre-Tranche-1 signals for a subset of stakeholder categories
The MP Framework covers the full project lifecycle (2026–2032 and beyond) and all ten stakeholder categories defined in Essay 11 (From Vision to Value). It is grounded in the theory and practice of platform evangelism: using social influence to accelerate the diffusion of an innovation, within a dynamic system, in the presence of network effects, for the benefit of society
The framework is built on three universal ladder templates, a principle of leverage-first design, and strict requirements for publicly verifiable state transitions.
For each stakeholder category, the MP ladder is constructed by:
Every MP state is defined by a publicly observable, verifiable boundary condition. The test: "Could two independent observers, given access to the specified evidence, agree on whether this entity has crossed from State N to State N+1?" If the answer depends on interpretation, the boundary is too soft.
Each state definition specifies the minimum observable evidence required — not a description of the general situation, but the specific artifact or event that proves the transition occurred.
Tier 1 — Publicly verifiable: Any informed observer can confirm the transition from public records (press releases, published documents, attendance records, certification registries, etc.).
Tier 2 — Convenor-verifiable: The Convenor (or Fiduciary Trustee) can attest that the transition has occurred, without disclosing the identity or details of the stakeholder. Reported in anonymized aggregate. Reserved for states involving necessarily confidential deliberations (e.g., DP due diligence, confidential commitment letters).
When a stakeholder crosses from a Tier 2 state to a Tier 1 state, that transition is itself a major social-proof event — the moment private momentum becomes public.
The resources available to execute each Stakeholder Alignment Programme are finite and limited. Each programme is designed to produce the largest possible alignment, within its category, across Africa, at the lowest possible cost in time and cash. In many cases, this requires working through intermediary amplifier organizations rather than engaging end-stakeholders individually.
The framework distinguishes between:
Even for directly tracked categories, the framework identifies amplifier organizations whose engagement can move multiple category members simultaneously.
MP weights follow a steep exponential curve: early states are cheap (low commitment, easily reversible, common), while late states are expensive (high commitment, operationally irreversible, rare). The ratio between the lowest and highest states is approximately 1:100.
Calibration test: Volume at early states must never outweigh depth at late states. Ten MoUs (10 × 5 = 50 MPs) must be worth less than one country-wide rollout (1 × 70 = 70 MPs). This ensures the framework rewards proof of reality over expressions of interest.
Momentum in one category lowers adoption barriers in others. An MoE reaching an active pilot (State 6) generates demand-side pull for App Developers, Localizers, RESPECT Certified Partners, and MNOs in that country. An App Developer achieving certification (State 7) increases the platform's value to every MoE and school network. These cross-category effects are the defining characteristic of a multi-sided platform and the primary mechanism by which the ecosystem becomes self-aligning.
Momentum must be distributed across the ecosystem, not concentrated in a single stakeholder category. The following rules apply when evaluating aggregate MP scores against decision thresholds:
Category cap: No single direct stakeholder category (Sections 3.1–3.6) may contribute more than 40% of any decision threshold toward that threshold. Points earned beyond the cap are real and tracked, but do not count toward the threshold calculation.
Minimum breadth: To reach the High Threshold (300 points), points must come from at least four of the six direct stakeholder categories. To reach the Medium Threshold (230 points), at least three.
Non-cumulative scoring: Each entity contributes the weight of its current (highest achieved) state only, not the sum of all states it has passed through.
Strategic Signals and Amplifiers are uncapped. Points from Strategic Signals (Section 3.7) and from Amplifier/Standards Body ladders (Sections 4–5) count toward the threshold without category caps, because they are cross-cutting credibility events that lower risk perception across all categories simultaneously.
Rationale: A multi-sided platform requires momentum on multiple sides. A project with a dozen certified apps but no operational pilots, no DP engagement, and no MNO progress is not ready for scale-up funding — it is a one-sided preparation effort. The breadth rule ensures that threshold scores reflect genuine ecosystem-wide traction, not single-axis overperformance.
The framework uses three universal ladder templates. Every entity in the framework is tracked on one (or occasionally two) of these templates.
Used for entities whose own adoption is tracked individually. Six category-specific versions exist (Sections 3.1–3.6), but all share the same structural logic: awareness → engagement → formal commitment → pilot/operational deployment → scale → self-sustaining operations.
A single universal template for any organization whose function is to produce, train, enable, convene, or advocate on behalf of a stakeholder category. The same ladder applies regardless of whether the amplifier is a developer network, a teacher training college, a teacher union, a Bible translation organization, or a research grant-maker.
A shorter template for any organization whose function is to set standards, accredit, validate, or endorse. These entities do not deliver services to a constituency; they set rules that other entities must follow. Their end-state is the incorporation of RESPECT-related requirements into their standards, which then cascades to every entity they regulate.
Population: 55 AU member states. Individually trackable.
End-state: The Ministry has completed a country-wide rollout of RESPECT, integrated RESPECT data flows into its EMIS, and funds ongoing operations from national budget lines.
| State | Description | Transition Evidence | Tier | Weight |
|---|---|---|---|---|
| 10 | National budget line: MoE funds RESPECT operations from recurrent national education budget | Published national budget document or gazette entry containing a RESPECT/DPI-Ed line item | 1 | 100 |
| 9 | Country-wide rollout operational: RESPECT deployed across all target schools nationwide | Published deployment report or MoE press release citing nationwide coverage figures and date | 1 | 70 |
| 8 | Scale-out decision taken: Cabinet or ministerial authority formally approves country-wide rollout with budget allocation | Published cabinet minute, ministerial directive, or official gazette entry authorizing rollout and specifying budget and timeline | 1 | 45 |
| 7 | Pilot evidence publicly reported: MoE cites pilot outcomes in at least one publicly accessible document (ministerial statement, published evaluation report, conference presentation with published proceedings) | Publication date of the citing document | 1 | 25 |
| 6 | Active pilot underway: Learners and teachers using RESPECT in Ministry-authorized schools, with data flowing to Ministry systems | Published pilot launch announcement by MoE or implementing partner, specifying schools, start date, and scope | 1 | 15 |
| 5 | Pilot Plan signed: MoE and Spix/RESPECT Certified Partner sign a Pilot Plan specifying schools, subjects, grades, timeline, success criteria, and EMIS integration points | Signed Pilot Plan document (Convenor-verifiable if MoE requests confidentiality; becomes Tier 1 upon pilot launch at State 6) | 2→1 | 8 |
| 4 | MoU signed: Non-binding Memorandum of Understanding signed, expressing intent to explore RESPECT adoption | Signed MoU document, with at least a public acknowledgment of its existence by one signatory | 1 | 5 |
| 3 | Senior official champions: A named official (Director-level or above) publicly advocates for RESPECT exploration | Published record: speech transcript, press quote, conference proceedings, social media post by the named official, or official correspondence released with consent | 1 | 3 |
| 2 | Formal briefing received: Ministry officials attend a structured briefing on RESPECT and Africa's DPI-Ed | Attendance record signed by at least one Ministry attendee, or written post-briefing follow-up request from a named Ministry official | 2 | 2 |
| 1 | Aware and engaged: Ministry has received introductory materials and responded | Documented response (email, letter, or equivalent) from a named Ministry official acknowledging receipt | 2 | 1 |
MoE Amplifiers (tracked on the Amplifier Ladder, Section 4): Regional Economic Communities (RECs).
Population: Finite — bilateral agencies, multilaterals, foundations. Individually trackable.
End-state: The DP has made a multi-tranche public funding commitment, is disbursing funds, and publicly cites the Breakthrough System as a flagship programme.
| State | Description | Transition Evidence | Tier | Weight |
|---|---|---|---|---|
| 10 | Flagship citation: DP presents the Breakthrough System as a flagship programme in at least one publicly accessible document (annual report, leader speech, board minutes, analyst call transcript) | Publication date of the citing document | 1 | 100 |
| 9 | Funds received: First tranche released and received by at least one designated recipient | Recipient's public acknowledgment of receipt, or auditable transfer record | 1 | 75 |
| 8 | Dated public funding commitment: DP publicly commits a specified amount to a named Breakthrough System component, with a stated disbursement date or timeline | Published commitment document (press release, signed agreement, or public statement) specifying amount, component, and date | 1 | 50 |
| 7 | Governance approval made public: DP's internal governance body formally authorizes the funding commitment, as evidenced by a publicly available record (ministerial press release, published board minutes, official gazette entry) | Publication date of the authorizing record | 1 | 35 |
| 6 | Confidential conditional commitment: DP issues a signed letter of intent or conditional commitment specifying amount, component, and conditions | Signed document (verifiable by Convenor and Fiduciary Trustee; becomes public upon conversion to State 7 or 8) | 2 | 20 |
| 5 | Due diligence recommendation issued: DP's review team completes assessment and issues a written internal recommendation | Written recommendation document (verifiable by Convenor upon DP's consent) | 2 | 12 |
| 4 | Due diligence formally initiated: DP assigns named staff and formally opens a review process for a specific funding opportunity | DP's written notification to Spix/Convenor naming the review lead and confirming scope | 2 | 7 |
| 3 | Convenor process participation: DP sends a named representative to at least one structured multi-donor coordination meeting | Attendance record of the coordination meeting | 1 | 4 |
| 2 | Senior decision-maker engaged: An individual with funding authority, identified by name and title, has attended a structured briefing and made a written request for follow-up | The written request (email, letter, or equivalent) | 2 | 2 |
| 1 | Aware and monitoring: DP staff have received introductory materials, as evidenced by a delivery confirmation or documented response | Delivery confirmation or written acknowledgment | 2 | 1 |
Population: ~100–150 licensed operators continent-wide; perhaps 20–30 strategically relevant. Individually trackable.
End-state: The MNO carries RESPECT educational data traffic at the AU's Education Rate across its network footprint, bundles or preinstalls RESPECT Compatible Apps on devices it sells, and publicly markets its role as a brand asset.
| State | Description | Transition Evidence | Tier | Weight |
|---|---|---|---|---|
| 10 | Brand integration: MNO features RESPECT/Education Rate participation in at least one public-facing document (annual report, sustainability report, consumer advertisement, investor presentation) | Publication date of the citing document | 1 | 100 |
| 9 | Education Rate operational at scale: E-Rate traffic flowing across the MNO's full network footprint in at least one country | Published service announcement or regulatory filing confirming E-Rate availability across the MNO's coverage area, specifying date | 1 | 70 |
| 8 | Bundling/preinstall live: MNO distributing devices with RESPECT Compatible Apps preinstalled, or distributing LearnTabs through its retail channel, in at least one market | First verified retail availability (product listing, retail announcement, or store confirmation) with date | 1 | 45 |
| 7 | Commercial terms signed: MNO and Spix/AUDA-NEPAD sign a binding commercial agreement specifying E-Rate terms, bundling arrangements, and/or LearnTab distribution, with stated effective date | Signed agreement (Convenor-verifiable; becomes Tier 1 upon public announcement or operational launch) | 2→1 | 30 |
| 6 | Public partnership announcement: MNO publicly announces engagement with RESPECT or Africa's DPI-Ed in at least one published record (press release, conference keynote, MWC/AfricaCom statement) | Publication date of the announcement | 1 | 20 |
| 5 | Technical integration pilot: MNO runs a bounded technical trial (E-Rate traffic classification, device configuration, or LearnTab connectivity) in a live network segment | Pilot completion report signed by both MNO and Spix technical leads, specifying dates, scope, and results | 2 | 10 |
| 4 | Formal engagement: MNO assigns named staff and confirms in writing to Spix's MNO Alignment Programme (IDEX Africa) that structured exploration is underway | Written confirmation from MNO naming their lead and confirming scope | 2 | 5 |
| 3 | Senior executive briefed: C-suite or VP-level executive attends a structured briefing | Written post-briefing follow-up request from the named executive, or signed attendance record | 2 | 3 |
| 2 | Industry event awareness: Named MNO staff engage with RESPECT at an industry event (MWC, AfricaCom, or IDEX-organized session) | Event attendance record or documented follow-up correspondence from a named MNO representative | 2 | 2 |
| 1 | Initial contact acknowledged: First introductory communication received and acknowledged in writing | Written acknowledgment from a named MNO representative | 2 | 1 |
Population: Tracked at the network/association level. Includes continental faith-based systems (Catholic, Anglican, Islamic), large private chains, and national associations (e.g., GNAPS in Ghana). A single large network can span multiple countries and deliver more classrooms than many MoEs.
Tracking approach: Each Non-MoE school network is tracked on this ladder (which matches the MoE ladder structure). Optionally, a network that chooses to develop its own RESPECT Compatible courseware is additionally tracked on the App Developer ladder (Section 3.5).
End-state: The school network has deployed RESPECT across its entire African footprint, integrated RESPECT data into its own management systems, and funds ongoing RESPECT operations from its own budget.
| State | Description | Transition Evidence | Tier | Weight |
|---|---|---|---|---|
| 10 | Self-funded network-wide operations: Network funds RESPECT operations from own resources (fees, diocesan funds, foundation grants) across its African footprint | Published financial report or leadership statement confirming self-funded RESPECT operations, with date | 1 | 100 |
| 9 | Network-wide rollout operational: RESPECT deployed across all or substantially all schools in the network's African footprint | Published deployment report from network leadership citing coverage figures and date | 1 | 70 |
| 8 | Rollout decision taken: Network's governing authority formally approves network-wide deployment | Published minutes, directive, or press release from governing authority specifying approval and timeline | 1 | 45 |
| 7 | Pilot evidence shared publicly: Network publicly reports pilot outcomes and endorses RESPECT to peer networks in at least one published document | Publication date of the citing document | 1 | 25 |
| 6 | Active pilot underway: Learners and teachers using RESPECT in network schools | Published pilot launch announcement by network or implementing partner, specifying schools, start date, and scope | 1 | 15 |
| 5 | Pilot agreement signed: Network and Spix/RESPECT Certified Partner sign a pilot plan specifying schools, scope, and success criteria | Signed agreement (Convenor-verifiable; becomes Tier 1 upon pilot launch) | 2→1 | 8 |
| 4 | MoU or Letter of Intent signed: Network leadership signs a non-binding agreement to explore RESPECT adoption | Signed document with at least a public acknowledgment of its existence by one signatory | 1 | 5 |
| 3 | Decision-maker champions: A named senior leader (Secretary General, Education Director, or equivalent) publicly advocates for RESPECT exploration | Published record: speech, press quote, conference proceedings, or official communication | 1 | 3 |
| 2 | Structured briefing received: Network leadership attends a dedicated briefing | Written post-briefing follow-up request from a named network leader, or signed attendance record | 2 | 2 |
| 1 | Aware and engaged: Initial contact made; introductory materials acknowledged in writing by a named network representative | Written acknowledgment | 2 | 1 |
Population: Finite and individually trackable. The strategically relevant set (those with FLN apps suitable for RESPECT-ification for Tranche 1) numbers perhaps 30–80. Also used for Non-MoE school networks that optionally develop their own courseware, and for PD courseware developers.
End-state: The developer's RESPECT Compatible App is certified, available to learners at scale, generating verified usage data, and earning Ecosystem Fund revenue.
| State | Description | Transition Evidence | Tier | Weight |
|---|---|---|---|---|
| 10 | Ecosystem Fund revenue flowing: Developer receiving Ecosystem Fund distributions based on verified learner-app interaction data | At least one payment receipt or published Ecosystem Fund disbursement report (Convenor-verifiable) | 2 | 100 |
| 9 | Verified usage at scale: App in active use by learners in at least three countries, with xAPI interaction data flowing to RESPECT data systems | Published usage report or dashboard showing multi-country deployment with date | 1 | 70 |
| 8 | App available on distribution channel: Certified RESPECT Compatible App publicly available on Google Play, LearnTab preinstall, or equivalent distribution channel | Publicly verifiable app listing with RESPECT Compatible certification mark and publication date | 1 | 50 |
| 7 | RESPECT Compatible certification achieved: App passes RESPECT Compatible test suite | Published certification record (certificate number, date, app name, version) in RESPECT's public certification registry | 1 | 30 |
| 6 | App submitted for certification: Developer formally submits app to RESPECT Compatible certification process | Submission confirmation with date (Convenor-verifiable; becomes Tier 1 upon certification) | 2→1 | 18 |
| 5 | Active engineering underway: Developer has assigned engineering resources and is building RESPECT compatibility | Convenor-verified evidence: named engineering lead, development timeline, demonstrated progress | 2 | 10 |
| 4 | Formal commitment to RESPECT-ify: Developer signs a written commitment specifying target app and timeline | Signed commitment document (Convenor-verifiable) | 2 | 6 |
| 3 | Technical evaluation completed: Developer's technical team has reviewed RESPECT APIs, SDK, and compatibility requirements and provided written feedback | Written feedback document (Convenor-verifiable) | 2 | 3 |
| 2 | Developer engaged: Named representative attends a structured briefing or Early Adopter Programme session | Attendance record or written follow-up request from named representative | 2 | 2 |
| 1 | Aware and interested: Developer has received introductory/enablement materials and acknowledged receipt | Written acknowledgment from named representative | 2 | 1 |
AppDev Amplifiers (tracked on the Amplifier Ladder, Section 4): Google Developer Relations (Africa), Andela Learning Community, AfriLabs, Injini, EdTech East Africa, XPRIZE Accelerate Learning Challenge.
Population: Starts at zero, grows through certification. Each is individually known. Expected to scale from dozens (Phase 1) to hundreds (Phase 3).
End-state: The Partner is certified, operating profitably in at least one country, is paid as a service provider by that country's MoE and/or School Leaders from Non-MoE Schools, delivering training and support at scale within that country, and generating revenue that sustains its RESPECT practice without DP subsidy.
| State | Description | Transition Evidence | Tier | Weight |
|---|---|---|---|---|
| 10 | Self-sustaining operations: Partner operates profitably in at least one country, funding its RESPECT practice from service revenue without DP subsidy | Published annual report or audited financial statement showing sustainability from RESPECT-derived revenue | 1 | 100 |
| 9 | Operational at scale in at least one country: Partner delivering RESPECT training and support across a significant portion of at least one country | Published service report or Ministry confirmation citing the Partner's coverage area and date | 1 | 70 |
| 8 | Contracted by MoE or school network: Partner has signed at least one service contract for RESPECT-related services | Signed contract (NDA-verifiable; becomes Tier 1 when services commence and are publicly referenced) | 2→1 | 40 |
| 7 | Successful pilot delivery: Partner has delivered training, integration, or support during at least one RESPECT pilot, with a published completion report | Published pilot completion report naming the Partner and specifying scope, dates, and outcomes | 1 | 25 |
| 6 | Deployed to pilot: Partner staff on the ground delivering services in at least one active RESPECT pilot | Published pilot launch announcement naming the Partner as implementing partner | 1 | 15 |
| 5 | RESPECT Certified: Partner organization passes RESPECT Certified Partner certification | Published certification record in RESPECT's public certification registry | 1 | 10 |
| 4 | Staff trained and individually certified: At least three of the Partner's staff hold individual RESPECT Certified Implementor (Impletor) certification | Published individual certification records in RESPECT registry | 1 | 6 |
| 3 | Staff in training: Partner has enrolled staff in RESPECT Impletor training programme | Enrollment confirmation from certification body (Convenor-verifiable) | 2 | 3 |
| 2 | Formal application submitted: Partner organization has submitted a formal application to become a RESPECT Certified Partner | Application receipt confirmation with date (Convenor-verifiable) | 2 | 2 |
| 1 | Aware and interested: Organization has received information about the RESPECT Certified Partner programme and acknowledged interest in writing | Written acknowledgment from named representative | 2 | 1 |
Purpose: Strategic Signals are one-time, high-weight, publicly verifiable events that establish the project's institutional credibility and governance infrastructure. They do not belong to any single stakeholder category — they are cross-cutting credibility events that lower risk perception for every category simultaneously.
Scoring: Strategic Signal points are uncapped (each signal is a unique event, not a repeatable per-entity progression). They count toward decision thresholds but are not subject to the 40% category cap defined in Section 1.7.
| Signal | Points | Transition Evidence | Tier |
|---|---|---|---|
| Convenor formally committed: A named, internationally credible institution publicly commits to serve as Convenor for the Breakthrough System's funding coordination process | 40 | Published announcement by the institution confirming the Convenor role, specifying scope and mandate | 1 |
| Technical Advisory Council established: A TAC with published membership of internationally recognized experts is formally constituted | 30 | Published announcement naming TAC members and their institutional affiliations | 1 |
| Major global foundation joins Convenor process: A foundation with a recognized education or development mandate formally joins the multi-donor coordination process | 30 | Published announcement or verified attendance record of the coordination process | 1 |
| International standards body acceptance: RESPECT or a RESPECT component is formally accepted into an international standards process (e.g., GovStack Education Working Group) | 25 | Published membership list or acceptance letter with date | 1 |
| AU-level political endorsement: The African Union Assembly, a Summit declaration, or an AU organ formally references or endorses the Breakthrough System or its components | 50 | Published AU decision, declaration, or communiqué text with date | 1 |
The Amplifier Ladder applies to any organization whose function is to produce, train, enable, convene, or advocate on behalf of a stakeholder category. The same ladder template is used regardless of the amplifier's type or the category it serves.
End-state: The organization has embedded RESPECT-related content into its standard programming, its constituency is being reached at scale as a recurring activity, and the organization actively promotes the RESPECT Ecosystem.
| State | Description | Transition Evidence | Tier | Weight |
|---|---|---|---|---|
| 10 | Constituency reached at scale: Organization's RESPECT-related activities have reached its constituency across a significant portion of one or more countries, as a recurring programme | Published programme report citing reach figures, locations, and dates | 1 | 100 |
| 9 | RESPECT embedded in standard operations: Organization's published programme description, curriculum, policy platform, or service catalog includes RESPECT-related content as a recurring standard component | Published programme materials with date | 1 | 70 |
| 8 | First constituency outcomes demonstrated: At least one cohort of the organization's constituency (graduates, trainees, members, grantees) has demonstrably engaged with RESPECT as a result of the organization's activities | Published outcome report (graduation records, training completion, member participation, certified outputs) with date | 1 | 45 |
| 7 | RESPECT content delivered across multiple settings: Organization has delivered RESPECT-related activities (courses, training, workshops, awareness sessions, grant rounds, publications) in at least three locations, cohorts, or events | Published delivery records specifying settings, dates, and participation | 1 | 30 |
| 6 | Pilot programme delivered: Organization runs at least one RESPECT-related activity (pilot course, training session, workshop, awareness event, pilot grant round) | Published event listing or completion report with date, attendance, and outcomes | 1 | 18 |
| 5 | RESPECT content developed or adapted: Organization has produced, adapted, or adopted RESPECT-related materials for use with its constituency (course modules, PD content, advocacy materials, enablement resources, call-for-proposals criteria) | Published or Convenor-verified materials with date | 1/2 | 10 |
| 4 | Formal partnership signed: Organization and Spix sign an agreement to collaborate on RESPECT integration, specifying scope and planned activities | Signed agreement with public acknowledgment by at least one signatory | 1 | 6 |
| 3 | Leadership engaged: Named programme director or equivalent attends a structured briefing and requests follow-up | Written follow-up request from named leader | 2 | 3 |
| 2 | Aware: Organization has received introductory materials and acknowledged receipt | Written acknowledgment from named representative | 2 | 1 |
| 1 | Identified as target: Organization identified as strategically relevant by the relevant Alignment Programme | Internal Spix record | — | 0 |
The following entities are tracked on the Amplifier Ladder. The Leverage Rationale column explains why each entity merits amplifier status — i.e., how engaging this single entity moves multiple members of the target category simultaneously.
| Entity Type | Examples | Leverage Rationale |
|---|---|---|
| Teacher Training Colleges / Education Faculties | ~500–1,000 across the continent; strategically important ones in pilot countries | One curriculum change produces RESPECT-competent graduates for decades |
| In-Service Professional Development Providers | Government PD units, NGO PD programmes, private PD firms | One provider reaching scale covers thousands of practicing teachers |
| Teacher Unions | EIRAF member unions, national unions | One union endorsement reaches every member; union networks reach teachers that top-down Ministry programmes miss |
| AFTRA (as advocate) | Continental federation of teaching regulatory authorities | AFTRA advocacy influences every national teaching authority in its membership |
| Entity Type | Examples | Leverage Rationale |
|---|---|---|
| Commercial Localization Firms | Dozens of firms with African-language capacity | Each firm can produce multiple localizations across multiple languages |
| Bible Translation Organizations | BICAM (Catholic/SECAM), SIL International, United Bible Societies, Wycliffe | Decades of African-language expertise, orthographies, glossaries, and trained translator networks for hundreds of languages; SIL maintains ISO 639-3 language registry |
| University Linguistics / Translation Departments | ~50–100 departments with relevant expertise | Graduates enter the localization workforce; faculty contribute to quality research |
| Entity Type | Examples | Leverage Rationale |
|---|---|---|
| African Curriculum Association (ACA) | Continental professional network of curriculum developers | One partnership reaches every national curriculum center through ACA's membership and annual conference |
| REC-Level Education Bodies | EAC Education Division, SADC Education Programme, ECOWAS Committee on Education | One REC adopting mapping as part of harmonization pulls every member state's curriculum center |
| UNESCO-IBE and Partner Universities | IBE plus ~4–5 African partner universities delivering curriculum specialist Master's programmes | ~400 trained curriculum specialists, many now national curriculum directors; IBE integration produces mapping-ready graduates |
| IMPACT Board | RESPECT Planet-Project for professional certification | The certification pipeline that defines Mapper standards, trains, and certifies; supply-side bottleneck |
| National Curriculum Development Centers | ~55 (one per AU member state); ~10–15 strategically relevant in Phase 1 | Each center's staff understand their country's curriculum most deeply; commitment of staff time solves that country's mapping |
| Entity Type | Examples | Leverage Rationale |
|---|---|---|
| Continental Research Conveners | ADEA (primary), ESSA | One Triennale session reaches the entire continental education research community; ADEA's ERAA awards confer prestige |
| Research Grant-Making Organizations | IDRC, Mastercard Foundation, Wellcome, GPE, NORRAG, national research councils | One funding line signals to every research institution that RESPECT research is fundable |
| Relevant Journals | International Journal of Educational Development, Journal of Learning for Development, etc. | One published paper validates the research agenda; a special issue establishes the field |
| University Research Centers / Faculties | ~50–100 strategically relevant institutions | Each active research programme generates findings that improve the system |
| Entity Type | Examples | Leverage Rationale |
|---|---|---|
| Google Developer Relations (Africa) | 173 GDG chapters + 200+ Developer Student Clubs across 36 countries | One partnership distributes RESPECT codelabs, SDKs, and hackathon templates to the largest organized developer community in Africa |
| Andela Learning Community | 110,000+ members across 49 countries | Training pathway integration reaches the largest trained-developer pool on the continent |
| AfriLabs | ~500 member hubs across 53 countries | Network-level partnership pushes RESPECT awareness to every hub |
| XPRIZE Accelerate Learning Challenge | Curated FLN developers globally (2025–2029) | Competition pipeline feeds high-quality apps directly into the ecosystem |
| EdTech-specialist accelerators | Injini (Cape Town), EdTech East Africa | Small but highly targeted — every cohort company is a strong RESPECT candidate |
| Entity Type | Examples | Leverage Rationale |
|---|---|---|
| Regional Economic Communities (Education Bodies) | EAC, SADC, ECOWAS, COMESA, ECCAS, AMU | Policy domestication flows from AU through RECs to member states; one REC adoption pulls 5–15 MoEs |
Note: AUDA-NEPAD is excluded from the Amplifier catalog because it is already fully committed as the political host of the Breakthrough System. It is a given, not a target.
The Standards/Regulatory Body Ladder applies to any organization whose function is to set standards, accredit, validate, or endorse. These entities do not deliver services to a constituency; they set rules that cascade to every entity they regulate. Their end-state is the incorporation of RESPECT-related requirements into their standards.
| State | Description | Transition Evidence | Tier | Weight |
|---|---|---|---|---|
| 9 | RESPECT requirement in standards: Body's published standards require RESPECT-related competency, compliance, or compatibility as a condition for accreditation, endorsement, or certification | Published standards document with effective date | 1 | 100 |
| 8 | Standards revision underway: Body has formally initiated a revision of its standards to incorporate RESPECT-related requirements, with a named working group and published timeline | Published revision notice or working group terms of reference with date | 1 | 60 |
| 7 | Pilot assessment completed: Body has assessed at least one entity against draft RESPECT-related criteria and published results | Published assessment report with date | 1 | 35 |
| 6 | Public endorsement: Body publicly endorses RESPECT integration or compatibility with its existing standards | Published endorsement statement with date | 1 | 20 |
| 5 | Standards alignment assessed: Body's technical staff have evaluated RESPECT-related requirements against existing frameworks and provided a written compatibility assessment | Written assessment (Convenor-verifiable) | 2 | 12 |
| 4 | Formal partnership signed: Body and Spix sign an agreement to collaborate on standards development | Signed agreement with public acknowledgment | 1 | 7 |
| 3 | Leadership briefed: Named director or equivalent attends a structured briefing | Written follow-up request from named leader | 2 | 3 |
| 2 | Aware: Body has received introductory materials and acknowledged receipt | Written acknowledgment | 2 | 1 |
| 1 | Identified as target: Body identified as strategically relevant by the relevant Alignment Programme | Internal Spix record | — | 0 |
| Entity Type | Category Served | Examples | Cascade Effect |
|---|---|---|---|
| Teacher Training Accreditation Bodies | Educators | National accreditation authorities; AFTRA (standard-setting function) | One accreditation requirement change compels every teacher training college in the jurisdiction to integrate RESPECT |
| Language Standardization Bodies | Localizers | National language boards, ACALAN (AU specialized institution for African languages) | Endorsement validates localization quality for every localizer and MoE in that language's jurisdictions |
Continental-level strategic signals: AFTRA incorporating RESPECT-related digital pedagogy into the CTQF or CFSCTP is a continental-scale cascade event affecting every national teaching authority. ACALAN endorsing RESPECT localization standards affects every national language board. These are tracked as one-time high-weight events rather than as ladder progressions.
| Category | Ladder | Population | Tracking Unit |
|---|---|---|---|
| Ministries of Education | Section 3.1 | 55 | Individual MoE |
| Development Partners | Section 3.2 | ~30–50 | Individual DP |
| Mobile Network Operators | Section 3.3 | ~20–30 strategically relevant | Individual MNO |
| Non-MoE School Networks | Section 3.4 (+ optionally 3.5) | ~20–40 networks | Individual network |
| App Developers | Section 3.5 | ~30–80 | Individual developer/firm |
| RESPECT Certified Partners | Section 3.6 | Grows from 0 | Individual partner firm |
| Category | Intermediary Types | Section |
|---|---|---|
| Educators | Teacher training colleges, PD providers, teacher unions, AFTRA-as-advocate | 4.2 |
| Localizers | Commercial firms, Bible translation organizations, university linguistics departments | 4.2 |
| Mappers | ACA, REC education bodies, UNESCO-IBE, IMPACT Board, national curriculum centers | 4.2 |
| Researchers | ADEA, grant-makers, journals, university research centers | 4.2 |
| Category Amplified | Amplifier Entities | Section |
|---|---|---|
| App Developers | Google DevRel Africa, Andela, AfriLabs, XPRIZE, EdTech-specialist accelerators | 4.2 |
| Ministries of Education | Regional Economic Communities | 4.2 |
| Entity Type | Category Served | Section |
|---|---|---|
| Teacher training accreditation bodies | Educators | 5.2 |
| Language standardization bodies | Localizers | 5.2 |
| Signal | Points | Section |
|---|---|---|
| Convenor formally committed | 40 | 3.7 |
| Technical Advisory Council established | 30 | 3.7 |
| Major global foundation joins Convenor process | 30 | 3.7 |
| International standards body acceptance | 25 | 3.7 |
| AU-level political endorsement | 50 | 3.7 |
| Threshold | Score | Minimum Breadth | Action |
|---|---|---|---|
| High | 300 | 4 of 6 direct categories | First-Mover proceeds with full commitment; Tranche 1 released |
| Medium | 230 | 3 of 6 direct categories | Convenor releases Ramp-to-Proof funding; proof window extended |
| Low | < 180 | — | Project paused, restructured, or terminated |
Category cap: No single direct stakeholder category may contribute more than 40% of the threshold toward the threshold score. Strategic Signals, Amplifiers, and Standards Bodies are uncapped. Scoring is non-cumulative (each entity contributes the weight of its current state only).
This framework is grounded in the theory and practice of platform evangelism: using social influence to accelerate the diffusion of an innovation, within a dynamic system, in the presence of network effects, for economic gain (to the platform vendor or to society as a whole).
Key theoretical underpinnings include:
Social influence (Cialdini): The MP ladder exploits commitment/consistency (each state makes the next state psychologically easier), social proof (each entity's public progression lowers the adoption barrier for others in the same category and in other categories), and authority (endorsements by standards bodies and continental institutions carry outsized weight).
Diffusion of innovations (Rogers): The ladder maps the adoption lifecycle from innovators (first MoEs to sign MoUs) through early adopters (first pilots) to early majority (scale-out decisions). The framework is designed to accelerate passage through the "chasm" (Moore) between early adopters and early majority.
Multi-sided platform economics (Rochet & Tirole, Eisenmann, Parker & Van Alstyne): Each stakeholder category is a "side" of the platform. Cross-side network effects mean that momentum in one category increases the platform's value to every other category. The framework measures momentum across all sides simultaneously, because a platform that is strong on only one side will not reach critical mass.
Platform evangelism (Plamondon): The five functions of platform evangelism — ecosystem sales, developer enablement, ecosystem feedback, ecosystem intelligence, and ecosystem regulation — inform the design of Stakeholder Alignment Programmes. The Amplifier Ladder directly implements the enablement function: creating the resources and institutional partnerships that enable stakeholders to progress swiftly through the adoption process.
Self-fulfilling prophecy and critical mass: A platform that is perceived to have the highest value tends to accumulate the most participants, which makes it more valuable, in a virtuous cycle. The MP Framework is designed to make this momentum visible and legible to all stakeholders, reinforcing the perception of inevitability that accelerates adoption.
This framework replaces and extends the scoring matrix in the Momentum Proof document (in this folder). The Momentum Proof's pre-Tranche-1 decision thresholds (300 points for full commitment, 230 for ramp-to-proof, 180 for pause) remain valid as a specific application of this broader framework. The Momentum Proof should be updated to reference this framework and to adopt its revised weight calibration and falsifiable transition evidence standards
The stakeholder categories and alignment programmes are defined in Essay 11 (From Vision to Value). This framework operationalizes those programmes by providing measurable progression ladders for every stakeholder type
The entity catalog (Section 6) should be maintained as a living document, updated as new amplifier organizations are identified and as the ecosystem matures.