- `taxonomy.yaml`

- `docs/maturity-scores.yaml`

- `docs/maturity-scorecard.md`

- `docs/taxonomy.md`

- `docs/taxonomy-outline.md`

- `scripts/render-maturity-docs.mjs`

- `.github/workflows/maturity-scorecard.yml`

- `docs/concepts/qa-e2e-automation.md`

- `qa/scenarios/index.yaml`

Keep person-specific, maintainer-private, Discord archive, and discrawl facts

out of this repo. If a score needs private evidence, use the redacted

- `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.

- `docs/maturity-scorecard.md`, `docs/taxonomy.md`, and

`docs/taxonomy-outline.md` are deterministic docs generated from the root

taxonomy and aggregate score source.

- There is no committed maturity-doc renderer or `pnpm maturity:*` script in

this repo. Do not invent generated scorecard files; update the source YAML

and current docs directly.

- `qa-evidence.json` artifacts provide per-run QA scorecard evidence. They can

enrich generated artifact docs, but they are not committed as inventory.

## Commands

Run from the openclaw repo root.

Render committed docs:

Validate YAML structure after source edits:

```bash

pnpm maturity:render

node <<'NODE'

const fs = require("node:fs");

const YAML = require("yaml");

for (const file of ["taxonomy.yaml", "docs/maturity-scores.yaml", "qa/scenarios/index.yaml"]) {

YAML.parse(fs.readFileSync(file, "utf8"));

}

NODE

```

Check generated docs are current:

Check docs when touching docs prose:

```bash

pnpm maturity:check

pnpm check:docs

```

Render an evidence-enriched docs artifact from downloaded QA artifacts:

Run focused QA/profile checks when changing coverage IDs or profile membership:

```bash

pnpm maturity:render -- --evidence-dir .artifacts/maturity-evidence --output-dir .artifacts/maturity-docs

pnpm openclaw qa coverage --json

```

## Scoring Workflow

discrawl or unredacted private archives.

5. Update `docs/maturity-scores.yaml` only when the score change is backed by

public or redacted artifact evidence.

6. Run `pnpm maturity:render`.

7. Run `pnpm maturity:check`.

6. Run the YAML validation command from this skill.

7. Run `pnpm check:docs` if docs prose changed, and focused QA coverage checks

if coverage IDs or profile membership changed.

For subjective score changes, make the smallest defensible edit and leave the

evidence path in the PR or task summary. The deterministic renderer owns

Markdown structure; manual prose tweaks belong in taxonomy, score source, or

the renderer rather than in generated docs.

evidence path in the PR or task summary. Keep manual prose in current docs and

keep score data in `docs/maturity-scores.yaml`.

## Default Completeness Process

- `Alpha`: 50-70

- `Experimental`: 0-50

## GitHub Action

The `Maturity scorecard` workflow verifies committed generated docs on PRs and

pushes. Manual dispatch can also download QA artifacts from another workflow run

with `source_run_id` and `artifact_pattern`, render evidence-enriched docs into

`.artifacts/maturity-docs`, and upload them as a GitHub artifact.

## Artifacts

Do not add the maintainer repo's `docs/kevinslin/maturity-scorecard/inventory/`

tree to openclaw. Those generated reports are intentionally replaced here by

short-lived artifact docs and the committed aggregate scorecard pages.

tree to openclaw. Evidence-enriched scorecard outputs belong in short-lived

artifacts, not committed generated docs, unless this repo adds an explicit

renderer/check workflow first.