Development record
development README conventions sentence says issues graduate rather than a ledger contradicting accepted adr-32 and the live work-tier ledger
development README conventions sentence says issues graduate rather than a ledger contradicting accepted adr-32 and the live work-tier ledger
Evidence
.abcd/development/README.md:23-24 (Conventions): "Issues graduate into intents/ or principles/ rather than a ledger." Contradicts accepted ADR-32 (decisions/adrs/0032-issue-ledger-is-working-tier-data.md: "The issue ledger lives in the work tier — .abcd/work/issues/"), the ~290-entry ledger, and record-lint rules (issue_id_unique/issue_impact_valid/record_schema pointing at .abcd/work/issues).
Adversarial verdict: CONFIRMED (minor)
The paragraph names all three tiers, so it is not scoped to the development/ dir; its pre-ADR-32 ancestor (plans/2026-07-06-go-rebuild.md:142) carried the scoping clause "Issues are not a record folder" and the README compressed it into a mechanism denial that is now false. Observed 2026-07-08 (research note :119), routed to iss-36/iss-38, both resolved WITHOUT fixing this line — resolved-but-unfixed, no open item covers it. Fix: replace with a sentence consistent with adr-32 (the ledger is working-tier data at ../work/issues/, and a design-significant issue graduates from it into intents/ or principles/).
Frontmatter
| id | iss-317 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-317-development-readme-conventions-sentence.md
open on GitHub ↗ · commit history ↗
mentions3
- adr-32The issue ledger is working-tier data, not authored record
- iss-36retired-name banlist population: roughly fifty stale references to retired locations and identifiers survive in the record, and the drift outlived a dedicated same-day consistency pass — development/activity (38 refs in the brief), .work/issues and bare .work/ as a root path (11 refs), scripts/abcd/, .abcd/logbook, .flow/, .github/workflows/lint.yml and lint-corpus.yml, --since-staged, and the python-lint-names pattern narrowly missing bare intent_lint (used by intents/README.md and adr-34). Detector (per retire-the-name and fix-the-detector): add each retired spelling to record-lint banned_tokens with allow_context for genuinely historical passages, widen the intent_lint pattern, then drain the references BEHIND the armed bans — never ahead of them. Acceptance corpus: the reference counts above; the bans are proven when they flag all ~50 on first run and the count ratchets to zero.
- iss-38hand-maintained index drift: intents/README.md corpus listings have drifted from the filesystem; commands/README.md lists three of the seven plugin verb files; internal/README.md still describes core as two capabilities with adapter/scanner as a planned seam; the repo README Layout omits skills/ from the plugin surface. Detector (per adr-5 derive-dont-store): hand enumerations of sibling files are generated or deleted — a lint flags a README that enumerates directory contents by hand, or the enumeration is emitted by tooling with a drift test. Acceptance corpus: the four stale indexes above.