Typed plans
Architect output becomes structured work with explicit file scope, interfaces and checks.
Technical portal
Orcho coordinates agent work as typed, provable runs.
Orcho is a local-first control plane for cross-agent, cross-project software work. A run is the protocol boundary: typed plans in, review contracts and phase events through, evidence bundles and an explicit readiness verdict out.
Pipeline
Agents ⟳² ( ▶ plan [Claude] → validate_plan [Codex] ) → implement [Claude] → ⟳² ( review_changes [Codex] → repair_changes [Claude] ) → final_acceptance [Codex] PLAN claude-opus-4-7 high
VALIDATE_PLAN gpt-5.5 medium
IMPLEMENT claude-opus-4-7 high
REVIEW_CHANGES gpt-5.5 medium
REPAIR_CHANGES claude-opus-4-7 high
FINAL_ACCEPTANCE gpt-5.5 low
run 2026-05-26 / lifecycle gated
plan accepted
validate_plan accepted
implement evidence open
review_changes findings open
repair_changes queued
final_acceptance awaiting signoff
Execution core
The CLI owns the run.
Orcho starts as a CLI-first engine: interactive in a developer TTY, structured for headless CI, durable enough that every other surface inspects the same run record instead of inventing its own history.
Review contracts
review_changes emits findings that can block release or route the run through repair_changes.
Inspectable record
Events, run diffs, metrics and handoff decisions become the trail for later readers and tools.
Evidence
Short summaries first. Artifacts remain reachable.
The evidence bundle pins the typed plan, gate findings, run diff, event spine, cost split and handoff decisions for a single run. Typed contracts are also a cost mechanism: in a live repeat-run, contract-first output cut API-equivalent cost from roughly $0.56–$0.69 to $0.15–$0.23 on the same task.
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
mcp_control_loop / run 2026-05-26 observable
start spawn run
watch phase events
handoff human decision
resume same run
inspect evidence
MCP available
MCP exposes the run without owning it.
The MCP server is the programmatic control surface today: start, watch, handoff, resume and inspect the same CLI-backed runs from any MCP client.
Cross-project
One feature, per-project runs, one integrated record.
The cross-run supervisor projects a shared plan into project-specific work, then accepts at system level: a child gate failure or missing integrated proof blocks the feature even when every local diff looks correct.
cross_project_handoff / spec-19f cross-project
api producer fixed
web contract guarded
mcp proof surface
review gate linked
Boundary
Honest about the public surface.
The technical portal explains the protocol and proof shape; the operating manual, install docs and release notes are live at docs.orcho.dev and in the package changelogs.
- IN DEVELOPMENT Hosted managed runs are not part of the first public surface. The current proof stays local-first.
- DOCS LIVE Install and usage docs are live at docs.orcho.dev — quickstart, operating model, architecture and reference.
- RELEASES LIVE Releases start at 0.1.0: each package keeps a CHANGELOG.md and GitHub Releases, without private dev history.