> 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/building-block/the-blank-instruments.md).

# The blank instruments

A blank instrument is an empty form for one document of the method. Each has the same shape: what the document is for, who writes it and who accepts it, the lines to fill in, and the questions a manager asks before accepting it. The forms are plain: they hold the lines the method asks for and nothing more.

| Blank instrument                                                                                                                                                                                              | Document of the twelve | Who writes it                                                                                        | Taught in     |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------- | ---------------------------------------------------------------------------------------------------- | ------------- |
| [The catalogue of the sector's services](/experience-digital-transformation/building-block/the-blank-instruments/the-catalogue-of-the-sectors-services.md)                                                    | —                      | The team that commissions the services, for the whole sector                                         | 2.1           |
| [The register of requirements](/experience-digital-transformation/building-block/the-blank-instruments/the-register-of-requirements.md)                                                                       | 2                      | An AI assistant extracts it; the analyst rules on each entry                                         | 2.2           |
| [The entity model, with its glossary and its business rules](/experience-digital-transformation/building-block/the-blank-instruments/the-entity-model-with-its-glossary-and-its-business-rules.md)            | 3                      | The analyst                                                                                          | 2.3           |
| [The use case model](/experience-digital-transformation/building-block/the-blank-instruments/the-use-case-model.md)                                                                                           | 4                      | One named architect                                                                                  | 2.4           |
| [The software architecture](/experience-digital-transformation/building-block/the-blank-instruments/the-software-architecture.md)                                                                             | 5                      | The solution architect                                                                               | 2.6, 5.4, 5.6 |
| [The shared groundwork: states, events, code lists and settings](/experience-digital-transformation/building-block/the-blank-instruments/the-shared-groundwork-states-events-code-lists-and-settings.md)      | 6                      | A person, with an assistant                                                                          | 2.5, 4.3      |
| [One use case, written out in full](/experience-digital-transformation/building-block/the-blank-instruments/one-use-case-written-out-in-full.md)                                                              | 7                      | An AI assistant writes it; a person rules on it                                                      | 3.1, 3.2      |
| [The screens of a use case](/experience-digital-transformation/building-block/the-blank-instruments/the-screens-of-a-use-case.md)                                                                             | 8                      | Whoever wrote the use case, beside it                                                                | 3.3, 3.4, 3.6 |
| [The interaction design](/experience-digital-transformation/building-block/the-blank-instruments/the-interaction-design.md)                                                                                   | 10                     | One analyst writes it; the owner accepts it                                                          | 4.1, 4.2, 4.3 |
| [The review of the application model](/experience-digital-transformation/building-block/the-blank-instruments/the-review-of-the-application-model.md)                                                         | 11                     | The person who reviews the model, from the list of assumptions and losses that the assistant reports | 4.4, 4.5, 4.6 |
| [The deliverables annex of the terms of reference for a supplier](/experience-digital-transformation/building-block/the-blank-instruments/the-deliverables-annex-of-the-terms-of-reference-for-a-supplier.md) | —                      | The ministry's procurement officer, with the team that commissions the service                       | 6.1           |

Three documents of the twelve have no blank instrument, because no person writes them as a blank. The customer's own documents are kept as received, the walk-through is produced from the screens, and the working application is generated from the application model.

## The pages of the toolkit

* [The catalogue of the sector's services](/experience-digital-transformation/building-block/the-blank-instruments/the-catalogue-of-the-sectors-services.md)
* [The register of requirements](/experience-digital-transformation/building-block/the-blank-instruments/the-register-of-requirements.md)
* [The entity model, with its glossary and its business rules](/experience-digital-transformation/building-block/the-blank-instruments/the-entity-model-with-its-glossary-and-its-business-rules.md)
* [The use case model](/experience-digital-transformation/building-block/the-blank-instruments/the-use-case-model.md)
* [The software architecture](/experience-digital-transformation/building-block/the-blank-instruments/the-software-architecture.md)
* [The shared groundwork: states, events, code lists and settings](/experience-digital-transformation/building-block/the-blank-instruments/the-shared-groundwork-states-events-code-lists-and-settings.md)
* [One use case, written out in full](/experience-digital-transformation/building-block/the-blank-instruments/one-use-case-written-out-in-full.md)
* [The screens of a use case](/experience-digital-transformation/building-block/the-blank-instruments/the-screens-of-a-use-case.md)
* [The interaction design](/experience-digital-transformation/building-block/the-blank-instruments/the-interaction-design.md)
* [The review of the application model](/experience-digital-transformation/building-block/the-blank-instruments/the-review-of-the-application-model.md)
* [The deliverables annex of the terms of reference for a supplier](/experience-digital-transformation/building-block/the-blank-instruments/the-deliverables-annex-of-the-terms-of-reference-for-a-supplier.md)


---

# 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/building-block/the-blank-instruments.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.