Development record

ledger

corestableledger

A ledger is a store a command writes on the user's behalf and a human reads back later. Bare, the word means the issue ledger: the structured per-repo capture store at .abcd/work/issues/, working-tier data by adr-32, with open/, resolved/ and wontfix/ as its buckets.

Senses

Sense	The one spelling	Where it lives
The captured-issue store	the issue ledger, or bare "the ledger"	`.abcd/work/issues/`, via `commands/capture.md`
Origin, grounds and disposition stamped at the point of commitment	the provenance ledger	`roadmap/phases/phase-7-ledger.md`
The append-only record of every disembark and embark run	the voyage ledger	voyage, `~/.abcd.noindex/voyage/<source-root-sha>/`
Source-to-decision provenance for the local sources corpus	the sources ledger	`04-surfaces/07-library.md`
The warm material a cold reading must not see, and its stores	ledger content, or the warm side	warm and read-block in the ledger context, which govern this sense
The uncommitted side where framing traces stay	the local ledger side	adr-50, adr-55

"Ledger content" in the cold-reading chapters means the warm sense. The reading surface says nothing in the repository's tiering prevents a reading reaching ledger content, meaning the warm material and its stores that the read-block exists to keep from it. Read as the issue ledger, that sentence says something else entirely, so the qualifier carries the whole claim, and the ledger context's warm entry is the canonical definition.

Where the record disagrees. The fifth sense is a side, not a store: adr-50 and adr-55 use "the local ledger side" for where framing traces live, which is a place no ledger command writes to. The glossary keeps the phrase because both ADRs are ratified, and marks it as the one sense that names no store.

When to use

Use bare "the ledger" only where the issue ledger is unambiguous — inside capture surface prose, or beside a iss-N id. Name the ledger in full everywhere else.

When NOT to use

Do not use "ledger" for the decision records in .abcd/work/decisions/, which the record calls the decision log. Do not use it for the native transcript store or the memory substrate: both are stores, neither is append-or-move over identified records.

Examples

"A half-formed observation goes to /abcd:capture; the issue ledger is where it lands."
"The provenance ledger adds conjecture granularity as a grounds argument on the selection surfaces."
"Writing to the destination passes the safety gate, and the run is appended to the voyage ledger."

record families — the one page that maps the record families and how they relate
record — what a ledger holds
voyage — the operations namespace the voyage ledger lives in
construal — the framing statement whose history stays on the local ledger side
reading-position — what "ledger content" is withheld from

Frontmatter

term	ledger
bounded_context	core
status	stable
aliases	issue ledger
definition	An append-or-move store a command writes and a human reads back, the issue ledger under .abcd/work/issues/ when the word stands bare; inside the cold-reading experiment the word means the warm material and its stores, which the read-block keeps from a reading (the ledger context's entries govern that sense). Four further ledgers share the word and are always named in full.