See the input → responsibility → output diagram.
Work items keep one list per project of who is doing which work, turn away a second claim on the same work, and report which branches are finished or abandoned. It exists because, on 29 September to 2 October 2026, three coordinators built on one checkout at once. Seven branches turned out to duplicate work that another coordinator had already landed in a different form, and they sat unmerged for days.
What it does first: find the lanes left behind
The stale report works before anyone adopts the register. It reads every branch under a project's prefixes and every worktree in its repository, read-only, and says for each whether it is already merged, superseded by work that landed in another form, stale, or still active. On 2 October 2026 the coordinator swept 120 worktrees by hand; this makes that one read command and a decision.
The report never deletes anything. It does not guess: a lane it cannot read, such as one on another machine, is unknown, not stale.
What it does
Each project has its own register. An item in it is one unit of work: a title, a handful of keys that identify it (a task or roadmap ID, a module name, the files it will change), who holds it, which branch and worktree it lives on, and where it stands, from proposed to merged.
Before anyone starts work, they claim it. The register compares the claim with every open item and with everything merged in the last two weeks, by fixed rules. A claim that shares a task or roadmap ID, or most of its files, with other work is refused, and the refusal names that work and its holder. A claim that only touches a shared file or module is allowed once it says it knows about the other work.
A refused claim has four honest ways forward:
- Talk to the holder and agree who does it.
- Take the work over openly, with a reason. The previous holder is recorded, and told if the work was active.
- Say the new work is a follow-up of work that has merged.
- Declare a comparison, on purpose, so two people build the same thing to see which is better. The owner, or the holder of each compared item, declares it. The loser closes as superseded when the winner is named.
The rules are the same for every holder: a Claude session, a Codex session, an agent the Factory dispatches or a lifecycle stage. The register records who claims what; it does not decide who is allowed to deliver. The Product gate does that.
The lane findings
A lane is a branch and the worktree that goes with it. The lane reader collects facts about each one from Git, without changing anything, and the register classifies them: whether its tip is already on the main branch, whether the register says its work is done, whether it looks like work that landed in another form, or whether it has simply been left. Each finding comes with its evidence, a proposed action as a plain word, and who should confirm it. The owner is not the default confirmer. A lane with uncommitted work is never proposed for removal without saving the work first, and that question goes to the owner.
Nothing here deletes a branch or a worktree. A person removes lanes, after reading the finding. A report also lists work that was claimed but never started, work that merged without being recorded, branches that two people are changing at once, and takeovers of work that was still active.
How it links
- It keeps its records in a caller-owned Command journal, so a retried command gets its recorded answer.
- A finding that needs the owner, such as a lane with uncommitted work, is meant to go through the Owner policy ask ledger. Nothing sends it yet.
- Intelligence declares that it uses no AI model.
- The Product gate still decides who may deliver. A holder in the register is a name, not a permission.
Limits and status
Honest limits:
- Holders are names. Anyone who can write the register's file can claim as anyone, so it is trusted local storage, not a lock.
- The rules are only as good as the keys a claim declares. A claim that declares nothing, or changes files it never listed, is caught only when it reaches review, or by the collision finding.
- The thresholds are a first guess measured on one set of lanes. They are reported with every result, never tuned in silence.
- Git facts are local and as fresh as the last fetch. A branch that exists only on the remote is never read, and a lane on another machine is unknown.
- Nothing reads a pull request, and nothing is wired into the lifecycle, the owner digest, the dashboard or a dispatcher yet.
- It works within one project at a time. Finding the same work in two projects and proposing a shared library is a separate, planned stage.
- There is no installable package for it yet.
Status: In progress. A candidate for stage 1 in two parts, the register and the lane reports, awaiting independent review; nothing is accepted, and no live register exists.
