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

# Your country workbook

The artefacts the plays produce, in dependency order — run a module, leave with a briefing pack about your own country.

Each play produces one artefact. Run them in order and the artefacts feed each other; run all seven plays of Module 1 and you hold a **draft cabinet-briefing pack** for your country. Run all five modules and you hold the architecture itself. This page is the map. If you have no country to hand, use Progressa — the worked examples on each play page show what each artefact looks like for it.

{% 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**   | Country context pack — landscape brief, programme list, ministry context, roles register, characteristics, sector bodies, legal list | [Play 0](/experience-digital-transformation/gea/start-here/play-0-build-your-country-context.md) 🔍 | the whole chain below |

## Module 1 — the cabinet-briefing pack

```mermaid
flowchart TD
    A0["A0 Country context pack\n(Play 0)"] --> A1["A1 Fragmentation diagnostic\n(1.1)"]
    A0 --> A2
    A0 --> A6
    A1 --> A3["A3 Re-use business case\n(1.3)"]
    A1 --> A5["A5 PAERA foundation map\n(1.5)"]
    A2["A2 Ministerial explainer\n(1.2)"] --> A4["A4 Joint business–IT agenda\n(1.4)"]
    A4 --> A6["A6 Phase RACI + role gaps\n(1.6)"]
    A5 --> A6
    A3 --> A7["A7 Governance Board ToR\n(1.7)"]
    A6 --> A7
    A7 --> PACK["Cabinet-briefing pack\n→ Module 3"]
```

## Every artefact in this course

*The numbers follow the curriculum order in which the plays were first written, not module order: **A8** (comparator-country cards) is produced in Module 5, play 5.1.*

### Module 1 — Why a PAERA-anchored EA

| Artefact | What it is                             | Produced by                                                                                                                                                    | Consumes                                                                 | Feeds    |
| -------- | -------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ | -------- |
| **A1**   | Fragmentation diagnostic               | [1.1](/experience-digital-transformation/gea/module-1-why-a-paera-anchored-ea/1.1-why-your-country-needs-a-national-ea.md) 🔍                                  | A0 §1 Digital-landscape brief                                            | 1.3, 1.5 |
| **A2**   | Ministerial explainer slide            | [1.2](/experience-digital-transformation/gea/module-1-why-a-paera-anchored-ea/1.2-what-an-ea-actually-is-in-one-breath.md) ✍️                                  | A0 §1 (the named institutions and services)                              | 1.4      |
| **A3**   | Re-use business case (directional)     | [1.3](/experience-digital-transformation/gea/module-1-why-a-paera-anchored-ea/1.3-why-projects-cant-do-this-themselves.md) ✍️                                  | A0 §2 Programme list                                                     | 1.7      |
| **A4**   | Joint business–IT agenda               | [1.4](/experience-digital-transformation/gea/module-1-why-a-paera-anchored-ea/1.4-why-an-ea-matters-more-now-and-what-it-lets-your-minister-actually-do.md) 🔁 | A0 §3 Ministry operating context                                         | 1.6      |
| **A5**   | PAERA foundation coverage map          | [1.5](/experience-digital-transformation/gea/module-1-why-a-paera-anchored-ea/1.5-why-paera-anchored-the-head-start-you-do-not-pay-for-twice.md) 🔍            | A0 §2 Programme list (plus any strategies from §1)                       | 1.6      |
| **A6**   | Phase RACI and role-gap list           | [1.6](/experience-digital-transformation/gea/module-1-why-a-paera-anchored-ea/1.6-the-lifecycle-on-one-page.md) ✍️                                             | A0 §4 Institutional roles register                                       | 1.7      |
| **A7**   | EA Governance Board Terms of Reference | [1.7](/experience-digital-transformation/gea/module-1-why-a-paera-anchored-ea/1.7-what-you-will-need-from-your-minister-and-how-to-ask-for-it.md) ✍️           | A0 §4 Institutional roles register (posts only) and the gap list from A6 | M3       |

### Module 2 — Principles, the metamodel and the BDAT layers

| Artefact | What it is                   | Produced by                                                                                                                                                                     | Consumes                               | Feeds         |
| -------- | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------- | ------------- |
| **A9**   | Four-layer reading template  | [2.1](/experience-digital-transformation/gea/module-2-principles-the-metamodel-and-the-bdat-layers/2.1-read-any-government-in-four-layers.md) ✍️                                | A0 §6                                  | 2.5           |
| **A10**  | Metamodel conformance report | [2.2](/experience-digital-transformation/gea/module-2-principles-the-metamodel-and-the-bdat-layers/2.2-the-shared-vocabulary-that-makes-re-use-possible.md) 🔍                  | a draft model, or the initiatives list | 2.5           |
| **A11**  | Principle card set           | [2.3](/experience-digital-transformation/gea/module-2-principles-the-metamodel-and-the-bdat-layers/2.3-adopt-your-principles-dont-draft-them.md) ✍️                             | A0 §7                                  | 2.6, 3.5, 4.5 |
| **A12**  | Body classification profile  | [2.4](/experience-digital-transformation/gea/module-2-principles-the-metamodel-and-the-bdat-layers/2.4-classify-any-public-body-before-you-model-it.md) 🔍                      | A0 §6                                  | 2.5, 4.1      |
| **A13**  | Sector BDAT skeleton         | [2.5](/experience-digital-transformation/gea/module-2-principles-the-metamodel-and-the-bdat-layers/2.5-bdat-on-a-real-ministry-the-progressa-walkthrough.md) ✍️                 | A0 §6, A5, A9, A12, A10                | 2.6, 3.1, 4.1 |
| **A14**  | Scored gap analysis          | [2.6](/experience-digital-transformation/gea/module-2-principles-the-metamodel-and-the-bdat-layers/2.6-run-a-phase-2-assess-what-good-looks-like-and-the-gaps-youll-find.md) 🔍 | A13, A11                               | 2.7, 4.3      |
| **A15**  | Two-trap screen              | [2.7](/experience-digital-transformation/gea/module-2-principles-the-metamodel-and-the-bdat-layers/2.7-the-two-traps-to-catch-at-assess-bespoke-and-vendor-driven.md) 🔍        | A14, BB status register                | 4.4, 4.7      |

### Module 3 — EA repository, tooling and governance

| Artefact     | What it is                       | Produced by                                                                                                                                              | Consumes                               | Feeds         |
| ------------ | -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------- | ------------- |
| **A16**      | EA repository structure          | [3.1](/experience-digital-transformation/gea/module-3-ea-repository-tooling-and-governance/3.1-set-up-the-one-place-your-architecture-lives.md) ✍️       | A13, A17                               | 3.2, 3.3, 3.6 |
| **A17**      | EA tool comparison + export test | [3.2](/experience-digital-transformation/gea/module-3-ea-repository-tooling-and-governance/3.2-choose-ea-tooling-without-locking-yourself-in.md) 🔍      | A16, candidate list                    | 3.1           |
| **A18**      | Repository update policy         | [3.3](/experience-digital-transformation/gea/module-3-ea-repository-tooling-and-governance/3.3-keep-the-repository-true-the-update-discipline.md) ✍️     | A16, A7                                | 3.5, 3.6      |
| **A7 rev.2** | EA Board ToR, standing version   | [3.4](/experience-digital-transformation/gea/module-3-ea-repository-tooling-and-governance/3.4-stand-up-an-ea-board-that-can-actually-say-no.md) ✍️      | A7, A0 §7                              | 3.5, 4.7      |
| **A19**      | Review-gate checklist            | [3.5](/experience-digital-transformation/gea/module-3-ea-repository-tooling-and-governance/3.5-review-projects-against-the-architecture.md) ✍️           | A7 rev.2, A11, BB status register, A18 | 4.7           |
| **A20**      | EA health scorecard              | [3.6](/experience-digital-transformation/gea/module-3-ea-repository-tooling-and-governance/3.6-show-the-ea-is-working-the-few-metrics-that-matter.md) ✍️ | A16, A18                               | 3.7           |
| **A21**      | Sustainment risk register        | [3.7](/experience-digital-transformation/gea/module-3-ea-repository-tooling-and-governance/3.7-keep-the-practice-alive-past-year-two.md) ✍️              | A20, A6                                | 5.2           |

### Module 4 — Progressa end-to-end — the method on one sector

| Artefact      | What it is           | Produced by                                                                                                                                                                   | Consumes                                      | Feeds              |
| ------------- | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------- | ------------------ |
| **A22**       | Demonstration canvas | [4.1](/experience-digital-transformation/gea/module-4-progressa-end-to-end-the-method-on-one-sector/4.1-meet-progressa-a-real-sector-with-a-real-fragmentation-problem.md) ✍️ | A0 §6, A12, A13, the sector problem paragraph | 4.2                |
| **A23**       | Discovery brief      | [4.2](/experience-digital-transformation/gea/module-4-progressa-end-to-end-the-method-on-one-sector/4.2-phase-1-discover-map-what-the-sector-has-today.md) ✍️                 | A22, A0 §7                                    | 4.3                |
| **A14 rev.2** | Ranked gap analysis  | [4.3](/experience-digital-transformation/gea/module-4-progressa-end-to-end-the-method-on-one-sector/4.3-phase-2-assess-find-the-gaps-and-rank-them.md) 🔍                     | A23, A14                                      | 4.4                |
| **A24**       | Sourcing matrix      | [4.4](/experience-digital-transformation/gea/module-4-progressa-end-to-end-the-method-on-one-sector/4.4-phase-3-adapt-fit-paera-and-decide-build-buy-or-share.md) 🔍          | A14 rev.2, BB status register, A15            | 4.5                |
| **A25**       | Target architecture  | [4.5](/experience-digital-transformation/gea/module-4-progressa-end-to-end-the-method-on-one-sector/4.5-phase-4-plan-design-the-target-architecture.md) ✍️                    | A24, A11, BB status register                  | 4.6                |
| **A26**       | Wave roadmap         | [4.6](/experience-digital-transformation/gea/module-4-progressa-end-to-end-the-method-on-one-sector/4.6-phase-4-plan-sequence-the-roadmap-and-cost-it.md) ✍️                  | A25, A3                                       | 4.7, 4.8, 5.3, 5.4 |
| **A27**       | Gate decision paper  | [4.7](/experience-digital-transformation/gea/module-4-progressa-end-to-end-the-method-on-one-sector/4.7-phase-5-execute-and-govern-stand-up-the-living-ea.md) ✍️              | A26, A19, A7 rev.2, BB status register, A15   | 5.2                |
| **A28**       | Sector transfer plan | [4.8](/experience-digital-transformation/gea/module-4-progressa-end-to-end-the-method-on-one-sector/4.8-run-this-on-your-own-sector-the-transferable-recipe.md) 🔁            | A26, A0 §6 (next sector)                      | 5.3, 5.3b          |

### Module 5 — Evidence, rollout and the case

| Artefact      | What it is                        | Produced by                                                                                                                                                         | Consumes                     | Feeds     |
| ------------- | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------- | --------- |
| **A8**        | Comparator-country cards, sourced | [5.1](/experience-digital-transformation/gea/module-5-evidence-rollout-and-the-case/5.1-is-this-proven-or-just-theory-evidence-from-real-programmes.md) 🔍          | A0 §5                        | 5.4, 5.6  |
| **A21 rev.2** | Programme risk register           | [5.2](/experience-digital-transformation/gea/module-5-evidence-rollout-and-the-case/5.2-what-the-evidence-says-works-and-what-quietly-kills-these-programmes.md) ✍️ | A21, A27                     | 5.4       |
| **A31**       | National rollout wave plan        | [5.3](/experience-digital-transformation/gea/module-5-evidence-rollout-and-the-case/5.3-roll-it-out-across-sectors-and-why-the-second-is-cheaper.md) ✍️             | A26, A28, BB status register | 5.3b, 5.6 |
| **A28 rev.2** | Second-sector map                 | [5.3b](/experience-digital-transformation/gea/module-5-evidence-rollout-and-the-case/5.3-roll-it-out-across-sectors-and-why-the-second-is-cheaper.md) 🔁            | A28, A31, BB status register | —         |
| **A29**       | Ministerial business case         | [5.4](/experience-digital-transformation/gea/module-5-evidence-rollout-and-the-case/5.4-win-the-commitment-the-business-case-that-gets-your-minister-to-yes.md) 🔁  | A3, A8, A21 rev.2, A26       | 5.6       |
| **A30**       | Capability-building plan          | [5.5](/experience-digital-transformation/gea/module-5-evidence-rollout-and-the-case/5.5-build-your-teams-capability-with-open-knowledge-products.md) ✍️             | A6                           | —         |
| **A29 rev.2** | Closing one-page case             | [5.6](/experience-digital-transformation/gea/module-5-evidence-rollout-and-the-case/5.6-the-closing-case-proven-portable-and-necessary-now.md) 🔁                   | A29, A31, A8                 | —         |

## What the Module 1 pack contains when you are done

1. **The problem:** A1, validated against named sources.
2. **The words:** A2, checked by a sector CIO.
3. **The money:** A3, directional, with a costing exercise commissioned.
4. **The first decisions:** A4, the agenda for a Board that does not yet exist.
5. **What we keep and what we build:** A5, corrected against the actual documents.
6. **Who does what, and who is missing:** A6, the role-gap list above the matrix.
7. **The Board:** A7, after legal counsel.

Bring items 1–7 as a single pack and make the four asks from [1.7](/experience-digital-transformation/gea/module-1-why-a-paera-anchored-ea/1.7-what-you-will-need-from-your-minister-and-how-to-ask-for-it.md) together, not in pieces.

## Where the chain goes next

Module 5 closes this course with the case for sustained commitment (A29 rev.2). In [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) the chain continues into the build pack, where the play outputs become the inputs to the interoperability proving slice.


---

# 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/gea/your-country-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.