Orca Orchestration

Run the delivery through Orca's tracked worktree and orchestration state. The coordinator directs workers and decides gates; it never edits code.

Non-Negotiable Ownership

Create a dedicated Orca worktree for every requirement or ticket. Isolation keeps worker changes out of the coordinator checkout.
Use Orca orchestration tasks and injected dispatches. A terminal prompt without a tracked task is not orchestration.
Assign all repository mutations to workers: code, tests, generated files, formatting, commits, pushes, PR creation, and review fixes.
Never let the coordinator run an editor, apply_patch, a formatter that writes files, git commit, or any equivalent code-changing command. The coordinator may inspect state, issue Orca/GitHub control commands, make decisions, and merge.
Keep one explicit owner per file or responsibility when multiple workers run. Shared worktrees make overlapping edits unsafe.