The tracker.

The problem.

A board that people drag by hand does not tell two agents to stay out of the same file. Parallel work collides on the files, and a claim left behind looks like someone is still on it.

What it is.

Every piece of work is an item in one of six states: backlog, next, in progress, review, blocked, done. You see them as a board or a list. Board is the default. There is no Ready state.

Agents claim ready work. A cluster claim takes related items together and reserves the files they touch, so two agents never edit the same ones. Agents heartbeat while they work. A lapsed lease frees the item for the next agent. Stopping early releases the item. A blocker that is still true tomorrow is blocked.

Example · project Core Platform · tag CORE

Board · List

● backlog

CORE-15

● next

CORE-14Paginate the export list

● in progress

CORE-12Redact tokens in exportsagent-2 · lease 4mapi/export.pyapi/redact.py

CORE-11agent-3

● review

CORE-9Add export to the CLI

● blocked

CORE-7Choose the export file formatWaiting on a decision

● done

CORE-5

What it isn't.

Not a queue you assign by hand. Nobody hands an agent work in a chat.

How work is split How a claim is built