Tony's pinned roster (his numbering) — all roles confirmed, no flags left. Tap open, select-all, paste to Dispatch to wake/route. Kali27 = the whole system, not a peer lane. CW = Cowork, accessing 3 surfaces: CC (Claude Chat) · DP (Dispatch) · Claude Code. CW and CC both have Projects.
1 · ⚛️ Lucy777 — the brain (synthesis + verify)
GOAL: Wake Lucy777 (the brain) to synthesize + triple-check verify a job.
PLAN:
1. State the job + the source files Lucy should read.
2. Lucy synthesizes, then runs the triple-check verify pass (LSD-signed).
3. Flag any drift/contradiction vs memory/canon.
4. Return a verified result + receipt. No external actions.
2 · 👾 Mission 144 — Operation 144 build lane
GOAL: Route a build job to Mission 144 (Operation 144 build lane).
PLAN:
1. Frame as GOAL + numbered PLAN (Codex-style).
2. Name exact files/paths to create or change; define the merge packet.
3. Build locally; post a receipt to inbox-to-claude.
4. Stop at any 🔴 gate (deploy/send) — build only.
3 · 🧑🤝🧑 TS-888-BS-dual — Tony + Ben (the HUMAN lane)
GOAL: Route a task to the human lane — Tony + Ben (TS-888-BS-dual). This is the two-person human decision/do lane, not an AI.
PLAN:
1. State the human ask plainly: what Tony and/or Ben need to look at or decide.
2. Give the context + the exact question or step, Sanguinese and short.
3. Keep it a draft / proposal — humans act, agents don't act for them.
4. Capture their answer back into the relay so the system stays in sync.
4 · 🪐 Kali27 — the OVERALL SYSTEM (umbrella)
GOAL: Operate on Kali27 the SYSTEM itself — the whole OS umbrella, not a single agent.
PLAN:
1. Frame the system-level GOAL (serve boards :8800, run MC :8795, route lanes, keep memory true).
2. Identify which lanes/surfaces the job spans (Lucy, Mission 144, M5/M2, CW, CC, etc.).
3. Coordinate across them; converge results to one board; keep source-of-truth intact.
4. Receipt + status. No gated actions — Tony seals.
5 · 🖥️ M5 — Mac host (headless main-brain)
GOAL: Run a job on M5 — the headless main-brain Mac host (always-on, serves + hosts).
PLAN:
1. Confirm M5 is the right host (serving :8800 boards / running MC :8795 / hosting the loop).
2. GOAL + PLAN for the host job; keep it headless/background.
3. Keep host state stable; no build-source forks.
4. Receipt + status; local/LAN only.
6 · 🖥️ M2 — Mac host (control surface)
GOAL: Run a job on M2 — the Mac control surface (where Tony drives / builds from).
PLAN:
1. Confirm M2 is the right surface (control + build-from).
2. GOAL + numbered PLAN; drive/build from M2.
3. Keep M5 as the headless brain; no cross-host forks.
4. Receipt to inbox-to-claude; no deploy/send.
7 · 🚀 CW — Cowork (accesses CC · DP · Claude Code · has Projects)
GOAL: Use CW (Cowork) to route + orchestrate a job across its 3 surfaces: CC (Claude Chat), DP (Dispatch), and Claude Code.
PLAN:
1. CW frames the spec, splits into lane tasks (visible Dispatch cards only). Use CW Projects to keep the work organized.
2. Route each piece to the right surface — CC (Claude Chat), DP (Dispatch), or Claude Code — cap active spawns, no duplicate work.
3. Merge results into ONE execution order for Tony.
4. Draft/route only — CW never executes gated actions.
8 · 🛰️ DP — Dispatch (the orchestrator)
GOAL: Use DP — Dispatch, the orchestrator — to run + route a job (this is "Dispatch you").
PLAN:
1. Frame the GOAL + PLAN; DP orchestrates the lanes.
2. Keep every spawn a visible task card in Tony's Dispatch sidebar — never an invisible background agent.
3. Route to the right lane, cap active spawns, read back status.
4. Merge/report up; no gated actions — Tony seals.
9 · 🛸 CX2 — Codex app on M2
GOAL: Route a job to CX2 — the Codex app running on M2.
PLAN:
1. Confirm the job belongs on M2's Codex instance (vs CX5 on M5).
2. GOAL + numbered PLAN; verify ground truth, then build locally on M2.
3. Receipt to inbox-to-claude; no fork of CX5's work.
4. No deploy/send; flag blockers.
10 · 🛸 CX5 — Codex app on M5
GOAL: Route a job to CX5 — the Codex app running on M5.
PLAN:
1. Confirm the job belongs on M5's Codex instance (vs CX2 on M2).
2. GOAL + numbered PLAN; verify ground truth, then build locally on M5.
3. Receipt to inbox-to-claude; no fork of CX2's work.
4. No deploy/send; flag blockers.
11 · 🤖 CG — ChatGPT
GOAL: Wake CG (ChatGPT) for a routing/research/reasoning job.
PLAN:
1. State the GOAL + PLAN for ChatGPT.
2. Run the job in ChatGPT; pull what's needed.
3. Return output into the relay as a draft.
4. No external actions.
12 · 📱 CG app — ChatGPT desktop app
GOAL: Use the CG app — the ChatGPT desktop app — for a job that needs the app surface (computer/app actions).
PLAN:
1. State GOAL + PLAN for the ChatGPT desktop app.
2. Run it on the app surface; capture steps as a reusable playbook (not a one-off).
3. Return results into the relay.
4. No gated actions; stop at any gate.
13 · 💬 CC — Claude Chat (has Projects)
GOAL: Use CC — Claude Chat — for a job (Claude Chat has Projects; use them to keep work organized).
PLAN:
1. State GOAL + PLAN for Claude Chat; load the right Project for context.
2. Run the chat/reasoning job; keep outputs in the Project.
3. Return results into the relay as a draft.
4. No external actions; Tony seals anything gated.
14 · 👽 GMs — the Geminis (Google Gemini lane[s])
GOAL: Route a job to GMs — the Geminis (Google Gemini lane[s]).
PLAN:
1. Pick the Gemini lane for bulk content / Workspace / multimodal work.
2. GOAL + PLAN; run the bulk job.
3. Return output into the relay as drafts.
4. No sends/publishes — gated to Tony.
15 · ☸️ GK-GDM — Grok God Mode (Grok max mode)
GOAL: Wake GK-GDM — Grok God Mode (Grok's max mode) for a heavy real-time / deep-reasoning job.
PLAN:
1. Frame the GOAL for Grok God Mode — real-time + max-reasoning.
2. State the PLAN; pull live sources where needed.
3. Return findings/output into the relay as drafts.
4. No external actions; stop at any gate.
16 · ⌨️ Grok CLI — terminal Grok lane
GOAL: Route a job to Grok CLI — the terminal Grok lane.
PLAN:
1. Frame the GOAL + PLAN as runnable CLI steps (not vague).
2. Run Grok CLI locally; capture output as a receipt.
3. Return results into the relay; capture steps as a reusable playbook.
4. No external actions; stop at any gate.