> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/roadmap/glossary.md). # Glossary The terms this guide uses, each with the subtopic or page that teaches it, and the names used for Progressa. | Term | What it means here | Where it is taught | | --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Acceptance check** | The check that proves a configuration works. Each configuration has one of the same name, which says what the check runs and what counts as a pass. Nothing is said to run until its check has passed and the run is recorded. | [5.4](/experience-digital-transformation/roadmap/module-5-join-the-blocks-and-prove-the-foundation/5.4-the-acceptance-checks-from-set-up-to-proven.md); the build plan | | **Adopting authority** | The authority that adopts the roadmap, so that it becomes the government's own. | [6.7](/experience-digital-transformation/roadmap/module-6-from-a-proven-foundation-to-a-national-roadmap/6.7-validate-revise-adopt.md) | | **AI usage tip** | The prompt each subtopic carries, in four parts: the problem it solves, the prompt, its inputs and outputs, and a safeguard. The assistant drafts; a person decides. | every subtopic; [6.9](/experience-digital-transformation/roadmap/module-6-from-a-proven-foundation-to-a-national-roadmap/6.9-the-ai-plays-step-by-step.md) | | **Architect register** | The way modules 2 to 5 are written: for the team that configures the service, one level deeper into configuration than the Strategist register. | the opening | | **Beacon project** | The roadmap's name for a service that shows the foundation working, so that support holds. | [6.3](/experience-digital-transformation/roadmap/module-6-from-a-proven-foundation-to-a-national-roadmap/6.3-the-roadmap-over-time-horizons-waves-and-tracks.md) | | **Building block** | A shared, reusable piece of digital infrastructure with a published specification, such as Registration, Digital Registries, Identity or Payments. GovStack publishes the specifications. | [1.8](/experience-digital-transformation/roadmap/module-1-where-your-country-stands-and-what-to-build-first/1.8-foundational-blocks-and-the-sectors-own.md), [1.10](/experience-digital-transformation/roadmap/module-1-where-your-country-stands-and-what-to-build-first/1.10-the-first-proof-for-education-one-service-on-four-blocks.md) | | **Configuration** | One thing the build sets up, named by its block: R for Registration, RG for Digital Registries, I for Identity, P for Payments, X for the composition on the data exchange layer. | the build plan | | **Core and supplementary** | A core video is one without which the method cannot be followed from assessment to roadmap, or the build from its first configuration to its proof. A supplementary video deepens a core one and can be left out without losing the thread. | the opening | | **Demonstration segment** | A recording of the screen with a voice-over, inside the video of its subtopic. Until it can be recorded, its storyboard stands in its place. | the build plan | | **Desk assessment** | A first reading of what the country has already published, run with an AI assistant against the question bank. Its results are claims to verify, not findings. | [1.4](/experience-digital-transformation/roadmap/module-1-where-your-country-stands-and-what-to-build-first/1.4-start-at-the-desk-a-first-assessment-from-public-sources-with-ai.md) | | **Digital public infrastructure (DPI)** | Foundational digital systems that serve the whole society. UNDP gives four marks: it serves the whole society, many services can connect to it, it is built on open standards, and clear rules govern it. Its three recognised categories are digital identity, digital payments and consent-based data sharing, with others emerging. | [1.1](/experience-digital-transformation/roadmap/module-1-where-your-country-stands-and-what-to-build-first/1.1-what-makes-infrastructure-foundational.md) | | **Domain report** | The report of one domain after scoring: the stage of each sub-component with the evidence for it, the domain's stage, a key strength and a development priority. | [1.7](/experience-digital-transformation/roadmap/module-1-where-your-country-stands-and-what-to-build-first/1.7-score-each-domain-five-stages-and-one-table.md) | | **Finding** | An answer that has been checked against documents, in interviews and workshops, and in a validation session with the people who gave it. A desk result or a questionnaire answer is not yet a finding. | [1.6](/experience-digital-transformation/roadmap/module-1-where-your-country-stands-and-what-to-build-first/1.6-verify-before-you-score.md) | | **Five domains** | The foundation of governance, policy and law, and the four pillars that stand on it: Access, Digital Data, Interoperability and Digital Identity. The names are PAERA's (section 3.3.1); reading the foundation as a fifth domain beside the pillars is the team's own reading. | [1.2](/experience-digital-transformation/roadmap/module-1-where-your-country-stands-and-what-to-build-first/1.2-the-five-domains-as-a-map.md) | | **Five stages** | The scale of the UNDP Digital Development Compass: Basic, Opportunistic, Systematic, Differentiating and Transformational, with scores between 0 and 5. | [1.7](/experience-digital-transformation/roadmap/module-1-where-your-country-stands-and-what-to-build-first/1.7-score-each-domain-five-stages-and-one-table.md) | | **Foundational block** | A block every sector uses: identity, payments and data exchange. It is funded as shared infrastructure. | [1.8](/experience-digital-transformation/roadmap/module-1-where-your-country-stands-and-what-to-build-first/1.8-foundational-blocks-and-the-sectors-own.md) | | **Gap register** | One register of every gap the assessment found, each ranked by impact, urgency, feasibility and what depends on it, and each naming the findings it comes from. | [6.1](/experience-digital-transformation/roadmap/module-6-from-a-proven-foundation-to-a-national-roadmap/6.1-from-findings-to-priorities-the-gap-register.md) | | **Horizon** | A period of years in the roadmap. The first horizon is written in waves; the later horizons in overview. | [6.3](/experience-digital-transformation/roadmap/module-6-from-a-proven-foundation-to-a-national-roadmap/6.3-the-roadmap-over-time-horizons-waves-and-tracks.md) | | **Information Mediator** | GovStack's name for the data exchange layer through which blocks call each other. In Progressa it is Linkup, an X-Road federation. | [5.1](/experience-digital-transformation/roadmap/module-5-join-the-blocks-and-prove-the-foundation/5.1-what-must-be-in-place-before-the-blocks-can-call-each-other.md), [5.2](/experience-digital-transformation/roadmap/module-5-join-the-blocks-and-prove-the-foundation/5.2-who-puts-the-steps-in-order-contracts-and-the-block-that-calls-them.md) | | **Investment case** | The roadmap's cost set out the way a finance ministry reads it, in four sheets: by horizon, wave and component with a low and a high estimate; by domain; by source of funds; and the expected returns. | [6.4](/experience-digital-transformation/roadmap/module-6-from-a-proven-foundation-to-a-national-roadmap/6.4-the-investment-case-your-finance-ministry-can-read.md) | | **Maturity table** | The table of the five domains, each with its stage, a key strength and a development priority, that shows the whole picture on one page. | [1.7](/experience-digital-transformation/roadmap/module-1-where-your-country-stands-and-what-to-build-first/1.7-score-each-domain-five-stages-and-one-table.md) | | **Once-only** | A person gives a piece of information to the government once; a service that needs it again takes it from the register that holds it, through the data exchange layer. | [5.3](/experience-digital-transformation/roadmap/module-5-join-the-blocks-and-prove-the-foundation/5.3-the-once-only-registration-from-beginning-to-end.md) | | **Phase** | PAERA's word for its steps of building: inception, high-priority use case implementation, initial transformation and mass-scale transformation. | [1.9](/experience-digital-transformation/roadmap/module-1-where-your-country-stands-and-what-to-build-first/1.9-what-comes-first-the-order-of-building.md), [6.3](/experience-digital-transformation/roadmap/module-6-from-a-proven-foundation-to-a-national-roadmap/6.3-the-roadmap-over-time-horizons-waves-and-tracks.md) | | **Progressa** | The fictional country on which every example of this guide is built. Its values are invented, and nothing in them is taken from any country's results. | the opening | | **Question bank** | Every question of the assessment, arranged by domain and sub-component, each with the evidence that answers it. | [1.4](/experience-digital-transformation/roadmap/module-1-where-your-country-stands-and-what-to-build-first/1.4-start-at-the-desk-a-first-assessment-from-public-sources-with-ai.md); the assessment toolkit | | **Response matrix** | The table in which every comment on the draft assessment and roadmap has its written answer and the decision on it. | [6.7](/experience-digital-transformation/roadmap/module-6-from-a-proven-foundation-to-a-national-roadmap/6.7-validate-revise-adopt.md) | | **Sectoral block** | A block that belongs to one sector and stands on the foundational blocks, such as a learner register and its registration service in education. | [1.8](/experience-digital-transformation/roadmap/module-1-where-your-country-stands-and-what-to-build-first/1.8-foundational-blocks-and-the-sectors-own.md) | | **Specimen** | A configuration file written for Progressa in a specification's terms and marked "specimen, not yet run". It is replaced by the file as built when its check has passed. | the build plan | | **Storyboard** | The steps of a demonstration in order, with what the viewer sees at each step and what counts as a pass. The recording follows it when the recording is made. | the build plan | | **Strategist register** | The way modules 1 and 6 are written: for the person who plans the work and makes the case to the minister. | the opening | | **Sub-component** | A part of a domain that is scored on its own, such as state registers within Digital Data. Each has a code, such as D2. | [1.7](/experience-digital-transformation/roadmap/module-1-where-your-country-stands-and-what-to-build-first/1.7-score-each-domain-five-stages-and-one-table.md); the assessment toolkit | | **Tiers of a load** | The five tiers through which a register is loaded, raw, bronze, staging, silver and gold, following Giga's published data flow, with quality checks that set a faulty row aside with its reason. | [3.2](/experience-digital-transformation/roadmap/module-3-the-registry-block/3.2-five-tiers-between-a-messy-file-and-a-trusted-record.md), [3.4](/experience-digital-transformation/roadmap/module-3-the-registry-block/3.4-quality-checks-that-stop-a-bad-row.md) | | **Track** | A line of work inside a wave of the roadmap: a governance track, and a track for each domain. | [6.3](/experience-digital-transformation/roadmap/module-6-from-a-proven-foundation-to-a-national-roadmap/6.3-the-roadmap-over-time-horizons-waves-and-tracks.md) | | **Wave** | The roadmap's own word for a part of the first horizon, each with its tracks and one visible service that shows the result. | [6.3](/experience-digital-transformation/roadmap/module-6-from-a-proven-foundation-to-a-national-roadmap/6.3-the-roadmap-over-time-horizons-waves-and-tracks.md) | | **Worked example** | What one step of the method produces, built for Progressa: one example for each of the nine steps, linked to one another. | the worked examples | ## The names used for Progressa Progressa is fictional, and so is every body named here. | Name | What it is | Its part in this guide | | --------------------------------- | ---------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | | **MoEYS** | Progressa's ministry of education | The sector whose service is built; it owns the school data | | **PLR** | Progressa Learner Registry | The learner register that module 3 sets up | | **PNIA** | Progressa National Identity Authority | The foundational identity that the registration service reuses in module 4 | | **The Payments block and PayPro** | The government's Payments block, and PayPro, Progressa's payment provider | Module 4 configures the Payments block; PayPro is one of the payment systems in the market and is reached through the block's payer bank | | **PDGA** | Progressa Digital Government Authority | It operates the data exchange federation and sets its technical rules | | **PNEA** | Progressa National Examination Authority | A member of the federation since the interoperability course; this course builds nothing on it | | **PDCA** | Progressa Digital Credentials Authority | Its credentials are built in the course on building-block services, on top of what this course proves | | **Linkup** | The X-Road federation that the interoperability course set up, release 7.7.0 | The data exchange layer, which GovStack calls the Information Mediator | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://experience-digital-transform.gitbook.io/experience-digital-transformation/roadmap/glossary.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.