Development record
development README record-map table omits specs release and release-gate and carries a stale personas-json migration promise
development README record-map table omits specs release and release-gate and carries a stale personas-json migration promise
Evidence
.abcd/development/README.md:6-7 frames the table as "one canonical home per concept" but lists only brief/intents/principles/decisions/roadmap/plans/research — omitting specs/, release/, release-gate/, all load-bearing (record-lint's spec_lifecycle/spec_id_unique/record_schema → specs; surface_coverage → release/surface.json; gate_lockstep → release-gate/README.md). :19 says personas.json "migrates to embedded Go data when the intent surface is built" — under-describing its now-shipped role as the persona_registry SSOT read by a blocker lint.
Adversarial verdict: CONFIRMED table omission (nitpick); "migration condition met" REFUTED
specs/ is a first-class record family (record_schema registers spc as a peer store; abcd <id> dispatches spc-N), not a sub-artefact of intents. The directory_coverage warn covers only specs/'s own missing README, not the parent table. The personas "condition met" framing does not survive (grill sub-verb unshipped → the intent surface is arguably not complete), so the residual is only that the parenthetical omits personas.json's shipped SSOT/lint role. Fix: add three table rows + one clause on personas.json's persona_registry role; ideally an index_drift region so the row set is gated (the iss-38 shape). Not prior art: iss-42 corrected a different row of this table.
Frontmatter
| id | iss-319 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | nitpick |
.abcd/work/issues/resolved/iss-319-development-readme-record-map-table.md
open on GitHub ↗ · commit history ↗
mentions2
- 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.
- 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.