Development record
regime
A regime is written by the definition and carried on the output contract; it is never typed at invocation, because a value the operator could set tests nothing. The four values are generative (candidate configurations that did not exist), explicative (statements of what the frame already carries), evaluative (characterisations of candidates against declared criteria, never an ordering or a recommendation) and registrative (named gaps between two things already present, never a proposed resolution). The supply-regime check validates at ingest what a reading was licensed to produce, as distinct from what it saw.
When to use
Use it of the licence and of the check that holds it.
When NOT to use
Do not call the regime a mode of the instrument or a level of trust; it is a licence on output, not a scale of risk.
Related terms
- record families — the one page that maps the record families and how they relate
- position
- disposition, the researcher's answer to what a regime produced
Frontmatter
| term | regime |
|---|---|
| bounded_context | ledger |
| status | draft |
| aliases | supply regime |
| definition | The licence a reading holds at its position, naming what it may produce and what the ingest verb refuses or flags: generative, explicative, evaluative or registrative. |
.abcd/development/brief/glossary/ledger/regime.md
open on GitHub ↗ · commit history ↗