Features & Specs
The single place to find any feature - search by name, module, or status, open its full spec, and see live status straight from Plane. Below: every feature's spec (the PRD register) and the per-module traceability chain.
Feature specs (PRDs)
One row per PRD, grouped by Epic. Status is live from each PRD's Plane work item -
Ready to devmeans the spec is locked and codeable. Click a PRD name for the document, or a Plane id for the work item.
Phase 2 · In progress22 PRDs21 of 22 ready
Phase 1 · Shipped35 PRDs34 of 35 ready
Uncategorized · needs a FEAT38 PRDs
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). It is the lightweight stand-in for a tooled Requirements Traceability Matrix (RTM), maintained by convention (see module docs structure §6), not auto-generated.
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 (AC) | ADR | Dev | Tests | Runbook |
|---|---|---|---|---|---|---|---|---|
| Commerce | 1-2 | In-progress | ✓ 9 | ✓ 26 | ✓ 3 | ✓ | - | - |
| User Management | 1-2 | In-progress | ✓ 6 | ✓ 15 | ✓ 5 | ✓ | - | - |
| Permissions | 1-3 | In-progress | ✓ 4 | ✓ 10 | ✓ 5 | ✓ | - | - |
| Licensing | 1-2 | In-progress | ✓ 3 | ✓ 9 | ✓ 3 | ✓ | - | - |
| Device | 1-3 | In-progress | ✓ 3 | ✓ 19 | ✓ 3 | ✓ | - | - |
| Products | 1-3 | In-progress | ✓ 8 | ✓ 28 | ✓ 3 | ✓ | - | - |
| Pricing | 1-3 | In-progress | ✓ 3 | ✓ 16 | ✓ 2 | ✓ | - | - |
| Inventory | 2 | In-progress | ✓ 16 | ✓ 56 | ✓ 6 | ✓ | - | - |
| Sale | 1-2 | In-progress | ✓ 12 | ✓ 20 | ✓ 5 | ✓ | - | - |
| Payment | 1 | Built | ✓ 1 | ✓ 2 | ✓ 4 | ✓ | - | - |
| Finance | 1-2 | In-progress | ✓ 5 | ✓ 13 | ✓ 3 | ✓ | - | - |
| Tax & Invoice | 1-2 | In-progress | ✓ 7 | ✓ 11 | ✓ 3 | ✓ | - | - |
| Customer | 1-2 | In-progress | ✓ 5 | ✓ 6 | ✓ 5 | ✓ | - | - |
| Reports | 1-3 | In-progress | ✓ 5 | ✓ 7 | ✓ 5 | ✓ | - | - |
| Helpdesk | 1-2 | In-progress | ✓ 3 | ✓ 11 | ✓ 3 | ✓ | - | - |
Computed from the content tree at build time: ✓ N = artifact files that actually exist; - = absent. URD shows acceptance (AC) blocks. Test cases and per-module runbooks are not yet authored - a - is a real gap, not decoration.
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
- Roadmap · Sprint Reviews · Modules
- Module Docs Structure - the ID & linking rules this matrix enforces