Nothing lost. Nothing twice.

A thin Postgres ledger where every unit of the rebuild is atomically claimed by exactly one agent and carries its state, attempts, cost, blocking questions and final disposition. Watch one unit live:

UNIT_IDSTATEDISPOSITIONCLAIMED_BY — DEVELOPER → AGENTATTEMPTSCOSTNOTE

U-88412READYnull—0$0.00registered from the audit backlog

DB-ENFORCED TRANSITIONS · ILLEGAL MOVES REJECTED BY THE SCHEMA, NOT BY HOPE

WHO CLAIMS — YOU. WHO WORKS — YOUR AGENTS.A developer claims units in batches; the claim reserves them for their fleet. Agents then claim one unit each inside the reservation — both claims atomic, both auditable.see the full day-loop on FleetOps →

01 / THE PEOPLE — 4 DEVELOPERS, 4 FLEETS, ONE LEDGER

CLICK A DEVELOPER TO FILTER THE LEDGER BELOW · CODEOWNERS MAKES THE BOUNDARY MACHINE-CHECKED — DOMAIN DRIFT BY AN AGENT IS AN ATTRIBUTABLE, BLOCKABLE EVENT

02 / OWNERSHIP — THE WHOLE ESTATE, WHO HOLDS WHAT

OWNERSHIP.MD + CODEOWNERS · MACHINE-CHECKED

⚙ TOMAS 765K⚙ ROBERT 152K⚙ JOSEF 536K⚙ SANTIAGO 566KSHARED · HUMAN-ONLY 130KUNOWNED 84K — SHRINKS WEEKLY OR THE KILL-GATE FLAGS IT

03 / HOW A CLAIM WORKS — THE DEVELOPER RESERVES, THE AGENT EXECUTES

DEVELOPER1

Claim a batch

Tomas picks 12 ready units inside his CODEOWNERS domain. The whole batch is reserved for fleet-a7.

POST /claims/batch · LEASE 60M

AGENT2

Ask for work

a7-03 requests a unit and gets U-88412 from Tomas's reservation. Any other fleet asking:409 RESERVED.

POST /units/claim · ATOMIC

AGENT3

Work — or block

Ports the path. A blocking question routes to Atlas with a 4h SLA; the answer unblocks and is written back to the corpus.

POST /units/:id/block

AGENT4

Prove it

Submits with a Harness evidence bundle → VERIFIED. No bundle, no verified —412.

TRANSITION {TO: "VERIFIED"}

DEVELOPER5

Review & dispose

Tomas reads the evidence and disposes MIGRATED. Immutable — kill-gate ready.

POST /units/:id/dispose

HUMAN MOVES — CLAIM & DISPOSEAGENT MOVES — EVERYTHING BETWEENWHO = ALWAYS A PERSON AND THEIR AGENT · BOTH CLAIMS ATOMIC, BOTH AUDITABLE

04 / THE ATOMIC CLAIM — ONE WINNER, ALWAYS

FOR UPDATE SKIP LOCKED · A UNIT IS CLAIMED FOR A DEVELOPER AND RESERVED FOR THEIR FLEET · A RETRY RETURNS THE SAME HELD UNIT↻ replay

Never duplicated

One atomic claim per unit. Two agents can race; exactly one wins the row lock.

Never lost

Leases expire, stalls surface on the stall list, and a dead agent's work is preserved as an attempt row.

Never silently abandoned

Every unit ends in exactly one immutable disposition: MIGRATED, DROPPED, DEFERRED or DEAD.

05 / THE LEDGER — WHO CLAIMED WHAT · TOMAS'S KILL-GATE READ

UNIT_IDCOMPONENT · WHATDEV → AGENTDISPOSITIONATTEMPTSCOSTEVIDENCE

DISPOSITIONS ARE IMMUTABLE · KILL-GATE READ AT M4/M8/M12 BY ⚙ TOMAS +⚙ ROBERT — ROW-LEVEL, EVIDENCE PER ROW · 5 SQL VIEWS ON THE BOARD, NO MORE

06 / HOW AGENTS USE IT — THE ERROR STRINGS ARE THE DOCS

one API session — fresh agent to claimed unit in under a minute↻ replay

▌

ACTUAL API ERROR COPY

"Dispositions are immutable once set — this is a ledger, not a scratchpad. If this was wrong, that is a new decision: record a superseding ADR and open a new unit row."

WHY IT WORKS

Every error names the violated invariant and the legal next move — an agent's context window accumulates real request/response pairs instead of a docs site. Full state in every response; idempotency keys on every write.

CROSS-WIRED

Blocked questions route to Atlas · verified needs aHarness bundle · every row renders live inFleetOps.

← FleetOpsWORKLEDGER · POSTGRES · UNIT / CLAIM / ATTEMPT / DISPOSITION — NEVER "TICKET"Next: Architecture →