Write an architecture decision

---
name: architecture-decision
description: "Make a technical decision explicit, with evidence, tradeoffs, and a reversal plan."
license: CC0-1.0
metadata:
  author: "SI Editorial"
  version: "1"
---

# Write an architecture decision

## When to use
Make a technical decision explicit, with evidence, tradeoffs, and a reversal plan.

## Workflow
1. Inspect the current architecture and constraints before suggesting tools.
2. Compare at least two viable options against scale, team skills, failure modes, and operational cost.
3. Write an ADR: context, decision, alternatives, consequences, and signals that would justify revisiting it.
4. Label estimates and avoid invented benchmarks.

## Boundaries
Use only tools and data authorized for the task. Ask for missing requirements when they affect the result. Report what you verified and what you could not verify.

## Try it
Compare an outbox and direct webhook delivery for our order notifications.

## Success looks like
An ADR grounded in the repository and a measurable revisit condition.