Bilingual Navigation: English (this document) · Versión en Español Up: Repository Portal
Goal: validate every business initiative through the Discovery gate before any design work begins (BR-001).
Objectives:
- Define the Discovery domain model (Initiative, Backlog, Epic, UserStory).
- Generate the agile backlog upon gate approval.
Epics
The Tracker backlog is organized into 7 epics covering the 5 value-stream modules plus cross-cutting capabilities. Click an epic to view its detailed story breakdown.
| Epic | Module | Goal | Stories | Pts | Priority Mix |
|---|---|---|---|---|---|
| EPIC-000 | Discovery (Gate 1) | Ensure no initiative proceeds without a validated business case | 14 | 50 | 9 Must · 3 Should · 2 Could |
| EPIC-001 | Design (Gate 2) | Translate requirements into immutable contracts before coding | 11 | 37 | 9 Must · 1 Should · 1 Could |
| EPIC-002 | Construction (Gate 3) | Every line of code traceable to an approved contract | 14 | 40 | 10 Must · 4 Should |
| EPIC-003 | QA (Gate 4) | Enforce a quality gate that no release can bypass | 11 | 31 | 9 Must · 2 Should |
| EPIC-004 | Release (Gate 5) | Deployment command center cross-referencing dates with quality | 10 | 28 | 7 Must · 3 Should |
| EPIC-005 | Cross-cutting | Governing platform for all agent execution and infrastructure | 23 | 77 | All Must Have |
| EPIC-006 | Cross-cutting | Real-time SDLC health and architectural compliance visibility | 12 | 36 | All Must Have |
Note: EPIC-005 and EPIC-006 also host cross-EPIC stories (stories shared with other epics). Total unique stories: 114.
ID Standard: Epics use the pattern EPIC-{NNN}. User stories use US-{MOD}-{NNN} where {MOD} is a 3-letter module code (DIS, DES, CON, QA, REL, GOV, ART, MET, INT, INF, CLI). See T-011.
Domain Model (DDD)
| Document | Description | Purpose | Type |
|---|---|---|---|
| DDD Model | Discovery Bounded Context: Initiative, Backlog, Epic, UserStory aggregates with tactical DDD detail (ubiquitous language, entities, value objects, domain events, invariants, Mermaid maps) | Understand the Discovery domain aggregates and their internal mechanics before writing code | DDD |
Business Modeling
| Document | Description | Purpose | Type |
|---|---|---|---|
| Discovery Canvas | Business model canvas: problem definition, value proposition, ROI, KPIs (DORA & SPACE), risks and assumptions, gate viability | Align on the business rationale and viability check before requirements are written | Canvas |
Scope and Backlog
| Document | Description | Purpose | Type |
|---|---|---|---|
| Functional Scope | System functional scope (SDLC suite): the 5 modules with their core workflow, cross-cutting capabilities, out of scope, and artifacts per phase | Know exactly what the suite covers before scope is frozen | Scope |
| User Stories | SM Agent breakdown: 114 stories, 372 points, Gherkin acceptance criteria, sprint sequencing | Feed sprint planning and trace every story back to its epic and gate | Backlog |