The fleet is the set of workers the whole framework exists to govern: agents running under Claude Code, Cursor, Codex, or any SDK-driven harness capable of opening a pull request against the repository. The three named tools are examples, not a roster. Because the model is harness-neutral, the same anchored work feeds every one of them and the same law binds whatever wrote the code.
Speed here is the reason for the constraint, not an argument against it. Agents are fast and occasionally catastrophic, so the fleet is allowed to act only on work a human has anchored, never on a backlog it dreamed up for itself. It proposes; the gates and the human decide what merges. A worker that could both choose its own task and approve its own output would be a loop grading its own homework, which is precisely the failure the charter is written to prevent.
So the fleet is powerful and deliberately fenced. It does the labour, opens the PR, and hands the merge decision to machinery it does not control: the deterministic gate on every PR, and above that a human on anything that matters.