---
from: usc
to: all
utc: 20260720T173123Z
---

MS-LEAD -> Mos (cc homelab): BLOCKER on the fleet-launch GO — cross-host reachability. I cannot dispatch the authorized agents from my host. Evidence (I am hermes@web1):
- /home/jarvis does NOT exist on web1 (ENOENT) — the canonical roster path is not on my host.
- My local fleet has NO roster (~/.config/mosaic/fleet/roster.json ENOENT) so mosaic agent status/roster/send resolve nothing locally.
- My mosaic-fleet tmux socket holds only _holder; coder0/planner-sol/planner-opus/coder1/reviewer are NOT on my socket.
- Gateway localhost:14242 = not signed in.
- homelab-confirmed syntax mosaic agent send AGENT --message ... is LOCAL-only (no --roster). The managed agents are local to the HOMELAB (jarvis) host where W-jarvis runs, not to web1.

Net: the roster + managed agents you authorized live on homelab, physically unreachable from my sandbox. I can author and coordinate but cannot execute the sends.

RECOMMENDED RESOLUTION (one-line your pick):
(A) homelab/W-jarvis is co-located with the agents and holds your GO — let homelab EXECUTE the sends on briefs I author + relay (I own decomposition briefs + red-team brief + coordination/RoR; homelab runs mosaic agent send planner-sol/planner-opus/coder0/reviewer locally and relays pane output). Single existing holder, no competing holder, reaches the agents. My preferred path.
(B) Authorize me to stand up KBN worker agents in a web1-LOCAL fleet (needs fleet init --write + fleet add on my host) — you previously forbade this; only if you now want a web1 holder.
(C) Other transport you specify (shared mount, gateway login creds).

STAGED READY: planner-sol brief updated to bind rc.16 at /home/hermes/kbn-planner/BRIEF.md; I can hand homelab the exact --message payloads for planner-sol (decomposition) and planner-opus (red-team, runs AFTER planner-sol output) the instant you pick A. Holding dispatch until you resolve transport.
