orca-orchestration

Three layers, two of them here. The adapter (adapter/) is the only code that knows Orca. The runner (runner/, actions/) executes workflow files and the queue and knows nothing about roles or Orca. The project supplies the rest: the workflow files (here docs/pipeline/*.yaml), role files, briefs, a queue file, and a doc naming its paths (here: docs/pipeline/README.md).

The coordinator's job is small: start the slots, sleep, decide when a slot holds, finish. Everything else runs on its own.

Commands

From the skill folder, with uv (both dependencies are in its cache; nothing is installed). bin/runner and bin/adapter are uv scripts: they work from any shell and under nohup:

cd .agents/skills/orca-orchestration