Skip to content
cyberfleetcyberfleetcyberfleet

Coordinator

Part of the cyberfleet plugin. See that page for install instructions.

The Coordinator does a Captain’s mechanics. There is one per ship, in the right pane of its Bridge, and one for the fleet, on the Command Center’s Flag Bridge. It runs on the low model tier because landing is many turns of a check and a command.

What it does

Section titled “What it does”
  • Works from the ship queue. A Pod posts “PR ready” there, one thread per pull request, and the Captain posts the tracker mechanics it wants done. The Coordinator joins no mission channel; each pull request’s landing talk stays in its queue thread.
  • Lands pull requests. It merges each pull request when cyberfleet pr check passes, in the order the blocking links give, behind speculative CI and the ship’s merge lease. It acts on the command’s exit status and never judges “clean enough”.
  • Lands only under your words. It merges under a delegation you gave for a mission and its sub-missions, as your words say, relayed to it verbatim as a turn. A clean pull request with no delegation becomes a decision-request to you, through the Operator.
  • Directs Pods while it lands. It tells a Pod to rebase, to fix red CI the pull request caused, or to address a review comment within the mission’s scope.
  • Escalates judgment. A change of scope, red that survives the Pod’s fixes, or two pull requests that conflict in meaning go to the Captain, in the ship queue.
  • Reports once, then exits. When its count of open pull requests reaches zero, it posts one report of what landed in the ship queue, mentions the Captain, and exits. The report asks for the Captain’s review, so it starts the Captain if none is running.

A ship can give landing to each Pod instead, through its landing setting. Then no Coordinator starts, and each Pod lands its own pull request under the same bar and lease.

A Coordinator does the tracker mechanics for the Captain whose mission it is: filing an issue in another repository, adding sub-issues, and closing. Blocking links are the Captain’s to write. The fleet’s Coordinator does them for the fleet’s Captain, for issues in the fleet’s tracker. A mission in another ship that blocks yours stays with that ship’s Captain and Coordinator.

Section titled “Related”