# Decisions

Store durable operating and architecture decisions here.

## When to write a decision file

- a rule changes future behavior
- a workflow or routing policy changes
- an architecture tradeoff is made
- a compatibility or precedence rule is introduced

## Suggested filename

`YYYY-MM-DD-short-slug.md`

## Suggested template

```markdown
# Decision Title

**Date:** YYYY-MM-DD
**Status:** Proposed | Accepted | Superseded

## Decision
One paragraph.

## Why
Key context and tradeoffs.

## Impact
- systems affected
- follow-up required
```