Apply to my task
arXiv:2610.18298 ★ 88 Oct 13, 2026

The “Candidates × Evidence” Falsification Protocol: Make the Model Rule Out Hypotheses Before It Picks One

Key result

Two years of new model generations barely moved the results: from −0.03 to +0.08 on a 0–1 scale. Model strength sets the ceiling; answer discipline sets the floor. The falsification protocol lets you pick one cause from a closed list of hypotheses and check the choice by eye, even if the model usually cuts its reasoning short, breaks the format, or swings between runs. The model builds a “hypothesis × evidence” table and can’t answer until it has ruled out at least half of the hypotheses. Every refutation is tied to an evidence number. Result: DeepSeek-V4-Flash gained +0.27, entirely because its reasoning finally finishes.

01

TL;DR

This is a falsification protocol. The model builds a table: hypotheses (candidates) in the rows, evidence in the columns. In every cell it writes “supports,” “contradicts,” or “irrelevant” and names the piece of evidence. A hypothesis with more contradictions than supports gets thrown out. The model may only draw a conclusion once at least half of the hypotheses are eliminated. The answer comes out as a single line in a fixed format.

The headline finding: on “pick one of a fixed set of options” tasks, model strength sets the ceiling, but output discipline sets the floor. Two years of new model generations barely moved the needle (from −0.03 to +0.08 on a 0–1 scale). Meanwhile, “discipline” failures persist even in top models: reasoning that never finishes, broken answer formats, results that swing wildly between runs on the same question. One model swung by as much as 0.39 of the whole scale, landing near zero one run and near the max the next. The root cause: out of habit, the model jumps to an answer based on surface similarity instead of checking hypotheses one by one.

The protocol puts the model on rails: hypotheses are listed, each one is checked, the answer fits on one line. It rescues “undisciplined” models: DeepSeek-V4-Flash gained +0.27, entirely because its reasoning finally finished. Kimi K3’s run-to-run spread dropped from 0.218 to 0.007. But the protocol hurts models that are already disciplined: Qwen3 lost 0.09–0.12. So switch it on selectively.

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.

02

Method Blueprint

STEP 1: Hypotheses (candidates) → closed list, nothing outside it allowed
STEP 2: “Candidate × evidence” matrix → each cell: supports / contradicts / irrelevant
        + for “contradicts,” the evidence must be named (“contradicts E3”)
STEP 3: Row verdict → a hypothesis is compatible if supports outnumber contradictions
        and the key evidence is confirmed; otherwise it is incompatible
STEP 4: Sufficiency check → are ≥ ½ of hypotheses eliminated? No → re-examine the evidence
STEP 5: Pick → the compatible hypothesis with the most supports
        → one line: [Verdict]: X
BANNED: picking by position in the list; copying a ready-made answer from an example

You can do all of this in a single prompt, in one pass.

In the full version of the paper, the protocol sits inside five stages: hypotheses → verification → causal chain → action → backward check. The template below covers all five.

03

Example

Task: An Amazon seller notices that orders for their “Oversized Hoodie” listing dropped 35% in a week. They don’t want to guess. They want a verifiable breakdown of the causes they can show their business partner.

Prompt:

<Role>
You are a marketplace analyst. You don’t guess; you test hypotheses against evidence.
</Role>

<Task>
Orders for the “Oversized Hoodie” listing (Amazon) dropped 35% over 7 days. Find the cause.
</Task>

<Candidates>
H1: A competitor cut their price
H2: The listing slipped in search because its rating dropped
H3: Key sizes (M, L) sold out
H4: Fees or shipping costs went up, so we raised our price
H5: Seasonal dip in demand
Do not add any other hypotheses.
</Candidates>

<Evidence>
E1: Listing rating went 4.8 → 4.7 this week
E2: Inventory: M — 0, L — 0, S and XL — 40 units each
E3: Our price went up from $24.99 to $27.99 (4 days ago)
E4: Top 3 competitors: prices unchanged
E5: Searches for “oversized hoodie” in the category: −5% vs. last week
E6: Rank for the main keyword: 12 → 31
KEY: E2
</Evidence>

<ReasoningLogic>
1. Build a matrix: rows H1–H5, columns E1–E6. Each cell gets exactly one of: support / oppose / irrelevant.
2. For every oppose, you must name the evidence: “oppose — contradicts E4.”
3. A hypothesis is compatible if support outnumbers oppose and the key evidence does not contradict it.
4. If fewer than half of the hypotheses are incompatible, write “Insufficient: re-examine evidence” and recheck the most contested cells.
5. Pick the compatible hypothesis with the most support. Ignore list order and examples.
</ReasoningLogic>

<OutputFormat>
First the matrix, then the row verdicts, then one line:
[Main cause]: Hx
</OutputFormat>

Result: The model returns a 5×6 table with a mark in every cell and an evidence reference for every “contradicts.” Next comes a verdict for each hypothesis (compatible or not), the “at least half eliminated” check, and the final line in the required format. You can eyeball every conclusion cell by cell.

04

Why It Works

The weakness. Models tend to answer by association: they see “orders dropped” and immediately blurt out “competitors.” Hypotheses never get enumerated, and the answer can’t be checked. Asking the model to “critique itself” without outside structure barely helps: self-checking with nothing to anchor it doesn’t improve reasoning and sometimes makes it worse. Even an explicit “fix the mistake” instruction works less than half the time.

The strength. Models are good at filling cells for small, local questions: “Does evidence E3 support hypothesis H1 or contradict it?” They handle a bite-sized task like that far more reliably than “find the cause.”

How the protocol connects the two. It breaks a big task into cells, forces the model to name the contradicting evidence (“contradicts E3”), and blocks any conclusion until half the hypotheses are gone. The one-line format makes the answer checkable. The paper shows that the effect comes from structure, not knowledge: when all injected domain knowledge was stripped out of the protocol, the result didn’t change.

Control knobs: - The “at least half” threshold → tighten it (two-thirds) for high-stakes decisions, loosen it for quick ones. - Key evidence (KEY) → set your own. It’s the “without this, the hypothesis is dead” fact. - Closed hypothesis list → let the model add one hypothesis if you need a wider search. This weakens the protocol. - One-line format → per the ablations, this layer is “the most expensive” on strong models. Drop it if you read answers yourself and don’t need machine checking. - Bans (“don’t pick by order,” “don’t copy the example”) → always keep them; they guard against laziness.

05

Prompt Template

<Role>
You are an analyst. You don’t guess; you test hypotheses against evidence.
</Role>

<Task>
{task: what needs to be determined or chosen}
</Task>

<Candidates>
{H1: hypothesis}
{H2: hypothesis}
{H3: hypothesis}
Do not add any other hypotheses.
</Candidates>

<Evidence>
{E1: evidence}
{E2: evidence}
{E3: evidence}
KEY: {number of the key evidence}
</Evidence>

<ReasoningLogic>
1. Build a matrix: rows are hypotheses, columns are evidence. Each cell gets exactly one of: support / oppose / irrelevant.
2. Justify every oppose by citing a specific piece of evidence: “oppose — contradicts E_.”
3. A hypothesis is compatible if support outnumbers oppose and the key evidence doesn’t refute it. Otherwise it is incompatible.
4. Sufficiency check: at least half of the hypotheses must be incompatible. If fewer, write “Insufficient” and recheck the contested cells.
5. Pick the compatible hypothesis with the most support. List order and examples must not influence the choice.
6. If a recommendation is needed, state the action that follows directly from the chosen hypothesis. Then check it against bans and risks: {constraints}.
</ReasoningLogic>

<OutputFormat>
Matrix → row verdicts → sufficiency check → one line:
[{verdict label}]: {hypothesis}
</OutputFormat>

What to fill in: - {task}: a single question (diagnosis, picking a cause, picking an option). - Hypotheses: 3–7 of them; if you don’t know them, have the model generate a list first and sign off on it. - Evidence: facts, numbers, observations, ideally numbered. - {constraints}: what must not be recommended (budget, legal limits, risks).

🚀 Quick start — paste into the chat:

Here is a template for the “candidates × evidence” falsification protocol. Adapt it to my task: [your task].
Ask me questions to fill in the fields.

[paste the template above]

The LLM will ask which hypotheses are on the table, what facts you have, and which piece of evidence is key. Without a closed list of hypotheses and numbered evidence there’s no matrix, and the matrix is what the whole method rests on. The model will take the pattern from the template and build a ready-to-use prompt for your task.

06

Limitations

⚠️ The protocol hurts disciplined models: on models that already reason carefully and finish their answers, quality drops on average (roughly 0.09–0.12 on a 0–1 scale). Test your model without the protocol first. Turn it on if answers keep getting cut off, breaking format, or swinging between runs.

⚠️ Only for tasks with enumerable hypotheses: the method needs a closed list of candidates and a set of evidence. It’s a poor fit for open-ended, creative, or “come up with something” tasks.

⚠️ The protocol doesn’t raise the ceiling: it removes discipline failures. If the model doesn’t know the domain or fills cells wrong, the matrix will record the mistake neatly but won’t fix it.

⚠️ The same model grades the cells: errors in individual cells can happen. The protocol makes them visible but doesn’t remove them. In the paper, the format is checked by code; in a chat, you check the cells by eye.

⚠️ One domain: the main test was diagnosis in traditional Chinese medicine, plus a separate check on math. Transferring it to business tasks makes sense, but the paper didn’t measure that directly.

⚠️ More tokens, longer answers: the matrix takes up space, which is overkill for simple questions.

07

How They Studied It

The researchers used the public TCMEval-SDT benchmark: 200 clinical cases where the task is to identify a syndrome from a set of signs. Each of five base models was run with and without the protocol, up to three repeats, with paired statistical tests. First they showed that two years of model progress delivered almost nothing in “bare” mode. What did show up were discipline failures: reasoning that never finished, broken formats, huge spread between repeats.

Then they tested the hypothesis “the protocol helps where discipline is missing and hurts where it’s already there.” It held up. DeepSeek-V4-Flash gained +0.27, and the breakdown showed it came entirely from rescuing unfinished reasoning. Kimi K3’s spread dropped from 0.218 to 0.007. On Qwen3-4B and Qwen3-32B (with the same token budget and controlled temperature), the protocol cost 0.09–0.12.

Ablations (removing parts of the protocol one at a time) turned up two interesting results. First, on strong models most of the cost comes from the strict-format layer, while the causal-chain-plus-format combo pulls in different directions under different conditions. Second, removing all injected knowledge didn’t change the score: the effect comes from structure, not knowledge. Finally, the protocol was adapted to math problems with planted false premises. It caught them 89.8% of the time with 6.8% false alarms and brought accuracy back to the no-misinformation level. Caveat: that was on a single model with little headroom for improvement.

The practical takeaway: don’t bolt structure onto everything. First see where your model’s discipline breaks down, and add guardrails exactly there.

08

Adaptations and Extrapolations

🔧 Technique: apply it to premise checking → protection against false inputs

The paper shows a two-stage version of the protocol for tasks with planted misinformation: the “candidates” are the task’s premises, and the “evidence” is a set of checks (numbers, relationships, internal consistency). False premises get rewritten as reminders, and only then does solving begin.

Before solving the problem:
1. List every premise in the problem statement (P1, P2, ...).
2. Check each one on three points: are the numbers right? are the relationships right? does it contradict other premises? Cells: ok / fail / n/a; for fail, say what doesn’t add up.
3. Rewrite every premise marked fail as a reminder: “Reminder: actually ...”.
4. Solve the problem using only the verified and corrected premises.

🔧 Technique: add a “key evidence” block → faster elimination

If you set KEY: E_ in <Evidence>, any hypothesis the key evidence contradicts is automatically incompatible. Handy when there’s a fact that makes a hypothesis impossible (say, zero inventory in the warehouse for the “demand dropped” hypothesis).

These are my adaptations; they don’t appear in the paper in this form. The first builds on the two-stage scheme described in the paper, the second on the “key evidence” rule.

09

Resources

  • Paper: Output Discipline Sets the Floor: A Falsification-Guided, Model-Agnostic Agent Protocol for Auditable Hypothesis-Driven Decision Making
  • Authors: Jing Liu, Yongxing Qi, Ping Yao, Ting Wu (Hangzhou Innovation Institute, Beihang University; 32007 Unit, Beijing)
  • Benchmark: TCMEval-SDT (syndrome identification in traditional Chinese medicine, 200 cases)
  • Related work: research on how false premises propagate through a chain of thought (10–72% accuracy loss); self-correction without external feedback; MedAgents, MDAgents (multi-agent approaches for comparison)
  • This breakdown is based on the available part of the paper (abstract, introduction, framework and protocol description); detailed result tables and appendices were not included in the material.

Research digest

Key result

Two years of new model generations barely moved the results: from −0.03 to +0.08 on a 0–1 scale. Model strength sets the ceiling; answer discipline sets the floor. The falsification protocol lets you pick one cause from a closed list of hypotheses and check the choice by eye, even if the model usually cuts its reasoning short, breaks the format, or swings between runs. The model builds a “hypothesis × evidence” table and can’t answer until it has ruled out at least half of the hypotheses. Every refutation is tied to an evidence number. Result: DeepSeek-V4-Flash gained +0.27, entirely because its reasoning finally finishes.

Principle

It works like a detective with a whiteboard. Hypotheses go in the rows, evidence in the columns, and each cell gets one verdict: supports, contradicts, or irrelevant. If you write “contradicts,” name the evidence, e.g. “contradicts E3.” A hypothesis with more contradictions than supports is out. Until half the hypotheses are out, no picking allowed. Then you take the surviving hypothesis with the most supports. The answer goes on one line: `[Verdict]: X`. The bans always stay: don’t pick by list position and don’t copy the answer from an example. All of it happens in one prompt, in one pass.

Why it works

Out of habit, the model answers by association. It sees “orders dropped” and immediately says “competitors.” It doesn’t walk through the hypotheses, so there’s nothing to check the answer against. Asking it to “critique yourself” with no anchor barely helps. Self-checking without structure doesn’t improve reasoning and sometimes makes it worse. Even a direct “fix the mistake” works less than half the time. On small questions, though, the model is strong. “Does evidence E3 support hypothesis H1 or contradict it?” — it handles that far more reliably than “find the cause.” The protocol slices the big task into cells like that. The effect comes from structure, not knowledge: when all injected domain knowledge was stripped from the protocol, the result didn’t change. Wild stat: Kimi K3’s run-to-run spread fell from 0.218 to 0.007. And one model without the protocol wandered across 0.39 of the scale, from nearly zero to nearly the max. There’s a flip side. Models that already reason carefully get worse with the protocol: Qwen3 dropped 0.09–0.12.

When to apply

Diagnosis and choosing among enumerable hypotheses → the cause of a sales drop, an outage, customer churn, picking one option out of 3–7 → especially when you have a set of facts and need to show the answer to a partner or your boss. Turn the protocol on if the model keeps cutting answers off, breaking format, or answering the same question differently. Run the task without the protocol first and see what kind of failures you get. NOT a fit for creative, open-ended “come up with something” tasks. It’s also pointless where the model doesn’t know the domain: the matrix will neatly record its mistake but won’t fix it. For simple questions it’s a waste of tokens.

Mini recipe

1. Ask one question: what exactly needs to be determined. Not “figure everything out” but “what’s causing X.” 2. Close the hypothesis list: 3 to 7 of them, marked “Do not add any other hypotheses.” Don’t know the hypotheses? Have the model brainstorm a list first, edit it yourself, and only then run the protocol. 3. Number the evidence: E1, E2, E3 — facts, numbers, observations. Without numbers, “contradicts E3” references won’t work. 4. Name the key evidence: KEY: E2. It’s the thing a hypothesis can’t survive without. 5. Describe the matrix: cells are support / oppose / irrelevant, and every oppose cites a piece of evidence. 6. Set the threshold: at least half the hypotheses eliminated, otherwise “Insufficient” and a recheck of the contested cells. For high-stakes decisions, tighten it to two-thirds. 7. Lock the output: one line `[Main cause]: Hx`. Add the bans: don’t pick by order, don’t copy the example. 8. Check the cells by eye: the model grades itself, so individual cells can be wrong. But now you can see them. Too lazy to write it from scratch? Paste the template into the chat and write: `Adapt this protocol to my task: [task]. Ask me questions to fill in the fields.`

Examples

[BAD]: `Orders for the “Oversized Hoodie” listing dropped 35% this week. Why?` (You’ll get a confident “competitors cut their prices.” No hypotheses tested, nothing to verify.) [GOOD]: `You are a marketplace analyst. You don’t guess; you test hypotheses against evidence. Task: orders for the listing dropped 35% over 7 days, find the cause. Hypotheses: H1 a competitor cut their price; H2 search ranking slipped because of the rating; H3 sizes M and L sold out; H4 fees went up and we raised our price; H5 seasonal dip. Do not add any other hypotheses. Evidence: E1 rating 4.8 → 4.7; E2 inventory for M and L is zero, S and XL have 40 units each; E3 our price went up from $24.99 to $27.99 4 days ago; E4 top-3 competitor prices unchanged; E5 category demand −5%; E6 rank for the main keyword 12 → 31. KEY: E2. Build a matrix: rows H1–H5, columns E1–E6, cells support / oppose / irrelevant. Justify every oppose by citing evidence. A hypothesis is compatible if support outnumbers oppose and the key evidence doesn’t contradict it. At least half must be incompatible; otherwise write “Insufficient” and recheck. Pick the compatible hypothesis with the most support. Ignore list order. End with one line: [Main cause]: Hx` (You’ll get a 5×6 table where H1 is knocked out by E4, H5 by E5, and every “contradicts” is tied to a specific piece of evidence. The seller can show it to their partner instead of arguing it out.)

In plain words

Neural nets are phenomenally lazy and run on the first association that pops up: they see the phrase “orders dropped” and instantly hand down a verdict about “competitors undercutting prices.” The usual “double-check yourself” requests are hot air that doesn’t work even half the time. A model simply can’t reflect without hard external guardrails. To make it actually think, the authors built a falsification protocol: an algorithm that beats the habit of grabbing the first shallow explanation right out of the LLM.

Picture a detective who storms in yelling “The butler did it!” — just because that’s the easiest call. But instead of letting him ramble, you hand him a strict interrogation protocol and forbid him from naming the culprit until he’s rock-solid on alibis and has crossed off at least half the suspects. No gut feelings — just cold facts, nailed to specific pieces of evidence.

The method boils down to mechanics: the model builds a hypothesis-by-evidence matrix where every version gets methodically tested against the facts. In each cell the LLM must put a label: “supports,” “contradicts,” or “irrelevant,” always citing a specific piece of evidence. A hypothesis that comes out net negative goes in the trash. The main safety catch is a 50% elimination threshold: the model isn’t allowed to conclude anything until it has demolished at least half the hypotheses, and the final answer must come out strictly as one line in a fixed format.

In the study this was run on the case of a seller whose listing orders sank 35% in a week, but the principle is completely universal. The same framework fits perfectly for hunting down server failures, auditing a traffic drop, or medical diagnosis. Anywhere that reading tea leaves could torch your budget, output-structure discipline is that reinforced-concrete floor the model won’t fall below.

Stop asking the model to “think really hard” — without hard guardrails, that’s a guaranteed generator of confident nonsense. Box the model into conditions where it has to cut the junk by strict rules. No format discipline, you get hallucinations; roll out the protocol, and you get an ironclad audit you won’t be embarrassed to show your business partner.

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 The “Candidates × Evidence” Falsification Protocol: Make the Model Rule Out Hypotheses Before It Picks One arXiv:2610.18298

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