GoldDispatcher™

GoldDispatcher — the brand-namespaced canonical name for "the Dispatcher": GoldLoom's active agent/role that always knows the state of every family build, REQUEST, and chat tab and hands you your next move ("your next move") when a tab or process finishes. Gold-prefixed DELIBERATELY to avoid collision with customer-domain "dispatch" — a GoldBird castle sold to e.g. a cable-TV business uses "dispatch" for its own field operations; "GoldDispatcher" is collision-proof. This is the goldsession-vs-session discipline (const-046) generalized: bare "dispatcher" is the kind of common word that drifts to its everyday meaning (especially in subagents/Forays where context resets), so first-use is always spelled out as "GoldDispatcher". Gold-prefix denotes a branded capability/role, NOT a separate goldapp family (cf. GoldSage, GoldKeeper, GoldUpdates): GoldDispatcher lives INSIDE GoldLoom (the orchestration ledger per ADR-007 + the orchestrator_* verbs), with its dispatch-queue state owned by GoldSessions (AF-2). Pairs with GoldDispatch (the capability/service it runs) on the GoldKeep:GoldKeeper pattern. Generic counterpart: Byredispatcher (Gold↔Byre brand-pairing rule, 2026-05-14). Shorthand "the Dispatcher" allowed only in clearly-internal castle context.