kibin/NetForge
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(03): create phase plan

Browse Source 
Phase 03: Operational Modules
- 5 plans in 3 waves
- Wave 1: 03-01 (zones), 03-03 (tickets) — parallel
- Wave 2: 03-02 (collector collections), 03-04 (job orders) — parallel
- Wave 3: 03-05 (technician compensation) — sequential
- Ready for execution

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
kevin-asprec
2026-03-05 06:05:55 +08:00
parent 4b4f7bce3b
commit ef0150654b
6 changed files with 1086 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
.planning/ROADMAP.md
View File

@@ -72,14 +72,14 @@ Plans:
3. Staff can create a support ticket from a client call, convert it to a job order, assign it to a technician, and the technician can mark it complete with outcome notes — all status transitions are synchronized between ticket and job order
4. The system generates a daily collection summary report per collector showing payments collected, remitted, and any variance
5. Admin can configure per-job compensation rates by job type; the system generates a compensation summary per technician per period correctly for both per-job and monthly-salary models
**Plans**: TBD
**Plans**: 5 plans
Plans:
- [ ] 03-01: Collector zone management — zone/territory setup, subscriber-to-collector assignment, collector role scoping (COLL-03, AUTH-03)
- [ ] 03-02: Collector field collection and remittance — payment logging by collector, two-party remittance verification, journal entry on verified remittance, daily summary report (COLL-01, COLL-02, COLL-04, COLL-05, COLL-06)
- [ ] 03-03: Ticketing system — ticket creation from staff or client call, priority and category, ticket lifecycle (open → assigned → resolved → closed), client portal ticket submission (TICK-01, TICK-05)
- [ ] 03-04: Job order workflow — ticket-to-job-order conversion, technician assignment, status tracking (pending → in progress → completed), outcome notes, ticket status synchronization (TICK-02, TICK-03, TICK-04)
- [ ] 03-05: Technician management — profiles, compensation model configuration (per-job rates by type, monthly salary), CompensationService, period compensation summary (TECH-01, TECH-02, TECH-03, TECH-04)
- [ ] 03-01-PLAN.md — Zone management: zone CRUD, subscriber-to-zone assignment, collector-to-zone assignment, collector-scoped subscriber queries (COLL-03, AUTH-03)
- [ ] 03-02-PLAN.md — Collector field collection and remittance: FIFO payment via Cash in Transit, two-party remittance verification with JE, daily collection summary report (COLL-01, COLL-02, COLL-04, COLL-05, COLL-06)
- [ ] 03-03-PLAN.md — Ticketing system: ticket CRUD with lifecycle (OPEN/ASSIGNED/RESOLVED/CLOSED), admin-configurable categories with ISP defaults, priority levels (TICK-01, TICK-05)
- [ ] 03-04-PLAN.md — Job order workflow: ticket-to-job conversion (1:many), technician assignment, status lifecycle, auto-resolve ticket when all jobs complete (TICK-02, TICK-03, TICK-04)
- [ ] 03-05-PLAN.md — Technician management: profiles with skills/zone, hybrid compensation model (per-job + salary), CompensationService, period summary report (TECH-01, TECH-02, TECH-03, TECH-04)
---