Category thesis

Agent work needs a delivery protocol.

AI agents can write, inspect and repair software. What teams still lack is a shared protocol for deciding what counts as delivered. Orcho names that missing layer: typed plans, review contracts, readiness gates, event timelines and evidence bundles that survive the worker session.

PUBLIC ALPHA

Read technical protocol Run a pilot with us

plan accepted

validate_plan accepted

implement evidence open

review_changes findings open

Problem

Private sessions do not make a delivery system.

A chat transcript can explain what happened, but it rarely defines a durable plan, a gate result or a handoff decision. Teams need the run itself to carry the contract.

Plans should be typed enough for another phase to consume.
Review should alter control flow, not sit outside it.
Evidence should outlive the agent that produced it.

Protocol

The phases become the product surface.

plan, validate_plan, implement, review_changes, repair_changes and final_acceptance form the core delivery vocabulary. Each phase can emit artifacts and findings that later tools can inspect.