fitness

# Fitness — read-only goal measurement Inspect the active goals document and run only the caller-selected measurement, validation, drift, history, export, or meta-goal command. Renamed from `goals` (2026-07-29): the semantic skill is `fitness`; the `ao goals` CLI command family is a separate product surface and keeps its name. A thin `goals` compatibility alias resolves to this skill. Measurement stays trustworthy only because it cannot mutate what it measures; the moment a fitness report edits a goal, the next report measures the editor, not the project. Named failure mode — **advice creep**: a measurement report that ends with "you should…" has silently become work selection. Anti-pattern: padding the report with recommendations to look helpful. Corrective: return the numbers, the evidence gaps, and checked/not-checked scope, and let the caller decide. ## Boundary - Prefer `GOALS.md` when both Markdown and legacy YAML exist. - Preserve stable directive and gate identities in the report. - Every measured gate must name its executable check and observed outcome. - Do not add, remove, prioritize, recommend, apply, prune, migrate, or otherwise mutate goals. - Do not translate a fitness gap into work selection or a next action. - No subcommand edits the goals source through its own logic. `measure`, `drift`, and `export` persist a best-effort JSON snapshot under the fixed derived path `.agents/ao/goals/baselines/`. `render --out <file>` writes a Gherkin spec to wh...