> For the complete documentation index, see [llms.txt](https://docs.devland.is/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devland.is/technical-overview/adr/template.md). # ADR Template * Status: \[proposed | rejected | accepted | deprecated | … | superseded by ADR-0005 (add link) * Deciders: \[list everyone involved in the decision] * Date: \[YYYY-MM-DD when the decision was last updated] Technical Story: \[description | ticket/issue URL] ## Context and Problem Statement \[Describe the context and problem statement, e.g., in free form using two to three sentences. You may want to articulate the problem in form of a question.] ## Decision Drivers * \[driver 1, e.g., a force, facing concern, …] * \[driver 2, e.g., a force, facing concern, …] * … ## Considered Options * \[option 1] * \[option 2] * \[option 3] * … ## Decision Outcome Chosen option: "\[option 1]", because \[justification. e.g., only option, which meets k.o. criterion decision driver | which resolves force force | … | comes out best (see below)]. ### Positive Consequences * \[e.g., improvement of quality attribute satisfaction, follow-up decisions required, …] * … ### Negative Consequences * \[e.g., compromising quality attribute, follow-up decisions required, …] * … ## Pros and Cons of the Options ### \[option 1] \[example | description | pointer to more information | …] * Good, because \[argument a] * Good, because \[argument b] * Bad, because \[argument c] * … ### \[option 2] \[example | description | pointer to more information | …] * Good, because \[argument a] * Good, because \[argument b] * Bad, because \[argument c] * … ### \[option 3] \[example | description | pointer to more information | …] * Good, because \[argument a] * Good, because \[argument b] * Bad, because \[argument c] * … ## Links * \[Link type]\[link to adr] * … --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.devland.is/technical-overview/adr/template.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.