Epistemic Status Ledger¶
Register of record — instantiates Propositional Mode Governance
A ledger that lists propositions, current modes, assignment bases, owners, dependencies, obligations, review dates, and transition history.
An Epistemic Status Ledger is the archetype's authoritative record of record: one row per governed proposition, holding its current mode, why it holds that mode, who owns it, what it depends on, what work is still owed on it, and when it is next due for review. Its distinguishing idea is that it is comprehensive but passive — the single inspectable place where the epistemic state of everything that matters is written down, so that state lives in the register rather than in people's heads. You read the ledger to know where things stand. It does not move propositions through a workflow, does not detect misuse in running text, and does not decide anything; it is the ground truth the active mechanisms write back to.
Example¶
A drug-discovery program keeps an epistemic status ledger for the propositions its campaign turns on. One row: "Target T is druggable" — mode: supported finding; basis: two orthogonal binding assays plus prior literature; owner: the biology lead; dependencies: none open; review: on any new structural data. Another: "Compound C's selectivity holds in vivo" — mode: hypothesis; basis: in-vitro only; owner: pharmacology; obligation: in-vivo selectivity study, due next quarter; depends on: the assay-validity premise two rows up. A third: "the 2 µM potency cutoff" — mode: assumption; basis: a program convention, not a measured threshold; scope: this chemical series only. A scientist joining the program reads the ledger and, in one pass, sees what is established, what is a bet, what is under test, whose it is, and what still has to happen — instead of reconstructing all of that from a year of meeting notes and Slack threads.
How it works¶
The ledger is a register keyed by proposition. Each row carries a small, fixed set of fields: the current mode, the assignment basis (the evidence, stipulation, or authority behind that mode), the owner, the dependencies and scope it inherits or imposes, the open obligations with their due dates, and a history column that logs transitions after they happen. That last column is a record, not an engine: it mirrors transitions authorized under the transition protocol elsewhere, so the ledger stays an account of what is true now and how it got here, without itself carrying out the moves. Its value is entirely in being trusted and current — a canonical single source of truth for epistemic status.[n1]
Tuning parameters¶
- Coverage — every proposition versus only the decision-critical ones. Logging everything is thorough but buries the load-bearing rows; logging too little leaves gaps that quietly fill with assumption.
- Field richness — how many columns each row carries. More fields capture provenance and obligation fully but raise the upkeep cost per row.
- Update discipline — who is allowed to write, and how promptly. A ledger is only as trustworthy as its freshest edit.
- Staleness policy — how review dates flag rows that have gone unexamined, and what happens to a row past its date.
- Access model — a single steward versus shared editing; central control keeps it coherent, open editing keeps it current.
When it helps, and when it misleads¶
Its strength is that it kills the "it's all in someone's head" failure: provenance, ownership, dependency, and outstanding obligations are queryable rather than tacit, so a reviewer can challenge a specific basis and a newcomer can orient in minutes. Its failure mode is ledger rot — a register no one updates is worse than none, because it keeps the authority of a record while quietly lying, and a stale "supported finding" row is more dangerous than an honest blank. Comprehensiveness invites its own noise: a thousand rows can bury the ten that decide everything. The guarding discipline is review dates plus ownership plus ruthless pruning, and treating any row past its review date as suspect until refreshed. The ledger records the outcomes of transitions; it never performs them, so it must be reconciled against whatever actually moves propositions.
How it implements the components¶
mode_assignment_basis— every row records why the proposition holds its current mode: the evidence, stipulation, or authority behind the assignment, not just the label.obligation_register— the obligation and review-date columns are the tracked epistemic work owed on each proposition, with owners and due dates.dependency_and_scope_trace— each row carries what the proposition depends on and the scope within which it holds, so conditional claims are never read as free-standing.
It does not move propositions through modes or execute the transitions its history column merely logs (mode_transition_protocol) — that is Proposition Lifecycle Board, its nearest twin: the ledger is the authoritative record you read, whereas the board is the workflow you work. Nor does it define which operations each mode licenses (licensed_operation_matrix), which is Mode-Operation Matrix.
Related¶
- Instantiates: Propositional Mode Governance — the ledger is the authoritative record of every governed proposition's mode, basis, and obligations.
- Sibling mechanisms: Assumption Expiry Timer · Axiom Boundary Statement · Claim Status Labeling Standard · Decision Memo Epistemic-Mode Section · Epistemic Mode Linter · Hypothesis Promotion Gate · Mode-Operation Matrix · Premise Discharge Checklist · Proposition Lifecycle Board
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: Epistemic Status Ledger operates as a durable record, ledger, register, or trace whose value depends on preserving actual state or history because it a ledger that lists propositions, current modes, assignment bases, owners, dependencies, obligations, review dates, and transition history.
Independent corroboration: The frozen evidence defines Epistemic Status Ledger as 'A ledger that lists propositions, current modes, assignment bases, owners, dependencies, obligations, review dates, and transition history', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Philosophy
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Epistemology established proposition-level distinctions among knowledge, belief, evidence, justification, assumption, and uncertainty.
Related originating lineages:
- Library & Information Science — Records and metadata practice supplied the authoritative register and provenance form.
- Organizational & Management Science — Issue ownership and review cadences supplied accountable upkeep and obligations.
- Security Studies & Intelligence Analysis — Analytic tradecraft operationalized explicit assumptions, evidentiary bases, confidence, indicators, and review.
Review resolution: Stanford's scholarly reference places proposition modes and evidence in epistemology, while ODNI requires explicit uncertainty, assumptions, sources, and change indicators; philosophy is primary for what is governed.
Attribution caveat: No single field supplies the whole ledger; its epistemic vocabulary, analytic controls, and register form are synthesized.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
- Stanford Encyclopedia of Philosophy: Epistemic Logic
- ODNI ICD 203 Analytic Standards
- CIA Tradecraft Primer
Notes¶
The ledger and the Proposition Lifecycle Board describe the same population from opposite stances: the board is optimized for movement (columns, work-in-progress, a standup ritual), the ledger for reference (rows, provenance, an audit trail). Teams often run both — the board to work the flow, the ledger to hold the record — and their one hard requirement is that they be reconciled, or the "record" drifts from what the workflow actually did.
[n1] Single source of truth is the data-architecture principle that each fact should have exactly one authoritative home, so downstream users reconcile to it rather than maintaining divergent copies. An epistemic status ledger applies the principle to the modes of propositions rather than to ordinary data values. ↩