Development record
three current-state records cite ADRs at development/research/adr/, a path that does not exist and a layout adr-30 explicitly rejected; all three are backticked code spans links_resolve never checks
issueresolvedminoriss-352
three current-state records cite ADRs at development/research/adr/, a path that does not exist and a layout adr-30 explicitly rejected; all three are backticked code spans links_resolve never checks
Evidence
brief/03-evidence/03-open-questions.md:28(live routing list; the two sibling pointers resolve),brief/03-evidence/04-tradeoffs.md:69(meta-section about the file's present role — line 3 of the same file links../../decisions/adrs/correctly),intents/disciplines/itd-37-modification-grammar.md:75(active discipline, present tense).development/research/adr/does not exist; all ADRs live atdevelopment/decisions/adrs/, and adr-30:66 namesresearch/adr/as a rejected alternative (that site is intended narration — untouched).- All three are backticked code spans, invisible to
links_resolve(internal/core/lint/lint.go:1398matches markdown links only) — a distinct gap from iss-303 (fragments). - The 2026-07-06 plan-consistency review caught this at four sites; one was fixed, three remain, no ledger handle carried the remainder.
- Refuter verdict: CONFIRMED substantive. Fix: repoint all three; render as markdown links so the class is gated.
Frontmatter
| id | iss-352 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-352-three-current-state-records-cite-adrs-at.md
open on GitHub ↗ · commit history ↗
mentions5
- adr-30Design-record information architecture — flat artefact-type folders
- dcn-26082000000000022026-08-20 — bughunt round 2 (branch bughunt-b/round-2): captured the round-2 records (iss-346..iss-357, with the two colliding ids re-minted as iss-358/iss-359), fixed
- iss-303links_resolve (internal/core/lint/lint.go checkLinks) strips the #fragment before resolving and skips same-file # links, so no gate validates heading anchors even though both record-lint and docs-lint declare the rule blocking and the Makefile advertises it as catching a broken relative link; ~18 broken anchors sit on a green tree. Proposed: extend the rule to slug the target file's ATX headings and validate the fragment, landing warn-first
- iss-391research notes README routes phase-scoped research to research/phase/N/ and names research/adr/ as a sibling — both layouts adr-30 rejected and the gated research-children index denies — and its Related display texts sit one level short of their hrefs
- itd-37Every Spec Externalises How It Should And Shouldn't Be Modified