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>
25 lines
705 B
YAML
25 lines
705 B
YAML
id: research
|
|
title: Research
|
|
description: >-
|
|
A research fleet that decomposes a question, gathers and analyzes evidence, and
|
|
synthesizes cited findings. The lead-researcher owns the agenda and assigns
|
|
individual questions to researchers and the analytics seats.
|
|
lead: lead-researcher
|
|
floor:
|
|
- lead-researcher
|
|
roster:
|
|
- class: lead-researcher
|
|
- class: researcher
|
|
reports_to: lead-researcher
|
|
multiplicity: 2
|
|
- class: data-analyst
|
|
reports_to: lead-researcher
|
|
- class: data-scientist
|
|
reports_to: lead-researcher
|
|
- class: market-analyst
|
|
reports_to: lead-researcher
|
|
- class: documentation
|
|
reports_to: lead-researcher
|
|
- class: review
|
|
reports_to: lead-researcher
|