INKWIRE(7) argument errors INKWIRE(7)
motte-and-bailey
Motte and Bailey
Advance a bold claim, retreat to a modest one when challenged, then quietly re-advance.
NAME
Definition
Named after the medieval arrangement of a fortified tower on a mound (the motte) beside a rich but indefensible farmstead (the bailey). The arguer occupies the bailey when unchallenged and retreats to the motte when attacked.
The bailey is the interesting claim — sweeping, useful for recruiting, easy to state. The motte is the tame claim that nobody disputes. The move is to defend the tame version while continuing to be understood as holding the bold one.
What makes it a fallacy rather than ordinary hedging is the return trip. Once the objection is spent, the bold claim comes back out, unmodified. The concession was never a concession.
SIGNALS
-
S1
Two versions of one claim are in circulation
The version that gets attention is strong; the version that gets defended is weak. Ask which one the person would defend in print.
-
S2
The retreat happens only under pressure
Nothing in the argument's own development motivates the weaker claim. It appears at the moment of attack and evaporates when the attack stops.
-
S3
Objections are never recorded
After the exchange, the strong version is restated as though the objection had been answered. Nothing was integrated; the argument is exactly where it started.
Three checks, in order
- Ask for the strong claim to be stated in one sentence, then ask whether that sentence is still held.
- Offer to accept the weak claim in writing, and watch whether the strong one is withdrawn. If agreement is refused, the weak claim was a shelter, not a position.
- Check whether the retreat survives the next conversation. A concession that lasts one reply is a tactic.
Where the link breaks
| The bailey (advocated) | The motte (defended) |
|---|---|
| Review is unnecessary | Review should not slow things down |
| The tool replaces the team | The tool removes repetitive work |
| The study proves the effect | The study is consistent with the effect |
EXAMPLES
"Modern teams do not need code review — shipping fast beats reviewing." Pressed on the bugs that reached production, the reply is "I never said review is useless, I said it should not be a bottleneck." A week later, the original claim is back in the next thread.
Why it fails
The defensible claim — review should not be a bottleneck — is uncontroversial and nobody attacked it. The claim that drew attention was that review is unnecessary. Defending the second while holding the first is the whole manoeuvre.
Kindred entries
- [F] begging-question The conclusion is loaded into the premise, so the argument travels in a circle.
- [F] false-dilemma Two options are presented as the only ones, so rejecting one awards the other.
- index — /t/fallacy/
[+] Notes and objections 3
- Is this just changing your mind under pressure?
- Changing your mind leaves the weaker claim in place permanently. Motte-and-bailey leaves the weaker claim in place only for the duration of the objection, then restores the original.
- Why is it so effective in writing rather than conversation?
- In writing the two versions can live in different documents. The bold claim is in the headline; the tame one is in paragraph nine; the reader who objects is answered with paragraph nine and never sees the headline corrected.
- What is the honest alternative?
- State the strongest version you actually hold and defend it. If you find the strong version indefensible, retire it in public — that is what a concession looks like.
Scope — Reference material for reading arguments, not professional advice.