# ADR Each template element appears on one line in the above example:[5](https://ozimmer.ch/practices/2020/04/27/ArchitectureDecisionMaking.html#fn:5) 1. *context*: functional requirement (user story or use case) or an architecture component, 2. *facing*: non-functional requirement, for instance a desired quality, 3. *we decided for*: decision outcome, arguably the most important part, 4. *and neglected*: alternatives not chosen (not to be forgotten!), 5. *to achieve*: benefits, the full or partial satisfaction of the requirement, 6. *accepting that*: drawbacks, impact on other properties/context and effort/cost. --- # Agent Instructions: 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: ``` GET https://jamiewen00.gitbook.io/tech-lead-handbook/engineering/adr.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.