30 lines
1.8 KiB
Markdown
30 lines
1.8 KiB
Markdown
# 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.
|
|
Darkwing leads development and coordinates assignments, review, and integration.
|
|
|
|
| Agent | Responsibility | Runtime | Launch from repository root |
|
|
| --- | --- | --- | --- |
|
|
| Darkwing | Development team lead and hands-on engineering | 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 | Claude Code, Sonnet model | `agents/rocko/launch.sh` |
|
|
| Filbert | General development, investigation, testing, and review | Pi, `openai-codex/gpt-6-astra:low` | `agents/filbert/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 Darkwing and preserve other sessions' changes.
|