Development record
itd-37 defines the concreteness lint as numbered codes MG001 to MG003; 06-lint says the engine has no numbered codes
issueopenminoriss-2610262038501901
itd-37 defines the concreteness lint as numbered codes MG001 to MG003; 06-lint says the engine has no numbered codes
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/intents/disciplines/itd-37-modification-grammar.md:56— "in the native intent lint with three codes:" - End B:
.abcd/development/brief/05-internals/06-lint.md:14— "The engine carries no numbered code catalogue: rules are named, not numbered"
itd-37 specifies its concreteness lint as three numbered codes, plus MG004 and VR001 elsewhere. 06-lint says the lint engine carries no numbered code catalogue and that rules are named in the JSON configs. Building itd-37 as written breaks the lint contract's naming rule.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 822.
Frontmatter
| id | iss-2610262038501901 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262038501901-itd-37-defines-the-concreteness-lint-as.md
open on GitHub ↗ · commit history ↗
References1
- itd-37Every Spec Externalises How It Should And Shouldn't Be Modifiedrelated