> 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-2-legal-framework-the-decree-drafting-kit.md). # Module 2 — Legal framework — the Decree Drafting Kit Six videos on the legal layer: why the bus needs a mandate, the five components of an interoperability decree, the Explanatory Memorandum. **Persona:** S (Strategist) — national interoperability authority, ministry CIO, Ministry of Justice sponsor, or development-partner lead. **You leave with:** B8, B9, B10, B11, B12, B13, filed in your framework workbook — the legal configuration — the decree. Runtime \~29 minutes across 6 videos. Six videos on the legal layer: why the bus needs a mandate, the five components of an interoperability decree, the Explanatory Memorandum, the Draft Articles and the Cover Note generated against published models, and the decree read as the legal configuration that authorises exactly the exchanges in your catalogue. ## Subtopics | # | Subtopic | Single message | Your play | Kit skill | | -------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | ------------------ | | [2.1](/experience-digital-transformation/gif/module-2-legal-framework-the-decree-drafting-kit/2.1-why-the-platform-needs-a-legal-mandate.md) | Why the platform needs a legal mandate | Without the legal layer, the bus cannot lawfully carry one cross-agency message — the decree is the on-switch, not paperwork. | 🔍 B8 | — | | [2.2](/experience-digital-transformation/gif/module-2-legal-framework-the-decree-drafting-kit/2.2-anatomy-of-an-interoperability-decree.md) | Anatomy of an interoperability decree | A sound decree is five parts; knowing them lets you brief a Ministry of Justice instead of waiting on it. | ✍️ B9 | `gif-decree-draft` | | [2.3](/experience-digital-transformation/gif/module-2-legal-framework-the-decree-drafting-kit/2.3-the-explanatory-memorandum-and-preamble.md) | The Explanatory Memorandum and Preamble | Draft the case-for and the recitals with Claude from your Strategic Foundation Document — then check every claim against a real statute. | ✍️ B10 | `gif-decree-draft` | | [2.4](/experience-digital-transformation/gif/module-2-legal-framework-the-decree-drafting-kit/2.4-the-draft-articles-package.md) | The Draft Articles Package | The operative articles — mandatory connection, once-only, data protection — generated against published models, every clause confirmed, not invented. | ✍️ B11 | `gif-decree-draft` | | [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) | The Cover Note and Two-Track Regulatory Memo | Transmit the package with a specific ask, and show how the decree and the data-protection law fit together — so the decree moves instead of sitting in a queue, and the data-protection authority backs it instead of blocking it. | ✍️ B12 | `gif-decree-draft` | | [2.6](/experience-digital-transformation/gif/module-2-legal-framework-the-decree-drafting-kit/2.6-the-decree-as-configuration.md) | The decree as configuration | The finished decree authorises exactly the exchanges in your Use-Case Catalogue — read it as the legal configuration that binds the technical bus. | 🔍 B13 | — | ## How the plays chain in this module ```mermaid flowchart TD A0["A0 Country context pack\n(Play 0 + supplement)"] B8["B8 Legal-readiness assessment\n(2.1)"] B9["B9 Decree outline (five components)\n(2.2)"] B10["B10 Explanatory Memorandum and Preamble\n(2.3)"] B11["B11 Operative article draft\n(2.4)"] B12["B12 Cover Note and two-track memo\n(2.5)"] B13["B13 Legal acceptance check\n(2.6)"] M1_B4["Module 1\nB4"] M1_B5["Module 1\nB5"] M4out["Module 4"] M5out["Module 5"] A0 --> B8 B8 --> B9 M1_B4 --> B9 B9 --> B10 B9 --> B11 M1_B4 --> B10 B10 --> B12 M1_B5 --> B11 B11 --> B12 B11 --> B13 B11 --> M4out B11 --> M5out M1_B5 --> B13 B13 --> M5out ``` 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-2-legal-framework-the-decree-drafting-kit.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.