Propositional Mode Governance¶
Keep propositions in the right epistemic mode and permit only the operations that mode licenses.
Essence¶
Propositional Mode Governance prevents a common collapse in reasoning: treating every sentence-like thing as the same kind of claim. A proposition can have the same content while occupying different epistemic modes. “This mechanism causes the effect” can be a hypothesis in a research plan, a belief in a decision meeting, an assumption in a model, a premise in an argument, a conjecture in a theory, or an asserted finding in a report. The content alone does not tell users what they are allowed to do with it.
The archetype therefore adds a status layer over propositions. The layer says: this proposition is currently an assumption, hypothesis, axiom, premise, conjecture, belief, asserted finding, estimate, value premise, or open question; here is why; here is what you may do with it; here is what must happen before it can change status.
Compression statement¶
Propositional Mode Governance is a reasoning-governance archetype for systems where the same proposition may be treated as a fact, assumption, axiom, hypothesis, premise, belief, conjecture, estimate, norm, or open question. It separates proposition content from epistemic mode, records why the mode was assigned, defines which operations that mode allows, and controls transitions between modes. The output is not just a label; it is an operating discipline for what may be relied on, tested, proved, challenged, communicated, updated, or discharged.
Canonical formula: proposition + epistemic_mode + assignment_basis + operation_license + transition_rule + obligation_record -> disciplined_reasoning_use
When This Archetype Applies¶
No catalog groundingNone of the structural conditions is currently represented by an accepted prime or domain-specific abstraction.
Diagnostic problem
A system contains propositions whose epistemic modes are implicit, unstable, inconsistently communicated, or collapsed into generic claim text, causing actors to rely on, test, prove, challenge, or communicate them under the wrong operating rules.
Applicability expression4 distinct conditions
groundedpartly groundedopen
4 conditions, all required.
4Required in every casenumbered 1–4
These hold no matter which pattern applies.
Mixed propositional modes · open
Claims, assumptions, hypotheses, premises, axioms, estimates, and beliefs appear together in one artifact.
Examples include strategy decks, research memos, mathematical proofs, model cards, risk registers, policies, and requirements documents. In this condition set, the requirement is: Claims, assumptions, hypotheses, premises, axioms, estimates, and beliefs appear together in one artifact.
Prematurely used proposition · open
A proposition must be used before it is fully warranted.
The system must know whether it is using the proposition as an assumption, a working hypothesis, a decision premise, or a provisional belief. In this condition set, the requirement is: A proposition must be used before it is fully warranted.
Context-bounded acceptance · open
A proposition is accepted within one system but challengeable outside it.
Axioms, model primitives, policy values, definitions, standards, and institutional premises often have this inside/outside structure. In this condition set, the requirement is: A proposition is accepted within one system but challengeable outside it.
Contingent conclusion · open
A conclusion depends on temporary premises, scope conditions, or unresolved tests.
The dependency must remain visible so the conclusion is not reported as unconditional. In this condition set, the requirement is: A conclusion depends on temporary premises, scope conditions, or unresolved tests.
Other requirements and context (2)
Why these sit outside the expression
Application gate — it governs whether applying the archetype is appropriate or material, rather than defining the structural problem itself.
Deployment constraint — it constrains how the intervention must be deployed, not the situation that calls for it.
Application gateDifferent modes imply different obligations.
Hypotheses require tests; assumptions require monitoring; premises require discharge or scope; asserted facts require warrant; axioms require boundary declaration. In this archetype, the relevant application gate is: Different modes imply different obligations. It narrows when choosing or applying the archetype is warranted or decision-relevant.
Deployment constraintTeams or tools move propositions across documents, models, databases, or decisions.
Mode labels and transition history must travel with the proposition, not remain in the original author’s head. In this archetype, the relevant deployment constraint is: Teams or tools move propositions across documents, models, databases, or decisions. It identifies a boundary that responsible implementation must respect.
Coverage
0 of 4 conditions grounded · 4 open.
Key components¶
| Component | Description |
|---|---|
| Propositional Unit Inventory ↗ | The inventory decomposes prose, requirements, arguments, models, and research artifacts into proposition-level units. This matters because mode governance cannot attach to a vague paragraph. It needs an inspectable target: a proposition that can be relied on, tested, challenged, scoped, or updated. |
| Epistemic Mode Taxonomy ↗ | The taxonomy defines the local set of modes. The best taxonomy is not the most philosophical taxonomy; it is the smallest set whose modes imply different obligations. A useful taxonomy usually distinguishes asserted findings, assumptions, hypotheses, axioms, premises, conjectures, estimates, value premises, beliefs, and open questions. |
| Licensed Operation Matrix ↗ | The matrix is the heart of the archetype. It states which operations each mode licenses. An assumption may be relied on temporarily but must be reviewed. A hypothesis must be tested or retained as unconfirmed. An axiom may be used for derivation inside a system but not treated as an empirical discovery. A premise may support an argument only under its declared scope. A conjecture may guide exploration but not serve as settled evidence. |
| Mode Transition Protocol ↗ | Mode labels are not static decorations. A hypothesis may become a supported finding after evidence; an assumption may become a rejected assumption after monitoring; an axiom may be replaced after external critique; a premise may be discharged or carried forward conditionally. The transition protocol records what changed, why, and who authorized it. |
| Obligation Register ↗ | Each mode creates work. The obligation register tracks that work: tests to run, premises to discharge, assumptions to expire, axioms to scope, findings to warrant, and open questions to escalate. This turns epistemic hygiene from an aspiration into a managed workflow. |
Common mechanisms¶
The simplest implementation is an Epistemic Status Ledger that lists propositions, modes, owners, evidence, obligations, and transitions. For documents, a Claim Status Labeling Standard and Decision Memo Epistemic-Mode Section are often enough. For formal reasoning, an Axiom Boundary Statement and Premise Discharge Checklist are more important. For models and knowledge bases, a Mode-Operation Matrix or Epistemic Mode Linter can detect mismatches between mode and use.
The critical test is whether the mechanism changes permitted operations. If a label says “hypothesis” but everyone still cites it as a fact, the mechanism is cosmetic.
Parameter dimensions¶
- Mode granularity: how many modes the local taxonomy recognizes.
- Evidence threshold: what must happen before a proposition can be promoted.
- Scope strictness: how narrowly assumptions, axioms, and premises are bounded.
- Transition authority: who may change a proposition’s mode.
- Communication visibility: whether labels are internal metadata, public labels, or both.
- Automation level: whether tools enforce mode restrictions or humans review them.
- Decision stakes: how strict the mode gate must be before action.
Invariants to preserve¶
The content of a proposition is separable from the mode in which it is held. A mode label must imply permitted operations and obligations. Transitions must be recorded. Scope must travel with the proposition. Confidence must not replace mode. A proposition may be useful while still not being a fact.
Outcomes¶
When the archetype works, decisions become more honest about their epistemic basis. Research teams stop reporting hypotheses as findings. Modelers stop treating assumptions as evidence. Formal systems make their primitives visible. Policy documents separate facts from values, estimates, and legal premises. Reviewers can challenge the right layer instead of arguing against a blended mass of claims.
Neighbor distinctions¶
Knowledge-Warrant Audit asks whether a claim’s support justifies confidence. Propositional Mode Governance asks what kind of epistemic commitment the proposition occupies and what operations follow from that mode. The two often work together.
Uncertainty Explicitness communicates unknowns and uncertainty. Propositional Mode Governance distinguishes roles that are not reducible to uncertainty level: an axiom can be certain inside a system, a hypothesis can be plausible, and an assumption can be operationally necessary despite weak evidence.
Implicit Assumption Surfacing makes hidden assumptions explicit. Propositional Mode Governance starts once propositions are explicit and governs their modes and transitions.
Hypothesis Testing Frame governs claims under test. Propositional Mode Governance covers hypotheses but also axioms, premises, assumptions, conjectures, beliefs, estimates, values, and asserted findings.
Deductive Chain Validation checks whether conclusions follow from premises. Propositional Mode Governance helps decide what a premise is, whether it is temporary, and whether it has been discharged.
Failure modes¶
The most common failure is label without license: documents add epistemic status labels but do not change review, use, or communication. Another common failure is assumption hardening, where temporary planning assumptions become settled facts through repetition. Hypothesis promotion by rhetoric occurs when plausible stories become conclusions before evidence arrives. Axiom scope confusion occurs when system primitives are treated as empirical discoveries or when internal axioms are attacked without recognizing the system boundary. Strategic relabeling occurs when actors mark inconvenient claims as “just hypotheses” or convenient assumptions as “facts.”
Examples¶
In a scientific lab, the archetype separates background findings, working assumptions, hypotheses under test, measurement estimates, and open questions before interpretation. In formal mathematics, it separates axioms, definitions, temporary premises, conjectures, lemmas, and theorems. In product management, it separates verified requirements, design assumptions, risk hypotheses, legal constraints, and open questions. In policy analysis, it separates empirical facts, forecasts, legal premises, model assumptions, and value judgments.
Non-examples¶
A confidence scale alone is not this archetype. An assumption register alone is not this archetype. A proof checker alone is not this archetype. A disclaimer at the end of a report is not this archetype. The distinguishing feature is mode-specific operation governance.
Common Mechanisms¶
10 documented mechanisms across 7 implementation forms.
The grouping reflects forms represented among the mechanisms currently documented for this archetype; an absent form is not necessarily an impossible implementation.
Assessment, Review & Assurance · 2 mechanisms
- Epistemic Mode Linter — A tool or review pass that flags mode mismatches, such as treating an assumption as a verified fact or citing a conjecture as settled evidence.
- Premise Discharge Checklist — A checklist that ensures temporary premises or proof assumptions are either discharged, scoped, or explicitly carried into the conclusion.
Control, Automation & Runtime · 1 mechanism
- Assumption Expiry Timer — A date, event, or evidence trigger requiring an assumption to be renewed, tested, replaced, or retired.
Decision, Gate & Allocation · 1 mechanism
- Hypothesis Promotion Gate — A review point that prevents a hypothesis from being promoted to accepted claim or operating premise without specified tests, evidence, and caveats.
Interface, Display & Cue · 1 mechanism
- Proposition Lifecycle Board — A board or workflow that moves propositions through modes while preserving obligations and transition records.
Record, Log & Register · 1 mechanism
- Epistemic Status Ledger — A ledger that lists propositions, current modes, assignment bases, owners, dependencies, obligations, review dates, and transition history.
Representation, Specification & Plan · 2 mechanisms
- Axiom Boundary Statement — A statement that declares which axioms or primitives are accepted inside the system and how they may be examined from outside that system.
- Decision Memo Epistemic-Mode Section — A decision memo section that separates facts, assumptions, hypotheses, premises, estimates, values, and unknowns before action is authorized.
Rule, Policy & Commitment · 2 mechanisms
- Claim Status Labeling Standard — A style and metadata standard for marking statements as fact, assumption, hypothesis, axiom, premise, conjecture, belief, estimate, or question.
- Mode-Operation Matrix — A table mapping each epistemic mode to allowed, required, discouraged, and forbidden operations.
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (7)
- Assumption: A proposition treated as true for the purposes of some reasoning without being currently demonstrated within it, forming the load-bearing layer between what is given and what is concluded.
- Axiom: A claim a system declines to derive — a load-bearing starting point accepted without proof so that the rest of the structure can be built on top of it.
- Belief Formation: Commitment-transition by which an agent comes to hold a proposition as true and act accordingly.
- Deductive Reasoning: General to specific conclusions.
- Epistemic Action: Changing the environment not to advance the goal directly but to make the next mental step cheaper, trading muscle for cognitive load.
- Epistemic Mode Of A Proposition: The same proposition can be held in different epistemic modes — asserted-fact, assumption, axiom, hypothesis, premise, belief, conjecture — and the mode, independent of the content, gates which operations are licensed on it: you may provisionally rely on an assumption, must test a hypothesis, cannot refute an axiom within its system, must discharge a premise.
- Hypothesis Testing (Null vs. Alternative): Null vs alternative evaluation.
Also references 23 related abstractions
- Abductive Reasoning: Infer the hypothesis that would best explain a surprising observation, accepted provisionally and held defeasibly against better candidates.
- Accountability: Responsibility for actions.
- Boundary: Defines system limits.
- Classification: Sorting entities into discrete categories by explicit rules, turning unbounded variation into a finite, reusable map for downstream reasoning and action.
- Completeness: No gaps in structure.
- Constraint: Limits possibilities to guide outcomes.
- Context: Surrounding state that selects which content a fixed focal signal carries.
- Data Integrity: Accuracy and consistency preserved.
- Decision: Committing to one alternative from a set under uncertainty and trade-off, collapsing open deliberation into a chosen path and foreclosing the others.
- Epistemic Humility: Calibrating the confidence of one's claims to the actual strength of the evidence and staying open to revision when new information arrives.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Assumption-Hypothesis Separation · subtype · recognized
A variant that prevents propositions provisionally relied on for action from being confused with propositions actively under test.
- Distinct from parent: The parent governs all proposition modes; this variant concentrates on the recurring assumption-versus-hypothesis boundary.
- Use when: A plan, model, research design, or decision contains both operating assumptions and testable hypotheses; The system is tempted to treat untested assumptions as findings or to treat hypotheses as already licensed premises; Different review obligations apply to assumptions and hypotheses.
- Typical domains: scientific research, product strategy, risk management, machine learning modeling
- Common mechanisms: assumption expiry timer, hypothesis promotion gate, decision memo epistemic mode section
Axiom Boundary Management · governance variant · recognized
A variant that declares which propositions are treated as primitive inside a formal or institutional system and how they can be critiqued from outside it.
- Distinct from parent: The parent governs all proposition modes; this variant specializes in axioms and primitives.
- Use when: A reasoning system, proof, model, policy, contract, or institution rests on primitives that are not refuted within the system; Reviewers need to distinguish internal derivability from external critique of foundational commitments; Different audiences may operate inside and outside the same axiom boundary.
- Typical domains: mathematics, formal methods, constitutional design, organizational policy
- Common mechanisms: axiom boundary statement, mode operation matrix, epistemic status ledger
Premise Discharge Tracking · implementation variant · candidate
A variant that tracks temporary premises or conditional assumptions until they are discharged, scoped, or carried forward explicitly.
- Distinct from parent: The parent governs the broader proposition lifecycle; this variant focuses on the proof or argument obligation attached to premises.
- Use when: Arguments, proofs, legal analyses, or decision chains contain temporary premises used for a bounded inference; Downstream conclusions risk inheriting assumptions that were supposed to be discharged; Reviewers need to know which conclusions are unconditional and which remain premise-dependent.
- Typical domains: mathematics, law, software verification, policy analysis
- Common mechanisms: premise discharge checklist, epistemic mode linter, epistemic status ledger
Near names: Epistemic Status Governance, Claim Status Discipline, Assertion-Assumption-Hypothesis Separation, Epistemic Status Labeling, Propositional Attitude Mode Governance.
Editorial Notes¶
Problem Classification¶
Classification: Representation, Classification & Model Misfit → Ontology, Identity, State & Part–Whole Modeling
Problem kernel: propositions lack explicit epistemic modes governing permitted operations
Rationale: Propositions lack explicit, stable representation of whether they are provisional, formal, normative, conditional, hypothetical, or settled, so actors apply operations their modes do not license. Logical validity describes the downstream invalid inferences; the earlier modeling defect is that proposition modes are collapsed into generic claim text, explicitly named in the ontology subfamily.
Boundary considered: Correctness, Conformance & Formal Validity Failure → Logical Claim & Derivation Validity
Why this classification prevailed: Ontology modeling represents which epistemic mode a proposition occupies; logical validity governs whether operations and conclusions are sound once those modes are explicit.
Review outcome: Adjudicated after independent review; high confidence.