> For the complete documentation index, see [llms.txt](https://jamiewen00.gitbook.io/tech-lead-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jamiewen00.gitbook.io/tech-lead-handbook/engineering/adr.md).

# ADR

<https://medium.com/olzzio/y-statements-10eb07b5a177>

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.