| Q | Raised against the PRD | Answer |
|---|---|---|
| Q1Gap |
Canonical invoice/payment status model: the PRD gives 4 conflicting enums (§13.3 §13.6 F-47 §12.2). Is there one status field, or two? What are the exact values? |
One invoice lifecycle status, single field: Ready to Invoice (pre-send) → Unpaid / Partial / Paid / Overdue / Cancelled (once sent). Separately: Payments/reconciliation = Pending / Saved as Task / Reconciled / Voided; Credit = Open / Partially Applied / Fully Applied. Badge colors not yet specified. the designer, 2026-07-21 |
| Q2ContradictionBlocking |
FR-9 says skip/override/cancel are “removed; team lead only”; the FR-31 permissions matrix grants Dispatchers “Skip current provider / tier,” “Override WO to manual,” “Cancel WO.” Which governs the dashboard’s action affordances? |
Team-lead-only (per the FR-9 v4 design-review change). FR-31 dispatcher skip/override/cancel rows treated as stale. [PRD-CLARIFIED] the designer, 2026-06-16 |
| Q3ContradictionBlocking |
FR summary table marks FR-5/6 (PM/Survey sweeps) “Yes (Post MVP)”; the WO-Types table marks PM “MVP (manual + optional auto).” Is the PM Sweep Dashboard (C5) in the MVP build or deferred? |
Defer to post-MVP (summary table authoritative). C5 stays documented but out of the current build. [PRD-CLARIFIED] the designer, 2026-06-16 |