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.
STOP: #443 timed out empty (2400s, zero output) - spec too large for one pass; split into #445 (part 1) + part 2
goal
STOP brake for #443 (forge family tree tool).
MEASURED FAILURE: #443 ran the full 2400s budget and wrote NOTHING - the deliverable was never created. This was NOT a worker fault. Its two siblings ran the same engine and the same 2400s timeout in the same window and both succeeded: #440 oriented ~18min then wrote 1723 lines; #438 completed two full worker/auditor rounds (2892 lines). The only distinguishing variable was SPEC SIZE: #443's body was 8268 bytes with 7 numbered requirements, a 7-class selftest matrix, AND reasoning over 264 repos of git plumbing. #440's was 4994 bytes.
CONCLUSION: a ~8KB / 7-requirement ticket exceeds one worker pass. The fix is to SPLIT, not to re-dispatch - re-dispatching a too-large ticket is what burned four attempts on #414.
SUPERSEDED BY #445 (PART 1: discover + cluster + classify + emit tree, 4590-byte body, sized to match the specs that succeeded). PART 2 (containment retirement gate + operator home mapping + merge-home worklist) is deliberately deferred and will be filed separately once part 1 lands.
DO NOT re-dispatch #443.
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