Files

T

jason.woltjeandClaude Opus 5.5 993673865a docs(records): Jason's walkthrough rulings, Sage moved to SetSpark, CHAT-02 go

Jason ruled on seven open items (20:27Z-20:45Z): seat Gitea tokens read in
place, one Discord restart after 6b with row 25 live, row 8 limited to the
dev seats, DYOR in dyor-stack-v4 with Sage moved to SetSpark, skills/aws-*
excluded locally, no second WebUI return defect, and go on CHAT-02 only.

Sage persona files name SetSpark as its business work. Darkwing's SOUL drops
harness names that were wrong for T3. DEFERRED adds the slash-prefix paste
hazard and the board Host/Origin gap, and moves the ledger T3 item to Done.
Dewey's approved CHAT-02 brief (636b0fac) and Filbert's review are recorded.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

2026-09-26 15:35:15 -05:00

2.4 KiB

Raw Blame History

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:

Which fleet seats move, which are retired and in what order.
Whether a moved seat runs under a Pi launcher, T3 or both.
How seat credentials move. Seat tokens live under ~/.mosaic/fleet/agents/<seat>/secrets/. Secrets never enter this repository (canon invariant 3).
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.

Rulings so far (appended 2026-09-26)

Scope (Jason, 20:36Z): the mosaic-stack dev seats only. They are orch-01, plan-01, rev-code-01, rev-code-02, code-be-01 and code-dogfood-01. They retire instead of moving, because the T3 seats already cover their work. They get no new work. Jason stops each process himself or tells Sage to, one seat at a time. The other live fleet seats are outside this row.
Credentials (Jason, 20:27Z): seat Gitea tokens are read in place, read-only, from ~/.mosaic/fleet/agents/<seat>/secrets/. Nothing is copied.
The AGENTS.md restriction on ~/.mosaic changes stands. Stopping a retired seat's process on Jason's word is the only exception.

2.4 KiB Raw Blame History

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