> 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/the-build-pack.md).

# The build pack

The runnable companion to the videos — the configuration the modules generate, the prompts that generate it, the scripts that deploy it, and the acceptance checks that prove it.

This is an implementation Knowledge Product, and this is the half that runs. The build pack stands up a real once-only exchange on an X-Road federation across Progressa's institutions: the National Examination Authority (PNEA) issues a credential and pre-fills identity from the National ID Authority (PNIA) and enrolment from the Learner Registry (PLR) — a learner asked once, over a real cross-server call, with the unauthorised caller denied. It is the Progressa "example output" of Modules 4 and 5: where a play page's worked example would be a pasted draft, here it is a file in the pack.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>🧰 What the build pack is</strong></td><td>The manifest, the three configuration layers, the requirements, and what the pack proves.</td><td><a href="/experience-digital-transformation/gif/the-build-pack/what-the-build-pack-is.md">What the build pack is</a></td></tr><tr><td><strong>▶️ Run it</strong></td><td>The run book — prerequisites, the steps, verifying a change, joining a member, teardown.</td><td><a href="/experience-digital-transformation/gif/the-build-pack/run-it-the-run-book.md">Run it — the run book</a></td></tr><tr><td><strong>✅ Acceptance — the once-only proof</strong></td><td>The headline check: PNEA ← PNIA + PLR, four assertions mapped to the four layers.</td><td><a href="/experience-digital-transformation/gif/the-build-pack/acceptance-the-once-only-proof.md">Acceptance — the once-only proof</a></td></tr><tr><td><strong>🧪 Exercises</strong></td><td>Break and restore the proof, join a member, detect contract drift, un-join, and watch the reproducibility proof.</td><td><a href="/experience-digital-transformation/gif/the-build-pack/exercises.md">Exercises</a></td></tr></tbody></table>

{% hint style="info" %}
**Which plays it belongs to.** [4.4](/experience-digital-transformation/gif/module-4-architecture-and-technical-standards/4.4-generate-the-semantic-map.md) the semantic map · [4.5](/experience-digital-transformation/gif/module-4-architecture-and-technical-standards/4.5-generate-a-service-contract.md) the contract · [4.7](/experience-digital-transformation/gif/module-4-architecture-and-technical-standards/4.7-wire-a-service-onto-the-bus.md) the wiring · [5.2](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.2-state-what-a-member-must-have-the-member-requirements.md)–[5.4](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.4-admit-a-member-to-the-bus.md) the member artefacts · [5.5](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.5-stand-up-the-federation.md) the stand-up · [5.6](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.6-run-the-once-only-exchange-live.md) the once-only exchange · [5.7](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.7-from-demonstration-to-production.md) the production gap · [5.8](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.8-watch-the-bus-monitoring-and-anomaly-detection.md) watching the bus · [5.9](/experience-digital-transformation/gif/module-5-implementation-and-onboarding/5.9-keep-the-documents-honest-the-consistency-cross-check.md) the gate register as the document cross-check made mechanical. Each of those pages says which pack file is its Progressa output.
{% endhint %}

{% hint style="success" %}
**Get it.** The pack is its own public repository: [github.com/alaponin/gif-linkup-demo](https://github.com/alaponin/gif-linkup-demo). Clone it — `git clone https://github.com/alaponin/gif-linkup-demo` — rather than downloading a zip: the join demo needs the checkout's `.git`. Then start at [Run it](/experience-digital-transformation/gif/the-build-pack/run-it-the-run-book.md).
{% 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/the-build-pack.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.