Development record
The intent chapter has an armed record-lint rule that checks the promote back-link, while the lint contract lists that check as an unbuilt full-corpus tier.
The intent chapter has an armed record-lint rule that checks the promote back-link, while the lint contract lists that check as an unbuilt full-corpus tier.
A premise contradiction (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/04-surfaces/05-intent.md:511— "related_issues_backlinkflags an intent'srelated_issuesentry whose issue'srelated_intentsomits the intent" - End B:
.abcd/development/brief/05-internals/06-lint.md:54— "for example a promote back-link between an intent and its source issue, which needs both files in view"
05-intent names related_issues_backlink as an armed record-lint rule. It flags an intent's related_issues entry when that issue's related_intents leaves the intent out. 06-lint gives that same promote back-link as its example of a check for a full-corpus tier that is a design target and not yet built. The check is either armed in the record gate or not yet built.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 427.
Frontmatter
| id | iss-2610262033399864 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262033399864-the-intent-chapter-has-an-armed.md
open on GitHub ↗ · commit history ↗