Work Order API

Benchmarked against: Anthropic — Using the Messages API MCP Tools: create_work_order, list_work_orders, get_work_order_detail, accept_work_order, update_work_order_status, complete_work_order, verify_work_order, patch_wo_fields Authority: Company Constitution §3 — "Work orders are the only task channel"

The Work Order system is SuperPortia's only task channel. No verbal promises, no chat-based assignments. Every task goes through a formal WO with tracked state transitions and role-based access control.

---

Quick start

Create a work order

create_work_order(
    title="[SS1-Operations] Deploy MTAAA Text Subgraph to production",
    assignee="Mac CLI 小克",
    project="SS1",
    description="Deploy the text_subgraph pipeline from dev to production...",
    priority="high",
    due_date="2026-03-10",
    estimated_hours=4,
    acceptance_criteria="Pipeline processes entries with >90% accuracy",
    deliverables="Deployed pipeline + test results"
)

Response

{
  "order_id": "WO-2026-0305-001",
  "status": "pending",
  "title": "[SS1-Operations] Deploy MTAAA Text Subgraph to production",
  "assignee": "Mac CLI 小克",
  "project": "SS1",
  "created_at": "2026-03-05T09:30:00Z"
}

---

WO ID format

IDs are auto-generated by the system: WO-YYYY-MMDD-NNN

Component	Meaning	Example
WO	Work Order prefix	WO
YYYY	Year	2026
MMDD	Month-day	0305
NNN	Hex sequence (per day)	001, 0A3, F72

---

Title convention

Titles must start with a [Project-Category] prefix:

[SS1-Operations] Deploy MTAAA Text Subgraph
[SP-Development] MTAAA P10 — Self-tuning
[EGS-CodeStandards] Research & Upgrade Ch.2
[Infrastructure-Critical] Migrate Dispatch Worker

Component	Values
Project	SS1, SS2, SS3, SP (SuperPortia), EGS, Infrastructure
Category	Operations, Development, CodeStandards, DevWorkflow, Critical

---

Available tools

create_work_order

Creates a new work order. The system auto-generates the WO ID.

Parameter	Type	Required	Description
title	string	Yes	Must start with [Project-Category] prefix
assignee	string	Yes	Exact agent identity (see valid identities below)
project	string	Yes	e.g., SS1, SP, catmints-cafe
description	string	No	Detailed work description
priority	string	No	high / medium (default) / low
requester	string	No	Default: 夏哥
due_date	string	No	YYYY-MM-DD format
estimated_hours	number	No	Estimated hours to complete
acceptance_criteria	string	No	What defines "done"
deliverables	string	No	Expected outputs
related_wo_ids	string	No	JSON array of related WO IDs
parent_wo_id	string	No	Parent WO for sub-work-orders
tags	string	No	JSON array of tags
notes	string	No	Additional notes

Valid agent identities

Identity	Ship	Platform
Mac App 小克	SS1	Claude Desktop App (Code tab)
Mac CLI 小克	SS1	Claude Code CLI
Win App 小克	SS2	Windows Claude App
Win CLI 小克	SS2	Windows Claude CLI
Web 小克	Any	Web-based Claude
小西	Any	Claude Chat (Strategist)
Mac App 小A	SS1	Antigravity agent (App)
Mac CLI 小A	SS1	Antigravity agent (CLI)
Win App 小A	SS2	Antigravity agent (App)
Win CLI 小A	SS2	Antigravity agent (CLI)
夏哥	—	Captain (manual tasks)
system:cron	—	Scheduled automation
system:webhook	—	External trigger

list_work_orders

Query work orders with filtering. By default shows only in-progress orders.

Parameter	Type	Default	Description
status	string	null	Filter by status
project	string	null	Filter by project
assignee	string	null	Filter by assignee
include_completed	bool	false	Include completed/cancelled
limit	number	20	Max results

get_work_order_detail

Returns full WO details including transition history — every state change with timestamp, operator, and notes.

get_work_order_detail(order_id="WO-2026-0305-001")

accept_work_order

Move from pending → accepted. Signals the assignee has seen and will work on the WO.

accept_work_order(order_id="WO-2026-0305-001", assignee="Mac CLI 小克")

update_work_order_status

General status transition. Must follow the state machine rules.

update_work_order_status(
    order_id="WO-2026-0305-001",
    new_status="in_progress",
    notes="Starting implementation"
)

complete_work_order

Submit for review (in_progress → review). Requires a completion summary.

complete_work_order(
    order_id="WO-2026-0305-001",
    summary="Deployed Text Subgraph to production. 327 entries processed, 94% accuracy.",
    actual_hours=3.5
)

verify_work_order (Captain only)

Captain approves or rejects a completed WO.

# Approve
verify_work_order(order_id="WO-2026-0305-001", approved=True, notes="Verified accuracy metrics")

# Reject — returns to assignee for revision
verify_work_order(order_id="WO-2026-0305-001", approved=False, notes="Accuracy below threshold")

patch_wo_fields

Update specific fields with role-based permissions:

Role	Can modify
Captain (夏哥/小西)	All fields
PM Agent	assignee, priority, due_date, estimated_hours, tags
Assignee	notes, completion_summary, actual_hours
Requester	description, acceptance_criteria, deliverables

---

Dispatch engine

Work orders can be executed by the Dispatch Engine using different AI engines:

dispatch_work_order(
    work_order_id="WO-2026-0305-001",
    engine="groq"  # or gemini, deepseek, claude, ingest, etc.
)

Event-driven dispatch: Only call when Captain or 小西 explicitly decides to execute. Do not dispatch proactively.

---

Constitution rules

From Company Constitution:

Rule	Requirement
§3	Work orders are the only task channel. No verbal promises.
§8	Start or report on a WO in the same session. Never say "next time."
§7	All reports use format: Status (color) / timestamp / key update / next step / notes

---

Related pages

Page	Relationship
WO Status Transitions	State machine rules and transition gates
Dispatch Engine	Execute WOs with AI engines
Company Constitution	§3 — WOs as the only task channel
HITL/HOTL	Decision boundaries for WO approvals
Features Overview	System overview