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.
RFC: local MCP-tooled agent stack (LangGraph + Ollama + Gemma 3 + Qwen2.5-Coder) on the ticket-authorization model
goal
GOAL: replace/augment the Claude-based pair_loop with a LOCAL, self-hosted agent stack whose agents draw tools ONLY from MCP. Motivation: control, trust, zero external telemetry. Roles map onto the 0029 ticket-authorization model: a DISPATCH agent (Gemma 3 — reasoning/routing ONLY, no code tools), adversarial WORKER PAIRS (Qwen2.5-Coder writes; a second model verifies, blind), orchestrated by LangGraph as a CHECKPOINTED state machine, all registered and journaled in the SAME append-only agents/ticket_events tables. LangGraph is the control plane; the DB stays the ledger. This RFC SPAWNS the research tickets below; each answers a make-or-break question before any build. DELIVERABLE of this ticket: docs/LOCAL_AGENT_STACK.md synthesizing the research into a build plan (RFC->spec->build->audit).
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