Software delivery has a new kind of worker in it. Agents can write real code, and the constraint has moved: not can it be built, but can anyone tell what is true. A tracker built for humans assumes someone is holding the plan in their head between standups — an assumption that breaks the moment five sessions are running at once, none of them remembers yesterday, and “done” is a column somebody dragged a card into.
Commission is the layer where that coordination lives. It is not a coding agent and not another tracker: it holds the task graph, the rules for who may work on what, and the context each piece of work needs, then hands them to whoever is doing the work in one read. Agents operate it; humans are asked only for judgment, and observe through a read-only web view.
Completion is a predicate rather than a status field. done is refused until acceptance criteria are ticked and the evidence a task’s gate requires is attached — and the refusal names the exact command that fixes it.
Features
- One truth, derived views — Status lives in exactly one row; boards, standup, and blocked state are queries, so drift is structurally impossible
- Atomic lease-based claims — N agents run
commission next --claimand each gets a different task; a crashed session never wedges one - Context bundles — A claim returns the body, criteria, dependency state, links, prior notes, and the exact commands that finish the task
- Evidence gates — A gate names the evidence it requires (PR, benchmark, rollback plan) and
donerefuses without it - Refusals are prompts — Every rejected action states what is missing and the command that supplies it
- Parallel by default — The ready frontier is everything workable now, with file-collision overlaps visible before work collides
- One core, four surfaces — CLI for agents, HTTP API, MCP server for tool-only contexts, and a read-only web view for humans
- Incremental adoption — Jira and markdown import, GitHub and Jira bindings, and supervised sync that stay dormant until you opt in