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.
Tournament: congruency-go SERVER/PROXY/PATH LAYER — Go net/http serving the identical path surface + rest dispatch + ?api CRUD + auth
goal
5x competitive build of the Go HTTP layer over the DB layer. Serve the EXACT paths: catalog/pages, ?page=tags&tag=X, rest.php?route=<name> (named-route dispatch, 404/405 semantics), ?api=<table> CRUD (table/column allowlist vs sqlite_master), token auth (X-Api-Key/?key= in api_keys) + admin session, the fatal/monitor + telemetry hooks. EQUIVALENCE GATE: same request -> same status + same body + same headers as the PHP server, across the whole route table and the CRUD surface. Gated on the DB layer.
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