Design

Settle choices that implementation must not invent. A useful design states the behavior, the main tradeoff, and the proof before code is written.

Process

1. Read the request, repository instructions, relevant code, and linked material.
2. Identify choices that would change behavior, interfaces, data, errors, security, operations, or tests.
3. Ask blocking questions before drafting. Ask only when the answer would change the design, and recommend an answer. Record non-blocking questions and a recommended default under Open questions.
4. Write docs/<feature-slug>/design.md using the numbered shape below. Keep it short and in order. Omit only sections that do not apply.
5. Run the review pass. Fix what you can. List the rest under Open questions.
6. Stop with the proposed design ready for review. Do not plan or implement it.

Document shape

# <Title>

> **Status:** Proposed for review