Agreement Before Diversity: Verification-First Complementarity for Heterogeneous Language-Model Coordination
The paper proposes Agreement-Before-Diversity (ABD), a verification-first coordination method for heterogeneous language models that uses a frozen, label-free decision rule to retain anchor answers only when corroborated by trusted samples, thereby achieving state-of-the-art performance on LiveCodeBench and GPQA-Diamond while providing exact theoretical identities to audit the trade-offs between accuracy gains and inference costs.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are trying to solve a tricky puzzle, and instead of asking just one person for the answer, you ask a whole team of experts. Some are math wizards, some are creative writers, and some are logic masters. This is the world of Large Language Models (LMs) working together. In science, this is called an "ensemble." The big idea is simple: if you have more people trying, you have a better chance of getting the right answer. It's like having ten people guess the number of jellybeans in a jar; the average of their guesses is usually closer to the truth than just one person's guess.
However, there's a catch. Just because you have ten guesses doesn't mean you know which one to pick. Sometimes, the most confident-sounding expert is actually wrong, and the quiet one is right. Worse, if you ask a "super-expert" to combine all the answers, they might accidentally talk over the correct answer with a fancy but wrong one. The big question scientists have been asking is: How do we know when to trust the new, fancy answer and when to stick with the one we already have? We need a rule that says, "Stop! This new answer is good enough to replace the old one," without just guessing.
This is where a new method called Agreement-Before-Diversity (ABD) comes in. Think of it as a strict but fair referee for a team of AI experts. Instead of blindly letting a fancy new answer overwrite an old one, ABD sets up a simple "safety check." Here's how it works:
- The Anchor: First, the team picks one "anchor" answer (the current best guess).
- The Safety Check: Before they even look at the fancy new answers, two other trusted experts from the same team check the anchor. If these two agree with the anchor perfectly, the referee says, "Great! We have a consensus. Keep the anchor. Don't waste time or money on anything else."
- The Switch: But if those two experts disagree with the anchor, the referee says, "Okay, the anchor is shaky. Now, go ahead and bring in the whole team of diverse experts to synthesize a brand new, fancy answer."
The paper proves that this simple rule is incredibly powerful because it separates diversity (having many options) from authority (the right to change the answer). The authors found that this method doesn't just guess; it uses math to show exactly why it works. They discovered two "magic formulas" (exact identities) that explain the results:
- The method beats a system that always makes a new fancy answer only when the anchor is actually better than the fancy answer on the specific cases where they agreed.
- The method beats a system that never changes the answer only when the new fancy answer fixes a mistake the anchor made, without accidentally breaking a correct answer.
In real-world tests, this referee system was amazing. On a coding challenge called LiveCodeBench, the ABD method got 59.43% correct, beating the standard methods which only got around 52%. On a tough science quiz called GPQA-Diamond, it hit 75.00%, again beating the others.
What's really cool is that the paper shows why it worked in each case. On the coding test, the "safety check" rarely passed (only 1.71% of the time) because computer code is so specific that two random tries rarely match perfectly. So, the system mostly just let the fancy team take over, which turned out to be the right move. But on the science quiz, the safety check passed often (73.33% of the time), and because the "anchor" was usually right, the system saved a ton of effort by sticking with the simple answer instead of overthinking it.
The paper also explicitly rules out some common ideas. It shows that just having a "diverse" team of different AI models isn't enough on its own; without a strict rule on when to switch, you might just get more wrong answers. It also proves that you don't need to know the "correct" answer beforehand to make this decision; the rule works just by looking at whether the experts agree with each other.
In short, Agreement-Before-Diversity teaches us that having more options is great, but you need a smart gatekeeper to decide when to use them. It turns the chaotic process of asking many AIs for help into a precise, auditable, and highly effective strategy. It's not about having the smartest AI; it's about having the smartest rule for using them.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.