> 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/the-interaction-design.md). # The interaction design How officers pick, find, move and act, settled once for the whole application, so that no screen decides it again. A program compares what this document lists with the screens. | | | | -------------------------- | -------------------------------------------------- | | **Document of the twelve** | 10 | | **Who writes it** | One analyst writes it; the owner accepts it | | **What goes in** | Documents 8, 3, 6 and 5 | | **Who accepts it** | The owner, before the application model is written | | **Taught in** | 4.1, 4.2, 4.3 | ## How to use this blank instrument Copy this page into your own document. Fill in the answer to every line. Do not leave a line empty: write "none" where nothing applies, and where the answer is not yet known write an open question with the name of its owner and a date. Do not guess an answer to close a question. When the document is finished, give it to the person who accepts it, together with the questions at the end of this page. ## The header Write these once. | Line | What to write | Your answer | | ----------------------------- | --------------------------------------- | ----------- | | **Application and increment** | Which application, and which part of it | | | **Version and status** | Draft, reviewed or accepted | | | **Goals covered** | Each goal, with its record of screens | | ## How an officer picks Write one row for each list from which an officer picks a value. | Line | What to write | Your answer | | ----------------------- | ----------------------------------------------------------------------------------------------------- | ----------- | | **The list** | Its name, as in the shared groundwork; or: not in the model | | | **Members in force** | How many values the list has now | | | **Maintained or fixed** | Whether the administration maintains the list, and by which role | | | **Categories** | No list longer than nine: the categories the officer picks first, or: none, because the list is short | | | **Code shown as label** | Whether the officer sees the code itself or its label | | ## How an officer finds Write one row for each place where an officer picks another record. | Line | What to write | Your answer | | ---------------------------- | ------------------------------------------------------------- | ----------- | | **Where** | The form and the field | | | **Found by** | A search, or a pick from a short list | | | **What the choice fills in** | The fields filled from the record picked, or: nothing | | | **What is then locked** | Which of those fields the officer may not change, or: nothing | | | **When nothing is found** | What the officer sees | | ## How a record moves Write one row for each move between two states of a record. The states come from the shared groundwork. | Line | What to write | Your answer | | ------------------- | ------------------------------ | ----------- | | **Record** | The record whose life this is | | | **From and to** | The two states | | | **Made by** | The goal and the act, in words | | | **Who may make it** | The roles | | | **The button** | The words on it | | | **Condition** | In the words shown | | ## How an officer acts Write one row for each act that opens a form or carries a record. | Line | What to write | Your answer | | ------------- | ------------------------------------------- | ----------- | | **Stands on** | The form, list or menu heading it stands on | | | **Opens** | The form it opens | | | **Carries** | The record it carries, or: nothing | | | **On a menu** | Yes or no | | ## Before you accept it 1. Is every list longer than nine divided into categories, with the category picked first? 2. Does every move between states name who may make it and the words on its button? 3. Does every place where an officer picks a record say what the choice fills in and what it locks? 4. Were the lists, moves and acts compared with the screens, and was every difference settled? --- # 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/the-interaction-design.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.