Work Order System Admin
Benchmarked against: Anthropic — Workspaces System: WO v4.0 (Cloud UB D1) Spec: ub-96dbb9947a3c (Captain Decision Record)
The Work Order (WO) system is SuperPortia's task management backbone. This admin page covers system configuration, state machine rules, RBAC permissions, and operational guidelines. For the developer-facing API, see Work Order API.
System design principles
| Principle | Implementation |
|---|---|
| WO is the only task channel | Constitution §3 — no verbal promises, no chat-based tasks |
| State machine enforced | Invalid transitions rejected by the system |
| RBAC built in | Different permissions for Captain, PM, Assignee, Requester |
| Full audit trail | Every transition logged with who, when, why |
| Gate conditions | Certain transitions require specific fields |
State machine
8 states with enforced transitions:
State definitions
| Status | Icon | Meaning |
|---|---|---|
pending | 🔴 | Created, awaiting acceptance |
accepted | :yellow_circle: | Agent accepted, not started |
in_progress | :blue_circle: | Work actively underway |
blocked | :orange_circle: | Cannot proceed, blocker identified |
review | :purple_circle: | Submitted for Captain review |
approved | :green_circle: | Captain approved — completed |
rejected | 🔴 | Captain rejected — needs rework |
cancelled | ⚪ | Cancelled (Captain only) |
Transition gates
Certain transitions require mandatory fields:
| Transition | Required fields | Who |
|---|---|---|
in_progress → review | completion_summary + actual_hours (> 0) | Assignee |
in_progress → blocked | notes (describe the blocker) | Assignee |
blocked → in_progress | notes (how it was resolved) | Assignee |
review → approved | review_notes | Captain only |
review → rejected | review_notes | Captain only |
Any → cancelled | notes (reason for cancellation) | Captain only |
If a required field is missing, the system returns an error with missing_fields hint.
RBAC permissions
| Role | Can do | Cannot do |
|---|---|---|
| Captain (夏哥, 小西) | Everything — approve, reject, cancel, patch any field | — |
| PM Agent | Patch: assignee, priority, due_date, estimated_hours, tags | Approve/reject/cancel |
| Assignee | Accept, update status, submit for review, patch: notes, summary, hours | Approve/reject/cancel, change assignee |
| Requester | Patch: description, acceptance_criteria, deliverables | Status changes, assignee changes |
Captain identities that have full permissions: 夏哥, 小西, system:captain-proxy.
WO ID format
IDs are auto-generated: WO-YYYY-MMDD-XXX
| Part | Meaning | Example |
|---|---|---|
WO | Work Order prefix | WO |
YYYY | Year | 2026 |
MMDD | Month and day | 0305 |
XXX | Random hex suffix | A1B |
Example: WO-2026-0305-A1B
Title convention
WO titles must start with a [Project-Category] prefix:
| Prefix | Example |
|---|---|
[SS1-Operations] | Ship 1 operational task |
[SP-Development] | SuperPortia platform development |
[EGS-CodeStandards] | EGS chapter 2 work |
[Infrastructure-Critical] | Critical infrastructure change |
[CatMints-Feature] | CatMints Cafe feature work |
This enables filtering WOs by project and category.
Valid agent identities
Only these identities can be assigned as WO assignee:
| Identity | Ship |
|---|---|
Mac App 小克 | SS1 |
Mac CLI 小克 | SS1 |
Mac App 小A | SS1 |
Mac CLI 小A | SS1 |
Win App 小克 | SS2 |
Win CLI 小克 | SS2 |
Win App 小A | SS2 |
Win CLI 小A | SS2 |
Web 小克 | SS3 |
小西 | Any |
夏哥 | Any |
system:cron | Automated |
system:webhook | Automated |
Dispatch engine integration
WOs can be executed automatically via the dispatch engine:
Engine selection should follow Cost Awareness rules:
- Free (Groq): Research, analysis, simple tasks
- Cheap (Gemini, DeepSeek): Quality-sensitive tasks
- Expensive (Claude): Only for code editing, file operations
Operational guidelines
| Guideline | Rule |
|---|---|
| Every task goes through WO | Constitution §3 — no exceptions |
| Submit for review when done | Include completion_summary + actual_hours |
| Captain reviews all WOs | Approve or reject with review_notes |
No WO stays in pending > 24h | Accept or discuss with Captain |
| Blocked WOs need notes | Describe what's blocking and potential solutions |
| Use Pre-Flight Check before starting | Especially for high-blast-radius WOs |
Related pages
| Page | Relationship |
|---|---|
| Work Order API | Developer-facing API reference |
| WO Status Transitions | State machine details |
| Fleet Management | Fleet-wide WO monitoring |
| EGS Compliance | WO compliance checks |
| Company Constitution | §3 — WO as only task channel |