No new nouns

majordomus://rule/project.no-new-nouns@1active design

it references

Nothing. This object declares no reference.

referenced by

put_in_force adr-0020
put_in_force adr-0025
put_in_force adr-0026
put_in_force adr-0033
put_in_force adr-0038
put_in_force adr-0039
put_in_force adr-0046
put_in_force adr-0069
put_in_force adr-0091
put_in_force adr-0104
put_in_force adr-0118
put_in_force adr-0164
depends_on project.canonical-order@1
depends_on project.optional-complexity@1
depends_on project.the-session-context-is-derived@1

Rationale

Every noun is a concept a worker has to learn and a surface that can drift; the design stays small on purpose, and docs/CONCEPTS.md is the whole vocabulary.

Required behaviour

The tool gains no agents, personas, roles, tiers or registries beyond the vocabulary it has.

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. test/cases/28_no_hardcoded_values.sh checks that every term in docs/CONCEPTS.md is one the tool uses.

Where this comes from

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