> 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/education-digital-public-infrastructure-dpi-roadmap.md). # Education Digital Public Infrastructure (DPI) Roadmap This guide teaches a government team how to produce a national roadmap for digital public infrastructure. 45 videos in six modules · about 217 minutes of video · an AI usage tip on every page · nine worked examples · an assessment toolkit · self-paced · free and open This guide teaches a government team how to produce a national roadmap for digital public infrastructure, and it shows the first step of such a roadmap working in the education sector. Digital public infrastructure, DPI for short, is the set of shared digital systems that many services of a country stand on: digital identity, digital payments and the exchange of data between public bodies, with others emerging. The guide has six modules and 45 subtopics. Each subtopic is one short video with a written page and an AI usage tip. Module 1 teaches how to find out where the country stands and how to choose what to build first. Modules 2 to 5 build one education service, the registration of a learner, on four shared building blocks, and prove that the blocks work together. Module 6 teaches how to turn that proof into a national roadmap: priorities, sequence, investment, sourcing, governance, adoption and upkeep. Everything is shown on Progressa, a fictional country, and the method is written so that another sector can use it. ![F1. The structure of the guide: its modules and the two ways through them](https://2615884909-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR64GcRtMZNpXXmn3HRFt%2Fuploads%2FfLwit9QZpQ3CIC8gdgvI%2FF1_structure-6b5ac753.png?alt=media) ## Outline | Module | Topic | Persona | Videos | AI tips | Status | | ------------------------------------------------------------------------------------------------------------- | -------------------------------------------------- | ---------- | ------ | ------- | ------------ | | [1](/experience-digital-transformation/roadmap/module-1-where-your-country-stands-and-what-to-build-first.md) | Where your country stands, and what to build first | Strategist | 10 | 10 tips | Prompts live | | [2](/experience-digital-transformation/roadmap/module-2-the-registration-block.md) | The Registration block | Architect | 6 | 6 tips | Prompts live | | [3](/experience-digital-transformation/roadmap/module-3-the-registry-block.md) | The Registry block | Architect | 7 | 7 tips | Prompts live | | [4](/experience-digital-transformation/roadmap/module-4-identity-and-payments.md) | Identity and payments | Architect | 6 | 6 tips | Prompts live | | [5](/experience-digital-transformation/roadmap/module-5-join-the-blocks-and-prove-the-foundation.md) | Join the blocks and prove the foundation | Architect | 6 | 6 tips | Prompts live | | [6](/experience-digital-transformation/roadmap/module-6-from-a-proven-foundation-to-a-national-roadmap.md) | From a proven foundation to a national roadmap | Strategist | 10 | 10 tips | Prompts live | *Prompts live — every page of the module is written, with its prompt. In production — the module's pages are added as its scripts are written.* {% hint style="success" %} **How the course works.** **Watch** the video → **Read** its page, the video written out in full → **Prompt** with its AI usage tip on your own country → **Compare** your draft with the worked example for Progressa. The nine [worked examples](/experience-digital-transformation/roadmap/the-worked-examples.md), E1 to E9, follow the nine steps of the method and link to one another: findings, gaps, roadmap components, investment lines and comments, so that any budget line can be followed back to the evidence behind it. Work through them in order and you have the shape of your own country's roadmap, step by step. {% endhint %} | Module | What you can do afterwards | What is built | | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------- | | 1 | Commission and defend an assessment of the country's DPI; read its result on one table; say which blocks are foundational, which belong to the sector, and which service to build first | Nothing is built. The module uses the assessment toolkit. | | 2 | Set up a registration service from a description, with its checks, its officer's decision and its write to the register | Configurations R1 to R10 | | 3 | Set up a register from a schema file, load it through checked tiers, account for every load and open it to other services under rules | Configurations RG1 to RG13 | | 4 | Connect a service to the identity block and to the Payments block instead of building either again | Configurations I1 to I7 and P1 to P7 | | 5 | Say what must be in place before blocks can call each other, name the block that holds the sequence, run the once-only registration and read its evidence | Configurations X1 to X7 | | 6 | Rank the gaps, decide what to fund first, write the roadmap over time and its investment case, choose how to source each block, set up its governance, have it adopted and keep it healthy | Nothing is built. The module uses the worked examples. | ## Audience — and the path for your role | Persona | Who that is in practice | Modules | What you leave with | | -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Strategist** | Director of a digital agency, head of a sector's ICT unit, or the officer who prepares the minister's brief: the person who plans the work and makes the case for it | [1](/experience-digital-transformation/roadmap/module-1-where-your-country-stands-and-what-to-build-first.md), [6](/experience-digital-transformation/roadmap/module-6-from-a-proven-foundation-to-a-national-roadmap.md) | The case and the plan: an assessment of the country's DPI read on one maturity table, the foundational blocks told apart from the sector's own, the first service chosen; then the ranked gaps, what to fund first, the roadmap over time with its investment case, its sourcing and its governance, and the route to its adoption and upkeep. | | **Architect** | The technical lead of a sector ICT unit or a digital agency: the team that sets the service up | [2](/experience-digital-transformation/roadmap/module-2-the-registration-block.md), [3](/experience-digital-transformation/roadmap/module-3-the-registry-block.md), [4](/experience-digital-transformation/roadmap/module-4-identity-and-payments.md), [5](/experience-digital-transformation/roadmap/module-5-join-the-blocks-and-prove-the-foundation.md) | The build: a registration service and a learner register set up from descriptions, connected to identity and payments through the data exchange layer instead of building either again, and one once-only registration run from beginning to end and read from its evidence. | In both, the listener is the person who builds the case upward, not the minister. A Strategist who follows only modules 1 and 6 gets the whole method; an Architect who follows only 2 to 5 gets the whole build. ### Two ways through | Way | Modules | What it gives | | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **The method alone** | [1](/experience-digital-transformation/roadmap/module-1-where-your-country-stands-and-what-to-build-first.md), [6](/experience-digital-transformation/roadmap/module-6-from-a-proven-foundation-to-a-national-roadmap.md) | A team that wants the roadmap method follows modules 1 and 6: the nine steps, from a desk assessment of what the country has to a roadmap that an authority adopts. | | **The build** | [2](/experience-digital-transformation/roadmap/module-2-the-registration-block.md), [3](/experience-digital-transformation/roadmap/module-3-the-registry-block.md), [4](/experience-digital-transformation/roadmap/module-4-identity-and-payments.md), [5](/experience-digital-transformation/roadmap/module-5-join-the-blocks-and-prove-the-foundation.md) | A team that wants the build follows modules 2 to 5: one registration service and one learner register, connected to identity and payments through the data exchange layer, and proved by checks. | The order of the modules follows the order in which a country that starts from little would work. It first assesses where it stands and picks one priority service. It then builds that service on the foundational blocks and proves it. With that proof it writes the full roadmap, with its costs and its governance, and has it adopted. ## All videos Core marks the content without which the method cannot be followed from assessment to roadmap, or the build from its first configuration to its proof. Supplementary marks a video that deepens a core one and can be left out without losing the thread.
Module 1 — Where your country stands, and what to build first | # | Video | Class | Demonstration | Page | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------ | ----- | ------------- | --------- | | [1.1](/experience-digital-transformation/roadmap/module-1-where-your-country-stands-and-what-to-build-first/1.1-what-makes-infrastructure-foundational.md) | What makes infrastructure foundational | Core | — | Page live | | [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) | The five domains, as a map | Core | — | Page live | | [1.3](/experience-digital-transformation/roadmap/module-1-where-your-country-stands-and-what-to-build-first/1.3-the-roadmap-method-in-nine-steps-who-does-what.md) | The roadmap method in nine steps: who does what | Core | — | Page live | | [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) | Start at the desk: a first assessment from public sources, with AI | Core | Yes | Page live | | [1.5](/experience-digital-transformation/roadmap/module-1-where-your-country-stands-and-what-to-build-first/1.5-ask-the-people-who-run-the-systems-the-five-questionnaires.md) | Ask the people who run the systems: the five questionnaires | Core | — | Page live | | [1.6](/experience-digital-transformation/roadmap/module-1-where-your-country-stands-and-what-to-build-first/1.6-verify-before-you-score.md) | Verify before you score | Core | — | Page live | | [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) | Score each domain: five stages and one table | Core | Yes | Page live | | [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) | Foundational blocks and the sector's own | Core | — | Page live | | [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) | What comes first: the order of building | Core | — | Page live | | [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) | The first proof for education: one service on four blocks | Core | — | Page live |
Module 2 — The Registration block | # | Video | Class | Demonstration | Page | | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ | ------------- | ------------- | --------- | | [2.1](/experience-digital-transformation/roadmap/module-2-the-registration-block/2.1-what-the-registration-block-does.md) | What the Registration block does | Core | — | Page live | | [2.2](/experience-digital-transformation/roadmap/module-2-the-registration-block/2.2-the-published-specification-and-how-to-judge-a-product-against-it.md) | The published specification, and how to judge a product against it | Supplementary | — | Page live | | [2.3](/experience-digital-transformation/roadmap/module-2-the-registration-block/2.3-generating-the-registration-service.md) | Generating the registration service | Core | Yes | Page live | | [2.4](/experience-digital-transformation/roadmap/module-2-the-registration-block/2.4-checks-before-the-officer-decides.md) | Checks before the officer decides | Core | Yes | Page live | | [2.5](/experience-digital-transformation/roadmap/module-2-the-registration-block/2.5-the-officer-decides-and-the-record-is-written.md) | The officer decides, and the record is written | Core | Yes | Page live | | [2.6](/experience-digital-transformation/roadmap/module-2-the-registration-block/2.6-the-whole-service-as-a-description-you-can-move.md) | The whole service as a description you can move | Supplementary | Yes | Page live |
Module 3 — The Registry block | # | Video | Class | Demonstration | Page | | ----------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- | ------------- | ------------- | --------- | | [3.1](/experience-digital-transformation/roadmap/module-3-the-registry-block/3.1-what-a-register-is-for-one-authoritative-record.md) | What a register is for: one authoritative record | Core | — | Page live | | [3.2](/experience-digital-transformation/roadmap/module-3-the-registry-block/3.2-five-tiers-between-a-messy-file-and-a-trusted-record.md) | Five tiers between a messy file and a trusted record | Core | Yes | Page live | | [3.3](/experience-digital-transformation/roadmap/module-3-the-registry-block/3.3-generating-the-registers-schema.md) | Generating the register's schema | Core | Yes | Page live | | [3.4](/experience-digital-transformation/roadmap/module-3-the-registry-block/3.4-quality-checks-that-stop-a-bad-row.md) | Quality checks that stop a bad row | Core | Yes | Page live | | [3.5](/experience-digital-transformation/roadmap/module-3-the-registry-block/3.5-a-published-pattern-followed-in-the-open.md) | A published pattern, followed in the open | Supplementary | — | Page live | | [3.6](/experience-digital-transformation/roadmap/module-3-the-registry-block/3.6-account-for-every-load.md) | Account for every load | Core | Yes | Page live | | [3.7](/experience-digital-transformation/roadmap/module-3-the-registry-block/3.7-the-register-as-a-service-others-can-use.md) | The register as a service others can use | Core | Yes | Page live |
Module 4 — Identity and payments | # | Video | Class | Demonstration | Page | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | ----- | ------------- | --------- | | [4.1](/experience-digital-transformation/roadmap/module-4-identity-and-payments/4.1-why-identity-is-built-once.md) | Why identity is built once | Core | — | Page live | | [4.2](/experience-digital-transformation/roadmap/module-4-identity-and-payments/4.2-the-published-identity-block-and-what-the-identity-authority-offers-today.md) | The published Identity block, and what the identity authority offers today | Core | — | Page live | | [4.3](/experience-digital-transformation/roadmap/module-4-identity-and-payments/4.3-generating-the-identity-connection.md) | Generating the identity connection | Core | Yes | Page live | | [4.4](/experience-digital-transformation/roadmap/module-4-identity-and-payments/4.4-the-payments-block-and-the-payment-systems-behind-it.md) | The Payments block and the payment systems behind it | Core | — | Page live | | [4.5](/experience-digital-transformation/roadmap/module-4-identity-and-payments/4.5-generating-the-payment-connection.md) | Generating the payment connection | Core | Yes | Page live | | [4.6](/experience-digital-transformation/roadmap/module-4-identity-and-payments/4.6-reuse-is-the-return-on-planning.md) | Reuse is the return on planning | Core | — | Page live |
Module 5 — Join the blocks and prove the foundation | # | Video | Class | Demonstration | Page | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------- | ------------- | ------------- | --------- | | [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) | What must be in place before the blocks can call each other | Core | Yes | Page live | | [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) | Who puts the steps in order: contracts, and the block that calls them | Core | — | Page live | | [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) | The once-only registration, from beginning to end | Core | Yes | Page live | | [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 acceptance checks: from "set up" to "proven" | Core | Yes | Page live | | [5.5](/experience-digital-transformation/roadmap/module-5-join-the-blocks-and-prove-the-foundation/5.5-reading-the-evidence-of-a-call.md) | Reading the evidence of a call | Supplementary | Yes | Page live | | [5.6](/experience-digital-transformation/roadmap/module-5-join-the-blocks-and-prove-the-foundation/5.6-what-the-next-services-can-now-use.md) | What the next services can now use | Core | — | Page live |
Module 6 — From a proven foundation to a national roadmap | # | Video | Class | Demonstration | Page | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------- | ----- | ------------- | --------- | | [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) | From findings to priorities: the gap register | Core | — | Page live | | [6.2](/experience-digital-transformation/roadmap/module-6-from-a-proven-foundation-to-a-national-roadmap/6.2-what-to-fund-first-cost-against-reuse.md) | What to fund first: cost against reuse | Core | — | Page live | | [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) | The roadmap over time: horizons, waves and tracks | Core | — | Page live | | [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) | The investment case your finance ministry can read | Core | — | Page live | | [6.5](/experience-digital-transformation/roadmap/module-6-from-a-proven-foundation-to-a-national-roadmap/6.5-sourcing-each-block-without-lock-in.md) | Sourcing each block without lock-in | Core | — | Page live | | [6.6](/experience-digital-transformation/roadmap/module-6-from-a-proven-foundation-to-a-national-roadmap/6.6-governance-that-keeps-shared-blocks-shared.md) | Governance that keeps shared blocks shared | Core | — | Page live | | [6.7](/experience-digital-transformation/roadmap/module-6-from-a-proven-foundation-to-a-national-roadmap/6.7-validate-revise-adopt.md) | Validate, revise, adopt | Core | — | Page live | | [6.8](/experience-digital-transformation/roadmap/module-6-from-a-proven-foundation-to-a-national-roadmap/6.8-keep-the-foundation-healthy-and-safe.md) | Keep the foundation healthy and safe | Core | — | Page live | | [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) | The AI plays, step by step | Core | Yes | Page live | | [6.10](/experience-digital-transformation/roadmap/module-6-from-a-proven-foundation-to-a-national-roadmap/6.10-carry-the-method-to-another-sector.md) | Carry the method to another sector | Core | — | Page live |
## How to use this guide Each subtopic page holds the content of its video written out in full, its worked example, its AI usage tip with the prompt ready to copy, and its sources with their links. A page can be read on its own, like the video it goes with. Every AI usage tip has four parts: the problem it solves, the prompt, what goes in and what comes out, and a safeguard. The assistant drafts and a person decides: no tip hands a decision over. Every worked example is built for Progressa. Its values are invented for Progressa, and nothing in it is taken from the results of any country. Figures from public sources are given with their source, their year and their page. Before your first prompt, read [Working with AI](https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-enterprise-architecture-gea/developing-a-gov-enterprise-architecture-gea/start-here/working-with-ai-the-ground-rules) and [How to use the plays](https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-enterprise-architecture-gea/developing-a-gov-enterprise-architecture-gea/start-here/how-to-use-the-plays): they hold the ground rules for using an assistant on government material, and they apply to every course in this knowledge base. ## Prerequisites [**Developing a Gov Enterprise Architecture (GEA)**](https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-enterprise-architecture-gea/developing-a-gov-enterprise-architecture-gea) **and** [**Building a Government Interoperability Framework (GIF)**](https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-interoperability-framework-gif/building-a-government-interoperability-framework-gif) **come before this course, but neither is a prerequisite.** Modules 1 and 6 stand on their own. Modules 2 to 5 assume a data exchange layer is already running, the one the interoperability course sets up; on Progressa it is Linkup, already in place, so you can follow them without having taken that course. **What you do need:** | | | | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **A real subject** | A country, or a sector within one, whose digital public infrastructure you are asked to assess or plan. The AI usage tips act on your context, not on a case study. No subject to hand? Follow everything on [Progressa](https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-enterprise-architecture-gea/developing-a-gov-enterprise-architecture-gea/start-here/progressa-the-demonstration-country) instead. | | **Enough access to describe it** | The desk assessment starts from the country's public record alone ([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 five questionnaires need the time of the people who run its systems ([1.5](/experience-digital-transformation/roadmap/module-1-where-your-country-stands-and-what-to-build-first/1.5-ask-the-people-who-run-the-systems-the-five-questionnaires.md)). | | **An AI assistant** | Any general assistant — Claude, ChatGPT, Gemini. A free account is enough. Nothing to install. | | **Nothing to run** | No code is written. Modules 2 to 5 show each configuration as a specimen until it has been built and checked; [the build plan](/experience-digital-transformation/roadmap/the-build-plan.md) says which. | | **About fifteen minutes, once** | The first pages of [Start here](https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-enterprise-architecture-gea/developing-a-gov-enterprise-architecture-gea/start-here) cover how to work with the prompts and the ground rules for using an assistant on government material. Read them before your first prompt. | Time: each subtopic is a video of about five minutes, its page, and an AI usage tip of ten to fifteen minutes. A module is an afternoon. The whole course is roughly two working days spread over as long as you like.

🛡️

Working with AIWhat an assistant is good for, the four ways it misleads you, and the safeguards. Read once; applies to all four Knowledge Products.https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-enterprise-architecture-gea/developing-a-gov-enterprise-architecture-gea/start-here/working-with-ai-the-ground-rules

🏁

Module 1 — Where your country stands, and what to build first10 videos for the Strategist: the five domains, the nine steps, the assessment and its scoring, and the first proof chosen.Module 1 — Where your country stands, and what to build first

📒

The worked examplesE1 to E9, one for each step of the method, built for Progressa and linked to one another: the shape of the roadmap you will write.The worked examples

🧰

The assessment toolkitThe question bank, the five questionnaires with their guides, the scoring criteria and the templates for verification.The assessment toolkit
## Reference pages
The nine stepsEach step of the method with its roles, inputs, outputs, tools or templates, decision point and validation.The nine steps
The assessment toolkitThe question bank, the five questionnaires with their guides, the scoring criteria and the templates for verification.The assessment toolkit
The worked examplesOne example for each of the nine steps, built for Progressa and linked to one another.The worked examples
The build planWhat the build will contain: every configuration of modules 2 to 5, its check, and how it is taught until it is built.The build plan
Frameworks and standardsThe public frameworks and standards this guide cites, in five kinds, each with its address.Frameworks and standards
GlossaryThe terms this guide uses, and the names used for Progressa.Glossary
FiguresThe sixteen figures of the guide.Figures
## Where this sits This course is the third of four Knowledge Products, after [Developing a Gov Enterprise Architecture (GEA)](https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-enterprise-architecture-gea/developing-a-gov-enterprise-architecture-gea) and [Building a Government Interoperability Framework (GIF)](https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-interoperability-framework-gif/building-a-government-interoperability-framework-gif); a fourth, on building-block services, is planned. | Part | What it takes | What it gives | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [Developing a Gov Enterprise Architecture (GEA)](https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-enterprise-architecture-gea/developing-a-gov-enterprise-architecture-gea) and [Building a Government Interoperability Framework (GIF)](https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-interoperability-framework-gif/building-a-government-interoperability-framework-gif), before this course | — | The enterprise architecture and its target state; the data exchange layer and the rules of interoperability | | Module 1 | Public information about the country, and the time of the people who run its systems | The map of the five domains, the maturity table, the list of foundational and sectoral blocks, the order of building, the first proof chosen | | Modules 2 to 5 | The first proof chosen, and the foundations the country already has | A registration service, a learner register, connections to identity and payments, and one proven run from beginning to end | | Module 6 | The findings of the assessment, and the proof | The gap register, the order of funding, the roadmap over time, the investment case, the choice of sourcing, the governance, the adopted roadmap and its upkeep | | The course after this one | The blocks this course has proven | Further education services built over them | All the courses in this knowledge base use [Progressa](https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-enterprise-architecture-gea/developing-a-gov-enterprise-architecture-gea/start-here/progressa-the-demonstration-country) as the one worked example and share one set of [ground rules](https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-enterprise-architecture-gea/developing-a-gov-enterprise-architecture-gea/start-here/working-with-ai-the-ground-rules). {% hint style="info" %} **Use this knowledge base from your AI assistant.** Every page is also published as plain Markdown, and the knowledge base exposes an `llms.txt` and an MCP endpoint at `/~gitbook/mcp`. Point Claude, ChatGPT or another assistant at the knowledge base and ask it to *run the AI usage tip of 1.4 with the following context* — the knowledge base becomes the tool's reference, not just yours. {% endhint %} --- # 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/education-digital-public-infrastructure-dpi-roadmap.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.