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.
Test: new code is auto-fingerprinted+omni-indexed and the ticket truly repopulates
goal
Prove: (1) add a new module to a repo -> after one index-watch run it is findable by similarity (#190) AND by name/sha via omni-git (#193); (2) the settled index-watch SPAWNED a successor with the advanced high-water-mark; (3) idempotency — a blob already fingerprinted is skipped (no duplicate vectors); (4) a stop ticket aimed at the chain halts repopulation (the brake holds). Adversary: ensure the delta computation misses NOTHING (a blob changed between runs is not skipped).
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