What is Human-AI Orchestration (HAIO)? — A practitioner reference
Search intent
You have already read the launch narrative. This article is the reference sheet: what HAIO names, what must be true in the protocol, and what is not implied by “workflow automation” or “agent framework.”
Definition (protocol-level)
Human-AI Orchestration (HAIO) is a class of systems where work crosses human and machine actors under explicit delegation, policy, and provenance — so that who acted, under what authority, and with what uncertainty can be verified at the handoff, not reconstructed from logs after the fact.
That handoff is the differentiator: not the model, not the DAG shape — accountability at the boundary where judgment, scope, and irreversibility meet.
Why this is a category, not a marketing label
Adjacent categories optimize for different primary goods:
| Adjacent category | Primary optimization |
|---|---|
| Workflow automation | Throughput and connectivity |
| Agent frameworks | Tool routing and developer velocity |
| Identity providers | Authentication to a tenant |
| LLM orchestration | Model calls and retries |
HAIO optimizes for governed coordination across those layers: portable identity, capability truth for routing, policy and escalation, and machine-attributable provenance — so the same story holds in audit, in court prep, and in engineering postmortems.
What changes when you take HAIO seriously
- Handoffs are first-class — Every meaningful transition emits or preserves a decision-shaped artifact (receipt), not only a log line.
- Delegation precedes execution — Agents do not “inherit” user power by UI session alone; scopes are explicit and revocable.
- Uncertainty is routed — Low confidence triggers escalation, not silent best-effort completion (see Fourth Law patterns in production governance).
Practitioner checklist
Before you recommend a stack, ask:
- Can we name the actor (human, agent, service) for each externally visible step?
- Can we show the delegation that permitted the action?
- Can we cite the policy version that applied?
- If confidence was insufficient, what escalation path fired — and what record exists?
If those four are muddy, you are not debating HAIO implementation details — you are missing architecture.
Next steps
- Product: What is HUMΛN? · Platform overview · Workflows
- Docs: Building your first extension · How platform extensions work
- Related: Introducing HAIO (narrative launch angle) · Agents before and after the trust layer · Four lines of Python, protocol enforced
This post complements introducing-haio.md, which remains the narrative introduction; this file is the evaluator/engineer reference.
Code & Docs