RFC / Design Doc Template

For non-trivial technical decisions — anything cross-team, anything hard to reverse, anything you'll want to remember why you did in a year. Async review. Time-boxed. The alternatives section is required because "we chose X" is only useful if we can see what X beat.

# [Title] — RFC

**Author:** [Name]
**Status:** Draft | In Review | Accepted | Rejected | Superseded
**Created:** [Date]
**Decision by:** [Date]
**Decision owner:** [Name]

## Context
[What's the problem? Why now? What's the cost of doing nothing?]

## Proposal
[What are we proposing to do? Concrete enough that someone could argue with it.]

## Alternatives considered
- **Option A:** [description] — [why not]
- **Option B:** [description] — [why not]
- **Do nothing:** [what happens if we don't do this]

## Trade-offs
- **Gains:**
- **Costs:**
- **What we're accepting we won't do:**

## Open questions
- 
- 

## Rollout / migration
[If this changes something in production, how does it get from here to there?]

## Decision (filled in after review)
**Decided:** 
**By:** 
**On:** 
**Notes:**