---
name: Argument Audit
status: draft
territory: argumentative-artifact-examination
msi_territory: argument-examination
sources:
  - title: Toulmin, Stephen (1958), The Uses of Argument, Cambridge University Press
    url: https://openlibrary.org/works/OL11860W
  - title: "Walton, Douglas N. (1989), Informal Logic: A Handbook for Critical Argumentation, Cambridge University Press"
    url: https://openlibrary.org/works/OL14852718W
  - title: Walton, Douglas N., Reed, Chris & Macagno, Fabrizio (2008), Argumentation Schemes, Cambridge University Press
    url: https://openlibrary.org/works/OL14852690W
---

# Argument Audit

## Why it matters

Most arguments that feel persuasive and turn out to be wrong don't fail where you're looking. The claim is clear, the evidence is real, the conclusion follows — *if* you grant the one thing nobody said out loud. An argument audit takes the argument apart into its working parts and tests each one separately, so the part that's actually carrying the weight — usually an unstated assumption — stops hiding behind the parts that are fine.

For example: "Crime is up since the new chief took over, so the new policing approach has failed." The claim is that the approach failed. The evidence is that crime rose. The hidden bridge between them — the part nobody states — is that *the approach is what caused the rise, and nothing else changed.* Say that bridge out loud and it buckles: maybe a recession hit, maybe reporting improved, maybe the rise started before the chief arrived. The evidence was true and the claim might even be true, but the argument as given never earned it, because the load-bearing premise was the one left unspoken.

- **What it reveals.** The hidden skeleton under a piece of persuasion — every claim, the evidence offered for it, and crucially the unstated assumption that connects the two — so you can see exactly which premise is doing the work and whether it holds.
- **How it changes the read.** You stop asking *"do I agree with the conclusion?"* and start asking *"does this argument, as written, actually get you there — and which specific step is it relying on that it never defends?"*
- **When to foreground it.** A self-contained piece of reasoning whose logic you want stress-tested — an op-ed, a policy memo, a contract clause, a scientific Discussion section, a debate claim — where the question is whether the argument works, not whether its conclusion happens to be true.
- **What you'd miss without it.** That an argument can be entirely true in its parts and still prove nothing, because the inference connecting the parts is unsupported; skim it and you absorb the conclusion while the broken joint slides past unnoticed.
- **Where it misleads.** It judges the argument as given, not the world: an audit can correctly find that a sloppy argument fails to establish a conclusion that nevertheless happens to be true. Mistaking *"this argument doesn't work"* for *"this conclusion is false"* is the error the discipline most has to guard against.

## Realtime examples

See real, dated analyses where this mode takes an argument from the news apart and tests each premise → **[Argument Audit on Main Street Independent](https://mainstreetindependent.com/analyses/technique/argument-examination/argument-audit)**

## How to invoke it in Ora

You have a self-contained argument — a paragraph or a page that reasons from some evidence to a conclusion — and you want to know whether it actually holds together, not whether you happen to agree with where it lands.

Paste the argument in its full form and ask:

> "Argument audit on this: [paste]. Is each step actually supported, and what is it assuming?"

The phrases *argument audit*, *is each step supported*, and *what is it assuming* are what route you here. Give the whole argument, not a snippet — the most revealing failures show up only when you can see how an early premise is quietly relied on three sentences later, and an excerpt that drops that span hides exactly the joint the audit exists to find.

One boundary worth knowing. This mode tells you whether the argument *works*; it does not tell you whether the conclusion is *true*, and it will not take a side. If what you want is the strongest possible version of the case built up, or a verdict for or against the proposal, that is stance-bearing work — a different tool. The audit produces the clear-eyed read those start from; it stays neutral on purpose.

## How it works

In the 1950s the philosopher Stephen Toulmin noticed that the way people actually argue looks nothing like the tidy syllogisms of textbook logic, and that the textbook was missing the part where real arguments go wrong. So he drew the anatomy of an everyday argument as a set of working parts, and that anatomy is what an argument audit lays bare.

Take a plain one: "Harry was born in Bermuda, so he's a British citizen." The **claim** is the thing you're being asked to accept — *Harry is a British citizen.* The **data**, or grounds, is the fact offered in support — *he was born in Bermuda.* And then comes Toulmin's key move. Between the data and the claim there is always a bridge, a general rule that licenses the jump: *people born in Bermuda are British citizens.* Toulmin called it the **warrant**, and the crucial thing about warrants is that arguers almost never state them. They're the assumptions the argument runs on, left silent because saying them out loud would invite the very scrutiny the arguer would rather skip. Most bad arguments are not bad at the claim or the data — those are right there in plain sight, easy to check. They're bad at the warrant: an unstated bridge that, once you drag it into the light, simply doesn't hold the weight being put on it.

So the heart of the method is this: for every step, recover the warrant the arguer didn't say, write it down, and ask whether it's actually true. Toulmin's anatomy adds three more parts that turn a yes-or-no check into a precise one. The **backing** is whatever stands behind the warrant if someone challenges it — the statute, the study, the track record. The **qualifier** is how strongly the claim is being made — *certainly, probably, in most cases* — because "X proves Y" and "X suggests Y" are different arguments and fail at different strengths. And the **rebuttal** is the set of conditions under which the warrant would *not* hold — *unless his parents were diplomats; unless the law changed* — the exceptions a fair argument acknowledges and a slippery one buries. Audit those exceptions and you often find the whole case lives inside one of them.

Walk the policing example through that grid and the failure has an exact address. Claim: the new approach failed. Data: crime rose. Warrant, dragged into the open: *a rise in crime under a new approach was caused by that approach.* That warrant needs backing — evidence that the approach, and not the economy or a change in how crime gets reported, drove the rise — and the argument supplies none. Its qualifier is doing sleight of hand too: the data support, at most, *crime rose during this period*, but the claim quietly upgrades to *the approach caused it.* And the rebuttal conditions the argument never mentions — a recession, a reporting change, a trend that predates the new chief — are precisely the live alternatives that would have to be ruled out. The audit doesn't declare the conclusion false; the approach may well have failed. It declares something sharper and more useful: *this argument, as written, does not establish that it did,* and it points to the exact unstated premise that would have to be true for it to. That is the difference between disagreeing with a conclusion and showing why the road to it never reached.

## Framework & implementation

*This section uses Ora's own terms for the parts of an analysis, so that if you open the actual mode file they line up. Each is glossed in plain language on first use.*

### Pipeline execution

Argument Audit is the heaviest mode in the **argumentative-artifact-examination** territory — the deep, integrated pass, sitting above the two lighter component modes (`coherence-audit`, which checks the inferential structure, and `frame-audit`, which surfaces the framing) and beside the adversarial `propaganda-audit`. It runs at **Gear 4**, Ora's most thorough setting: a **Depth analyst** and a **Breadth analyst** examine the artifact in parallel and then critique each other (**cross-adversarial evaluation**) before a consolidator integrates the result — depth chasing each inferential joint to the bottom while breadth keeps every claim and every imported assumption in view, each covering the other's blind spot.

The pass works in stages. It first runs the full **coherence pass** — a charitable reconstruction of the argument, then a decomposition of each inferential move into its **Toulmin components** (claim, data, warrant, backing, qualifier, rebuttal — the anatomy from *How it works*), naming any fallacies with full structural specification (the quoted text, the move it makes, the principle it violates, and why it fails *here* rather than as a label slapped on). It runs the full **frame pass** alongside — surfacing the operative frame the argument imports, what it makes salient and what it leaves silent. Then comes the part neither component could produce alone: a **synthesis** that pairs each Toulmin move with the framing bearing on it, catching the cases where a *warrant* secretly rests on a contested frame — an argument that looks internally sound only because a loaded assumption is quietly doing the reasoning. The output is assembled per claim, coherence and frame read together, not stapled side by side.

The mode's reasoning tools ride in its **`ANALYTICAL PERSPECTIVES`** block — the lenses it loads as it works. The load-bearing ones here are the **Toulmin-model** lens (the anatomy that recovers each unstated warrant), **Walton's argumentation schemes with their critical questions** (which classify the *kind* of inferential move — appeal to expert opinion, argument from analogy, argument from consequences — and supply the standard questions each kind must answer to be sound), and the **fallacy-taxonomy** lens (which names structural failures precisely rather than gesturing at them).

### Output contract

The deliverable is a fixed set of sections, so the audit is checkable rather than a verdict you have to take on faith: the **reconstructed argument** (the charitable, explicit restatement, with the unstated premises filled in), the **premises** (each one the argument depends on, surfaced including the silent ones), the **warrants** (the hidden bridges from data to claim, made explicit and individually tested), the **inference structure** (how the moves chain — which premise feeds which claim, where the load actually sits), the **fallacies and structural failures** (each specified with quoted text, the move, the violated principle, and why it fails in context — including failures outside the named-fallacy list, like premise-smuggling, scope shift, and definitional drift), and the **assessment** — the load-bearing verdict that holds two findings apart: *this argument, as given, does not establish its conclusion* versus *this conclusion is false.* The mode delivers the first and refuses the second without independent grounds, flagging where stance-bearing follow-up would be needed instead.

### Origin and evidence

The anatomy at the center of the mode is Stephen Toulmin's. *The Uses of Argument* (1958) broke with the formal-logic tradition by modelling argument as it is actually practised — claim, data, warrant, backing, qualifier, rebuttal — and put the **warrant**, the usually-unstated inferential bridge, where the action is. The mode's second pillar is the tradition of **informal logic and argumentation theory** built largely by Douglas Walton: *Informal Logic* (1989) treats real arguments as dialectical moves to be judged in context rather than abstract forms to be checked for validity, and *Argumentation Schemes* (Walton, Reed & Macagno, 2008) catalogues the recurring patterns of defeasible reasoning — each paired with the **critical questions** that test whether the pattern holds in a given case, the discipline that keeps the audit from rubber-stamping a familiar-looking move. Behind both sits the long lineage of **fallacy theory** — the study, running from Aristotle through modern textbooks, of the recurring ways inferences go wrong — which supplies the named failures the audit can point to precisely.

### Applications and common uses

- **Opinion and persuasion.** The native use: an op-ed, editorial, or manifesto taken apart to show whether its case actually holds and which unstated premise it leans on.
- **Policy and analysis documents.** White papers and policy memos, where a chain of reasoning from evidence to recommendation is exactly what should be stress-tested before anyone acts on it.
- **Scientific and technical claims.** The Discussion section of a paper, where conclusions outrun what the results strictly support — the audit finds the warrant the data don't actually license.
- **Contracts, briefs, and formal reasoning.** Legal and technical arguments where a hidden premise or a buried exception (a rebuttal condition the drafter would rather you not weigh) changes everything.
- **Your own drafts.** Running the audit on an argument you are about to make, to find the joint a critic would go for before you publish it.

### Failure modes and when not to use it

- **Treating "doesn't establish" as "false."** The sharpest misuse: an audit can correctly show a bad argument fails to prove a conclusion that is nonetheless true. The mode keeps those two findings strictly apart and refuses the truth verdict without independent grounds.
- **Fallacy-hunting as a checklist.** Naming fallacies by label without showing the actual inferential move produces pedantry, not insight. The mode requires each named failure to come with quoted text and the specific reason it fails *here*.
- **Excerpt blindness.** Audited on a snippet, the mode cannot see how an early premise is relied on later, which is where motte-and-bailey alternations and frame substitutions across claims live. The full artifact is required; a fragment will defeat the cross-cutting findings.

**When not to reach for it.** When you only care whether a piece of reasoning hangs together internally — the inferential structure alone, with no interest in the framing — the lighter **coherence-audit** is the right tool. When the real question is what *frame* a piece imports — what it makes salient and what it silences — reach for **frame-audit**. And when the artifact is **propaganda** — the strategic deployment of frames combined with deliberate inferential trickery — the audit's neutral, stance-suspending posture is insufficient; route sideways to **propaganda-audit**, the adversarial-stance variant built for persuasion-engineered material.

## Related

- **Coherence Audit** — the lighter component mode in the same territory: it runs the inferential-structure pass alone, when you care whether the argument holds together and not what frame it imports.
- **Frame Audit** — the other component mode: it surfaces the operative frame an argument imports — what it foregrounds and what it leaves silent — the pass this mode runs alongside the coherence check.
- **Steelman Construction** — the stance-bearing route for when you want the argument's strongest possible version *built up* rather than taken apart and tested.
- **Walton Schemes and Critical Questions** — the lens this mode leans on to classify each inferential move and apply the standard questions that decide whether that kind of move actually holds.

## Sources

- [Toulmin, Stephen (1958), The Uses of Argument, Cambridge University Press](https://openlibrary.org/works/OL11860W)
- [Walton, Douglas N. (1989), Informal Logic: A Handbook for Critical Argumentation, Cambridge University Press](https://openlibrary.org/works/OL14852718W)
- [Walton, Douglas N., Reed, Chris & Macagno, Fabrizio (2008), Argumentation Schemes, Cambridge University Press](https://openlibrary.org/works/OL14852690W)