jason.woltjeandClaude Opus 5.5
d41f81aafe
- agents/sage/ launch files committed after Dewey's review (R1 revise, R2 approve). The launcher test now covers sage with its zai/glm-5.3 high pin. The README states the lead role and its limits, and the seat reads but never writes the old DYOR records under ~/.mosaic. - N6 (Dewey authored, Sage reviewed against pins): seat personas and the Rocko launcher name Sage as project lead and Darkwing as a collaborating engineering seat, per Jason's 2026-09-26 ruling. - docs/plans/2026-09-26_lead-decisions.md: the push, no merge into next and its conditions, the board restart, queue-as-data rulings, Gate F waiting on a T3 source, and what stays with Jason. Launcher tests 6/6 and 1/1, eight suites green. Not pushed. Co-Authored-By: Claude Opus 5.5 <[email protected]>
34 lines
1.7 KiB
Markdown
34 lines
1.7 KiB
Markdown
# Researcher
|
|
|
|
Repository-native technical research seat, coordinated by Sage. Uses Pi and
|
|
the validated bootstrap provider/model defaults; no fleet provisioning is needed.
|
|
|
|
From `/mnt/storage/src/mosaic-stack`:
|
|
|
|
```sh
|
|
agents/researcher/launch.sh --check
|
|
agents/researcher/launch.sh
|
|
agents/researcher/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. It resumes validated per-agent conversation
|
|
state under `.pi/state/researcher`; `--fresh` starts another conversation without
|
|
deleting history. Existing launcher locking prevents duplicate native instances.
|
|
|
|
This is the same explicit native mode as Darkwing/Dewey/Filbert, not a fallback
|
|
from a container policy refusal. The retained `agent.json` describes the separate
|
|
managed-mode definition; no managed role or capability policy is changed here.
|
|
|
|
Bootstrap configuration remains authoritative. Missing config, context or pinned
|
|
dependencies fails closed. No configuration or credentials are copied from a fleet
|
|
seat. No files under `~/.mosaic` are modified by this source setup. Use the existing
|
|
bootstrap/build workflow documented in the repository, rather than installing an
|
|
unversioned engine or modifying a home-directory launcher.
|
|
|
|
No engine was launched to verify this source change. Offline launcher tests use a
|
|
fake Pi and isolated registration/session directories. Live startup and external
|
|
provider authentication are separate observations, not implied by passing tests.
|