Decision Memo Epistemic-Mode Section¶
Document template — instantiates Propositional Mode Governance
A decision memo section that separates facts, assumptions, hypotheses, premises, estimates, values, and unknowns before action is authorized.
A Decision Memo Epistemic-Mode Section is a fixed part of a decision document that, before anyone authorizes action, breaks the argument into its propositions and sorts them by epistemic mode — and states what each mode licenses the reader to do. Its distinguishing idea is that separation is tied to operations at the point of decision: a fact may be relied on, an assumption is a bet to be monitored, a hypothesis must still be tested and may not yet be cited as a reason to act, a premise scopes the conclusion, a value is normative rather than empirical, an open question blocks or bounds. Unlike a portable labeling convention, this lives inside one memo and its purpose is authorization: the decision-makers who sign the memo are signing off on the mode assignments, not just the recommendation.
Example¶
A product team is drafting the go/no-go memo for launching a paid subscription tier, and the memo carries a mandatory epistemic-mode section. It separates the argument: Fact — "the free base has roughly N active users" (verified analytics; rely on it). Assumption — "about a fifth of power users will convert to paid" (a bet on comparable products; proceed on it but monitor weekly). Hypothesis — "bundling extra storage lifts conversion" (plausible, untested; must be A/B tested; may not be used as a reason to launch). Premise (scoped) — "legal confirms auto-renew is compliant" — but only for the EU market; the recommendation is therefore scoped to EU. Value — "we will not dark-pattern the cancellation flow" (a commitment, not an empirical claim). Open question — "retention past month three is unknown." The VP approves an EU-only launch, seeing exactly which lines are load-bearing bets versus established facts — and, because the storage claim is flagged hypothesis, knowing it may not be leaned on until the test reads out.
How it works¶
The section performs two moves a normal brief skips. First it decomposes the memo's case into discrete propositions rather than letting them blur into persuasive prose. Then it sorts each into a mode and states the operation that mode licenses — rely / bet-and-monitor / test-before-citing / scoped-to / hold — so no proposition is used above its warrant. Scoped premises carry their boundary explicitly into the recommendation, so a conclusion true "for the EU only" is never read as unconditional. The section is deliberately positioned at the authorization point: it is the artifact reviewers examine and ratify before signing, which is what distinguishes it from a caveat box appended for cover.
Tuning parameters¶
- Mode granularity — how many modes the section recognizes. Finer separation resists false certainty but can bury the call; coarser is readable but blurs distinctions that matter.
- Placement — front-and-center versus an appendix. Up front, the modes shape how the recommendation is read; buried, they become deniable.
- Sign-off requirement — whether reviewers must explicitly ratify the mode assignments, not merely the recommendation. Requiring it turns the section into a real review; skipping it invites rubber-stamping.
- Scope explicitness — how loudly a scoped premise's boundary is stamped onto the conclusion.
- Value-premise inclusion — whether normative commitments are surfaced as their own mode or quietly folded into "facts."
When it helps, and when it misleads¶
Its strength is that reviewers can challenge the right layer: a value premise cannot masquerade as a fact, a hypothesis cannot be cited as a settled reason, and a scoped premise cannot smuggle an unconditional-sounding conclusion past the room. It is a working instance of the fact–value distinction — the insight that empirical claims and normative commitments are different kinds of thing and cannot be derived from one another.[n1]
Its failure mode is that the section is run backwards: the recommendation is decided first and the mode section bolted on afterward as tidy-looking cover, its hypotheses quietly filed as facts to make the case look stronger. A subtler misuse hedges every line until no actual call survives. The guarding discipline is that reviewers must sign off on the mode assignments themselves — a hypothesis marked as fact is the thing to catch — and that the memo must still make a call, an explicit recommendation, not a fog of qualifications.
How it implements the components¶
propositional_unit_inventory— the section decomposes the memo's argument into discrete propositions so each can be assigned a mode instead of hiding in prose.dependency_and_scope_trace— scoped premises carry their boundary into the recommendation, so a conclusion that holds only under a condition is never presented as unconditional.stakeholder_mode_review— it is the artifact at which decision-makers examine and ratify the mode assignments before authorizing action.
It does not define a reusable, transportable marking convention (communication_label_standard) — that is Claim Status Labeling Standard, its nearest twin: the memo section sorts one argument at the moment of decision, whereas the standard is the portable convention any statement carries everywhere. Nor does it define which operations each mode licenses in the abstract (licensed_operation_matrix), which is Mode-Operation Matrix.
Related¶
- Instantiates: Propositional Mode Governance — the section is where modes are separated and ratified at the point of authorizing action.
- Consumes: Claim Status Labeling Standard supplies the mode vocabulary and markers the section sorts propositions into.
- Sibling mechanisms: Assumption Expiry Timer · Axiom Boundary Statement · Claim Status Labeling Standard · Epistemic Mode Linter · Epistemic Status Ledger · Hypothesis Promotion Gate · Mode-Operation Matrix · Premise Discharge Checklist · Proposition Lifecycle Board
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Decision Memo Epistemic-Mode Section operates as a non-executable information artifact that externalizes static or prospective structure because it a decision memo section that separates facts, assumptions, hypotheses, premises, estimates, values, and unknowns before action is authorized.
Independent corroboration: The frozen evidence defines Decision Memo Epistemic-Mode Section as 'A decision memo section that separates facts, assumptions, hypotheses, premises, estimates, values, and unknowns before action is authorized', so its operative form is Representation, Specification & Plan.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Philosophy
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Epistemology and logic cohered distinctions among fact, premise, assumption, hypothesis, value, and unknown, including limits on what each kind of proposition can warrant.
Related originating lineages:
- Organizational & Management Science — Decision-memo practice supplied the fixed authorization document and operational consequences attached to each mode.
Review resolution: Epistemology and logic cohered distinctions among fact, premise, assumption, hypothesis, value, and unknown, including limits on what each kind of proposition can warrant.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] The fact–value distinction — Hume's observation that an "ought" cannot be derived from an "is" alone — is why a decision memo must keep value premises in their own mode: a normative commitment stated as though it were an empirical finding lets a choice pose as a discovery, exactly the collapse this section prevents. ↩