fb61b26818
Add declarative system-type profiles: framework/fleet/profiles/*.yaml map a system type to a persona roster + org topology (reports_to, multiplicity). Profiles are DATA, seeded like roles, so an operator declares a system type and gets the matching roster from the baseline library with no code change (NS-9 / AC-NS-6). - 5 baseline profiles: software-delivery, personal-assistant, research, business (company-in-a-box), marketing. - fleet-profiles.ts: loadProfiles/loadProfile/parseProfile/validateProfile + listPersonaClasses (extracts valid classes from the role library by unioning inline `class:` markers, LIBRARY.md rows, and role filenames so marker-less personas like planner/decomposition resolve). - CLI: `mosaic fleet profile list|show [--json]`; invalid profiles exit non-zero. - Spec covers parse/validate, the library-drift guard (every referenced class resolves against the real role library), and unknown-class/reports_to rejection. - install.sh: profiles seed via the existing rsync (comment clarified; the preserved top-level `fleet/*.yaml` glob does not shadow fleet/profiles/*.yaml). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Examples
examples/minimal.yamlstarts one local canary slot.examples/local-canary.yamlstarts a small generic dogfood fleet.
Initialize a roster:
mosaic fleet init --profile minimal --write
mosaic fleet install-systemd
mosaic fleet start
mosaic fleet verify