Development record
lapse
ledgerdraftlapse
A lapse is evidence, not confession. The causal claim behind the ledger is that recording at the point of commitment prevents retrospective reconstruction, and the lapse log is the evidence that bears on that claim. The three opening entries are written at the outset rather than discovered: the pre-tooling window, anticipation, and commitments made outside the tooling.
When to use
Use it for a discipline that gave way, with the point in the process at which it did.
When NOT to use
Do not capture a code defect as a lapse; a lapse is about the record's discipline, not about the tree.
Related terms
- record families — the one page that maps the record families and how they relate
- warm, the side the lapse log lives on
Frontmatter
| term | lapse |
|---|---|
| bounded_context | ledger |
| status | draft |
| aliases | lapse-log entry |
| definition | A recorded point at which the recording discipline was suspended, deferred or evaded, captured as its own category in the issue ledger and timestamped at the lapse rather than at write-up. |
.abcd/development/brief/glossary/ledger/lapse.md
open on GitHub ↗ · commit history ↗