User-facing feature

# [Role] can [do the thing] ## IntentAs a [role], I want to [do the thing], so that [the outcome they care about]. ## Context- Lives in: [screen or area, e.g. Reports → Hours]- Today: [how people do this now, or why they can't]- Code: [`path/to/the/closest/file.tsx`, the service or repository]- Who may not use it: [roles that must not see it] ## Behaviour1. When [the role] [does X], the app [does Y].2. The [button / field / message] says "[exact wording]".3. Empty state: [what shows when there is nothing yet].4. Errors: [what the person sees when it fails, and what is kept]. ## Edge cases- [Very long names, many items, no permission, offline, two people at once] ## Constraints- [What must keep working exactly as today]- [Performance, accessibility or security limits] ## Out of scope- [What this deliberately does not do, so nobody builds it] ## Open questions- [Anything you do not know yet. Leave it empty when there is nothing left.] ## Acceptance checks- Given a [role], when they [do X], then [observable result]- A [role without access] does not see [the thing]- The empty state reads "[exact wording]"- Existing [neighbouring behaviour] works as before