Workforce
Workforce puts humans in the execution path as a first-class protocol feature. When a governed call needs judgment an agent should not exercise alone — low confidence, high stakes, an explicit gate you configured — HumanOS routes it to a qualified person. Not a notification into the void: a task, with context, to someone whose Capability Graph evidence says they can handle it.
The model
| Piece | What it does |
|---|---|
| Escalation | ctx.escalate() from agent code, or a policy gate firing — either way, work enters a human queue |
| Capability routing | The queue is not round-robin. Tasks route on evidence: who has demonstrably done this kind of work |
| Context transfer | The human sees what the agent saw — inputs, reasoning trail, prior steps. No handoff amnesia |
| Decision record | The human's decision lands in the Ledger with the same signed provenance as any agent action |
In-org today, extra-org in closed beta
Inside your organization, this is live: escalation queues, the Workforce inbox, capability-routed review — running in the Console now. Routing to verified experts beyond your org — on-demand external judgment under the same trust rules — is in closed beta with design partners; the Enterprise page tracks its current status.
Not a gig marketplace
Workforce routes on demonstrated capability and produces signed decisions under delegation — it is not a labor marketplace and not a staffing product. The human is accountable, attributed, and context-equipped, which is precisely what ad-hoc "send it to the ops channel" escalation never provides.
Work with Workforce
- Patterns: workforce patterns — escalation wiring, queue handling, decision capture
- CLI:
human executionfor monitoring escalated runs — see the CLI reference - Product view: the Workforce pillar shows the live queues and inbox
Next in the ladder: Academy →