Skip to content

Where orc is going ​

Orc grows toward the full orchestrator one step at a time.

CapabilityState
Chat and backlog as the front doorShips today
Runs placed by free slot and account quota, across machinesShips today
Code changes through checks and review into a pull requestShips today
Terminal dashboard with quota, machines, queues, tasks and alertsShips today
Orchestrator rules the chat followsNext
The chat posts every close, after a restart tooNext
Decisions held for you with a reason, answered from the chatShips today
Runs parked on a question resume on your answerShips today
Reports, investigations and machine tasks that end without a pull requestShips today
Per-project delivery: direct pull request or full reviewShips today
Merge on your word, refusing red checksShips today
Stalled runs and machine load flagged in the chatShips today
Alerts and pull request events posted in the chatShips today
Decision boards you answer onceShips today
Per-project instructions the run and the chat both readShips today
A fresh checkout before every runShips today
Follow-ups on upstream changesShips today

Today a ship run counts as done once Pi stops cleanly with ORC_COMPLETE and the branch holds a new commit. The checks must pass too, and no-mistakes must open a pull request with green CI. A direct-PR ship run counts as done once the checks pass and its pull request opens. A ship task that changes no code closes failed. A scout or task run counts as done once its report exists. A queued run from the backlog runs without the nono sandbox.