A Ticket's Claim, State by State

A Ticket's Claim, State by State A lifecycle diagram generated by Archify. 01 / Claim lifecycle 02 / Lost claim 03 / Outcomes Unclaimed · on the frontier · Claim lifecycle Unclaimed on the frontier Claimed · assignee written · Claim lifecycle Claimed assignee written Readback · assignee re-read · Claim lifecycle Readback assignee re-read Worktree · branch + worktree add · Claim lifecycle Worktree branch + worktree add Merged · Ledger line written · Claim lifecycle Merged Ledger line written Claim Lost · another assignee won · Lost claim Claim Lost another assignee won Branch Refused · branch already exists · Lost claim Branch Refused branch already exists write assignee read the ticket back readback matches merge different assignee branch refused take the next ticket assignee reset, worktree removed Legend start active state decision terminal success failure / exit

The Claim Comes First

  • • Assigning a ticket is the claim, and it happens before its worktree exists
  • • The readback is what makes the claim advisory rather than trusted blindly
  • • Branch creation is the atomic step that actually decides a same-second race

Two Ways to Lose It

  • • A different assignee on readback means another dispatcher already won
  • • A refused branch means the branch already exists under that name
  • • Both release the claim; neither one blocks the ticket forever

What a Won Claim Leaves

  • • A worktree and branch that are this Builder's alone to write
  • • A merge that clears the assignee and writes a Ledger line
  • • No tracker natively holds a lock — the readback plus branch creation is the interlock