01 Worker routing
Route by phase, not brand loyalty.
Different workers can be useful for hypothesis, planning, implementation, review or inspection. The protocol keeps their outputs comparable.
Anti-lock-in
Your agents will change. Your delivery protocol should not.
Orcho ships runtimes for Claude Code, Codex, Gemini and Claude-compatible wrappers, with a registry for plugin runtimes. Workers remain replaceable participants under one delivery record, so changing a worker does not erase plan history, gates or evidence.
PUBLIC ALPHA
evidence_bundle / run 2026-05-26 inspectable
typed plan cross_plan.md
gate findings review_changes.json
run diff diff.patch
event spine events.jsonl
cost split metrics.json
handoff decision phase_handoff.json
02 Record
The durable object is the run.
Typed plans, findings, diffs, event timelines and handoff decisions remain the source of truth after a worker session ends.
Next step
Move from the claim to the operating surface.
Inspect the technical contract, watch the proof, or run Orcho on one task. The deeper layer is always one explicit step away.