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.
Document the ticket-authorization surface (0029/0030)
goal
Write docs/TICKETS.md: the ticket-as-authorization model for agents and humans. Cover: (1) the ticket object and its governance (append-only journal, permanent work UIDs, no deletes — and WHY: the erased-history incident); (2) kinds and the pair/solo patterns with role names (kind.roster); (3) the lifecycle-as-data and steps_remaining (lifecycle.steps); (4) the routes an agent actually calls, in order, with curl examples: agent.register, ticket.assign, ticket.progress, work.record, ticket.journal, ticket.manifest, ticket.crew, ticket.kind, ticket.stops, agent.prompt, agent.roster, agent.trail; (5) stop/start tickets and grafting via edges; (6) the pair_loop.py harness: what one iteration does. Ground every claim in migrations/0029_ticket_authorization.sql, migrations/0030_pair_loop_routes.sql, and checkouts/current/congruency/tools/pair_loop.py.
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