> 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/gif/module-1-why-interoperability-and-the-four-layers.md). # Module 1 — Why interoperability and the four layers Seven videos for the Strategist making the case: why interoperability is built rather than bought, the four layers it fails at, the once-only promise it exists for. **Persona:** S (Strategist) — national interoperability authority, ministry CIO, Ministry of Justice sponsor, or development-partner lead. **You leave with:** B1, B2, B3, B4, B5, B6, B7, filed in your framework workbook — the foundation. Runtime \~31 minutes across 7 videos. Seven videos for the Strategist making the case: why interoperability is built rather than bought, the four layers it fails at, the once-only promise it exists for, and the three foundation artefacts — the Strategic Foundation Document, the Use-Case Catalogue and the stakeholder map — every later module reads. ## Subtopics | # | Subtopic | Single message | Your play | Kit skill | | ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | ----------------------- | | [1.1](/experience-digital-transformation/gif/module-1-why-interoperability-and-the-four-layers/1.1-why-interoperability-cant-be-bought-only-built.md) | Why interoperability can't be bought, only built | Procurement rules can require interoperability. Only whole-of-government planning delivers it — and once the framework exists, procurement is how you enforce it. | 🔍 B1 | — | | [1.2](/experience-digital-transformation/gif/module-1-why-interoperability-and-the-four-layers/1.2-the-four-layers-of-interoperability.md) | The four layers of interoperability | Interoperability fails at whichever of the four layers — Technical, Semantic, Organisational, Legal — you skip. The framework makes you address all four on purpose. | 🔍 B2 | — | | [1.3](/experience-digital-transformation/gif/module-1-why-interoperability-and-the-four-layers/1.3-the-once-only-promise.md) | The once-only promise | Once-only — the state never asks a citizen for the same data twice — is the outcome interoperability is for, and the test of whether it works. | 🔍 B3 | — | | [1.4](/experience-digital-transformation/gif/module-1-why-interoperability-and-the-four-layers/1.4-the-strategic-foundation-document.md) | The Strategic Foundation Document | Name the mandate, the scope and the principles once, in writing, before any wiring — it is what every later decision is checked against. | ✍️ B4 | — | | [1.5](/experience-digital-transformation/gif/module-1-why-interoperability-and-the-four-layers/1.5-the-use-case-catalogue.md) | The Use-Case Catalogue | Turn your integration map into a ranked catalogue of exchanges worth building — and start with the one that removes the most burden from citizens. | ✍️ B5 | — | | [1.6](/experience-digital-transformation/gif/module-1-why-interoperability-and-the-four-layers/1.6-mapping-your-stakeholders.md) | Mapping your stakeholders | Sort the agencies into Champions, Early Adopters and Observers, and you know who to onboard first and who to convince. | 🔍 B6 | — | | [1.7](/experience-digital-transformation/gif/module-1-why-interoperability-and-the-four-layers/1.7-what-the-world-already-proved.md) | What the world already proved | Estonia's X-Road and the EU's once-only systems show the pattern; the education semantic standards show the vocabularies you will reuse rather than invent. | 🔍 B7 | `paera-reference-check` | ## How the plays chain in this module ```mermaid flowchart TD A0["A0 Country context pack\n(Play 0 + supplement)"] B1["B1 Procured-vs-planned diagnostic\n(1.1)"] B2["B2 Four-layer exchange map\n(1.2)"] B3["B3 Highest-value once-only exchange\n(1.3)"] B4["B4 Strategic Foundation Document\n(1.4)"] B5["B5 Use-Case Catalogue\n(1.5)"] B6["B6 Stakeholder tier map\n(1.6)"] B7["B7 Standards-to-reuse shortlist\n(1.7)"] M2out["Module 2"] M3out["Module 3"] M4out["Module 4"] M5out["Module 5"] HOME["The country storyboard\n(course home)"] A0 --> B1 B1 --> B4 A0 --> B2 A0 --> B3 B3 --> B4 B3 --> B5 A0 --> B4 B4 --> M2out B4 --> M3out A0 --> B5 B5 --> M2out B5 --> M4out B5 --> M5out B5 --> HOME A0 --> B6 B6 --> M3out B6 --> M4out B6 --> M5out A0 --> B7 B7 --> M4out ``` The full chain, including where these artefacts come from and go next, is on [Your framework workbook](/experience-digital-transformation/gif/your-framework-workbook.md). {% hint style="info" %} **Before you start.** Every play asks you to paste country context. Build it once with [Play 0](https://experience-digital-transform.gitbook.io/experience-digital-transformation/government-enterprise-architecture-gea/developing-a-gov-enterprise-architecture-gea/start-here/play-0-build-your-country-context) — that is **A0** — and add the three interoperability sections from the [Play 0 supplement](/experience-digital-transformation/gif/play-0-supplement.md). No country to hand? Run them 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), the fictional demonstration country; for Modules 4 and 5 the [build pack](/experience-digital-transformation/gif/the-build-pack.md) is Progressa's finished output. {% endhint %} {% hint style="info" %} New to the plays? Read [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) and [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) first — part of the about fifteen minutes of Start here, and they apply to every module of every Knowledge Product. {% 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/gif/module-1-why-interoperability-and-the-four-layers.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.