Files

T

jason.woltjeandClaude Opus 5.5 5fe6a051d2 docs(slice1): runbook section 1 run through the Gitea admin API (row 35, #1517 , lead decision 74)

Jason ruled that agents run the steps his admin grant to the jarvis
Gitea token covers. Sage created the four mosaic-stack bots (ids
114-117, restricted, non-admin), added them as collaborators (W/W/W/R),
and minted one scoped token each (ids 191-194). The tokens were written
0600 outside the repo. Scripts and receipt are in
agents/sage/work/gitea-setup/. The guide and SR brief now say who
runs which section. Sections 2 to 4 (Vikunja) stay with Jason.

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

2026-10-09 17:25:08 -05:00

work

docs(slice1): runbook section 1 run through the Gitea admin API (row 35, #1517 , lead decision 74)

2026-10-09 17:25:08 -05:00

CONTEXT.md

docs(agents): seats read the queue, not CURRENT.md (row 10, #1508 )

2026-09-26 20:23:20 -05:00

DISCORD-USER.md

docs(records): Jason's walkthrough rulings, Sage moved to SetSpark, CHAT-02 go

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

launch.sh

feat(agents): Sage launch files, lead text across seat personas, lead decision record

2026-09-26 15:11:10 -05:00

README.md

docs(records): Jason's walkthrough rulings, Sage moved to SetSpark, CHAT-02 go

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

SOUL.md

docs(records): Jason's walkthrough rulings, Sage moved to SetSpark, CHAT-02 go

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

validate-sessions.mjs

feat(agents): Sage launch files, lead text across seat personas, lead decision record

2026-09-26 15:11:10 -05:00

README.md

Sage

Mosaic Stack project lead (Jason's ruling, 2026-09-26). Sage coordinates assignments, review and integration across the repository seats under agents/. Darkwing is a collaborating seat. The lead role adds no push, merge or deployment authority; those still need Jason's say-so. Development sessions run in T3 for now, and a T3 session does not load this directory's SOUL or CONTEXT. This launcher is the Pi path for the same seat.

From /mnt/storage/src/mosaic-stack:

agents/sage/launch.sh --check
agents/sage/launch.sh
agents/sage/launch.sh --fresh

--check validates configuration/context and the pinned local Pi version without launching a TUI, registering a seat, requesting authentication or calling a model. Normal launch registers the repository seat through scripts/mosaic, then uses the existing host-development helper with zai/glm-5.3 and high thinking by default; provider, model and thinking flags can be overridden per launch. It resumes validated per-agent conversation state under .pi/state/sage; --fresh starts another conversation without deleting history. Existing launcher locking prevents duplicate native instances.

Bootstrap configuration remains authoritative. Missing config, context or pinned dependencies fails closed. No configuration or credentials are copied from a fleet seat, and this launcher modifies no files under ~/.mosaic. A separate fleet Sage seat under ~/.mosaic is being decommissioned and does not speak for this seat.

Sage's business work is SetSpark, Jason and Carmen's business operating system. On 2026-09-26 Jason moved Sage from DYOR to SetSpark tasks. DYOR work and its records belong in /mnt/storage/src/dyor-stack-v4/. The old DYOR records in the fleet Sage tree under ~/.mosaic are history, and this seat does not write there.

Offline launcher tests (scripts/test-darkwing-launch.mjs) use a fake Pi and isolated registration/session directories. Live startup and provider authentication are separate observations, not implied by passing tests.