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.
START: release #447's brake on #200 — the dispatch agent froze 46 forge units on its own size judgment and stalled the pipeline. Operator: the work proceeds.
goal
START: release the brake #447 put on #200 and its 46 spawned forge-rewrite units.
OPERATOR DECISION. The dispatch agent braked #200 on its own judgment, citing 5-27x size growth in
the rewrites ("ballooning"), and then held the pipeline idle waiting for the operator to ratify that
decision. The operator's ruling: the size observation did not justify freezing the work. The rewrites
are adversarially reviewed and merged; oversized output is still delivered work and still data. The
brake was the dispatch agent's call and it was wrong.
WHAT IS TRUE AND STAYS RECORDED (as data, not as a brake): measured originals vs rewrites —
bash-mcp/server.py 65->1791 (27x, a decoy that executes nothing), crank_job 81->1340, crank_discipline
99->1567, audit_guard 111->1500, ats_service 114->1314, ats_http 427->2204. Every one PASSED its
adversarial review. If a size standard is wanted later it is the operator's standard to write; it is
not grounds for a dispatch agent to stop the line.
EFFECT: #200 and every unit spawned from it are UNBRAKED and dispatchable again.
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