# Quality Score

Use this rubric to judge whether a change is documented well enough to be
maintainable.

## Scoring Dimensions

Score each dimension from `0` to `2`.

- Discoverability
  - `0`: important context is hidden in code or ticket history
  - `1`: context exists but takes effort to find
  - `2`: the right entrypoint is obvious from `AGENTS.md` or a nearby doc
- Accuracy
  - `0`: the doc contradicts code or current operations
  - `1`: mostly right but missing an important caveat
  - `2`: matches current code paths, commands, and dependencies
- Operability
  - `0`: a reader cannot act on the docs
  - `1`: partial commands or incomplete recovery guidance
  - `2`: commands, caveats, and validation are concrete
- Boundary clarity
  - `0`: responsibilities between services or docs are blurred
  - `1`: boundaries are implied but not stated
  - `2`: module ownership and source-of-truth locations are explicit
- Change discipline
  - `0`: the change added knowledge but no durable doc home
  - `1`: docs exist but are duplicated or hard to maintain
  - `2`: docs live in the right place and link to each other cleanly

## Interpretation

- `8-10`: healthy and maintainable
- `5-7`: acceptable but needs follow-up
- `0-4`: likely to decay quickly