Backlog (Epics & Stories) — Per-Epic Navigation
Companion to:
07-epics-and-user-stories.md(the canonical, full-AC monolith). Thisbacklog/folder provides AI-loadable per-epic navigation files so an agent can load a single epic's slice (~5-10 KB) instead of the 90 KB master.
The master 07 doc remains the single source of truth for acceptance criteria, services, frontend surfaces, DoD refs, test types, and complexity. Files in this folder are navigation indices, not content duplicates.
Contents
| File | Purpose | Audience |
|---|---|---|
EPICS.md | Slim index of all 20 epics (ID, title, owner, journeys, wave, story count). | All. |
USER_STORIES.md | Flat index of all 161 stories (ID, title, epic, complexity, wave). | All. |
IMPLEMENTATION_STATUS.md | Interim monorepo implementation status per story (In progress / Done), until Jira MEL is system of record. | Engineers + agents shipping code. |
EP-MEL-NN.md (×20) | Per-epic file: outcome, owner, journeys, cross-cutting AC, story list. Each story links back to its anchor in 07-epics-and-user-stories.md. | AI agents and engineers focusing on one epic. |
SERVICE_TO_STORIES.md | Reverse index: service → list of story IDs that touch it. | Service-oriented work and audits. |
Development workflow (implementation monorepo)
All coding work must follow ../standards/DEVELOPMENT_WORKFLOW.md: backlog work item (US-MEL-* and/or MEL-*) per change, specs in freeze (changes only through ADRs and approved doc updates), and IMPLEMENTATION_STATUS.md updated when a story’s implementation status changes. No ad-hoc features outside the spec corpus and backlog.
Loading rules for AI agents
- One epic in scope → load
backlog/EP-MEL-NN.md+ the matching anchored sections in../07-epics-and-user-stories.md. - One service in scope → load
backlog/SERVICE_TO_STORIES.md+ the matchingEP-MEL-NN.mdfiles for the listed stories, andbacklog/IMPLEMENTATION_STATUS.mdif you need to know what is already built vs still open. - Cross-cutting work (e.g., observability) → load
backlog/EPICS.mdfor the index, then drill into specific epics as needed. - Never treat a
backlog/file as more authoritative than the master 07 doc. If they disagree, the master wins; open a fix PR for the per-epic stub.
Cross-references
- docs/07-epics-and-user-stories.md — canonical backlog.
- docs/13-traceability-matrix.md — derived cross-views.
- docs/standards/JIRA_PROJECT_SETUP.md — Jira project structure.
- docs/standards/JIRA_TICKET_TEMPLATE.md — per-issue templates.
- docs/roadmap/jira-epic-based-sprint-ruleset.md — sprint planner rules.