> 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-3-the-registry-block.md). # Module 3 — The Registry block A register set up from a schema file, loaded through checked tiers, accounted for after every load and opened to other services under rules **Written for:** the team that configures the service (Architect register). **Videos:** 7. **What it teaches.** A register set up from a schema file, loaded through checked tiers, accounted for after every load and opened to other services under rules. **What you can do afterwards.** Set up a register from a schema file, load it through checked tiers, account for every load and open it to other services under rules. **What is built.** Configurations RG1 to RG13 ## Subtopics | # | Subtopic | Class | Demonstration | Single message | | ----------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- | ------------- | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [3.1](/experience-digital-transformation/roadmap/module-3-the-registry-block/3.1-what-a-register-is-for-one-authoritative-record.md) | What a register is for: one authoritative record | Core | — | A register gives every service one authoritative record of each learner, held as a service with rules on who may read and change it, and filled through a disciplined load. | | [3.2](/experience-digital-transformation/roadmap/module-3-the-registry-block/3.2-five-tiers-between-a-messy-file-and-a-trusted-record.md) | Five tiers between a messy file and a trusted record | Core | Yes | Data reaches the register through five tiers, raw, bronze, staging, silver and gold, with quality checks at bronze and a person's approval before silver. | | [3.3](/experience-digital-transformation/roadmap/module-3-the-registry-block/3.3-generating-the-registers-schema.md) | Generating the register's schema | Core | Yes | The register is set up from one schema file, with its fields, rules, links and key, which an AI assistant drafts from the law and the form and the owner corrects and publishes. | | [3.4](/experience-digital-transformation/roadmap/module-3-the-registry-block/3.4-quality-checks-that-stop-a-bad-row.md) | Quality checks that stop a bad row | Core | Yes | Every row is checked at the bronze tier, and a row that fails is set aside with its reason, so that the people who sent the data know what to correct. | | [3.5](/experience-digital-transformation/roadmap/module-3-the-registry-block/3.5-a-published-pattern-followed-in-the-open.md) | A published pattern, followed in the open | Supplementary | — | Giga's School Master Data shows the pattern at work for schools, and you may follow it for learners if you say what you took and changed and copy no unlicensed code. | | [3.6](/experience-digital-transformation/roadmap/module-3-the-registry-block/3.6-account-for-every-load.md) | Account for every load | Core | Yes | After every load, show that the rows received equal the rows passed plus the rows set aside, and that the rows approved equal the records the register added or changed. | | [3.7](/experience-digital-transformation/roadmap/module-3-the-registry-block/3.7-the-register-as-a-service-others-can-use.md) | The register as a service others can use | Core | Yes | Other services reach the register only through its published interface, each seeing no more than its role allows, and every learner or parent can see who read their record. | {% 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-3-the-registry-block.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.