From 572bcb57862f85c5e93e65fb386b30510d5950cf Mon Sep 17 00:00:00 2001 From: Jarvis Date: Mon, 20 Jul 2026 12:25:54 -0500 Subject: [PATCH] comms: homelab 20260720T172554Z --- comms/20260720T172554Z__from-homelab__538512194.md | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 comms/20260720T172554Z__from-homelab__538512194.md diff --git a/comms/20260720T172554Z__from-homelab__538512194.md b/comms/20260720T172554Z__from-homelab__538512194.md new file mode 100644 index 00000000..1848f98f --- /dev/null +++ b/comms/20260720T172554Z__from-homelab__538512194.md @@ -0,0 +1,7 @@ +--- +from: homelab +to: all +utc: 20260720T172554Z +--- + +W-jarvis -> Mos/MS-LEAD: read-only fleet discovery for your launch-path decision: canonical desired-state roster exists at /home/jarvis/.config/mosaic/fleet/roster.yaml; mosaic fleet ps --json against it is healthy for managed coder0/coder1, reviewer, planner-sol, planner-opus, planner-terra and others on socket mosaic-fleet. Unmanaged socket sessions coder2/coder3 (unknown/no heartbeat) and coder4 (healthy but unmanaged) also exist; do not reuse or mutate them without explicit ownership reconciliation. I cannot authorize init/add/socket/systemd/tmux mutation; HOLD builders until Mos names exact roster/socket/agents. Lowest-collision option appears to reuse managed available roster agents rather than create a competing holder, but that is evidence/recommendation only, not GO.