Development record
research/notes/README.md prescribes topic-kind note naming while adr-30 and development/README.md ratify date-prefixed naming and the record-lint successor plus ideate both emit dated notes; the notes README is the outlier and 29 of 41 notes are dated
issueresolvedminoriss-353
research/notes/README.md prescribes topic-kind note naming while adr-30 and development/README.md ratify date-prefixed naming and the record-lint successor plus ideate both emit dated notes; the notes README is the outlier and 29 of 41 notes are dated
Evidence
research/notes/README.md:29-35prescribes<topic>-<kind>.mdwith no date slot; adr-30:47 (accepted, unsuperseded) rules "Plans, research notes, and the Tier-2 DECISIONS.md log are date-prefixed";development/README.md:24-25restates it;record-lint.json:17names the successor asresearch/notes/<date>-<slug>.md;internal/core/ideate/ideate.go:50writes dated notes. Disk: 29 dated / 12 not (one numeric-prefixed, a form line 35 disowns).- Prior art: flagged in the 2026-07-06 review (
05-link-structure.md:160) but the iss-42 disposition scoped to note location, not naming; the drift has since inverted sides. - Refuter verdict: CONFIRMED substantive;
notes/README.mdyields to the ADR. Fix rewrites the naming section to<YYYY-MM-DD>-<topic>[-<kind>].md, keeps the kind vocabulary as an optional suffix, notes pre-ADR-30 undated files as legacy, renames nothing.
Frontmatter
| id | iss-353 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-353-research-notes-readme-md-prescribes.md
open on GitHub ↗ · commit history ↗
mentions4
- 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-42record orientation currency: CONTEXT.md is stale on the record trust caveat — its single most important orientation fact; phase-shift updates are not a required handoff step so the staleness recurs structurally; record README routing claims point at moved locations; research/ contradicts its own naming convention. Detector: a handoff checklist rule (a phase shift or trust-caveat change requires a CONTEXT.md update in the same change) plus banlist coverage for the moved routing targets. Acceptance corpus: the four instances above.
- 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