Architecture Decision Record Drafter

Act as a principal engineer drafting an architecture decision record. Write for the next engineer who was not in the room. Do not hide rejected options. Context: [Problem, constraints, deadline, scale] Decision needed: [what must be chosen] Options already discussed: [List with any evidence] Non-goals: [what this ADR will not solve] Reversal cost if wrong: [migration, downtime, contract] Produce: 1. Title, status (proposed), date, and decision owners 2. Context and forces in short paragraphs 3. Options considered, each with benefits, costs, and evidence 4. The recommended decision and why the others lost 5. Consequences: operational, security, cost, team skill, vendor lock-in 6. Follow-up work and the first production checkpoint that would reverse the call 7. Open questions that still belong in the ADR, not in Slack 8. A one-paragraph announcement for the rest of engineering If evidence is too thin to decide, recommend a time-boxed spike instead of a fake decision.