Orca Mission Control¶
ORCA
Local mission control for AI coding work: explicit acceptance criteria, attributable evidence, guarded completion, portable state, and durable history.
First Mission¶
orca mission create "Prepare this change for review" \
--criterion "The repository has no whitespace errors" \
--criterion "The change is documented"
orca mission check AC-1 -- git diff --check
orca mission satisfy AC-2 --evidence "README updated"
orca mission complete
Orca refuses the last command until every criterion carries evidence and every blocker is resolved. Run orca dashboard to operate the same Mission visually.
The Product Boundary¶
- A Mission owns the outcome, criteria, evidence, blockers, readiness, and lifecycle.
- An agent performs the work.
- A skill teaches the agent a useful procedure.
- An integration connects an optional external system.
The Mission remains inspectable even when the agent, skill, or harness changes.
Start Here¶
| If you want to... | Open this |
|---|---|
| prove Orca works | First 10 Minutes |
| understand the product | Intro |
| run the complete product loop | First Workflow |
| operate the browser application | Mission Control |
| move a Mission between machines | Portability |
| install Orca | Quickstart |
| use an agent procedure | Commands |
| understand skills | Skills |
| verify a release | Releases |
Beyond Mission Control¶
Orca ships optional workflow definitions and skills for planning, building, review, QA, release work, and integrations. Those are extensions to the mission runtime, not substitutes for it. Start with one Mission; add a workflow only when it helps prove a criterion.