harness-score / rules

---
description: Non-negotiable conventions for the harness-score monorepo
alwaysApply: true
---

- The scanner is deterministic by contract: no model calls, no network, no
  time-dependent output. If a proposed check needs judgment, it does not
  belong in the CLI — it belongs in the guide as advice.
- `packages/cli` has zero runtime dependencies. Do not add one.
- Check changes touch three files together: `packages/cli/src/score.ts`,
  `docs/guide/maturity-model.md`, `docs/guide/measure-and-improve.md` —
  enforced in CI by `docs.test.ts` and `maturity-sync.test.ts`.
- Guide edits must keep **all five locales** in sync — see `.cursor/rules/docs-i18n-parity.mdc`
  and `docs.test.ts` (file set + anchor parity).
- Check IDs are stable public API (they are documentation anchors and appear
  in users' CI logs). Never renumber, reuse, or delete an ID — deprecate by
  making the check always-pass if truly needed.
- This repository must keep scoring L4 on `npm run scan`.