jason.woltje
ad21ad7ac5
Ratifies the Mosaic Stack PRD rev1 (Jason Woltje, 2026-09-01) as project source of truth and installs the GOV.1 lifecycle model: - docs/PRD.md becomes a permanent shim (kind: shim, current_rev -> docs/PRDs/2026-08-31_PRD_rev1/). Its path never changes again. - docs/PRDs/2026-08-26_PRD_rev0/PRD.md archives the 2026-08-26 North Star verbatim (sha256 60cc2f98...36afdf unchanged). Archive, never delete. - docs/PRDs/2026-08-31_PRD_rev1/ is the frozen rev1 bundle: 18 sectioned documents (VIS, DATA, AUTHN, AUTHZ, SEAT, ROLE, HARN, PROV, SESS, UI, CLI, GOV.1-5) consolidating rev0 D1-D15, the fleet north star, the agent-runtime L1/L2 contracts and the control-plane-surfaces lane findings, with a single decision map (GOV.3) and a closed open-questions frontier (GOV.5, grill rounds 1-8). Drafting inputs (_source-* snapshots) are not shipped. Consequences of the ratified rulings carried in the same change: - Q-T1 (ruling B, "shipped but frozen"): D3 amended in GOV.3/VIS.1; federation M1-M3 acknowledged as shipped behind tier === 'federated', excluded from the v1 bar and frozen, with a security re-audit gate before any resumption. docs/MISSION-MANIFEST.md, docs/federation/MISSION-MANIFEST.md and docs/scratchpads/mvp-20260312.md get status: superseded + banners (content preserved verbatim); docs/guides/deployment.md gains a "Relationship to the PRD (D15)" section. NORTH_STAR.yaml adds dormant workstream M (projects no goals by design); NORTH_STAR.md regenerated. - Q-G2 (distinct registry prefixes): every citation of the operator DECISION-REGISTER in the bundle reads OD-nn; the stack registry stays D1-D15; L1-Dnn/L2-Dnn untouched. Prefix rule recorded in GOV.1. Follow-ups (not in this PR): CI parity drift-gate witness (Q-C1); brain-side DECISION-REGISTER rename to OD- with redirect table on its next touch.
Fleet Configuration Management
This book documents the local roster-v2 desired-state control plane delivered under issue #758. The normative requirements are the FCM section of the repository PRD, not the older fleet-suite or observability planning pages.
Authority boundary
<MOSAIC_HOME>/fleet/roster.yaml is the sole writable desired-state authority for local fleet membership, launch policy, and persisted lifecycle. Generated environment files, systemd enablement, tmux sessions, heartbeat files, and status output are derived or observed. Rebuild projections from the roster; never edit them as desired state.
This control plane is local tmux/systemd only. Remote/SSH entries and connectors are inventory, not reconciliation targets. Arbitrary commands, channels, secret references, gateway catalog convergence, and UI configuration storage are outside this workstream. mos-comms is temporary transport glue, not permanent fleet architecture.
Choose the right workflow
- Need to inspect intent? Read the roster and use mosaic fleet get; see desired versus observed state.
- Need to inspect reality? Use
statusordoctor; useverifyfor a strict non-zero drift/ownership gate. These commands do not repair anything. - Need to change membership or persisted policy? Use generation-guarded
plan,create,update, ordelete; see safe CRUD. - Need a one-time runtime action? Use
start,stop, orrestart. These do not change persisted desired state. - Need convergence? Review apply --dry-run, resolve blockers, then use
applywith the same current generation; see reconcile and recover. - Need v1 migration evidence? Use preview only. Cutover, canary, and rollback remain held for FCM-M4-002.
- Need the gateway-backed agent catalog? That is the separate mosaic agent surface, not local fleet desired state.
Concepts
- Desired versus observed state
- Identity, class, runtime, provider, and model
- Role authority and leases
- Generated environment launch chain
Operator how-to
- Create, inspect, update, and delete
- Start, stop, restart, and reconcile
- Configure an interaction instance
- Configure a validator instance
- Customize roles
Operations and recovery
- Reconcile and recover
- Environment quarantine
- Systemd/tmux troubleshooting
- Backup and restore boundary
- Upgrade and asset-drift hold
Reference and migration
- Roster v2 fields · executable JSON Schema · validated example
- CLI and exit codes
- Role classes
- Lifecycle transitions
- Status and drift
- Generated environment boundary
- v1-to-v2 preview
- Example/profile dispositions
- Legacy class aliases
Acceptance evidence and holds
- M0/M5 IA checklist
- Legacy example/profile inventory
- M5 closure evidence
- Approved-existing deferrals and live-action holds
The canonical publishing source remains this repository. This card does not publish externally, run a migration, operate a live fleet, or close parent issue #758.