mosaicstack/stack

Fork 1

Files

T

History

topher 2435e74b8e

ci/woodpecker/pr/ci Pipeline was successful

Details

fleet: T110 rework - exact fleet/bin ownership, absolute fallback guard, mutation-controlled suite

B1 (rev-code-02): fleet/bin/** made keep-mode update prune existing estate
executables absent from the package source. Replaced with exact entries
(fleet/bin/mosaic, fleet/bin/test-mosaic-launcher.sh); parity spec gains a
dedicated ownership probe asserting the two shipped files are framework-owned
while seat-up.sh, launch-seat.sh and the directory itself stay operator-owned,
on both resolvers.

B2: a relative HOME bypassed the fallback guard (component probes were
absolute-prefixed, so a relative candidate walked nonexistent absolute paths
and a planted cwd-relative CLI executed). The untrusted fallback candidate is
now refused unless absolute, with parent-escape (..) components refused as
well; the symlink walk then applies.

B3: A6 planted the executable off the resolved candidate path, so a
guard-bypass mutant stayed green (nothing executable at the candidate). The
symlink now points at $PLANT/.npm-global so the candidate resolves exactly to
the planted binary, and the suite gains two mutation controls: a
guard-bypassed copy MUST execute both the absolute-symlink plant and the new
relative-HOME plant (sentinels asserted present), while the real launcher
refuses both (rc 127, diagnostics, sentinels absent).

Marker T110-DISPATCH-TOPHER-1N2O / ORCH-T110-REWORK-M5N6.

2026-08-29 19:30:23 -05:00

bin

fleet: T110 rework - exact fleet/bin ownership, absolute fallback guard, mutation-controlled suite

2026-08-29 19:30:23 -05:00

examples

feat(tess): add configurable Pi interaction service (#728 )

2026-07-13 02:59:27 +00:00

profiles

feat(fleet): dedicated orchestrator persona, split from planner (#662 )

2026-06-24 16:42:23 +00:00

roles

docs(fleet): tier the north star and declare the tier-0 operator surface (#1337 )

2026-08-20 23:05:34 +00:00

services

feat(tess): add configurable Pi interaction service (#728 )

2026-07-13 02:59:27 +00:00

README.md

feat(fleet): brain-home split — fleet state under ~/.mosaic, templates stay config-home (#1298 )

2026-08-18 03:23:15 +00:00

roster.schema.json

fix(fleet): enforce exact comms authority (#787 )

2026-07-16 00:32:23 +00:00

README.md

Mosaic Fleet Rosters

The local fleet canary uses a product-owned roster schema with site-owned roster files. Product examples live here; active local rosters should live outside the package, normally at:

~/.config/mosaic/fleet/roster.yaml

The default tmux socket is mosaic-fleet so fleet commands do not touch the default tmux server. The roster is the desired-state authority; generated environment files are rebuildable projections, never a second source of configuration.

Brain-home split (fleet state vs framework templates)

When a mosaic-brain clone is present, fleet state resolves from the brain home while framework templates and dispatch state stay in the config home (three-tree model, canon docs/STRUCTURE-CANON.md §2):

Path	Without brain (legacy)	With brain
`fleet/agents/<seat>.env.*`	`~/.config/mosaic/fleet/agents/`	`~/.mosaic/fleet/agents/`
`fleet/roles.local/` (overrides)	`~/.config/mosaic/fleet/roles.local/`	`~/.mosaic/fleet/roles.local/`
`fleet/profiles/` (working copies)	`~/.config/mosaic/fleet/profiles/`	`~/.mosaic/fleet/profiles/`
`fleet/roster.yaml`, `fleet/roles/` (baseline), `fleet/run/`, `fleet/services/`	`~/.config/mosaic/fleet/…`	unchanged (config home)

Activation (packages/mosaic/src/fleet/brain-home.ts, mirrored in tools/fleet/start-agent-session.sh):

MOSAIC_BRAIN_HOME env var — explicit, always wins.
Canonical ~/.mosaic — adopted only when MOSAIC_HOME is the default ~/.config/mosaic AND ~/.mosaic/fleet/agents exists. Custom --mosaic-home values (tests, sandboxes, canaries) never adopt, keeping them hermetic.
Otherwise the config home (legacy single-tree behavior).

Seat env dirs under a brain are subject to the same privacy boundary (0700 dirs, 0600 files); .env.generated files are structure-valuable and tracked in the brain repo, hand-maintained .env/.env.local stay ignored and private.

Examples

examples/minimal.yaml starts one local canary slot.
examples/local-canary.yaml starts a small generic dogfood fleet.
examples/operator-interaction.yaml is an example Pi operator-interaction service; replace its example agent name before provisioning.

Operator interaction service

services/operator-interaction.yaml pins the Pi runtime, GPT-5.6 Sol model, high reasoning, and the operator-interaction tool policy. The agent identity is provisioning data: choose a roster name, generate its per-agent environment file, then start the matching generic systemd instance. The service fails before launch if the configured identity does not match the instance or any pinned policy field drifts.

The installed tools/fleet/print-interaction-effective-policy.sh prints only the resolved name, runtime, model, reasoning, and tool policy. It never reads or prints credential variables.

Generated agent environment boundary

mosaic fleet install writes a private deterministic projection at ~/.config/mosaic/fleet/agents/<agent>.env.generated. It may relocate only approved local machine data to <agent>.env.local; generated keys, arbitrary commands, secret-like keys, duplicate keys, unknown keys, and unsafe permissions fail before a tmux session is created. Legacy .env input is regenerated, relocated, or quarantined and is not a launch authority.

See docs/fleet/reference/generated-env-boundary.md for allowed local keys and the USC downstream interface evidence.

Initialize a roster:

mosaic fleet init --profile minimal --write
mosaic fleet install-systemd
mosaic fleet start
mosaic fleet verify