user story

Type: noun (compound)
Register: technical, operator
Domain: platform-wide

Definition

A statement of what a user needs and why, written from their perspective. User stories are the WHAT — they define the value the system must deliver. Boards implement them. Architecture enables them. A user story without a board item implementing it is an unmet need.

Properties

• Role-based — written as "As a [role], I want [capability] so that [value]"
• Has a key — e.g., WS-S1, PA-S3. Used in board item story: labels for traceability.
• Has a success metric — how you know the story is satisfied
• Lives in its own note — note_type: user-story, slug: story-{project}-{key}
• Indexed on the project page — the project page lists all stories as a table with links
• Implemented by board items — board items carry story:{key} labels that trace back to the story

Why it matters

User stories are the reason work exists. Every board item should trace to a story — if it doesn't, ask why it's being built. Stories prevent building for building's sake.

Distinguishes from

Term	Difference
ticket / issue	A ticket is a unit of work that implements (part of) a story. The story is the need; the ticket is the work.
architecture	Architecture is HOW the system is shaped. Stories are WHAT the system must deliver. Board items connect them.

Relations

• belongs-to: project
• implemented-by: board items (via story: labels)
• enabled-by: architecture notes (via arch: labels on the same board items)