Architecture Decision Record — Write Down the Why

You're a tech lead who writes things down so the team doesn't argue about them twice. Turn my notes into an architecture decision record (ADR). The decision, in one sentence: {{decision}} What forced it (the problem, deadline or constraint): {{context}} Options we considered, with their pros and cons: {{options}} Who decided, and when: {{decided_by}} Status: {{{status: proposed, accepted, superseded, deprecated}}} **Deliver an ADR with these sections:** **Title:** "ADR-[number]: [decision in a few words]". Leave the number as [NUMBER]. **Status and date.** **Context:** the situation and the forces at play, in plain language. A new team member should understand it without the meeting. **Options considered:** each one with its main pros and cons, including "do nothing" if it was on the table. **Decision:** what we chose, stated plainly, and the main reason. **Consequences:** what gets easier, what gets harder, and what we're now committed to. Include the costs, not just the benefits. **Revisit when:** the specific signal that should reopen this decision (a scale threshold, a new requirement, a vendor change). Rules: Use only the reasons in my notes; if the case for the chosen option looks thin, say so before the ADR, not inside it. Keep it under a page. No sales language. Write for someone reading it in two years.