One Ticket, One Worktree, One Pane

One Ticket, One Worktree, One Pane A sequence diagram generated by Archify. claim claim claim claim merge merge merge merge claim (staggered) build + review (isolated per worktree) merge (staggered return) Tracker · frontier + assignee · Sequence participant Tracker frontier + assignee TRA-139 · Builder worktree · Sequence participant TRA-139 Builder worktree TRA-142 · Builder worktree · Sequence participant TRA-142 Builder worktree TRA-125 · Builder worktree · Sequence participant TRA-125 Builder worktree TRA-087 · Builder worktree · Sequence participant TRA-087 Builder worktree Legend request return

Claim, Then Build

  • • Every Builder gets its own branch and its own checkout
  • • Git decides the claim; the tracker records who holds it
  • • Claims land at different moments — nothing here is synchronized

No Cross-Lane Edges

  • • No worktree reads or writes another worktree's files
  • • Concurrency stops being a race once isolation is structural
  • • Four tickets, four independent spans, no shared HEAD

Merge Returns Out of Phase

  • • Each ticket merges back to the tracker on its own schedule
  • • A slow ticket does not block a fast one
  • • The tracker, not the clock, is what all four spans share