Files
stack/docs/plans/2026-09-26_fleet-seats-onto-mosaic-launch.md
T
jason.woltjeandClaude Opus 5.5 0f5b7cb9be docs(records): Sage lead handover, rows 23-25 state, row 8 stub, BUILD-LOG rebuilt on HEAD
Records Jason's 2026-09-26 ruling: Sage leads the project, Darkwing is a
collaborating seat, development stays in T3, and the old ~/.mosaic fleet is
being retired. The lead role adds no push, merge or deploy authority.

- QUEUE rows 23-25 show their commits and pushes; row 8 links a parked stub
  brief listing the rulings Jason must make before fleet seats move.
- Shared records from Darkwing (rows 6, 16, 18, 22, #1511, #1512) and Dewey
  (row 5) that were waiting on one owner for the shared files.
- DEFERRED: T3 headers counted as human in the ledger (#1506), #1509 engine
  test leak and busy gap, #1512 re-run outcome.
- BUILD-LOG.md rebuilt as HEAD plus the uncommitted entries; the working copy
  had dropped the row 23-25 entries. Diff against HEAD is additions only.

All eight suites green. Not pushed.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-09-26 14:59:24 -05:00

1.7 KiB

Row 8: fleet seats onto mosaic launch (stub brief)

State: parked. Owner: unassigned. Issue: none yet. Written by Sage (lead) on 2026-09-26 so the queue can carry the row under the mandatory-brief rule (#1508 J3, J9). This stub authorizes no work.

Why the row exists

The old estate runs seats from ~/.mosaic/fleet/agents/<seat>/ under the npm-global mosaic CLI and the mosaic-fleet tmux socket. The new stack launches seats from agents/<name>/launch.sh in this checkout and registers them for the control board (row 2, #1504).

On 2026-09-26 Jason said the work MUST move to the new stack, because a fleet seat (the fleet Sage) was acting outside his instructions. That makes the retirement a stated goal. It does not make this row active.

What is known

  • Development seats (Sage, Darkwing, Dewey, Filbert, Rocko) run in T3 for now. T3 threads set no MOSAIC_AGENT_NAME and write no registration.
  • Fleet seats still live on the mosaic-fleet socket, including orch-01, rev-code-01, rev-code-02, jarvis and joe.
  • The Discord Sage runs as mosaic-discord@shared-signals, a new-stack service, and is not a fleet seat.
  • AGENTS.md forbids changes to ~/.mosaic launchers, provisioning or live fleet processes during the internal bootstrap.

Before this row can leave parked

Jason must rule on:

  1. Which fleet seats move, which are retired and in what order.
  2. Whether a moved seat runs under a Pi launcher, T3 or both.
  3. How seat credentials move. Seat tokens live under ~/.mosaic/fleet/agents/<seat>/secrets/. Secrets never enter this repository (canon invariant 3).
  4. Lifting the AGENTS.md bootstrap restriction on ~/.mosaic changes.

A full brief replaces this stub once he rules. Until then, queue next never returns this row.