No counts in prose

majordomus://rule/project.no-counts-in-prose@1active documentation

it references

Nothing. This object declares no reference.

referenced by

put_in_force adr-0023
depends_on project.a-verdict-states-its-subject@1
depends_on project.every-link-and-control-is-tested@1
depends_on project.performance-evidence@1
depends_on project.product-surface-derived@1
depends_on project.providers-are-data@1
depends_on project.ui-conformance@1

Rationale

A count written down is stale the moment the thing it counts changes, and README, .rules and .windsurfrules of the source environment disagreed with each other about the same counts for that reason.

Required behaviour

Prose never states a number the repository can compute; it states the command that computes it.

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.

Review. test/cases/28_no_hardcoded_values.sh proves that every list the tool knows about itself is derived, and the majordomus.context-budget doctrine fails on a hardcoded count in the always-loaded projection.

Where this comes from

canonical file: .ai/repo/rules/project/no-counts-in-prose.v1.md
identity: project.no-counts-in-prose@1
also served as: MCP resource majordomus://rule/project.no-counts-in-prose@1 · majordomus entity show rule/project-no-counts-in-prose-1 · GET /api/v1/entity?uri=majordomus://rule/project.no-counts-in-prose@1
in the Cockpit: /cockpit/objects/rule/project-no-counts-in-prose-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.