0aee2c0981
All checks were successful
ci/woodpecker/pr/ci Pipeline was successful
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
5.3 KiB
5.3 KiB
FCM-M5-001 Fleet Documentation IA Closure Evidence
Issue: #758 · Task: FCM-M5-001
Artifact map
- Fleet entry point and desired/observed decision tree:
docs/fleet/README.md. - Concepts:
docs/fleet/concepts/covers authority/projections, identity separation, role authority/leases, and the generated launch chain. - Operator workflows:
docs/fleet/how-to/covers CRUD, lifecycle, interaction and validator instances, and role overrides. - Operations:
docs/fleet/operations/covers reconciliation/recovery, quarantine, systemd/tmux troubleshooting, backup/restore boundaries, and upgrade-asset holds. - References: executable schema, complete field/default/constraint reference, CLI/JSON/exit behavior, lifecycle/status/drift, role authority, and generated environment boundary under
docs/fleet/reference/. - Migration: preview field map, lifecycle preservation, backup/recovery prerequisites, aliases, and executable artifact dispositions under
docs/fleet/migration/. - Navigation:
docs/SITEMAP.mdand the fleet entry point.
Acceptance mapping
| Checklist area | Evidence |
|---|---|
| Roster authority and fail-closed legacy handling | Root PRD FCM-REQ-01/05/08; desired/observed and quarantine pages. |
| Classes and authority | Root PRD FCM-REQ-07; role authority concept/reference; configurable interaction/validator how-tos. |
| Lifecycle | Root PRD FCM-REQ-04; lifecycle transition table and operator lifecycle how-to. |
| Local-only generated launch boundary | Root PRD FCM-REQ-05/09; generated launch concept/reference. |
| Complete DAG and artifact inventory | docs/TASKS.md; M0 inventory; executable disposition tests. |
| IA pages | Every path named by the M0 checklist exists and is linked from docs/fleet/README.md. |
| Examples | docs/fleet/examples/roster-v2.yaml validates through production v2 compiler/shared resolver; shipped artifact dispositions validate through declared production readers. |
| Links | Deterministic local Markdown link test covers the entire fleet book and sitemap. |
| Sensitive/example safety | Validator scans every fenced fleet-book example plus the canonical roster for sensitive-like keys, arbitrary command override, and hardcoded Tess/Ultron identities; docs consistently state value-free diagnostics. |
| Holds | docs/reports/deferred/758-fleet-config-deferrals.md records M3-002, M4-002, M5-002, compatibility, and repository-structure boundaries. |
Documentation completion checklist
- Root PRD exists and remains the #758 requirements authority.
- Accepted project-specific fleet book is complete and indexed.
- Sitemap links the fleet entry point and operator-critical pages.
- No HTTP/API/auth contract changed; OpenAPI/endpoint rows are not applicable.
- Working evidence remains under
docs/scratchpads/; closure and deferral evidence remains underdocs/reports/. - Canonical source remains in-repository; no external publishing action is in scope.
- Independent exact-head documentation review, PR CI, and FCM-M5-002 release certificate remain post-PR gates and are not claimed here.
Live-action boundary
No migration, canary, rollback, deployment, systemd/tmux/session operation, generated projection, or product mutation was performed. roster.yaml remains the sole writable desired-state authority. mos-comms remains temporary. Parent issue #758 remains open.
Validation command results and exact commit/tree evidence are recorded in the task scratchpad and PR body after execution.