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: wire index-watch onto the dispatch schedule (continuous, hands-off)
goal
Make the self-repopulating chain run without a human: dispatch-01 (or the schedule) picks up the newest OPEN index-watch ticket each cycle and runs it; on settle it has already spawned its successor, so the chain is perpetual. Bound: one index-watch in flight at a time (a stop ticket aimed at the chain halts it — the brake). ACCEPTANCE: over several scheduler cycles with intermittent new commits, every new blob ends up fingerprinted+omni-indexed with no manual step, and exactly one open index-watch exists at any time.
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