First Run¶
The first run should prove Orca’s product contract with as little setup as possible.
Success Means¶
- Orca creates a Mission in the target project.
- At least one real verification command runs through Orca.
- A failed check does not increase readiness.
- Every satisfied criterion shows its evidence.
- Completion is rejected until the contract is fulfilled.
- The final Mission remains readable in
.orca/missions/and through--json.
Recommended First Run¶
Use First Workflow with a small project change whose verification command you already know.
Do not begin by configuring Notion, subagents, a hosted service, or the full skill set. A local Mission can prove Mission Control works on its own; GitHub is the default work ledger when the workflow is managing repository work.
After The First Mission¶
Add only the layer the next Mission needs:
- an agent workflow from Commands;
- a reusable procedure from Skills;
- a host adapter from Compatibility Matrix;
- an external integration from Integrations Overview.