Development record
The glossary defines a record as an itd, spc, adr, iss or rdg document; the record dispatcher treats dcn, adm, srp and rfm ids as records and gives rdg no dispatch.
The glossary defines a record as an itd, spc, adr, iss or rdg document; the record dispatcher treats dcn, adm, srp and rfm ids as records and gives rdg no dispatch.
A terminology drift (severity nitpick) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/glossary/core/record.md:4— "One identified, filed document that a command mints and a lint gate reads — an itd-N, spc-N, adr-N, iss-N or rdg-id." - End B:
.abcd/development/brief/04-surfaces/08-abcd.md:83— "spc-N,adr-N,dcn-N,adm-N,srp-Norrfm-Nand reports, read-only, what that"
glossary/core/record.md defines a record as one identified, filed document, 'an itd-N, spc-N, adr-N, iss-N or rdg-id'. 08-abcd's abcd < record-id> takes iss, itd, spc, adr, dcn, adm, srp and rfm ids and reports 'what that record is', and says the reading families have no record dispatch. The two pages give different sets as what 'record' covers, so the term's extent is not fixed.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 448.
Frontmatter
| id | iss-2610262033548897 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | nitpick |
.abcd/work/issues/open/iss-2610262033548897-the-glossary-defines-a-record-as-an-itd.md
open on GitHub ↗ · commit history ↗
mentions2
- iss-2610262035505656The glossary defines a record by five id kinds and leaves out dcn-; the ideate chapter calls a decision a record cited by its dcn- id like any other
- iss-2610262041590949The glossary defines a record as an itd, spc, adr, iss or rdg id; the decisions intent mints decision records with ids of their own.