Belief Premise Register¶
Artifact — instantiates Warranted Belief Formation
A standing ledger of the propositions a decision currently rests on, each with its confidence and scope, an owner, an adoption state, and a recheck date.
A Belief Premise Register is the durable ledger of the beliefs a plan, model, or policy is currently standing on. It answers a question no gate or comparison answers: months after a decision, which propositions are we still treating as true, who owns each, and when were they last checked? Its defining move is turning adopted beliefs into a maintained inventory — each entry has an adoption state (live, suspended, retired), a confidence-and-scope tag, a named owner, and a recheck date — so a load-bearing assumption cannot silently go stale. It is not the place claims are compared and not the moment they are gated; those happen elsewhere and their winners get logged here. The register is memory and maintenance: it exists so that when the world changes, you can find every decision resting on the belief that just broke.
Example¶
A product org commits to building a self-serve onboarding flow. The strategy rests on premises that everyone "knows" but no one has written down. The Belief Premise Register makes them entries: P1 — "the majority of churn happens in the first session" (confidence: high; scope: SMB segment only; owner: analytics lead; recheck: quarterly). P2 — "customers prefer self-serve to a guided call" (confidence: moderate; scope: under-50-seat accounts; owner: PM; recheck: after the next NPS wave).
Two quarters later the analytics lead's recheck on P1 finds churn has shifted to week three. Because P1 was a registered premise with dependent decisions attached, the team can immediately see that the entire self-serve bet was resting on it, mark P1 suspended, and reopen the plan — instead of discovering the broken assumption only after another two quarters of building on it. The register did not decide anything; it made sure the belief the decision depended on could not quietly rot unnoticed.
How it works¶
- One entry per adopted premise, admitted only after it has been gated or compared elsewhere — the register holds conclusions, not candidates.
- Each entry carries state, owner, confidence/scope, and a recheck date, so the belief is both attributed and scheduled.
- Dependent decisions are linked, so changing a premise's state immediately shows what must be revisited.
- State transitions are logged — live → suspended → retired — giving a history of what the organization believed and when it stopped.
- The recheck cadence is enforced, not aspirational; an overdue premise is flagged as unmaintained.
Tuning parameters¶
- Admission bar — how much warrant a belief needs before it earns an entry. A high bar keeps the register lean and trusted; a low bar makes it comprehensive but noisy.
- Recheck frequency — per premise, tuned to how fast its underlying reality moves. Frequent rechecks catch drift early at real maintenance cost.
- Owner granularity — one steward for the whole register versus a named owner per premise. Per-premise owners raise accountability but diffuse oversight.
- Dependency depth — logging only direct dependents versus full downstream chains. Deeper linking makes blast radius visible but is heavier to maintain.
When it helps, and when it misleads¶
Its strength is institutional memory: it stops confidence and scope caveats from being stripped away as beliefs travel downstream, and it converts "we assumed that" from a post-mortem lament into a live, owned, dated record — much as an engineering or project assumption register keeps a plan's load-bearing premises explicit and revisitable.[n1]
Its failure mode is the stale register: created with fanfare, never maintained, so its recheck dates lapse and its confidence tags fossilize — at which point it is worse than nothing, lending false authority to premises no one has revisited. A related misuse is dumping every passing belief into it until the signal drowns. The guarding discipline is to keep the admission bar high, enforce the recheck cadence as a real obligation with real owners, and treat an unmaintained entry as suspended rather than trusted.
How it implements the components¶
belief_state_transition_record— each entry's live/suspended/retired state and its logged history are recorded and maintained here.belief_decay_or_recheck_cadence— the owner-plus-recheck-date on every premise is the register's signature, forcing periodic re-examination.confidence_and_scope_label— every entry carries the confidence and scope it holds within, kept attached as the belief is reused downstream.
It does not assemble the underlying evidence or the reading each claim assumes (warrant_basis_register, interpretation_frame_boundary) — that is its nearest twin, Claim-Warrant Matrix. The matrix compares rival candidates at decision time; the register is the standing ledger of the ones already adopted.
Related¶
- Instantiates: Warranted Belief Formation — the register is the premise-inventory the archetype recommends for decisions, models, and policies.
- Consumes: Claim-Warrant Matrix — the matrix's selected claim becomes a registered premise.
- Sibling mechanisms: Belief Adoption Checklist · Claim-Warrant Matrix · Doxastic Commitment Ladder · Bias and Pressure Prompt · Falsification Trigger Card · Reflective Belief Dialogue · Confidence and Scope Label Template
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: A standing ledger of the propositions a decision currently rests on, each with its confidence and scope, an owner, an adoption state, and a recheck date, making its operative form a durable account of actual events, decisions, or transitions whose value depends on history or provenance.
Independent corroboration: The frozen evidence defines Belief Premise Register as 'A standing ledger of the propositions a decision currently rests on, each with its confidence and scope, an owner, an adoption state, and a recheck date', so its operative form is Record, Log & Register.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Project and risk management established assumption logs and registers that record a plan's assumptions, assign ownership, connect them to decisions, and schedule validation or review.
Related originating lineages:
- Accounting & Auditing — Ledger discipline contributes dated, stateful entries, ownership, and preserved transitions.
- Philosophy — Epistemology supplies propositions, warrant, confidence, scope, and rational revision.
Review resolution: PMI formally defines an assumption log as the project document recording assumptions and constraints, and its assumptions-management guidance requires ownership, scheduled reviews, repeat testing, status, and traceability. UK model guidance likewise specifies owner, review date, and refresh date for assumptions. Those are the defining mechanics of this register, making organizational management primary; ledger form and epistemic content are formative additions.
Attribution caveat: The page applies an established organizational assumption register to epistemic premises and adds confidence, scope, and belief-state transitions.
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:
- Project Management Institute — Lexicon of Project Management Terms
- Project Management Institute — Using Assumptions Effectively
- UK Government — Should Cost Modelling Development Guidance
Notes¶
[n1] An assumption register is a standard project- and risk-management artifact: a maintained list of the assumptions a plan depends on, each with an owner and review status, so that when an assumption proves false its dependents can be traced and revisited. The Belief Premise Register applies the same discipline to decision-guiding beliefs generally. ↩