Assumption Audit¶
An audit procedure — instantiates Premise–Action Decoupling
Sweeps a whole plan or decision for the assumptions it silently rests on, keeps the load-bearing ones, tests their support, and names what would have to be true instead where support is thin.
Assumption Audit is the reasoning-level pass that takes an entire plan, argument, or decision — not a single sentence — and drags its unstated premises into daylight. Every plan runs on assumptions; most are never written down, and the dangerous ones are exactly those confident enough to go unspoken. The audit enumerates them, then does the two things that make it more than a brainstorm: it triages by materiality, keeping the load-bearing few and discarding the trivia, and it tests each survivor's support, grading how well the evidence actually backs it. For the load-bearing assumptions that turn out thin, it names the alternative — what would have to be true instead, and what that would do to the plan. Its whole point is to decouple the plan's commitments from its premises: to know which beliefs the action is leaning on, so a wrong belief can be caught before it takes the action down with it.
Example¶
A relief agency is finalizing a pre-positioning plan for cyclone season: warehouse stock forward, deliver cash grants so families buy locally. The plan reads as a set of actions, but the audit rewrites it as the set of beliefs those actions require. Enumerated: the coastal road stays passable; forward warehouses have spare capacity; caseload will resemble the last event; and — the quiet one — local markets keep functioning, since the entire cash-grant approach assumes families can actually buy food.
Triaged by materiality, two assumptions are load-bearing enough to decide the plan's fate: road passability and market function. Tested for support, they split. Road passability has a recent engineering survey behind it — well warranted. Market function has almost nothing but hope; in the last severe cyclone, markets collapsed for weeks. So the audit marks that assumption thin and load-bearing and states the alternative plainly: if markets don't function, cash aid fails and an in-kind pipeline is needed. That single line converts a hidden bet into an explicit contingency the plan can pre-build and watch for, rather than discover in the wreckage.
How it works¶
- Enumerate the premises — walk the plan and list what must be true for each step to work, forcing out the assumptions confident enough to have gone unwritten.
- Triage by materiality — keep the assumptions the plan's outcome actually hinges on; set aside the ones that could be wrong without moving the result. Effort goes only to the load-bearing few.
- Test support — for each survivor, ask what evidence backs it and grade the warrant honestly: solid, contested, or hope dressed as fact.
- Name the alternative — for every thin-but-load-bearing assumption, state what would be true instead and what that does to the plan, so the exposure is concrete rather than a vague worry.
The distinguishing discipline is that it operates on a decision's whole premise-set, prioritizing by consequence — not decomposing one utterance, and not testing a claim in isolation for its own sake.
Tuning parameters¶
- Materiality threshold — where you draw the line between load-bearing and ignorable. Set it low and the audit drowns in trivial premises; set it high and a quietly critical assumption slips under the bar.
- Evidence bar — how much warrant an assumption must have to pass. A strict bar surfaces more exposures but can stall a plan on unavoidable uncertainty; a lax bar clears the plan but launders hope as fact.
- Search breadth — how hard you hunt for hidden assumptions versus cataloguing the stated ones. Broad search catches the dangerous unspoken premises but costs time and can feel adversarial.
- Disposition routing — what a flagged assumption gets marked for: drop, test now, build a contingency, or hand to standing monitoring. Tunes the audit between a one-off scrub and the front-end of ongoing governance.
When it helps, and when it misleads¶
Its strength is catching the fatal premise while it is still cheap — before the plan is built on it — and doing so in priority order, so scarce scrutiny lands on the assumptions that can actually sink the effort. It converts "we just assumed that would hold" from a post-mortem line into a pre-mortem checklist.
It misleads when the triage or the evidence bar is off. A materiality threshold set wrong is the classic failure: the whole value is in catching the load-bearing assumption, and an audit that spends itself on trivia while missing the one that matters is worse than none, because it manufactures false confidence. It also tends to over-scrutinize the assumptions that are easy to articulate and under-scrutinize the ones so deep they never get listed. And it is readily run backwards — staged to bless a plan's premises after the plan is chosen, rather than to stress them. The discipline that keeps it honest is to fix the materiality bar and the evidence standard up front, and to treat the audit as a live instrument re-run as conditions change, not a one-time sign-off.[n1]
How it implements the components¶
Assumption Audit realizes the premise-testing components — the reasoning-layer work of deciding which beliefs a decision may safely lean on:
materiality_threshold— its triage step: it separates the load-bearing assumptions from the ones that could be wrong without changing the outcome, so scrutiny is rationed by consequence.evidence_test— it grades each material assumption's warrant against the evidence actually available, distinguishing solid from contested from hope.alternative_assumption— for each thin-but-critical premise it states what would be true instead and what that does to the plan, turning an exposure into a concrete, plannable alternative.
It does not extract premises from a single utterance (embedded_premise, surface_action) — that is Literal Content Parsing; and it does not own or record premises over time (assumption_owner, consequence_record) — that is the Decision Premise Register, which consumes the audit's findings.
Also instantiates¶
Assumption Stress Testing — Stress testing goes one step past grading warrant: it deliberately breaks, reverses, delays, or compounds a premise to trace what fails, then converts the fragility into safeguards, buffers, staged commitments, and monitoring triggers. The audit is the discovery-and-prioritization front end of that loop — it does not itself break assumptions, but it produces the ranked, evidence-graded premise set the break-tests operate on. The distinct angle from the primary facet is that here the audit feeds a downstream pre-commitment fragility process rather than being the whole intervention: its output is the input to stress design.
key_assumption— the audit names the premises the plan actually depends on, the objects a break-test will later violate.assumption_inventory— it gathers scattered explicit and implicit premises into one structured view rather than leaving them across slides and models.criticality_filter— its materiality triage plus warrant grading is the filter that selects which assumptions deserve full stress testing (consequence, uncertainty, weak evidence).
False Convergence Prevention — Here the problem is not a plan's premises but an apparent settling — a team that looks aligned, a decision that looks ready to close. Often that agreement rests on a shared background assumption nobody has challenged, so the smooth consensus is brittle. Turned on a convergence claim, the audit decomposes the agreement into the premises it quietly rests on and grades their support, exposing the unexamined, thinly-warranted assumption the apparent stability depends on — a very different use from sweeping a plan for its own load-bearing beliefs.
hidden_variation_probe— the audit breaks an apparently settled agreement into its underlying premises, surfacing an unexamined shared assumption the convergence is silently leaning on.convergence_validation— it serves as one of the checks in the validation bundle, testing whether the agreement reflects genuine shared judgment or a common blind spot before commitment.
Implicit Assumption Surfacing — This archetype's demand is narrower and more structural than a materiality sweep: it insists that each hidden premise be stated as a proposition, connected to the specific decision it silently governs, and given a disposition — revise, monitor, preserve deliberately, or document as owned risk. The audit realizes exactly this chain when it does not merely list premises but maps how each one steers a step of the plan and marks the thin ones for a defined follow-up. The distinct angle from the primary facet is the influence-path-and-disposition emphasis: making a premise inspectable and dispositioned, not just triaged by consequence.
implicit_assumption— the audit forces out the premises confident enough to have gone unwritten and states them as testable propositions.influence_path— it connects each surfaced premise to the choice, exclusion, or risk it shapes, so the assumption's leverage on the plan is explicit.update_or_documentation_rule— its disposition step (drop, test now, build a contingency, hand to monitoring) is the rule for what happens to each premise that survives surfacing.
Parsimony Filter — Parsimony Filter uses the audit for pruning rather than protection. Its problem is unjustified complexity — a plan resting on more premises than the evidence supports, brittle precisely because so many things must hold. Surfacing the assumptions and testing which are load-bearing lets the unsupported ones be removed, deferred, or demoted to explicit risks, so the plan depends only on premises that earn their place. The angle differs from the primary facet: not "catch the fatal premise before it sinks the plan," but "strip the unnecessary assumption-load so the plan is not needlessly brittle."
assumption_list— the audit makes visible the premises a candidate depends on, the raw inventory parsimony works from.necessity_test— its keep-the-load-bearing-few / discard-the-trivia step is the necessity test: does this premise materially change adequacy, or can it go?complexity_cost— by exposing a plan built on many thin premises, the audit surfaces assumption-load as a fragility cost rather than a sign of rigor.
Simplification Audit — Simplification Audit is a downstream governance pass over an artifact that has already been simplified — a compact model, rule, or summary — asking what the simplification removed and whether any of it now matters. Pointed at the premises a simplification introduced, the audit surfaces what was assumed away and checks whether those assumptions still hold in the current context, flagging the ones whose failure would make the simplified artifact wrong, unfair, or unsafe. The distinct angle from the primary facet is the target: assumptions created by a simplification, tested for continued validity, rather than the native premises of a fresh plan.
omitted_detail_list— the audit catalogs the premises a compact artifact quietly assumed away, the omissions its validity now rests on.omission_relevance_criterion— its materiality-and-warrant grading judges which assumed-away premises still hold and matter for the decision versus which can stay omitted.revision_path— where an assumption no longer holds, the audit states what would be true instead, feeding a caveat, exception, or revision of the simplified artifact.
Related¶
- Instantiates: Premise–Action Decoupling — Assumption Audit is the pass that isolates a plan's premises so a wrong one can be caught before it constrains the action.
- Sibling mechanisms: Decision Premise Register · Literal Content Parsing · Burden-of-Proof Rule · Context-Condition Testing · Presupposition Challenge Marker
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Sweeps a whole plan or decision for the assumptions it silently rests on, keeps the load-bearing ones, tests their support, and names what would have to be true instead where support is thin, making its operative form a bounded evaluation of existing evidence or work that produces a finding or disposition.
Independent corroboration: The frozen evidence defines Assumption Audit as 'Sweeps a whole plan or decision for the assumptions it silently rests on, keeps the load-bearing ones, tests their support, and names what would have to be true instead where support is thin', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Futurism & Strategic Foresight
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: RAND assumption-based planning established identification of load-bearing assumptions, vulnerability assessment, alternatives, and signposts under uncertainty.
Related originating lineages:
- Military & Strategic Studies — RAND developed Assumption-Based Planning for uncertain strategic and Army planning, including load-bearing assumptions and signposts.
- Organizational & Management Science — Planning reviews, ownership, and contingency routing turn the premise audit into an operational governance practice.
- Philosophy — Epistemology supplies the distinction between an asserted premise and one warranted by evidence, plus explicit alternatives.
Review resolution: RAND identifies Assumption-Based Planning as its tool for uncertain planning and describes the same sequence of underlying assumptions, load-bearing selection, vulnerability, signposts, and hedges. That establishes futurism and foresight as the best primary taxonomy fit, with military strategy, organizational planning, and philosophy as formative contributors. Statistics and engineering are important testing settings rather than the mechanism's principal lineage.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
- RAND — A Methodology for Developing Army Acquisition Strategies for an Uncertain Future
- CIA — Structured Analytic Techniques: Key Assumptions Check
Notes¶
The audit is a point-in-time sweep; it grades warrant as of now. The premises it flags for watching do not monitor themselves — a "test later" or "hold under review" disposition is only as good as the standing ledger it is handed to. That ongoing tracking is the Decision Premise Register's job; the audit feeds it rather than replacing it.
[n1] Assumption-Based Planning (RAND; James Dewar) is the established practice of identifying the load-bearing assumptions under a plan, judging their vulnerability, and setting signposts to watch — the same load-bearing-first logic this audit applies, and the reason materiality triage precedes evidence testing. ↩