- `taxonomy.yaml` is the hand-edited source of truth for surfaces, levels,

QA profiles, categories, feature coverage IDs, docs refs, LTS overrides, and

completeness-instruction paths.

- Feature `coverageIds` are ANDed proof targets, not aliases. A feature may

list multiple IDs when each ID proves part of one capability.

- Keep categories and feature names unique, product-shaped, and broader than raw

coverage IDs. Do not promote generic IDs into standalone feature names.

- Avoid duplicate coverage-ID bundles under different feature names in one

category.

- `docs/maturity-scores.yaml` is the aggregate score source committed in this

repo. It is the only committed score data; do not add generated inventory

directories.

The resulting `qa-evidence.json` includes a profile scorecard summary with

selected-category counts and missing coverage IDs; the individual evidence

entries remain the source of truth for the tests, coverage roles, and results.

Taxonomy feature coverage IDs are exact proof targets, not aliases. Primary

scenario coverage fulfills matching IDs; secondary coverage stays advisory.

Slim evidence omits per-entry `execution` and sets `evidenceMode: "slim"`;

`smoke-ci` defaults to slim, and `--evidence-mode full` restores full entries:

# - add `coverage.secondary` only when a scenario intentionally protects another behavior

# - keep IDs behavior-shaped, broad enough to reuse, lowercase, and dotted or dashed

# - use the exact values listed under feature `coverageIds` in `taxonomy.yaml`

# - taxonomy feature coverage IDs are exact proof targets, not aliases

# - scenario primary can list multiple IDs only when this scenario is primary

# proof for each

# - prefer reusing an existing coverage ID over minting a scenario-shaped ID

# - avoid copying the scenario title into coverage IDs

# - use `pnpm openclaw qa coverage` to render the current inventory