jason.woltjeandClaude Opus 5.5
bee89d107d
Jason's R26 via Mos: Claude first, Codex only on gpt-6.1-sol, never Astra. Rocko's Codex thread ran gpt-6-astra; the seat now runs as T3 thread b84bb264 on Opus 5.5, because its only row, S4, builds mosaic decide and the gated decision DM. Roster updated. Filbert's launcher still pins Astra; recorded as a follow-up, unused while Filbert runs in T3. Co-Authored-By: Claude Opus 5.5 <[email protected]>
3.0 KiB
Mosaic Stack development team
These are interactive host development agents working in the canonical
checkout. They do not create managed fleet registrations or change role policy.
Sage leads the project and coordinates assignments, review, and integration
(Jason's ruling, 2026-09-26). Development sessions run in T3 for now.
For the current bootstrap phase, direct coding, review and research use Darkwing,
Dewey, Filbert, Rocko, Researcher and further seats Jason launches from this repository's agents/ directory,
not fleet seats. Keep changes in /mnt/storage/src/mosaic-stack; do not modify
~/.mosaic launchers/provisioning or migrate/stop live fleet processes.
| Agent | Responsibility | Runtime | Launch from repository root |
|---|---|---|---|
| Darkwing | Hands-on engineering; collaborating seat under Sage | Pi, configured Mosaic model | agents/darkwing/launch.sh |
| Dewey | Frontend design, UX, accessibility, and UI implementation | Pi, configured Mosaic model | agents/dewey/launch.sh |
| Rocko | General development, investigation, testing, and review | T3 session (Claude Code, Opus 5.5, thread b84bb264, lead decision 69); launcher Claude Code, Sonnet model | agents/rocko/launch.sh |
| Filbert | General development, investigation, testing, and review | T3 session (Claude Code, Opus 5.5); launcher Pi, openai-codex/gpt-6-astra:low, not to be used under R26 until it changes (lead decision 69) |
agents/filbert/launch.sh |
| Researcher | Source-grounded technical research and evidence | Pi, configured Mosaic model | agents/researcher/launch.sh |
| Sage | Project lead: coordination, review, integration; earlier DYOR strategy records retained | T3 session (Claude Code); Pi launcher zai/glm-5.3:high retained |
agents/sage/launch.sh |
Each script supports --check and --fresh. Normal launches resume the agent's
own conversation; a first launch starts one. See each agent's README for
context inputs, authentication, and recovery details. Launch scripts can also
be invoked by absolute path from any directory. No assignment or model request
is submitted by the launcher itself.
The shared Pi helper supports --provider NAME, --model ID, and
--thinking LEVEL as per-launch overrides of the validated system defaults.
Filbert's wrapper appends the required provider, model and thinking flags so
its launch configuration remains fixed, including on resume. Use Filbert's
wrapper to select that configuration; a direct shared-helper invocation uses
its own supplied flags or the system defaults.
All agents follow repository governance and current user direction. Team leadership does not add deployment or push authority. Coordinate overlapping work with Sage and preserve other sessions' changes.
Before 2026-09-26 Sage worked only on DYOR strategy and sat outside the
development queue. Jason then made Sage the project lead and Darkwing a
collaborating seat. A separate fleet Sage seat under ~/.mosaic is being
decommissioned; it does not speak for this seat. Whether the DYOR strategy work
continues is Jason's call. Joe retains DYOR engineering.