← Latest papers
🤖 AI

Locally Coherent, Globally Incoherent: Bounding Compositional Incoherence in Multi-Component LLM Agents

This paper formalizes and quantifies the "locally coherent, globally incoherent" failure mode in multi-component LLM agents using a runtime-computable compositional residual, demonstrating that local coherence often fails to ensure global probability consistency and that current LLM-side mitigations are ineffective while deterministic projection and sequential monitoring offer viable solutions.

Original authors: Anany Kotawala

Published 2026-05-29
📖 5 min read🧠 Deep dive

Original authors: Anany Kotawala

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

The Big Problem: The "Too Many Chefs" Dilemma

Imagine you are running a restaurant where you have hired four different expert chefs to plan a single, massive banquet.

  • Chef A is only told to plan the Appetizers.
  • Chef B is only told to plan the Main Course.
  • Chef C is only told to plan the Dessert.
  • Chef D is only told to plan the Drinks.

Each chef is a genius. They are perfectly confident in their own section. Chef A says, "I'm 80% sure we'll need 50 appetizers." Chef B says, "I'm 80% sure we'll need 50 main courses." And so on.

The Problem: The restaurant owner (the "Agent") just adds up all the numbers. But because the chefs didn't talk to each other, they might accidentally plan for 200 people when the restaurant only seats 100. Or, they might plan for 100% chance of appetizers and 100% chance of main courses, even though the menu only allows for one of those to happen per table.

In the world of AI, this is called "Locally Coherent, Globally Incoherent."

  • Locally Coherent: Each AI model (chef) is doing a good job on its own tiny task.
  • Globally Incoherent: When you put their answers together, the total math doesn't make sense. The probabilities add up to more than 100% (or less), creating a logical mess.

The Paper's Main Discovery

The authors found that even if every single AI model is perfectly calibrated and logical on its own, combining them often breaks the math.

They call this broken math a "Compositional Residual" (ϵ\epsilon^\star). Think of this as a "Garbage Meter."

  • If the meter reads 0, the combined answer is perfect.
  • If the meter reads high, the combined answer is logically broken (e.g., claiming there is a 150% chance of rain).

They tested this on nearly 2,000 different scenarios (like predicting election winners, sports outcomes, or tech IPOs) using four different AI models. They found that 33% to 94% of the time, the combined answer was broken, even though the individual AI parts were working fine.

Why Does This Happen?

The paper explains that the AI models are "blind" to the big picture.

  • The Blind Specialist: When you ask an AI, "What is the chance the US wins the World Cup?", it answers based on its training.
  • The Missing Context: It doesn't know that you also asked another AI, "What is the chance Brazil wins?" and "What is the chance Germany wins?"
  • The Result: The US AI says 60%, Brazil says 60%, and Germany says 60%. The total is 180%. This is impossible. The AI didn't know it was part of a team where the total must equal 100%.

The Solutions They Tried (and Failed)

The researchers tried to fix this using "soft" methods, which are like giving the chefs better instructions:

  1. Retrieval: Letting the chefs look up facts on Google. (Failed: They still couldn't agree on the total).
  2. Better Prompts: Telling the chefs, "Remember, you are part of a team, and your answers must add up to 1." (Failed: They still made mistakes).
  3. The "Boss" AI: Having a smart AI manager listen to all the chefs and rewrite the answers. (Failed: The manager often made things worse or didn't fix the math).

The Conclusion: You cannot fix this just by talking to the AI better. The AI models are too isolated by design.

The Real Fix: The "Mathematical Corrector"

Since you can't fix the chefs, you need a Mathematical Corrector that steps in after the chefs are done.

The authors propose a method called Hierarchical Boyle–Dykstra Projection.

  • The Analogy: Imagine the chefs hand you a list of ingredients that weighs 200kg, but your truck can only carry 100kg. Instead of asking the chefs to rewrite their lists (which they do poorly), you simply use a machine to trim the excess weight off the top of the pile until it fits exactly in the truck, while keeping the relative proportions of the ingredients as close to the original as possible.
  • How it works: The system takes the broken, over-100% answer and uses a strict mathematical formula to "project" it onto a valid, logical shape (a "polytope"). It forces the numbers to obey the laws of probability without needing the AI to "think" about it.

This method is deterministic (it always works the same way) and fast. It turns a broken, 150% probability answer into a perfect 100% answer instantly.

Why Should You Care? (The "Regret" Factor)

The paper shows that this isn't just a theoretical math problem; it costs real money in decision-making.

  • If you are a bettor or a decision-maker using these AI agents, a broken answer leads to regret. You might bet on a horse that the AI says has a 60% chance, but because the AI's math was broken, that 60% was actually a lie.
  • By using their "Mathematical Corrector," they showed that you can save money (measured in "nats," a unit of information gain) because you stop making bets based on impossible math.

Summary in One Sentence

When you ask multiple AI models to solve parts of a big puzzle, they often give answers that don't add up; the best way to fix this isn't to ask them to try harder, but to use a mathematical "trimming tool" to force their answers to make sense before you use 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.

Try Digest →