Operational infrastructure
Baton
The shared task graph connecting engineering work across an entire repository portfolio — one Portfolio → Project → Task hierarchy that both people and AI agents read and write directly, instead of status living in someone's head or a Slack thread.
Most organizations coordinate cross-repo work by hand: spreadsheets, standups, and whoever remembers to update the ticket. Baton replaces that with a single live graph that every repo, every agent, and every person reads from and writes to — so "what's the state of this work" is always answerable, not reconstructed after the fact.
What it does
- A Kanban board tracking work across every connected repository, not just one.
- An MCP server so AI agents can query and update tasks as part of their own tool loop, instead of a human relaying status by hand.
- Bidirectional sync to version-controlled YAML — the task graph is never only a database row.
- Automated review scoring for agent-completed work, so task completion carries an evidence trail, not just a status flip.