Ticket graphs

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.

← all ticket-graphs

DONE#177 jazz-agents

Build: LangGraph orchestrator for the ticket-authorization lifecycle

goal

Implement brake->pair->work->validate->settle->harvest as a LangGraph graph with a checkpointer, conditional edges (pass/fail/dry), and an interrupt node for wallet-signed approval. Nodes call the governed ticket routes; the append-only DB stays the source of truth (LangGraph state = in-flight cursor, not a second ledger). ACCEPTANCE: drive a ticket through the graph, KILL it mid-run, RESUME from checkpoint, settle correctly. Gated on R1.

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

source (forge tree)

browse congruency source (forge-parked tree)

children

#205 RFC (all-hands, DEEP): why do agents STOP when loaded with tasks — why don't they carry through? Grounded in observed orphaning (spawned · REQUESTED)
#180 Test: local Qwen-Coder worker pair produces working code vs the Claude baseline (spawned · REQUESTED)