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.
pair_loop: auditor with no JSON verdict crashes the pair (UNEXPECTED) instead of respawning the round
goal
When the blind tester emits no parseable JSON verdict on its last line, pair_loop raises UNEXPECTED and the pair process DIES, abandoning a committed, self-verified deliverable on its branch (observed: #179, worker 66/66 selftest, lost to a rambling non-verdict auditor). A missing/%malformed verdict should be treated as a ROUND FAILURE (respawn a fresh auditor up to --rounds), OR retried, not a fatal crash. Also consider forcing the tester to emit JSON (schema/grammar) per the #175 structured-output findings. Repro: any run where tester final line is prose.
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