Development record
The glossary keeps 'disposition' apart from 'fixed'; launch uses fixed, invalid and deferred as the dispositions of a release-gate finding
The glossary keeps 'disposition' apart from 'fixed'; launch uses fixed, invalid and deferred as the dispositions of a release-gate finding
A terminology drift (severity minor) found by the cross-document consistency pass.
- End A:
.abcd/development/brief/glossary/ledger/disposition.md:25— "Do not call a disposition a resolution: resolved means fixed" - End B:
.abcd/development/brief/04-surfaces/04-launch.md:151— "disposition every finding as fixed, invalid or deferred"
The glossary limits disposition to answering a reading item, in four states (accepted, rejected, declined, held), or to a scope condition, and it warns against calling a disposition a resolution because 'resolved means fixed'. The launch receipts protocol has every finding dispositioned as fixed, invalid or deferred. That is a third vocabulary for the term, and it includes the one value the glossary sets against it.
Evidence: .abcd/work/reviews/2026-10-26-consistency/00-summary.md, finding 347.
Frontmatter
| id | iss-2610262033006141 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610262033006141-the-glossary-keeps-disposition-apart.md
open on GitHub ↗ · commit history ↗
mentions2
- iss-2610262034072525itd-2610141956319695 names a release-receipt finding's fixed/invalid/deferred state its 'disposition'; the capture surface's disposition is the researcher's record answering a reading item
- iss-2610262042284906Disposition has four states in the glossary; the deferred-finding discipline gives it three different words