Development record
Seven registry personas are given he/she/his/her pronouns across intents/drafts (itd-92,97,98,108,126,128) and intents/shipped (itd-100), violating the they/them persona discipline (itd-79); review-enforced convention with no mechanical gate, concentrated in one 2026-08 authoring batch — a cosmetics-batch cleanup
Seven registry personas are given he/she/his/her pronouns across intents/drafts (itd-92,97,98,108,126,128) and intents/shipped (itd-100), violating the they/them persona discipline (itd-79); review-enforced convention with no mechanical gate, concentrated in one 2026-08 authoring batch — a cosmetics-batch cleanup
Evidence
- Registry personas given gendered pronouns:
intents/drafts/itd-92:20,itd-97:32,itd-98:28,itd-108:48,itd-126:17,29,31,itd-128:23;intents/shipped/itd-100:17,25. - Rule:
itd-79-persona-registry.md:18,personas.json:4,intents/README.md:241, dcn-2607080000000005 -- every persona is they/them.
Refuter verdict -- CONFIRMED, severity NITPICK (recorded, not fixed)
All ten referents are registry personas (real cited authors correctly excluded); none is a first-person self-description; the narrative attribution clauses sit outside the quotes. No drafts/ exemption exists; itd-100 is shipped/. But comparable persona findings (iss-300, iss-49) are filed nitpick, and no document states the rule wrongly -- only ~7 of ~88 persona-quote files deviate, concentrated in one 2026-08 authoring batch. A natural addition to the iss-49 cosmetics batch; recording is the outcome.
Frontmatter
| id | iss-338 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | nitpick |
.abcd/work/issues/resolved/iss-338-seven-registry-personas-are-given-he-she.md
open on GitHub ↗ · commit history ↗
mentions13
- dcn-26070800000000052026-07-08 — Persona SSOTs reconciled: `personas.json` is the single registry
- dcn-26082000000000012026-08-20 — bughunt round 2 (branch bughunt-a/round-2): captured iss-331..iss-343 and fixed (ids 339-343 re-minted from an initial 326-330 after main concurrently took those numbers in the v0.6.1 cut)
- dcn-26082000000000052026-08-20 — bughunt round 3 (branch bughunt-a/round-3): captured twelve findings (iss-360..iss-369, plus two renumbered to iss-373/iss-374 after round 2's own collision re-mint landed inside this round's block — the week's fourth collision,
- iss-49record cosmetics batch: an orphaned .gitkeep; two verbatim doctrine blocks duplicated in the record; the ACKNOWLEDGEMENTS ccpm entry was added retroactively against its own same-change rule; the brief lacks a one-page arc42 crosswalk and an open-questions precedence line; 05-personas.md should be rewritten role-first with personas.json as the roster source of truth. Low individual impact; batched so the cleanup pass has one handle. Detector: none warranted beyond the existing lints — this is the residue after detector-shaped clusters were extracted, fixed directly per the fix-the-detector one-off bound.
- iss-300The persona glossary (brief/glossary/core/persona.md) and brief/01-product/05-personas.md say the persona picker 'chooses at random', contradicting personas.json and itd-79 whose rule is 'selection is by role, never by name'; the glossary's worked examples also assign off-role names (Carol as product lead, Alice as developer)
- itd-79Personas Come From the Registry; the Role Picks the Name
- itd-92abcd tells every repo the truth about its fence
- itd-97The Facilitator Is a Mode, Not a Person
- itd-98Solo vs. Duo Is Measured, Not Debated
- itd-100Alice Reads One Page and Knows Exactly Where abcd Stands in the Agentic-AI Landscape
- itd-108The plugin installs from the curated release artifact, not the repo, and every cut release reaches users automatically
- itd-126A Team Shares One Bibliography Without Sharing Anyone's Corpus
- itd-128One canonical YAML scalar resolver: frontmatter exports the single null/bool/quote resolution helper and the capture, lint, lifeboat, and memory decoders all delegate to it, so a cross-package verdict split on any scalar axis becomes unrepresentable