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.
Tag test harness: rendered vs predicted, logged as tickets (with bet predictions)
goal
Build a harness that, for every tag under invocators/tags, records a PREDICTED rendering as a `bet` ticket, then renders the tag (standalone, as ?page=tags&tag=NAME does) and compares rendered result vs predicted. Log each outcome as a ticket (pass/fail), and provide a view. Model on the tournament predictions harness (predict.py / predictions.jsonl). Uses ticket types: bet (prediction) + test (result). [progress] tools/tagcheck.py added (renders every tag, asserts 200 + no PHP error). It refuted the all-pass bet and surfaced bug #58. Next: predicted-output bets per tag. [progress] tagcheck drove the shim-STDERR fix (#58 closed) and surfaced bug #60 (Content::__toString null). [green] tag-render harness passes 29/29 after fixing #58 + #60. [note] Core shipped this session; remainder is optional enhancement.
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