No claim without a test

majordomus://rule/project.no-claim-without-test@1active documentationevidence

it references

Nothing. This object declares no reference.

referenced by

put_in_force adr-0028
put_in_force adr-0041
put_in_force adr-0054
put_in_force adr-0070
depends_on project.a-brief-is-kept-as-received@1
depends_on project.a-failed-read-is-not-an-empty-answer@1
depends_on project.a-personal-layer-changes-nothing-shared@1
depends_on project.a-producer-declares-what-it-writes@1
depends_on project.benchmarkable-commands@1
depends_on project.cache-is-invisible@1
depends_on project.conventional-commits@2
depends_on project.distribution-canonical@1
depends_on project.github-projection-gated@1
depends_on project.native-cli-documented@1
depends_on project.rust-command-tested-in-file@1
depends_on project.rust-public-api-quality@1
depends_on project.the-projection-is-applied-at-landing@1
depends_on project.work-serves-a-declared-intent@1

Rationale

A claim nobody can run is a promise; docs/CLAIMS.yaml exists so that every guaranteed claim names the test that proves it and the site refuses to render one that does not.

Required behaviour

A capability sentence in README.md or docs/ is backed by a case in test/cases/ or is phrased as a target.

Failure behaviour

No command decides this rule; a reviewer does, and a change that violates it is not merged. Where a behavioural case covers part of it, that case is named below.

Verification

Review. scripts/generate-site-data refuses a guaranteed claim with no test, and test/cases/28_no_hardcoded_values.sh checks every claim's detail page and test path.

Where this comes from

canonical file: .ai/repo/rules/project/no-claim-without-test.v1.md
identity: project.no-claim-without-test@1
also served as: MCP resource majordomus://rule/project.no-claim-without-test@1 · majordomus entity show rule/project-no-claim-without-test-1 · GET /api/v1/entity?uri=majordomus://rule/project.no-claim-without-test@1
in the Cockpit: /cockpit/objects/rule/project-no-claim-without-test-1

This page is generated from the file above by scripts/generate-site-data; editing the page changes nothing, editing the file changes every surface. The relations above are edges of docs/generated/graph.json, which the executable writes from the same index.