Development record
The record entry and the record-families page use 'record family' for two different sets.
The record entry and the record-families page use 'record family' for two different sets.
A naming conflict (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/glossary/core/record.md:32— "One lifecycle-bucketed set of records of a single kind" - End B:
.abcd/development/brief/glossary/core/record-families.md:4— "The one page that maps abcd's record families (intent, spec, step, bundle, issue, release, status)"
The record entry defines a record family as a lifecycle-bucketed set of filed, identified records of one kind, pointing at the four families embark writes (ADRs, issues, intents, specs). The record-families page uses the same phrase for intent, spec, step, bundle, issue, release and status. That list leaves out ADRs and includes step, bundle, release and status, none of which is a filed record with its own id. One name covers two sets.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 935.
Frontmatter
| id | iss-2610262040295570 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262040295570-the-record-entry-and-the-record-families.md
open on GitHub ↗ · commit history ↗
mentions2
- iss-2610262037095269The record-families page lists the record families as intent, spec, step, bundle, issue, release and status; the inbox chapter calls adr, itd, iss, spc and dcn the record families.
- iss-2610262041364605The record-families page claims to be the one map of record families and lists seven; the reframe intent adds a reframe record family beside other reading families, none of which has a row