Development record
commitment records (issue ledger, .abcd/work/decisions/, intents) must not name an external tool before its adoption is decided; names live in the dated research note. Convention exists only as maintainer guidance + docs-lint harness rules scoped to docs/ and README; the working record has no principle file or record-lint rule enforcing it
issueopenminoriss-218
commitment records (issue ledger, .abcd/work/decisions/, intents) must not name an external tool before its adoption is decided; names live in the dated research note. Convention exists only as maintainer guidance + docs-lint harness rules scoped to docs/ and README; the working record has no principle file or record-lint rule enforcing it
Remedy grounds (2026-09-29)
- Why: the record's convention needs a list of undecided tools to be lintable at all; a per-candidate banned token is the existing mechanism (.abcd/record-lint.json), and the ruling is unanswered, so both answers are stated.
- Rejected: seeding the rule from the harness/* patterns in .abcd/docs-lint.json, which name adopted hosts the record legitimately discusses; widening the roots also touches the owed question in iss-2608271804494611.
Frontmatter
| id | iss-218 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-218-record-tier-tool-naming-convention.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2608271804494611everything under .abcd/work/ sits under no lint root: record-lint's root is .abcd/development and docs-lint's roots are docs and README.md, so the issue ledger, the reviews charter, rulesets/, DECISIONS.md, the .abcd root config files, the plugin trees, and every root prose file except README.md are gated by nothing — which means structural fixes in those areas can silently regress. iss-279 and iss-2608230752354928 capture two slices (docs-lint roots; relative links under work/); this record is the umbrella: decide the lint-root coverage for the working tier and root prose, or record why they stay ungated.