docs: add Plan 5 (subcontractor task state machine)
This commit is contained in:
@@ -515,7 +515,8 @@ Each plan = one phase, produces working/verifiable software on its own, and is e
|
||||
### Plan 5 — Subcontractor task state machine
|
||||
- **What:** the §10 stage machine (Not Assigned → Assigned → Pre-Work Inspection → Work In Progress → On Hold ↔ → Post-Work Review → Pass→Completed / Fail→Rework), per-transition notes + actor + timestamp, pre/post-inspection attribution; owner table gains Task Category + Assigned Date; richer task modal (stage timeline + issues with photos).
|
||||
- **Why:** mirrors the real field workflow and gives the subcontractor an interactive inbox; the review/rework loop is a credible operational story feeding owner-side visibility.
|
||||
- **How:** extend `MOCK_SUBCONTRACTOR_TASKS` + status constants + mutators in `mockStore.jsx` (sequential); update the owner `SubcontractorTasksPage` (columns) and the task modal/detail components (parallel — different files). Verify: stages advance with notes in both owner and subcontractor views.
|
||||
- **How:** extend `MOCK_SUBCONTRACTOR_TASKS` + status constants + mutators in `mockStore.jsx` (sequential); update the owner `SubcontractorTasksPage` (columns) and the task modal/detail components (parallel — different files). Verify: stages advance with notes in both owner and subcontractor views. (Note: much of the machine already exists — `setSubcontractorTaskStatus` writes history+activities+notifications for any status, and the subcontractor detail page already has a status picker/history/timeline; Plan 5 mainly adds the §10 stages — Pre-Work Inspection / Post-Work Review / Rework Needed — the owner review gate, the Category/Assigned-Date columns, and the owner modal stage timeline.)
|
||||
- **Plan file:** `docs/superpowers/plans/2026-05-29-plan5-subcontractor-state-machine.md`.
|
||||
|
||||
### Plan 6 — Subcontractor portal data + project parity
|
||||
- **What:** realistic data on `/subcontractor/*`; a subcontractor viewing their task sees the **same project** the owner sees (permitted subset — address, scope, schedule, their slice of budget/payments).
|
||||
|
||||
Reference in New Issue
Block a user