When Verification Is Late: Delay Floors and Placement Flips in Corrected Multi-Agent Systems
This paper establishes that in delayed multi-agent correction systems, verification latency imposes an inescapable accuracy floor determined by the Dottie number, creates a budget ceiling for performance gains, and reverses the optimal strategy from concentrating to spreading correction resources beyond a specific threshold.
Original paper licensed under CC BY 4.0 (https://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 a group of friends trying to solve a mystery together. They pass notes back and forth, sharing clues and theories. Usually, the more people you have and the more carefully they check each other's work, the closer the group gets to the truth. This is the basic idea behind "multi-agent systems," where many computer programs (agents) work together to solve problems. But there's a catch: checking the work takes time. If a friend takes a long time to verify a clue before passing it on, the whole group might start arguing in circles or getting confused. Scientists have long known that adding "verification" (checking the work) helps, but they haven't fully understood what happens when that checking is slow. They wondered: Is there a limit to how good the group can get, no matter how many checkers you add? And does it matter if you have one super-fast checker or many slower ones?
This paper, titled "When Verification Is Late," dives into that exact question. It treats a group of AI agents like a swarm of bees or a school of fish, where some agents are "correctors" designed to pull the group back to the truth if they start drifting. The authors use math to model what happens when these correctors are delayed—when they take a moment to think before acting. They discover some surprising rules about how to build these teams.
The "Too Late" Problem
Think of the AI swarm as a boat trying to stay in a straight line on a choppy lake. The "correctors" are like a rudder that steers the boat back to the center. If the rudder moves instantly, the boat stays straight no matter how rough the water gets. But in the real world, the rudder takes a split second to react. If the water is calm, a slow rudder is fine. But if the waves are big, that split-second delay can make the rudder steer the boat away from the center just as it's trying to fix it, causing the boat to wobble wildly.
The paper finds that this "wobble" creates a floor on how accurate the group can ever be. No matter how much money (budget) you spend on hiring more checkers or making them smarter, you cannot push the accuracy past this floor if the delay is there. It's like trying to fill a bucket that has a hole in the bottom; you can pour in as much water as you want, but the water level will never rise above a certain point.
The Magic Number: The Dottie Number
Here is the most playful part of the discovery. The authors calculated exactly what this "wobble limit" looks like. They found that the best possible performance happens when the strength of the correction and the delay multiply together to equal a very specific, weird number: 0.739085...
This number is famous in math as the Dottie number. It's the only number that, if you take the cosine of it, gives you back the same number (cos 0.739085... = 0.739085...). The paper proves that for these AI swarms, the "sweet spot" for efficiency is tied to this exact mathematical constant. If you try to make the correctors stronger than this sweet spot, the delay makes them so unstable that the whole system gets worse, not better.
The Great Flip: One Big Brain vs. Many Small Brains
The paper also changes the rules on how to spend your budget. Before this, the common sense was: "If you have a limited budget, put it all on one super-strong checker." This works perfectly if the checker is instant.
But once you add delay, the rules flip. The paper shows that there is a specific, calculated budget threshold (called ). If you spend less than this amount, concentrating your money on a few strong agents is best. However, if you spend more than this specific threshold, it becomes better to spread your budget out over many weaker checkers rather than one strong one.
Imagine you are trying to keep a line of people walking straight.
- No Delay: You hire one giant, super-strong person to push everyone back into line instantly. This works great.
- With Delay: That giant person takes a second to think before pushing. By the time they push, the people have already moved, so the push knocks them over. Instead, it's better to hire a hundred small people who give tiny nudges. Even if they are a little slow, the fact that there are so many of them keeps the line steady without causing a crash.
The authors calculated this specific tipping point. If you ignore it and keep dumping money into one strong agent past this limit, you actually make the group's answers worse.
Testing the Theory
To make sure this wasn't just a math game, the authors tested their model against real data from a swarm of large language models (specifically a corrected version of the Qwen3.6-35B-A3B model). They simulated a scenario where the AI agents had to check facts.
The results were a strong match for the model's overall shape, but the real-world data had limitations. The model fit the trajectories well, confirming that the delayed-relaxation concept is a valid description of the system. However, the data was too noisy and averaged over many different questions to definitively isolate the specific delay mechanism on its own. Because the effects of delay and correction strength were mixed together in the averaged data, the researchers could not confirm the specific "flip" or the Dottie number constant directly from the real-world numbers alone. While the theory predicts a hard ceiling on accuracy due to delay, the data could not separately prove this specific effect in isolation; it simply showed that the model's general behavior aligned with the observed system dynamics.
The Bottom Line
The main takeaway for anyone building these AI teams is simple: Speed matters more than power.
If your verification process is slow, throwing more money at it won't help. In fact, it might hurt. There is a hard limit to how accurate your AI swarm can be, determined entirely by how long it takes to check the work. Once you hit that limit, the only way to improve is to make the checking faster, not stronger. And if you do have to spend a lot of money, don't put it all on one superstar; spread it out among many smaller helpers to keep the system stable, but only after you've crossed the specific budget threshold where this strategy becomes better.
The paper doesn't just suggest this; it proves it with mathematical formulas. While the real-world data was too complex to isolate every single variable perfectly, the theory provides a clear rule: Don't let your checkers be too strong if they are too slow, or the whole team will spin out of control.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.