Problem
Changelog and release-notes ledes — the ## What section of a PR body — drift into second-person address. The KB records seven occurrences across two repositories since mid-June, two rated high impact.
lede-voice.md models third-person register in every worked example but states no rule about grammatical person, so changelog-writer self-audits clean. One capture records the subagent reading Rule 1's outcome test ("what the reader will experience, see, or be able to do") as licensing direct address.
Proposed solution
Add a fourth rule to lede-voice.md, under "The rules":
Rule 4: No second person
Do not use the second person.
Under "The rules" rather than the "Voice" section: grammatical person is mechanically checkable in a way register and jargon are not, and "The rules" is the numbered set that voice-checklist.md mirrors and changelog-writer's audit output is keyed to.
One sentence, with no rationale paragraph and no Bad/Good pair — the doctrine's existing examples already model the register.
lede-voice.md and nothing else. Mirroring the rule into voice-checklist.md (reaching commit and merge-pr), adding a Rule 4: line to changelog-writer's audit-output template, and constraining the person of summarize-change's outcome: dispatch field are all deliberately deferred, so a later round can tell whether the single-surface change sufficed.
Acceptance criteria
Must have
Problem
Changelog and release-notes ledes — the
## Whatsection of a PR body — drift into second-person address. The KB records seven occurrences across two repositories since mid-June, two rated high impact.lede-voice.mdmodels third-person register in every worked example but states no rule about grammatical person, sochangelog-writerself-audits clean. One capture records the subagent reading Rule 1's outcome test ("what the reader will experience, see, or be able to do") as licensing direct address.Proposed solution
Add a fourth rule to
lede-voice.md, under "The rules":Under "The rules" rather than the "Voice" section: grammatical person is mechanically checkable in a way register and jargon are not, and "The rules" is the numbered set that
voice-checklist.mdmirrors andchangelog-writer's audit output is keyed to.One sentence, with no rationale paragraph and no Bad/Good pair — the doctrine's existing examples already model the register.
lede-voice.mdand nothing else. Mirroring the rule intovoice-checklist.md(reachingcommitandmerge-pr), adding aRule 4:line tochangelog-writer's audit-output template, and constraining the person ofsummarize-change'soutcome:dispatch field are all deliberately deferred, so a later round can tell whether the single-surface change sufficed.Acceptance criteria
Must have
lede-voice.mdstates an explicit prohibition on second-person address, placed under "The rules".lede-voice.mdand no other file.