> 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/figures.md). # Figures The sixteen figures of the guide, with the subtopics that use them. The figures are made for this written guide; the slides of the videos stay text-only. A figure marked "from the specification" is drawn from the published specifications and corrected when the configuration is built. A figure drawn from a worked example is illustrative, like the example. | Figure | What it shows | Used by | State | | ------ | ------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----- | | F1 | The structure of the guide: its modules and the two ways through them | The opening | Drawn | | F2 | The five domains on one page | [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) | Drawn | | F3 | The nine steps with their roles and outputs | [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) | Drawn | | F4 | The maturity table of Progressa's five domains, marked illustrative | [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) | Drawn | | F5 | The order of building: PAERA's four phases and the blocks of each | [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) | Drawn | | F6 | The first proof: four blocks on the data exchange layer | [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) and [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) | Drawn | | F7 | The workflow of the registration service | [2.5](/experience-digital-transformation/roadmap/module-2-the-registration-block/2.5-the-officer-decides-and-the-record-is-written.md) | Drawn | | F8 | The data model of the learner register | [3.3](/experience-digital-transformation/roadmap/module-3-the-registry-block/3.3-generating-the-registers-schema.md) | Drawn | | F9 | The five tiers of the load | [3.2](/experience-digital-transformation/roadmap/module-3-the-registry-block/3.2-five-tiers-between-a-messy-file-and-a-trusted-record.md) | Drawn | | F10 | The sign-in between the service, the learner and the identity block | [4.3](/experience-digital-transformation/roadmap/module-4-identity-and-payments/4.3-generating-the-identity-connection.md) | Drawn | | F11 | The path of a payment: programme account, Payments block, payer bank, payment system | [4.4](/experience-digital-transformation/roadmap/module-4-identity-and-payments/4.4-the-payments-block-and-the-payment-systems-behind-it.md) and [4.5](/experience-digital-transformation/roadmap/module-4-identity-and-payments/4.5-generating-the-payment-connection.md) | Drawn | | F12 | The once-only registration as a sequence of calls | [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) and [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) | Drawn | | F13 | The roadmap over time: horizons and waves | [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) | Drawn | | F14 | The matrix of dependencies | [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) | Drawn | | F15 | The investment case: its four sheets as tables | [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) | Drawn | | F16 | The governance structure on one page | [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) | Drawn | ## F1. The structure of the guide: its modules and the two ways through them ![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) ## F2. The five domains on one page ![F2. The five domains on one page](https://2615884909-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR64GcRtMZNpXXmn3HRFt%2Fuploads%2F74JjgxpKTwjx2zhIRnFO%2FF2_five-domains-a797e57e.png?alt=media) ## F3. The nine steps with their roles and outputs ![F3. The nine steps with their roles and outputs](https://2615884909-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR64GcRtMZNpXXmn3HRFt%2Fuploads%2FRHiJgWFGO1yLjUWYSwd2%2FF3_nine-steps-529953da.png?alt=media) ## F4. The maturity table of Progressa's five domains, marked illustrative ![F4. The maturity table of Progressa's five domains, marked illustrative](https://2615884909-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR64GcRtMZNpXXmn3HRFt%2Fuploads%2FI5NGYTrij3cWQ4VkDkEf%2FF4_maturity-table-71103d17.png?alt=media) ## F5. The order of building: PAERA's four phases and the blocks of each ![F5. The order of building: PAERA's four phases and the blocks of each](https://2615884909-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR64GcRtMZNpXXmn3HRFt%2Fuploads%2Fvu8Y9tgNN5bf8D7IQoh4%2FF5_order-of-building-3db84e30.png?alt=media) ## F6. The first proof: four blocks on the data exchange layer ![F6. The first proof: four blocks on the data exchange layer](https://2615884909-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR64GcRtMZNpXXmn3HRFt%2Fuploads%2Fsz05wImINjthI5XJm1oy%2FF6_first-proof-3db9ba62.png?alt=media) ## F7. The workflow of the registration service ![F7. The workflow of the registration service](https://2615884909-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR64GcRtMZNpXXmn3HRFt%2Fuploads%2FqaDrNSvrqhe95C7t4h3x%2FF7_registration-workflow-c8d1a700.png?alt=media) ## F8. The data model of the learner register ![F8. The data model of the learner register](https://2615884909-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR64GcRtMZNpXXmn3HRFt%2Fuploads%2FyNVdx6r48qL2EKH5PlE6%2FF8_learner-register-model-21559a8b.png?alt=media) ## F9. The five tiers of the load ![F9. The five tiers of the load](https://2615884909-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR64GcRtMZNpXXmn3HRFt%2Fuploads%2F669GPNzJcUqNmER8NpbI%2FF9_five-tiers-8c20e9c8.png?alt=media) ## F10. The sign-in between the service, the learner and the identity block ![F10. The sign-in between the service, the learner and the identity block](https://2615884909-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR64GcRtMZNpXXmn3HRFt%2Fuploads%2FnDnJf2RwoV9IGyuzQLBn%2FF10_sign-in-32fc4ed1.png?alt=media) ## F11. The path of a payment: programme account, Payments block, payer bank, payment system ![F11. The path of a payment: programme account, Payments block, payer bank, payment system](https://2615884909-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR64GcRtMZNpXXmn3HRFt%2Fuploads%2FCWvrdhMgaTcNAulp4N8J%2FF11_payment-path-40fb3826.png?alt=media) ## F12. The once-only registration as a sequence of calls ![F12. The once-only registration as a sequence of calls](https://2615884909-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR64GcRtMZNpXXmn3HRFt%2Fuploads%2Fp4ORnWKAHqLfM2TpcMmp%2FF12_once-only-sequence-c9656742.png?alt=media) ## F13. The roadmap over time: horizons and waves ![F13. The roadmap over time: horizons and waves](https://2615884909-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR64GcRtMZNpXXmn3HRFt%2Fuploads%2FHRlkPjQKF60P7uWGIBzz%2FF13_roadmap-over-time-8756a9d9.png?alt=media) ## F14. The matrix of dependencies ![F14. The matrix of dependencies](https://2615884909-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR64GcRtMZNpXXmn3HRFt%2Fuploads%2FdtmuI4Ud2nQBPNeEy0J6%2FF14_dependency-matrix-aa7d7f32.png?alt=media) ## F15. The investment case: its four sheets as tables ![F15. The investment case: its four sheets as tables](https://2615884909-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR64GcRtMZNpXXmn3HRFt%2Fuploads%2FTj4TvtxdzCyEbq4AlDLB%2FF15_investment-case-38d08a16.png?alt=media) ## F16. The governance structure on one page ![F16. The governance structure on one page](https://2615884909-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FR64GcRtMZNpXXmn3HRFt%2Fuploads%2F16YUvdYBOoZAxeV57wR8%2FF16_governance-cbaa3dd1.png?alt=media) --- # 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/figures.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.