# I want so "> ## Context & Why Constitution principles this feature depends on: - [§ ](../../constitution.md#) — Related: . ## User Journey ## Requirements > One requirement per line, each with a `REQ-NNN` id and one EARS pattern. Include the > patterns the feature actually needs — do not force all five, but a mutating feature almost > always needs at least one Event-driven and one Unwanted-behavior requirement. - **REQ-001** (Ubiquitous) — The `` shall ``. - **REQ-002** (Event-driven) — When ``, the `` shall ``. - **REQ-003** (State-driven) — While ``, the `` shall ``. - **REQ-004** (Optional-feature) — Where ``, the `` shall ``. - **REQ-005** (Unwanted-behavior) — If ``, then the `` shall ``. ## Acceptance Criteria > One measurable criterion per REQ-NNN. Numbers, limits, status codes — never adjectives. - **REQ-001** — . - **REQ-002** — . - **REQ-003** — . - **REQ-004** — . - **REQ-005** — . ## Out of Scope - - <…> ## API / Contract Stub ## Data Model Changes `, and the rollback note. Write "none" if not applicable.> ## Security Considerations ## Open Questions > Each item is a BLOCKER until resolved. Empty this list before implementation starts. - [ ] — owner: - [ ] — owner: ## Traceability | REQ-ID | Task ID(s) | Test ID(s) | Status | |---|---|---|---| | REQ-001 | | | Planned | | REQ-002 | | | Planned | ## Persona Review Results | Persona | Status | Key Findings | Resolved | |---|---|---|---| | Requirements Engineer | PENDING | | | | Developer | PENDING | | | | Security | PENDING | | | | DevOps | PENDING | | | | UI/UX | PENDING | | | | Architect | PENDING | | |