Or Orcho Install the public alpha

Protocol hub

The run is the protocol boundary.

Orcho models agent work as typed, inspectable runs. The protocol defines how a task becomes a plan, how gates approve or reject work, how evidence is attached and how a run can halt, resume or finish.

TECHNICAL PROOF Route status
Plans Gates
run / protocol gated
plan accepted
validate_plan accepted
implement evidence open
review_changes findings open
repair_changes queued
final_acceptance awaiting signoff

Surface

Typed artifacts before broad claims.

The protocol starts with plan contracts, review findings, phase events, run diffs, metrics and evidence bundles. Each artifact gives a later tool something stable to inspect.

  • plan defines work scope and interfaces.
  • validate_plan checks the plan before implementation.
  • review_changes and final_acceptance can block release.
  • events and evidence preserve the run after the worker exits.

Boundary

The worker is not the boundary.

Claude, Codex, Gemini, Cursor, Cline and internal scripts can all be routed through the same delivery vocabulary when the run owns the contract.