Traceability Matrix
The cross-project coverage view. Each row is a module; each column is a link in the chain from requirement to running-and-operable. An empty cell (—) is a visible gap, not an omission.
✓ linked— gap
This is the lightweight stand-in for a tooled Requirements Traceability Matrix (RTM): maintained by convention (see module docs structure §6), not auto-generated. Pick any module and walk its whole chain from this one table.
How to read this
| Column | Means |
|---|---|
| Module | The product module hub (/modules/<tier>/<module>) |
| Phase | Roadmap phase (see Roadmap) |
| PRD | Product requirement doc(s) for the increment |
| URD | User requirement doc (requirements + acceptance) |
| ADR | Architecture decisions in the implementing package |
| Dev | Developer package docs (how it's built) |
| Tests | Test cases traceable to URD IDs |
| Runbook | Operate / deploy docs |
Core modules
| Module | Phase | Status | PRD | URD | ADR | Dev | Tests | Runbook |
|---|---|---|---|---|---|---|---|---|
| Inventory | 1–3 | In-progress | ✓ | ✓ | ✓ | ✓ | ✓ | — |
| Products | 1 | In-progress | ✓ | ✓ | ✓ | ✓ | ✓ | — |
| Orders | 1 | In-progress | ✓ | ✓ | ✓ | ✓ | ✓ | — |
| Payment | 1 | In-progress | ✓ | ✓ | ✓ | ✓ | ✓ | — |
| Tax & Invoice | 1 | In-progress | ✓ | ✓ | ✓ | ✓ | ✓ | — |
| Commerce | 1 | In-progress | ✓ | ✓ | ✓ | ✓ | ✓ | — |
| User Management | 1 | In-progress | ✓ | ✓ | ✓ | ✓ | ✓ | — |
| Permissions | 1 | In-progress | ✓ | ✓ | ✓ | ✓ | ✓ | — |
| Device | 1 | In-progress | ✓ | ✓ | — | — | ✓ | — |
| Reports | 1–3 | In-progress | ✓ | ✓ | — | ✓ | ✓ | — |
| Expenses | 1–2 | In-progress | ✓ | ✓ | ✓ | ✓ | ✓ | — |
| CRM | 1–3 | Planned | ✓ | ✓ | — | ✓ | ✓ | — |
| Helpdesk | 2–3 | Planned | ✓ | ✓ | ✓ | ✓ | ✓ | — |
Gaps to close
Runbook is the systemic gap
The recurring empty column is Runbook — operate/deploy docs are not yet linked per module (the /runbook section holds only overview stubs today).
Highest-priority gaps for the Phase-1 UAT modules:
- Runbook entries for inventory worker, payment webhooks, invoice/ledger generation, and the alpha deploy.
- ADR ↔ module reciprocal links — currently ADRs are only referenced from dev pages (see WK22 review).
- Device has no developer package or ADRs (it is FE/integration-driven).
Related Pages
- Delivery hub · Roadmap · Sprint Reviews
- Module Docs Structure — the ID & linking rules this matrix enforces
- Modules — the module hubs themselves