Development record
whether an adopted open-licensed style guide (Google, Microsoft, GitLab, errata-ai/Vale packages) replaces parts of the house writing guide, and how a managed repo names its chosen guide in .abcd/rules.json: routed out of itd-141 at its closure (adr-54); files as its own intent if it goes live
issueopennitpickiss-2608280801427648
whether an adopted open-licensed style guide (Google, Microsoft, GitLab, errata-ai/Vale packages) replaces parts of the house writing guide, and how a managed repo names its chosen guide in .abcd/rules.json: routed out of itd-141 at its closure (adr-54); files as its own intent if it goes live
Remedy grounds (2026-09-29)
- Vale projects name a guide by its package-library name (Google, Microsoft, write-good) in a Packages key (https://docs.vale.sh/keys/packages, checked 2026-09-30), which gives rules.json a naming scheme managed repositories already recognise.
- Adversary filter (prefer-sota): running Vale itself is a new external tool, and a vendor guide's rules can collide with the house guide's host-agnostic and British-English rules, so the remedy borrows the naming, not the engine. Rejected: bundling the packages.
Frontmatter
| id | iss-2608280801427648 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | nitpick |
.abcd/work/issues/open/iss-2608280801427648-whether-an-adopted-open-licensed-style.md
open on GitHub ↗ · commit history ↗
mentions2
- adr-54Punctuation enforcement stays mechanical-only
- itd-141docs-lint enforces the writing style guide's machine-checkable rules: an em dash inside a list item, a lower-case letter opening a list lead-in after its colon, and a capital letter after a semicolon are flagged as findings, with code spans and fenced blocks masked, so the canonical style guide's machine-enforceable subset is a shipped gate rather than a review habit — and the guide marks a rule machine-enforced only once its lint ships