> 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/your-framework-workbook.md).

# Your framework workbook

The artefacts the plays in this course produce, grouped by configuration layer — run the five modules and you hold your own framework's legal, organisational and technical configuration.

Each play produces one artefact. Run them in order and the artefacts feed each other. These artefacts are not briefing documents, as those of *Developing a Gov Enterprise Architecture (GEA)* were; they are the **configuration of your framework** — the decree is the legal configuration, the Governance Pack the organisational, the semantic map and service contracts the technical — and Module 5 stands them up as one running solution. This page is the map. If you have no country to hand, use Progressa: the [build pack](/experience-digital-transformation/gif/the-build-pack.md) is Progressa's finished configuration, and the worked examples on each play page show what each artefact looks like.

{% hint style="info" %}
Keep the artefacts in one folder, named as below. The **Consumes** and **Feeds** columns are the chain: every play names what it reads and what reads it, so you can start anywhere and see what you need first.
{% endhint %}

## A0 — the pack everything starts from

| Artefact      | What it is                                                                                                                           | Produced by                                                                                                                                                                                                                     | Feeds                        |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------- |
| **A0 §1–§7**  | Country context pack — landscape brief, programme list, ministry context, roles register, characteristics, sector bodies, legal list | [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) 🔍 | the whole chain below        |
| **A0 §8–§10** | The Play 0 supplement — the current exchange approach, the integration map, the data-protection law and DPA                          | [Play 0 supplement](/experience-digital-transformation/gif/play-0-supplement.md) 🔍                                                                                                                                             | 1.1, 1.2, 1.3, 1.5, 2.1, 4.8 |

## Hand-offs from Developing a Gov Enterprise Architecture (GEA)

If you ran [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), three of its artefacts enter the chain here; if not, the plays named build the equivalent.

| GEA artefact                               | Enters this course at                                                                                                                                                                                                                                                                                                                                                                                                  | If you do not have it                                                                                                                                                                                                                                                                                              |
| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **A0** country context pack                | [1.1](/experience-digital-transformation/gif/module-1-why-interoperability-and-the-four-layers/1.1-why-interoperability-cant-be-bought-only-built.md), [1.5](/experience-digital-transformation/gif/module-1-why-interoperability-and-the-four-layers/1.5-the-use-case-catalogue.md), [1.6](/experience-digital-transformation/gif/module-1-why-interoperability-and-the-four-layers/1.6-mapping-your-stakeholders.md) | run [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) and the [supplement](/experience-digital-transformation/gif/play-0-supplement.md) |
| **A7** Governance Board terms of reference | [3.1](/experience-digital-transformation/gif/module-3-governance-model-three-tiers-with-raci/3.1-why-a-bus-needs-an-owner.md) — the Operating Authority                                                                                                                                                                                                                                                                | 3.1 drafts the mandate from A0 §6                                                                                                                                                                                                                                                                                  |
| **A24** sourcing matrix                    | [4.3](/experience-digital-transformation/gif/module-4-architecture-and-technical-standards/4.3-adopt-the-standards-portfolio.md) — the standards portfolio                                                                                                                                                                                                                                                             | 4.3 assembles it from the published menu and 1.7's shortlist                                                                                                                                                                                                                                                       |

## The three configuration layers, and where they run

```mermaid
flowchart LR
    F["Module 1\nB1–B7 the foundation"] --> L["Module 2\nB8–B13 the decree\n(legal configuration)"]
    F --> O["Module 3\nB14–B19 the Governance Pack\n(organisational configuration)"]
    F --> T["Module 4\nB20–B27 semantic map, contracts,\nwiring (technical configuration)"]
    L --> R["Module 5\nB28–B34 the runnable slice"]
    O --> R
    T --> R
    R --> OPS["Module 5\nB35–B37 operate and extend"]
    R --> SB["B38 the storyboard\n(course home)"]
```

## Every artefact in this course

### Module 1 — Why interoperability and the four layers

*The foundation.*

| Artefact | What it is                       | Produced by                                                                                                                                              | Consumes      | Feeds                                    |
| -------- | -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | ---------------------------------------- |
| **B1**   | Procured-vs-planned diagnostic   | [1.1](/experience-digital-transformation/gif/module-1-why-interoperability-and-the-four-layers/1.1-why-interoperability-cant-be-bought-only-built.md) 🔍 | A0 §1, A0 §8  | 1.4                                      |
| **B2**   | Four-layer exchange map          | [1.2](/experience-digital-transformation/gif/module-1-why-interoperability-and-the-four-layers/1.2-the-four-layers-of-interoperability.md) 🔍            | A0 §1, A0 §9  | —                                        |
| **B3**   | Highest-value once-only exchange | [1.3](/experience-digital-transformation/gif/module-1-why-interoperability-and-the-four-layers/1.3-the-once-only-promise.md) 🔍                          | A0 §2, A0 §9  | 1.4, 1.5                                 |
| **B4**   | Strategic Foundation Document    | [1.4](/experience-digital-transformation/gif/module-1-why-interoperability-and-the-four-layers/1.4-the-strategic-foundation-document.md) ✍️              | B1, B3, A0 §7 | 2.2, 2.3, 3.1                            |
| **B5**   | Use-Case Catalogue               | [1.5](/experience-digital-transformation/gif/module-1-why-interoperability-and-the-four-layers/1.5-the-use-case-catalogue.md) ✍️                         | A0 §9, B3     | 2.4, 2.6, 4.2, 4.4, 4.8, 5.1, storyboard |
| **B6**   | Stakeholder tier map             | [1.6](/experience-digital-transformation/gif/module-1-why-interoperability-and-the-four-layers/1.6-mapping-your-stakeholders.md) 🔍                      | A0 §4, A0 §6  | 3.3, 3.4, 4.7, 5.1                       |
| **B7**   | Standards-to-reuse shortlist     | [1.7](/experience-digital-transformation/gif/module-1-why-interoperability-and-the-four-layers/1.7-what-the-world-already-proved.md) 🔍                  | A0 §1         | 4.3                                      |

### Module 2 — Legal framework — the Decree Drafting Kit

*The legal configuration — the decree.*

| Artefact | What it is                          | Produced by                                                                                                                                           | Consumes      | Feeds              |
| -------- | ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | ------------------ |
| **B8**   | Legal-readiness assessment          | [2.1](/experience-digital-transformation/gif/module-2-legal-framework-the-decree-drafting-kit/2.1-why-the-platform-needs-a-legal-mandate.md) 🔍       | A0 §7, A0 §10 | 2.2                |
| **B9**   | Decree outline (five components)    | [2.2](/experience-digital-transformation/gif/module-2-legal-framework-the-decree-drafting-kit/2.2-anatomy-of-an-interoperability-decree.md) ✍️        | B4, B8        | 2.3, 2.4           |
| **B10**  | Explanatory Memorandum and Preamble | [2.3](/experience-digital-transformation/gif/module-2-legal-framework-the-decree-drafting-kit/2.3-the-explanatory-memorandum-and-preamble.md) ✍️      | B4, B9        | 2.5                |
| **B11**  | Operative article draft             | [2.4](/experience-digital-transformation/gif/module-2-legal-framework-the-decree-drafting-kit/2.4-the-draft-articles-package.md) ✍️                   | B9, B5        | 2.5, 2.6, 4.8, 5.9 |
| **B12**  | Cover Note and two-track memo       | [2.5](/experience-digital-transformation/gif/module-2-legal-framework-the-decree-drafting-kit/2.5-the-cover-note-and-two-track-regulatory-memo.md) ✍️ | B10, B11      | —                  |
| **B13**  | Legal acceptance check              | [2.6](/experience-digital-transformation/gif/module-2-legal-framework-the-decree-drafting-kit/2.6-the-decree-as-configuration.md) 🔍                  | B5, B11       | 5.2                |

### Module 3 — Governance model — three tiers with RACI

*The organisational configuration — the Governance Pack.*

| Artefact | What it is                                                                                 | Produced by                                                                                                                                | Consumes   | Feeds    |
| -------- | ------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- |
| **B14**  | Owner's mandate, regulator and operator split                                              | [3.1](/experience-digital-transformation/gif/module-3-governance-model-three-tiers-with-raci/3.1-why-a-bus-needs-an-owner.md) ✍️           | A0 §6, B4  | 3.2      |
| **B15**  | Three-tier governance structure                                                            | [3.2](/experience-digital-transformation/gif/module-3-governance-model-three-tiers-with-raci/3.2-the-three-tiers-of-governance.md) ✍️      | A0 §4, B14 | 3.3, 3.5 |
| **B16**  | Governance RACI                                                                            | [3.3](/experience-digital-transformation/gif/module-3-governance-model-three-tiers-with-raci/3.3-the-raci-matrix.md) ✍️                    | B15, B6    | 3.4, 3.6 |
| **B17**  | Member obligations and agreement                                                           | [3.4](/experience-digital-transformation/gif/module-3-governance-model-three-tiers-with-raci/3.4-member-obligations.md) ✍️                 | B16, B6    | 5.3      |
| **B18**  | Four Working Group charters                                                                | [3.5](/experience-digital-transformation/gif/module-3-governance-model-three-tiers-with-raci/3.5-the-four-technical-working-groups.md) ✍️  | B15        | 3.6      |
| **B19**  | Change control, standards register (with conformance fields) and semantic-registry charter | [3.6](/experience-digital-transformation/gif/module-3-governance-model-three-tiers-with-raci/3.6-governance-as-living-configuration.md) ✍️ | B16, B18   | 5.9      |

### Module 4 — Architecture and technical standards

*The technical configuration.*

| Artefact | What it is                                      | Produced by                                                                                                                                                 | Consumes | Feeds                    |
| -------- | ----------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ------------------------ |
| **B20**  | Component-to-layer map                          | [4.1](/experience-digital-transformation/gif/module-4-architecture-and-technical-standards/4.1-place-every-component-the-four-functional-layers.md) 🔍      | A0 §6    | 4.2, 4.3                 |
| **B21**  | Trust-zone trace                                | [4.2](/experience-digital-transformation/gif/module-4-architecture-and-technical-standards/4.2-secure-every-call-the-three-trust-zones.md) ✍️               | B5, B20  | —                        |
| **B22**  | Standards portfolio                             | [4.3](/experience-digital-transformation/gif/module-4-architecture-and-technical-standards/4.3-adopt-the-standards-portfolio.md) 🔍                         | B7, B20  | 4.4, 4.5, 5.2, 5.9, 5.10 |
| **B23**  | Semantic map                                    | [4.4](/experience-digital-transformation/gif/module-4-architecture-and-technical-standards/4.4-generate-the-semantic-map.md) ✍️                             | B5, B22  | 4.5, 4.6, 5.10           |
| **B24**  | OpenAPI service contract                        | [4.5](/experience-digital-transformation/gif/module-4-architecture-and-technical-standards/4.5-generate-a-service-contract.md) ✍️                           | B23, B22 | 4.7                      |
| **B25**  | Bronze/silver/gold source map                   | [4.6](/experience-digital-transformation/gif/module-4-architecture-and-technical-standards/4.6-put-a-real-data-source-on-the-bus-the-giga-case.md) ✍️       | B23      | —                        |
| **B26**  | X-Road service description and wiring checklist | [4.7](/experience-digital-transformation/gif/module-4-architecture-and-technical-standards/4.7-wire-a-service-onto-the-bus.md) ✍️                           | B24, B6  | 5.4                      |
| **B27**  | Data-protection envelope                        | [4.8](/experience-digital-transformation/gif/module-4-architecture-and-technical-standards/4.8-make-the-exchange-lawful-the-data-protection-envelope.md) ✍️ | B5, B11  | 5.6                      |

### Module 5 — Implementation and onboarding

*The runnable slice, then the framework in operation.*

| Artefact | What it is                                                                                          | Produced by                                                                                                                                          | Consumes                                                                      | Feeds                 |
| -------- | --------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- | --------------------- |
| **B28**  | Implementation plan: phased schedule, investment, procurement, workforce, risk register and metrics | [5.1](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.1-plan-the-build-in-four-phases.md) ✍️                         | B5, B6                                                                        | 5.7, 5.10, storyboard |
| **B29**  | Member Requirements checklist                                                                       | [5.2](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.2-state-what-a-member-must-have-the-member-requirements.md) ✍️ | B22, B13                                                                      | 5.4                   |
| **B30**  | Service-Level Agreement template                                                                    | [5.3](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.3-make-connected-mean-dependable-the-sla.md) ✍️                | B17                                                                           | —                     |
| **B31**  | X-Road member registration                                                                          | [5.4](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.4-admit-a-member-to-the-bus.md) ✍️                             | B26, B29                                                                      | 5.5                   |
| **B32**  | Federation stand-up run book                                                                        | [5.5](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.5-stand-up-the-federation.md) ✍️                               | B31                                                                           | 5.6, 5.7              |
| **B33**  | Once-only acceptance script                                                                         | [5.6](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.6-run-the-once-only-exchange-live.md) ✍️                       | B32, B27                                                                      | —                     |
| **B34**  | Demonstration-to-production gap checklist                                                           | [5.7](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.7-from-demonstration-to-production.md) 🔍                      | B32, B28                                                                      | —                     |
| **B35**  | Bus-health summary and anomaly list                                                                 | [5.8](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.8-watch-the-bus-monitoring-and-anomaly-detection.md) 🔍        | your bus's operational monitoring data (metadata only, never the message log) | —                     |
| **B36**  | Document-consistency report                                                                         | [5.9](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.9-keep-the-documents-honest-the-consistency-cross-check.md) 🔍 | B11, B19, B22                                                                 | —                     |
| **B37**  | Sector-portability map                                                                              | [5.10](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.10-carry-the-framework-to-the-next-sector.md) ✍️              | B28, B22, B23                                                                 | —                     |

### The storyboard

| Artefact | What it is                                                                                            | Produced by                                                                                                                                                        | Consumes | Feeds |
| -------- | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------- | ----- |
| **B38**  | Country storyboard — a minister-ready narrative of your country's path to its first once-only service | [Course home](/experience-digital-transformation/gif/building-a-government-interoperability-framework-gif.md#from-no-framework-to-first-service-the-storyboard) ✍️ | B5, B28  | —     |

## What the pack contains when you are done

1. **The foundation:** B4 the Strategic Foundation Document and B5 the Use-Case Catalogue, with B6 telling you who to onboard first.
2. **The legal configuration:** the decree — B9 to B12 — checked by B13 against the catalogue it must authorise exactly.
3. **The organisational configuration:** the Governance Pack — B14 to B19 — with one Accountable per decision and a named standards-portfolio owner.
4. **The technical configuration:** B22 the standards portfolio, B23 the semantic map, B24 the contract, B26 the wiring and B27 the data-protection envelope, for the first exchange.
5. **The runnable slice:** B28 the phased plan, the member artefacts B29–B31, B32 the run book, and B33 the once-only acceptance script that proves all four layers in one call.
6. **The framework in operation:** B34 the production gap, B35 the bus watched from its logs, B36 the three documents kept honest, B37 the map to the next sector.

## Where the chain goes next

The planned course on the national DPI roadmap reads the framework this workbook describes as one of the shared platforms a country sequences; the one on building-block services puts services on the bus this course stood up. Those pages are added as each Knowledge Product is published.


---

# 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/your-framework-workbook.md?ask=<question>&goal=<user_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.