> 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/building-block/figures.md). # Figures The 14 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 that shows a document of the worked example is drawn when that document exists. Every figure is illustrative, like the example. | Figure | What it shows | Used by | State | | ------ | ------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----- | | F1 | The structure of this course: its modules and the two ways through them | The guide's opening | Drawn | | F2 | The three places an agreed service gets lost | [1.1](/experience-digital-transformation/building-block/module-1-why-digital-services-go-wrong-and-the-method-that-prevents-it/1.1-where-an-agreed-service-gets-lost.md) | Drawn | | F3 | The twelve documents in order, with where the manager stands | [1.4](/experience-digital-transformation/building-block/module-1-why-digital-services-go-wrong-and-the-method-that-prevents-it/1.4-twelve-documents-from-the-request-to-the-running-service.md) and [6.1](/experience-digital-transformation/building-block/module-6-run-the-method-in-your-administration/6.1-what-to-require-from-a-supplier.md) | Drawn | | F4 | Who writes, who checks, who accepts | [1.5](/experience-digital-transformation/building-block/module-1-why-digital-services-go-wrong-and-the-method-that-prevents-it/1.5-who-writes-who-checks-who-accepts.md) and [6.4](/experience-digital-transformation/building-block/module-6-run-the-method-in-your-administration/6.4-the-ai-assistant-at-every-step-and-the-person-who-rules.md) | Drawn | | F5 | The sector's catalogue: many services resting on the same blocks | [2.1](/experience-digital-transformation/building-block/module-2-break-the-service-down-before-you-design-it/2.1-one-catalogue-of-the-sectors-services-and-the-blocks-they-share.md) and [6.5](/experience-digital-transformation/building-block/module-6-run-the-method-in-your-administration/6.5-the-next-service-on-the-same-foundation.md) | Drawn | | F6 | The records of the service and whose each one is, as a data model | [2.3](/experience-digital-transformation/building-block/module-2-break-the-service-down-before-you-design-it/2.3-the-records-the-service-keeps-and-whose-each-one-is.md) | Drawn | | F7 | The architecture: two applications, the shared blocks and the crossing | [2.6](/experience-digital-transformation/building-block/module-2-break-the-service-down-before-you-design-it/2.6-what-the-service-is-built-on-and-what-crosses-its-boundary.md), [5.4](/experience-digital-transformation/building-block/module-5-generate-the-service-on-a-low-code-platform-and-connect-the-blocks/5.4-identity-and-registries-use-the-block-do-not-rebuild-it.md), [5.5](/experience-digital-transformation/building-block/module-5-generate-the-service-on-a-low-code-platform-and-connect-the-blocks/5.5-the-services-contract-with-the-registration-block-and-its-data-interface.md) and [5.6](/experience-digital-transformation/building-block/module-5-generate-the-service-on-a-low-code-platform-and-connect-the-blocks/5.6-payments-and-information-mediation-as-named-crossings.md) | Drawn | | F8 | One goal as a story, with its failures and their endings | [3.1](/experience-digital-transformation/building-block/module-3-design-one-service-as-a-story-your-officials-can-check/3.1-one-goal-written-as-a-story-a-builder-can-follow.md) and [3.2](/experience-digital-transformation/building-block/module-3-design-one-service-as-a-story-your-officials-can-check/3.2-every-way-it-can-go-wrong-written-down.md) | Drawn | | F9 | A screen with the source of every value | [3.3](/experience-digital-transformation/building-block/module-3-design-one-service-as-a-story-your-officials-can-check/3.3-screens-worked-out-from-the-story-every-value-with-its-source.md) | Drawn | | F10 | The four questions of the interaction design | [4.1](/experience-digital-transformation/building-block/module-4-settle-the-whole-application-once-then-describe-it-for-the-machine/4.1-four-questions-decided-once-for-every-screen.md) | Drawn | | F11 | The service workflow of the licence: states, moves and who may make each | [4.3](/experience-digital-transformation/building-block/module-4-settle-the-whole-application-once-then-describe-it-for-the-machine/4.3-the-service-workflow-states-moves-and-who-may-make-each.md) | Drawn | | F12 | From one file to a running application, with the refusal before it | [4.4](/experience-digital-transformation/building-block/module-4-settle-the-whole-application-once-then-describe-it-for-the-machine/4.4-one-file-a-program-reads-the-application-model.md), [4.6](/experience-digital-transformation/building-block/module-4-settle-the-whole-application-once-then-describe-it-for-the-machine/4.6-refused-not-worked-around.md) and [5.1](/experience-digital-transformation/building-block/module-5-generate-the-service-on-a-low-code-platform-and-connect-the-blocks/5.1-from-one-file-to-a-running-application.md) | Drawn | | F13 | Correct up, generate down | [5.2](/experience-digital-transformation/building-block/module-5-generate-the-service-on-a-low-code-platform-and-connect-the-blocks/5.2-nothing-generated-is-edited-by-hand.md) and [6.2](/experience-digital-transformation/building-block/module-6-run-the-method-in-your-administration/6.2-when-something-changes-correct-the-document-that-owns-the-fact.md) | Drawn | | F14 | The data interface between the two bodies across the data exchange | [5.5](/experience-digital-transformation/building-block/module-5-generate-the-service-on-a-low-code-platform-and-connect-the-blocks/5.5-the-services-contract-with-the-registration-block-and-its-data-interface.md) | Drawn | ## F1. The structure of this course: its modules and the two ways through them ![F1. The structure of this course: its modules and the two ways through them](https://3194217719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrVBocIKfigDPd5E7eF77%2Fuploads%2FMpBrL5IHxrF2JjssG4n9%2FF1_structure-b86e2ea0.png?alt=media) ## F2. The three places an agreed service gets lost ![F2. The three places an agreed service gets lost](https://3194217719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrVBocIKfigDPd5E7eF77%2Fuploads%2Fx5Vfm12rnDXvSzS8jEoc%2FF2_three-places-f527cecd.png?alt=media) ## F3. The twelve documents in order, with where the manager stands ![F3. The twelve documents in order, with where the manager stands](https://3194217719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrVBocIKfigDPd5E7eF77%2Fuploads%2FrTaZ2ilh5nLpkmz9JNbr%2FF3_twelve-documents-4b243c86.png?alt=media) ## F4. Who writes, who checks, who accepts ![F4. Who writes, who checks, who accepts](https://3194217719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrVBocIKfigDPd5E7eF77%2Fuploads%2FDYRvIxYJytSuY9WLcgEe%2FF4_who-writes-checks-accepts-1f23ab37.png?alt=media) ## F5. The sector's catalogue: many services resting on the same blocks ![F5. The sector's catalogue: many services resting on the same blocks](https://3194217719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrVBocIKfigDPd5E7eF77%2Fuploads%2FTYCKgofIPUyhmPVWplEE%2FF5_sector-catalogue-20968c46.png?alt=media) ## F6. The records of the service and whose each one is, as a data model ![F6. The records of the service and whose each one is, as a data model](https://3194217719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrVBocIKfigDPd5E7eF77%2Fuploads%2F0uhjLZPDexwkbb4zrmFX%2FF6_records-and-keepers-e6e179a9.png?alt=media) ## F7. The architecture: two applications, the shared blocks and the crossing ![F7. The architecture: two applications, the shared blocks and the crossing](https://3194217719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrVBocIKfigDPd5E7eF77%2Fuploads%2FLt4iV6EaaaNwpHa3U8ad%2FF7_architecture-d7ac6551.png?alt=media) ## F8. One goal as a story, with its failures and their endings ![F8. One goal as a story, with its failures and their endings](https://3194217719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrVBocIKfigDPd5E7eF77%2Fuploads%2FIVSwxveHGCMHx2WHfEtC%2FF8_story-and-failures-f0bf26ee.png?alt=media) ## F9. A screen with the source of every value ![F9. A screen with the source of every value](https://3194217719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrVBocIKfigDPd5E7eF77%2Fuploads%2FcNDlTkeNMBJhFi0GGkB3%2FF9_screen-sources-7090456f.png?alt=media) ## F10. The four questions of the interaction design ![F10. The four questions of the interaction design](https://3194217719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrVBocIKfigDPd5E7eF77%2Fuploads%2F4kD0HOTh2L3nsOkMlDP3%2FF10_four-questions-08f01a7f.png?alt=media) ## F11. The service workflow of the licence: states, moves and who may make each ![F11. The service workflow of the licence: states, moves and who may make each](https://3194217719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrVBocIKfigDPd5E7eF77%2Fuploads%2F9n8nLrnYZO3MPhC6Z7sZ%2FF11_licence-workflow-d5489564.png?alt=media) ## F12. From one file to a running application, with the refusal before it ![F12. From one file to a running application, with the refusal before it](https://3194217719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrVBocIKfigDPd5E7eF77%2Fuploads%2FhcYaKlFbHMdvUwJtEc3o%2FF12_one-file-to-running-application-cec782e0.png?alt=media) ## F13. Correct up, generate down ![F13. Correct up, generate down](https://3194217719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrVBocIKfigDPd5E7eF77%2Fuploads%2FO6kyf0Tevv9GtGQCHBvC%2FF13_correct-up-generate-down-a80b1ff8.png?alt=media) ## F14. The data interface between the two bodies across the data exchange ![F14. The data interface between the two bodies across the data exchange](https://3194217719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrVBocIKfigDPd5E7eF77%2Fuploads%2FdnDxEGk1xSidfYKGOLeD%2FF14_data-interface-a0d971da.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/building-block/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.