> 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/roadmap/module-2-the-registration-block.md).

# Module 2 — The Registration block

A registration service set up from a description: the application, the checks, the officer's decision, the write to the register

**Written for:** the team that configures the service (Architect register). **Videos:** 6.

**What it teaches.** A registration service set up from a description: the application, the checks, the officer's decision, the write to the register.

**What you can do afterwards.** Set up a registration service from a description, with its checks, its officer's decision and its write to the register.

**What is built.** Configurations R1 to R10

## Subtopics

| #                                                                                                                                                          | Subtopic                                                           | Class         | Demonstration | Single message                                                                                                                                                                                                   |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ | ------------- | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [2.1](/experience-digital-transformation/roadmap/module-2-the-registration-block/2.1-what-the-registration-block-does.md)                                  | What the Registration block does                                   | Core          | —             | A registration block takes an application, lets an officer decide and, on approval, writes to a register and gives the applicant proof, and built once it serves every ministry that registers people or things. |
| [2.2](/experience-digital-transformation/roadmap/module-2-the-registration-block/2.2-the-published-specification-and-how-to-judge-a-product-against-it.md) | The published specification, and how to judge a product against it | Supplementary | —             | Ask every vendor to show the product against the published specification, requirement by requirement, and check whether GovStack lists it and at which compliance level.                                         |
| [2.3](/experience-digital-transformation/roadmap/module-2-the-registration-block/2.3-generating-the-registration-service.md)                               | Generating the registration service                                | Core          | Yes           | Describe your registration in the specification's terms, and an AI assistant drafts the service description that sets the block up, which you then import, test and correct.                                     |
| [2.4](/experience-digital-transformation/roadmap/module-2-the-registration-block/2.4-checks-before-the-officer-decides.md)                                 | Checks before the officer decides                                  | Core          | Yes           | Three kinds of check stop a bad application before it reaches the officer: rules on each field, a comparison with the identity authority's record, and a test of completeness on sending.                        |
| [2.5](/experience-digital-transformation/roadmap/module-2-the-registration-block/2.5-the-officer-decides-and-the-record-is-written.md)                     | The officer decides, and the record is written                     | Core          | Yes           | A registrar approves, rejects or sends back each application, and only on approval does the block write the record to the register, in a sequence the specifications leave you to define and test.               |
| [2.6](/experience-digital-transformation/roadmap/module-2-the-registration-block/2.6-the-whole-service-as-a-description-you-can-move.md)                   | The whole service as a description you can move                    | Supplementary | Yes           | The whole service is a description you can test, publish, export and import elsewhere, so a second ministry starts from yours and not from nothing.                                                              |

{% hint style="info" %}
The reference pages hold what every module uses: [the nine steps](/experience-digital-transformation/roadmap/the-nine-steps.md), [the assessment toolkit](/experience-digital-transformation/roadmap/the-assessment-toolkit.md), [the worked examples](/experience-digital-transformation/roadmap/the-worked-examples.md), [the build plan](/experience-digital-transformation/roadmap/the-build-plan.md), [the frameworks and standards](/experience-digital-transformation/roadmap/frameworks-and-standards.md), [the glossary](/experience-digital-transformation/roadmap/glossary.md) and [the figures](/experience-digital-transformation/roadmap/figures.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/roadmap/module-2-the-registration-block.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.