Every ticket as the root of its provenance graph — goal, patch, approval, runs and (as the ticket-class build lands) mandate, manifestations, guarantees, journey, artifacts and children. Rendered through the <<<TicketGraphList>>> tag.
Build: refactor pair_loop + ticketing to BRANCH-PER-TICKET with worktree isolation (iterative)
goal
Refactor the pair-loop/ticket flow per the RFC #root specs, in ITERATIONS: (i1) on dispatch, create+checkout branch ticket/<id> in a dedicated git WORKTREE; the worker/adversary operate there; the deliverable is committed on the branch. (i2) on settle DONE, merge branch->base per the chosen policy, record branch+merge in the journal, then reap the worktree (clean tree per #213/#216); on fail/conflict the branch persists and the ticket stays open. (i3) enable PARALLEL pairs — N tickets, N worktrees/branches, no contention. Each iteration is committed + clean-checked-out (#213). ACCEPTANCE: dispatching #ID produces branch ticket/<ID> with the deliverable committed there; DONE merges it to base and reaps the worktree; two pairs on distinct tickets run concurrently in separate worktrees with no conflict.
patch
none
approval
unapproved
runs
no runs recorded
mandate (clauses)
not yet recorded — lands with the ticket-class build
manifestations
not yet recorded — lands with the ticket-class build
guarantees
not yet recorded — lands with the ticket-class build
journey (blunders & successes)
not yet recorded — lands with the ticket-class build
artifacts (forge)
not yet recorded — lands with the ticket-class build