> 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-4-architecture-and-technical-standards.md).

# Module 4 — Architecture and technical standards

Eight videos on the technical layer: the four functional layers and three trust zones, the standards portfolio adopted rather than written.

**Persona:** A (Architect) — chief or senior architect, integration lead, or agency technical lead building on the interoperability bus.

**You leave with:** B20, B21, B22, B23, B24, B25, B26, B27, filed in your framework workbook — the technical configuration. Runtime \~40 minutes across 8 videos.

Eight videos on the technical layer: the four functional layers and three trust zones, the standards portfolio adopted rather than written, the semantic map and the OpenAPI contract generated for a real exchange, Giga's school data taken bronze-to-gold onto the bus, the X-Road wiring, and the data-protection envelope that makes an exchange lawful.

## Subtopics

| #                                                                                                                                                        | Subtopic                                                | Single message                                                                                                                                                 | Your play | Kit skill               |
| -------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | ----------------------- |
| [4.1](/experience-digital-transformation/gif/module-4-architecture-and-technical-standards/4.1-place-every-component-the-four-functional-layers.md)      | Place every component — the four functional layers      | Four functional layers — Service Access, Event Distribution, Trust and Security, Governance and Administration — give every component of the platform a place. | 🔍 B20    | —                       |
| [4.2](/experience-digital-transformation/gif/module-4-architecture-and-technical-standards/4.2-secure-every-call-the-three-trust-zones.md)               | Secure every call — the three trust zones               | Public, Member-Internal, Trust-Anchor — knowing which zone a call crosses tells you exactly what security it needs.                                            | ✍️ B21    | —                       |
| [4.3](/experience-digital-transformation/gif/module-4-architecture-and-technical-standards/4.3-adopt-the-standards-portfolio.md)                         | Adopt the standards portfolio                           | Adopt the published standards — REST/OpenAPI, OAuth/OIDC, mTLS, X-Road — instead of writing your own; the portfolio is the menu every member shares.           | 🔍 B22    | `paera-reference-check` |
| [4.4](/experience-digital-transformation/gif/module-4-architecture-and-technical-standards/4.4-generate-the-semantic-map.md)                             | Generate the semantic map                               | Generate a semantic map so two agencies mean the same 'learner' before they exchange one — the hardest layer, made tractable.                                  | ✍️ B23    | —                       |
| [4.5](/experience-digital-transformation/gif/module-4-architecture-and-technical-standards/4.5-generate-a-service-contract.md)                           | Generate a service contract                             | Turn a service brief into an OpenAPI contract, then an X-Road service description — the configuration that puts a service on the bus.                          | ✍️ B24    | —                       |
| [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)       | Put a real data source on the bus — the Giga case       | Take Giga's real school data through a bronze/silver/gold pipeline onto the bus — a worked exchange you can copy for your sector.                              | ✍️ B25    | —                       |
| [4.7](/experience-digital-transformation/gif/module-4-architecture-and-technical-standards/4.7-wire-a-service-onto-the-bus.md)                           | Wire a service onto the bus                             | The OpenAPI contract becomes an X-Road service description and the call resolves — the GovStack Information Mediation pattern.                                 | ✍️ B26    | —                       |
| [4.8](/experience-digital-transformation/gif/module-4-architecture-and-technical-standards/4.8-make-the-exchange-lawful-the-data-protection-envelope.md) | Make the exchange lawful — the data-protection envelope | Letters of Interest plus a data-protection envelope make a real exchange lawful as well as technically possible.                                               | ✍️ B27    | —                       |

## How the plays chain in this module

```mermaid
flowchart TD
    A0["A0 Country context pack\n(Play 0 + supplement)"]
    B20["B20 Component-to-layer map\n(4.1)"]
    B21["B21 Trust-zone trace\n(4.2)"]
    B22["B22 Standards portfolio\n(4.3)"]
    B23["B23 Semantic map\n(4.4)"]
    B24["B24 OpenAPI service contract\n(4.5)"]
    B25["B25 Bronze/silver/gold source map\n(4.6)"]
    B26["B26 X-Road service description and wiring checklist\n(4.7)"]
    B27["B27 Data-protection envelope\n(4.8)"]
    M1_B5["Module 1\nB5"]
    M1_B7["Module 1\nB7"]
    M5out["Module 5"]
    M1_B6["Module 1\nB6"]
    M2_B11["Module 2\nB11"]
    A0 --> B20
    B20 --> B21
    B20 --> B22
    M1_B5 --> B21
    M1_B7 --> B22
    B22 --> B23
    B22 --> B24
    B22 --> M5out
    M1_B5 --> B23
    B23 --> B24
    B23 --> B25
    B23 --> M5out
    B24 --> B26
    M1_B6 --> B26
    B26 --> M5out
    M1_B5 --> B27
    M2_B11 --> B27
    B27 --> 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-4-architecture-and-technical-standards.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.