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: customize the Claude Code GUI (this Mac) into an optimal DISPATCHER — restrict capability + memory, lean on custom tools
goal
THESIS (counterintuitive, load-bearing): a dispatcher is MORE reliable when it is LESS capable. Observed failure mode (exhibited by this very session): over long runs the dispatcher DRIFTS — it forgets to dispatch, starts answering queries as a general-purpose agent, writes/edits code ITSELF instead of creating a build context and handing it to a properly-tooled agent, and leans on degrading internal context instead of the durable ledger. EVIDENCE: performance is higher when the system does NOT use its internal memory / Claude-backed reasoning for dispatch decisions — deterministic custom tools outperform the model 'remembering' what to do next. MANDATE: create a DEFAULT DISPATCH TOOL-SET + a RESTRICTED dispatcher profile for the Claude Code GUI installed on this Mac, such that: (1) the dispatcher CANNOT write or edit code — the only way it can effect change is to DISPATCH (build-context + tooled agent); (2) its agentic memory reliance is minimized — it reads pipeline state from the durable ledger each turn via tools, holding little in context; (3) role drift is prevented — the dispatcher role is re-anchored every turn so it cannot slide into general-purpose responding; (4) overhead on the agent is reduced — the dispatch COGNITION (what to run next, is capacity free, requeue the chains) is offloaded to deterministic tools, not model reasoning. This RFC spawns the build tickets below. Relates to #205 (agent carry-through) — same root: don't rely on session/internal state; rely on the durable ledger + tools. DELIVERABLE: docs/DISPATCHER_PROFILE_RFC.md — the restriction+toolset design + the minimal change to make Claude Code on this Mac boot in dispatch mode.
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