Design Doc

1. Read the brief and any linked docs, code, or plans. Ask one question at a time, with a recommended answer, only when a missing fact would change the design.
2. Write docs/<design-slug>/design.md, 1-3 pages, using the template below. Omit sections that do not apply.
3. Stop after writing. Do not continue into spec, plan, or implementation until the human confirms.

Rules

• Make the design choice and its tradeoffs easy to review.
• Focus on decisions code will not explain later.
• Do not copy full schemas, APIs, or code unless the exact shape is central.
• Leave Status as Draft and Decision empty. Both are filled during review.

Template

# <Title>

**Status:** Draft | In review | Approved
**Author:** <name>  **Date:** <date>