Development record
The docs-lint ban on the retired role word (itd-2609212137129937, ac-2) reaches the docs roots, the command pages, .abcd/rules.json and the bundled rules source only: .abcd/docs-lint.json's 'roles/retired-role-word' entry lists extra_roots commands, .abcd/rules.json and internal/core/rules/defaults, and the top-level roots are docs and README.md. The brief (.abcd/development/brief, 22 occurrences before the sweep, the largest share), the principles (.abcd/development/principles, 5) and the personas registry (.abcd/development/personas.json) were swept by ac-1 but are in no root the token reads, and the ac-5 test walks only the rendered help, commands/*.md and agents/*.md, so the word can return to the brief or a principle with nothing refusing it, against the press release's 'the word cannot come back' and the mechanism claim that agents say what they read (the OPINIONS domain points agents at the principles).
The docs-lint ban on the retired role word (itd-2609212137129937, ac-2) reaches the docs roots, the command pages, .abcd/rules.json and the bundled rules source only: .abcd/docs-lint.json's 'roles/retired-role-word' entry lists extra_roots commands, .abcd/rules.json and internal/core/rules/defaults, and the top-level roots are docs and README.md. The brief (.abcd/development/brief, 22 occurrences before the sweep, the largest share), the principles (.abcd/development/principles, 5) and the personas registry (.abcd/development/personas.json) were swept by ac-1 but are in no root the token reads, and the ac-5 test walks only the rendered help, commands/.md and agents/.md, so the word can return to the brief or a principle with nothing refusing it, against the press release's 'the word cannot come back' and the mechanism claim that agents say what they read (the OPINIONS domain points agents at the principles).
Grounds
- pursued: the retired role word written into a brief page, a principle or the personas registry is refused by abcd lint docs as a blocker, while an intent body is not; a brief or principle page carrying the word unescaped that lints clean would show it wrong.
Frontmatter
| id | iss-2610020731591808 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2610020731591808-the-docs-lint-ban-on-the-retired-role.md
open on GitHub ↗ · commit history ↗
mentions2
- iss-2610021502084298No check meets the retired role word in an intent's press release at the record: the docs-lint rule roles/retired-role-word roots at the docs, the command pages and the rules, so a shipped or planned intent's press release carrying it is refused only when the site composer renders it as the landing page's hero quote, which is how itd-60's first MET audit broke the site-render gate (iss-2610021446271464). After the R5 reword of itd-60, thirteen shipped press releases still carry the word (itd-65, itd-66, itd-67, itd-69, itd-73, itd-74, itd-93, itd-102, itd-111, itd-114, itd-125, itd-2609111003026787, itd-2609212137129937), so the next MET audit ingested for any of them refuses the render again on a branch that only recorded an audit; the product thinker's ruling R5 (2026-10-02) accepted that a future slip breaks the build and did not ask for this check. Related to iss-2610020731591808, which names the brief, the principles and the personas registry as swept but unguarded.
- itd-2609212137129937abcd's text names the product thinker or the technical facilitator, never the maintainer