Solutions
Solutions
One control plane for a whole GitHub org. What changes is the kind of repo and the kind of task.
One maintainer, many repos
Delegate well-defined tasks across every repo in the org from one board.
- Onboard each repo once; it gets labels and a Project link, not new workflow files.
- Queue tasks by moving them to Next; one runner works through them.
- Review pull requests, not agent sessions.
Dependency upkeep
Let dependency bumps merge on their own once the evals and CI agree.
- Dependency bumps are on the auto-merge allowlist.
- They still need a DONE verdict and the target repo’s green CI.
- Each merge is a ledger row, and later reverts can be counted.
Repos that reach the public
Add a last, hard gate for sites, packages and content.
- Mark the repo public-facing in its knowledge base; a human decides, never the tool.
- publish-safety-eval runs last; HOLD pushes nothing.
- Public-facing changes are never on the auto-merge allowlist.