Amends the machine-readable North Star (docs/fleet/NORTH_STAR.yaml) to encode a scope expansion: Mosaic is reframed as a general-purpose multi-agent system where the user declares the system type and the orchestrator provisions a matching persona roster + topology. The delivery/coding fleet becomes one profile among many.
The Markdown projection (docs/fleet/NORTH_STAR.md) was regenerated byte-for-byte with the deterministic generator (generateNorthStarMarkdown in packages/mosaic/src/commands/fleet.ts) — not hand-edited.
Additive changes (YAML source of truth)
Mission — expanded to frame Mosaic as general-purpose (system-type declaration → persona roster provisioning).
NS-9 (standing objective) — general-purpose multi-agent system; user declares SYSTEM TYPE; orchestrator provisions roster + org structure from a cross-domain baseline persona library.
AC-NS-6 / AC-NS-7 (success criteria) — declare-a-system-type provisioning with no code change; user-customized personas survive mosaic update (baseline reseed never clobbers overrides).
Workstream H — Personas & system profiles (cross-domain library, system-type provisioning, update-surviving customization).
Goals H1–H4 — baseline persona library (H1, phase 1, depends_on A1); system-type profiles (H2); system-type provisioning (H3); update-surviving persona customization in a PRESERVE-protected override layer (H4).
ASM-4 (vetoable assumption) — baseline personas in framework/fleet/roles/ (reseeded on update); user overrides in a separate PRESERVE_PATHS-protected layer that wins on merge.
No changes to version, substrate, spend, or existing ids.
Spec fixtures
Updated packages/mosaic/src/commands/fleet-north-star.spec.ts: the mission-substring assertion changed from self-driving Mosaic delivery fleet to self-driving Mosaic system + Mosaic is general-purpose to track the new mission wording. The byte-equality fixture test (committed .md == generator output) passes against the regenerated projection.
## Summary
Amends the machine-readable North Star (`docs/fleet/NORTH_STAR.yaml`) to encode a scope expansion: Mosaic is reframed as a **general-purpose multi-agent system** where the user declares the system type and the orchestrator provisions a matching persona roster + topology. The delivery/coding fleet becomes one profile among many.
The Markdown projection (`docs/fleet/NORTH_STAR.md`) was regenerated byte-for-byte with the deterministic generator (`generateNorthStarMarkdown` in `packages/mosaic/src/commands/fleet.ts`) — not hand-edited.
## Additive changes (YAML source of truth)
- **Mission** — expanded to frame Mosaic as general-purpose (system-type declaration → persona roster provisioning).
- **NS-9** (standing objective) — general-purpose multi-agent system; user declares SYSTEM TYPE; orchestrator provisions roster + org structure from a cross-domain baseline persona library.
- **AC-NS-6 / AC-NS-7** (success criteria) — declare-a-system-type provisioning with no code change; user-customized personas survive `mosaic update` (baseline reseed never clobbers overrides).
- **Workstream H** — Personas & system profiles (cross-domain library, system-type provisioning, update-surviving customization).
- **Goals H1–H4** — baseline persona library (H1, phase 1, depends_on A1); system-type profiles (H2); system-type provisioning (H3); update-surviving persona customization in a PRESERVE-protected override layer (H4).
- **ASM-4** (vetoable assumption) — baseline personas in `framework/fleet/roles/` (reseeded on update); user overrides in a separate PRESERVE_PATHS-protected layer that wins on merge.
No changes to `version`, `substrate`, `spend`, or existing ids.
## Spec fixtures
Updated `packages/mosaic/src/commands/fleet-north-star.spec.ts`: the mission-substring assertion changed from `self-driving Mosaic delivery fleet` to `self-driving Mosaic system` + `Mosaic is general-purpose` to track the new mission wording. The byte-equality fixture test (committed .md == generator output) passes against the regenerated projection.
## Gates
- vitest: 568 passed (40 files), incl. fleet-north-star.spec.ts
- typecheck (tsc --noEmit): clean
- lint (eslint): clean
- prettier --check on NORTH_STAR.md / .yaml: clean
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Amends the machine-readable North Star (
docs/fleet/NORTH_STAR.yaml) to encode a scope expansion: Mosaic is reframed as a general-purpose multi-agent system where the user declares the system type and the orchestrator provisions a matching persona roster + topology. The delivery/coding fleet becomes one profile among many.The Markdown projection (
docs/fleet/NORTH_STAR.md) was regenerated byte-for-byte with the deterministic generator (generateNorthStarMarkdowninpackages/mosaic/src/commands/fleet.ts) — not hand-edited.Additive changes (YAML source of truth)
mosaic update(baseline reseed never clobbers overrides).framework/fleet/roles/(reseeded on update); user overrides in a separate PRESERVE_PATHS-protected layer that wins on merge.No changes to
version,substrate,spend, or existing ids.Spec fixtures
Updated
packages/mosaic/src/commands/fleet-north-star.spec.ts: the mission-substring assertion changed fromself-driving Mosaic delivery fleettoself-driving Mosaic system+Mosaic is general-purposeto track the new mission wording. The byte-equality fixture test (committed .md == generator output) passes against the regenerated projection.Gates
🤖 Generated with Claude Code