> 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-standings-of-the-methods-standards.md). # The standings of the method's standards A manager who relies on a document of the method should know how far the standard it is written to has come: some are drafts, some are in force, and some came into force before anyone used them on a real project. The written guide states once, here and in no video, how far each standard behind the twelve documents has come. A draft is written for review and has not been approved. In force means approved for use. Not yet tested by use means the standard came into force before anyone used it on a real project. | Document | The standard that governs it | Its standing | | ----------------- | ----------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- | | All | The method itself: the twelve documents, their order, the review and the rules that always hold | In force | | Before the twelve | The sector's catalogue of services | Draft | | 2 | The register of what was asked | Draft | | 3 | The records, with their glossary and business rules | In force; not yet tested by use | | 4 | The list of goals | In force | | 5 | The architecture | In force; not yet tested by use | | 6 | The shared lists, settings and states | In force; not yet tested by use | | 7 | One goal written out in full | In force | | 8 and 9 | The screens of a goal, and the walk-through produced from them | In force | | 10 | The interaction design | Draft | | 11 | The application model | In force; not yet tested by use | | 8 | The rules for screens officers use | Its first page gives a version and a date, and states neither draft nor in force | | 8 | The rules an assistant follows when it generates screens | In force | Subtopic [6.7](/experience-digital-transformation/building-block/module-6-run-the-method-in-your-administration/6.7-before-you-rely-on-it-what-the-method-does-not-claim.md) teaches what the method does not claim about itself, and why a manager reads these standings before relying on it. --- # 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-standings-of-the-methods-standards.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.