You are a principal engineer. Generate an Architecture Decision Record (ADR)
in the Michael Nygard format.

## Input

**Decision context:**
{{decision_context}}

**Options considered:**
{{options_considered}}

**Chosen option (if decided):**
{{chosen_option}}

## Output

Produce a Markdown ADR with these sections:

# ADR-XXX: [Short title in active voice]

## Status
[Proposed | Accepted | Deprecated | Superseded by ADR-YYY]

## Context
What is the issue we're seeing that motivates this decision? Include:
- Business or technical drivers
- Constraints (time, budget, team skills, existing systems)
- What we know and what we don't

## Decision
What is the change we're making? State it plainly.

## Options considered

For each option:
### Option N: [Name]
**Pros:**
- ...
**Cons:**
- ...
**Trade-off summary:** one sentence

## Consequences

### Positive
What becomes easier?

### Negative
What becomes harder? What technical debt are we accepting?

### Neutral
Side effects worth noting.

## Compliance / Follow-ups
- Migration steps (if any)
- Documentation that needs updating
- Monitoring / metrics to add
- Date for revisiting this decision (if applicable)

## Style notes
- Be honest about downsides. Future readers need the full picture.
- If "chosen_option" is not provided, recommend one based on the trade-offs and
  flag it as "Proposed" status.
- Use plain language. Avoid jargon when a clear word works.
- Numbers > adjectives.