# [Module Name] — Business Context

> **Purpose:** [One sentence — what this module does for the business]

## Key Rules

[Numbered list of business rules, ordered by business impact:
1. Security and money-handling rules first
2. Workflow enforcement rules second
3. Data quality rules third

Each rule should be understandable by someone who has never seen code.
No file paths, line numbers, or technical jargon.]

1. [Rule]
2. [Rule]

## User Flows

[3-5 most important user journeys. Prioritize flows that involve
status transitions or multi-step processes.]

1. **[Flow name]** — [Actor] does [action] → [result] → [what happens next]
2. ...

## Constraints

[Business constraints that affect product decisions]

- [Constraint]

## Open Questions

[Product-level ambiguities that stakeholders should weigh in on.
NOT code-level issues — those are resolved in the technical spec.
These are genuine business decisions that may need revisiting.]

- [Question]
