Apply to my task
arXiv:2511.22854 ★ 77 Nov 28, 2025

CRAwDAD: Sharper Causal Reasoning Through a Two-Agent Debate

Key result

Finding: a model can be 90%+ sure of a wrong answer and, without outside critique, stick to it. The study logged 577 such cases. The CRAwDAD method lets you find and fix errors in causal reasoning: telling correlation from causation and stress-testing logic through argument. Two models argue until consensus (4 rounds max). The first gives a structured answer + a confidence percentage. The second looks for holes in the logic and critiques it. If they disagree, rounds of arguments and counterarguments follow. The paradox: even a strong model gains from arguing with a weak one. Qwen3 starts out more accurate than DeepSeek-R1, yet debating it still gives Qwen3 +5% accuracy. The weaker model gains even more: +9%.

CRAwDAD: Sharper Causal Reasoning Through a Two-Agent Debate

CRAwDAD: Sharper Causal Reasoning Through a Two-Agent Debate

02

TL;DR

CRAwDAD is a technique where two models argue with each other until they reach consensus. The first gives a structured answer with a confidence score. The second hunts for logical errors and pushes back. If they disagree, a debate kicks off: arguments, counterarguments, revised positions. Four rounds max.

The headline finding: even a strong model gains from arguing with a weaker one. Qwen3 starts out more accurate than DeepSeek-R1, yet debating with it still lifts Qwen3's results by 5%. The weaker model gains even more: +9% accuracy. Pushback from the opponent forces the model to revisit confident but wrong answers: 577 cases where the model was 90%+ sure and the opponent talked it out of its answer.

The method shines on tricky "what if" questions (counterfactuals). When you have to imagine an alternate reality ("What would have happened if Jake hadn't had coffee before the exam?"), a lone model slips up more often. Debate delivers a +12% accuracy boost on exactly these tasks.

Want this for your own case? Apply this study to your task: AI adapts its method to what you are working on and writes the prompt.

03

Method Blueprint

ROUND 1: Agent A → structured answer + confidence (%)
ROUND 2: Agent B → critique of the logic OR agreement
         ↓
         [If agreement] → FINAL
         [If disagreement] → ROUND 3
         
ROUND 3: Agent A → defends position OR revises
ROUND 4: Agent B → final answer (even without consensus)

Each round is a separate request. Context is passed from one to the next.

04

Example in Practice

Task: You're prepping a pitch for an investor. You need to figure out what actually moves user conversion: the landing page redesign or the new offer.

Prompt (simulated debate in a single request):

You are two analysts arguing about a causal relationship. Keep debating until you reach consensus.

CONTEXT:
- After the landing page redesign, conversion rose from 2% to 3.5%
- At the same time as the redesign, we added a 20% discount for new users
- Both changes went live on the same day

QUESTION: What drove the conversion increase — the redesign or the discount?

DEBATE FORMAT:

[ANALYST A — first answer]
1. Formalization: which cause-and-effect relationships are possible
2. Analysis: which data support each hypothesis
3. Conclusion: what is the most likely cause
4. Confidence: X%

[ANALYST B — critique]
1. Weak spots in Analyst A's logic
2. Alternative interpretation
3. Own conclusion + confidence

[ANALYST A — response to critique]
Defend the position OR revise it in light of the arguments

[CONSENSUS]
Final agreed conclusion. If there is no consensus, explain what data would be needed to settle the dispute.

Result: The model will generate 3-4 rounds of debate. Analyst A might argue the redesign is the cause (better UX → more people reach the offer). Analyst B will point out that without an A/B test you can't separate the effects, and the discount may have been the main driver. The consensus acknowledges the uncertainty and recommends: roll back the discount for a week and measure conversion.

05

Why It Works

The LLM's weakness: a model is often confident in a wrong answer. Especially on causal questions, where you have to separate correlation from causation. The study found 577 cases where the model was 90%+ sure and still wrong. Without outside criticism, it would have stuck to its guns.

The LLM's strength: a model makes an excellent critic when it is explicitly given that role. It finds logical holes, points out alternative explanations, and demands evidence.

How the method works: debate forces a rethink through structured conflict. The first agent has to either defend its position with arguments or admit the mistake. It works even when the opponent is weaker: what matters is the challenge itself, not the strength of the critic.

Control knobs:

  • Number of rounds: 4 is the sweet spot per the study. Fewer, and they don't have time to agree. More, and things stall as the models repeat themselves.
  • Confidence: demand a numeric estimate (%). Models change their minds more often when the opponent is more confident.
  • Roles: you can give the agents different "personalities": optimist vs. skeptic, practitioner vs. theorist.
06

Prompt Template

You are two experts with different positions. Run a structured debate.

TASK: {task description}

DATA:
{facts, figures, context}

QUESTION: {specific cause-and-effect question}

FORMAT:

[EXPERT A]
Analysis:
- Which cause-and-effect relationships are possible
- Which data support my hypothesis
Conclusion: [specific answer]
Confidence: [X]%

[EXPERT B — CRITIQUE]
Weak spots in A's logic:
- [specific errors or gaps]
Alternative interpretation:
- [another explanation of the same data]
My conclusion: [agree/disagree + own answer]
Confidence: [X]%

[EXPERT A — RESPONSE TO CRITIQUE]
[Defend the position with new arguments OR revise it in light of the critique]
Final conclusion: [answer]
Confidence: [X]%

[CONSENSUS]
Agreed answer: [yes/no/more data needed]
Rationale: [why we reached this conclusion]
What remains uncertain: [if anything]

Placeholders:

  • {task description} — the context of the situation
  • {facts, figures, context} — the specific data to analyze
  • {question} — exactly what needs to be determined

🚀 Quick start — paste into the chat:

Here is a two-expert debate template. Adapt it to my task: [your task]. 
Ask me questions to fill in the fields.

[paste the template above]

The LLM will ask about the data, the context, and the specific question, because causal analysis needs facts, not abstractions.

07

Limitations

⚠️ Synthetic benchmark: The study used CLadder, a dataset of "clean" questions. Real business problems are messier: incomplete data, ambiguous wording, hidden variables.

⚠️ Counterfactuals are still hard: Even after debate, accuracy on "what would have happened if..." questions is around 80%. Humans do better (~95% by the researchers' estimates). Don't rely on the model as your only source for high-stakes "what if" decisions.

⚠️ Time: Debate = multiple requests. 10,000 questions took 380 hours. Fine for hard problems, overkill for routine work.

⚠️ Short answers hurt: DeepSeek-R1 often gave 1-2 sentence answers with no reasoning. That made it less persuasive even when it was right. If you simulate a debate, demand detailed answers from both agents.

08

How They Tested It

A team from the University of Calgary took 10,112 questions from CLadder, a benchmark where every question is tied to a formal causal model. The questions are split into three difficulty levels: Rung 1 (statistical associations: "is there a correlation?"), Rung 2 (interventions: "what happens if we intervene?"), Rung 3 (counterfactuals: "what would have happened if?").

The debaters were Qwen3-32B and DeepSeek-R1-Distill-Qwen-32B, two open reasoning models. Picking two different models is deliberate: research shows that same-type agents often "collude" in one direction and miss each other's errors.

Key finding: on Rung 1 (simple questions), 93% were settled without debate: the models agreed right away. On Rung 3 (counterfactuals), a quarter of the questions required an argument. Makes sense: the harder the task, the more room for disagreement.

The surprise: the weaker model (DeepSeek-R1) helped the stronger one (Qwen3). Even when DeepSeek was wrong, its critique pushed Qwen to re-examine and reinforce the correct answer. The value of debate isn't in the opponent being right, it's in the challenge itself.

The baseline was GPT-4 + Chain-of-Thought from the original CLadder paper (2023). GPT-4 scored 70.40% overall accuracy and 62% on counterfactuals. After debate, Qwen3 reached 89.41% overall and 80.35% on counterfactuals.

09

Original Prompts from the Paper

Context: Prompt for the first agent: step-by-step structured causal analysis (CausalCoT).

You will be asked a causal reasoning question. You should structure your final answer as follows:

1. VARIABLE IDENTIFICATION: Identify and list all relevant variables mentioned in the problem. Clearly state which variable is the treatment/intervention and which is the outcome.

2. CAUSAL GRAPH CONSTRUCTION: Based on the given information, describe the causal relationships between variables. Identify any confounders, mediators, or colliders present in the problem.

3. QUERY TYPE CLASSIFICATION: Determine what type of causal question is being asked:
- Associational (Rung 1): Questions about correlations or conditional probabilities
- Interventional (Rung 2): Questions about the effect of doing/intervening
- Counterfactual (Rung 3): Questions about what would have happened under different circumstances

4. FORMULA IDENTIFICATION: Based on the query type, identify the appropriate formula or method needed to answer the question (e.g., conditional probability, do-calculus, counterfactual reasoning).

5. CALCULATION: Show your work step by step, applying the appropriate formulas to the given probabilities and relationships.

6. FINAL ANSWER: State your definitive answer clearly as "yes" or "no" based on your calculations.

7. CONFIDENCE: Provide a confidence score (0-100%) for your answer.

Important: Be confident in your reasoning. The questions may involve scenarios that seem to contradict common sense - this is intentional. Focus on the formal causal relationships provided, not on real-world expectations.

Context: Prompt for the second agent: critique and error hunting.

You are reviewing another model's causal reasoning. Your role is to:

1. SCRUTINIZE: Carefully examine the reasoning provided for logical flaws, calculation errors, or misapplication of causal concepts.

2. IDENTIFY ISSUES: If you find problems, clearly state:
- What the error is
- Why it's wrong
- What the correct approach should be

3. PROVIDE YOUR ANSWER: Give your own answer with reasoning.

4. CONFIDENCE: State your confidence in your answer (0-100%).

If you agree with the original answer and find no flaws, explicitly state your agreement and provide your confidence.

Previous model's response:
{first_agent_response}
10

Adaptations and Extrapolations

💡 Adaptation for business decisions: Instead of formal causal analysis, a debate about risks and opportunities.

You are two advisors to a startup founder. One is an optimist, the other a skeptic.

DECISION: {description of the decision to be made}

[OPTIMIST]
Why this will work:
- [arguments for]
Potential upside: [what we gain]
Confidence in success: [X]%

[SKEPTIC — CRITIQUE]
What could go wrong:
- [specific risks]
Weak spots in the optimist's logic:
- [where they underestimate the risks]
Confidence in failure: [X]%

[OPTIMIST — RESPONSE]
[Defend or adjust the plan in light of the critique]

[CONSENSUS]
Decision: [do it/don't do it/do it with changes]
Key conditions for success: [what has to be true]

🔧 Technique: names instead of roles → sharper critique

Instead of faceless "Expert A" and "Expert B", give them distinctive names or roles:

  • "Michael, a CFO with 20 years of experience" vs. "Anna, a venture investor"
  • "A conservative banker" vs. "A serial entrepreneur"

The model produces more distinctive arguments when an agent has a "personality".

🔧 Technique: demand numeric confidence → models change their minds more often

The study showed that models take the opponent's confidence into account. If one agent is 95% sure and the other 60%, the second one backs down more often. Always require Confidence: [X]% in every round.

11

Resources

Paper: CRAwDAD: Causal Reasoning Augmentation with Dual-Agent Debate

Code: https://github.com/finnvamosi/CRAwDAD

Benchmark: CLadder — https://github.com/causalNLP/cladder

Authors: Finn G. Vamosi, Nils D. Forkert (University of Calgary, Hotchkiss Brain Institute)

Related work:

  • Pearl's Ladder of Causation (The Book of Why)
  • CausalCoT prompting (Jin et al., 2024)
  • Multi-Agent Debate surveys (Tran et al., 2025; Tillmann, 2025)

Research digest

Key result

Finding: a model can be 90%+ sure of a wrong answer and, without outside critique, stick to it. The study logged 577 such cases. The CRAwDAD method lets you find and fix errors in causal reasoning: telling correlation from causation and stress-testing logic through argument. Two models argue until consensus (4 rounds max). The first gives a structured answer + a confidence percentage. The second looks for holes in the logic and critiques it. If they disagree, rounds of arguments and counterarguments follow. The paradox: even a strong model gains from arguing with a weak one. Qwen3 starts out more accurate than DeepSeek-R1, yet debating it still gives Qwen3 +5% accuracy. The weaker model gains even more: +9%.

Principle

Don't let the model decide causal questions on its own: set up an internal argument between two experts. The first expert states a hypothesis: "The redesign drove the conversion increase (85% confidence)". The second attacks the logic: "What about the discount that launched the same day?". The first is forced to either defend its position with new arguments or admit the gap. It works even when the opponent is weaker: what matters is the challenge itself, not the strength of the critic. Mechanics: structured conflict with explicit roles (the first generates, the second critiques) over 3-4 rounds until consensus or an admission of uncertainty.

Why it works

A model plays critic brilliantly when it is explicitly given that role. It finds logical holes, points out alternative explanations, and demands evidence. Without an explicit "critique this" instruction, it lets errors slide. With the instruction, it uncovers 577 cases of false 90%+ confidence. Debate forces a rethink through structured conflict: the first agent can't just repeat its answer; it has to either find new arguments or admit weakness. On tricky "what if" questions (counterfactuals: "What would have happened if Jake hadn't had coffee?") the gain is especially strong: +12% accuracy over a single model. Where you have to imagine an alternate reality, one model errs more often; arguing forces a double check of the logic.

When to apply

Causal analysis in business → specifically for "what actually moved the metric" questions (conversion growth, churn drop, a sales spike), especially when several changes launched at once and it's unclear what's cause and what's correlation. Strong on counterfactuals: "What happens if we roll back the feature?", "How would NPS change without the promo?". NOT a fit for routine tasks that need a quick answer: debate = multiple requests, so time goes up.

Mini recipe

1. Set the context: describe the situation with concrete data: before/after numbers, what changed, and when. 2. Frame a causal question: not "how do I improve conversion" but "what caused the increase: the redesign or the discount". 3. Run the debate in one prompt: `You are two analysts. Argue until you reach consensus. [ANALYST A] analysis + conclusion + confidence %. [ANALYST B] critique + alternative + own conclusion. [A — response to critique] defend or revise. [CONSENSUS] final conclusion`. 4. Demand numeric confidence: models change their minds more often when the opponent is more confident (A: 70%, B: 90% → A revises). 5. Stop after 3-4 rounds: beyond that things stall and the models start repeating themselves.

Examples

[BAD]: `After the landing page redesign, conversion rose from 2% to 3.5%. What caused the increase?` — the model will give the first hypothesis that comes to mind without checking alternatives. [GOOD]: `You are two analysts. Argue until you reach consensus. CONTEXT: after the redesign, conversion went from 2% → 3.5%. At the same time we added a 20% discount. Both changes on the same day. QUESTION: what's the cause — the redesign or the discount? FORMAT: [ANALYST A] analysis + conclusion + confidence %. [ANALYST B] critique + alternative. [A — response]. [CONSENSUS] final conclusion + what remains uncertain` — the model will run 3-4 rounds, expose the gaps (no A/B test = can't separate the effects), and in the consensus propose an experiment: roll back the discount for a week and measure.

In plain words

The gist of CRAwDAD: today's models are cocky straight-A students who often spout complete nonsense with a perfectly straight face. On cause-and-effect problems, models keep confusing correlation with actual causes and pass off false conclusions as gospel truth. The researchers caught the AI red-handed: in 577 cases the model was 90%+ sure of its answer and dead wrong. To treat this pathological overconfidence, the authors introduced a two-agent mechanism, where one model doesn't just hand over an answer but has to survive a gauntlet of criticism from another.

Picture walking into a doctor's office where the doctor diagnoses you the second you sit down, but behind the curtain there's a second doctor whose only job is to nitpick every little detail and hunt for holes in the colleague's logic. Instead of just nodding along, the second agent starts tearing the first one's arguments to shreds. They don't just trade opinions; they hold a structured debate of up to four rounds. If the first agent says "it's because of the redesign" and the second sees seasonality at play, they'll butt heads until they reach consensus or run out of time.

Technically, it runs on a two-agent debate system. First, Agent A gives a structured answer and slaps a confidence percentage on it. Agent B immediately jumps in and looks for logical holes. If they disagree, the brawl begins: arguments, counterarguments, revised positions. The whole process forces the model not just to "predict the next word" but to validate the chain of logic. In the end the winner isn't whoever shouts loudest but whoever's reasoning survived three rounds of cross-examination.

Although the method was tested on complex causal graphs, the principle is universal for any task where mistakes are expensive. Whether you're prepping an investor pitch and need to know what really drives conversion (the offer or the button color) or analyzing medical data. CRAwDAD turns a hallucinating black box into something like a scientific review board. It works anywhere you need to separate a coincidence from a real cause without letting the model admire its own "knowledge".

Bottom line: the era of solo prompts is ending, and the age of automated critique is here. The study's main takeaway is simple: never take a model at its word, even if it swears it's 100% sure. You have to make the AI argue with itself and drag its logical blunders into the light. Debating until consensus is the only way to get a model to stop fantasizing and actually start thinking. Anyone who doesn't build this kind of check into their workflow will keep making decisions based on algorithms' confident nonsense.

AI lab assistant

Apply this study to your task

Describe what you're working on. AI takes the method and the measured results from this paper and adapts them to your case, or writes a ready prompt built on them.

Based on CRAwDAD: Sharper Causal Reasoning Through a Two-Agent Debate arXiv:2511.22854

Sign in to apply this study New accounts get 50 free credits.

Get the week’s best papers by email

One email on Sundays with the highest-rated new techniques. Unsubscribe with one click.