# [Readable Name] — Requirements Dossier

## Overview

[2–4 sentences on the goal, background, and intended outcome]

## Confirmed Scope and Non-Goals

**Scope:**
- [What we ARE doing]

**Non-Goals:**
- [What we're NOT doing]

## Current State and Key Discoveries

- What exists today (with file:line references where helpful)
- Patterns/conventions to follow
- Constraints to respect

## Open Questions and Resolutions

- [Question 1]: [Resolution or "Pending – needs user input"]
- [Question 2]: [Resolution]

## Design Direction and Rationale

- Recommended approach and why
- Alternatives considered and why not chosen

## Impacted Areas and File Targets

- Likely files/directories to modify or create (explicit list)
- Dependencies or contracts to honor

## Risks and Mitigations

- Technical risks, operational risks, and mitigations

## Testing and Verification Emphasis

- Key automated checks (unit/integration/e2e)
- Manual verification must-haves and edge cases

## References

- Tickets, prior artifacts, reference examples, related plans
