← Latest papers
🤖 machine learning

In Defense of Information Leakage in Concept-based Models

This paper challenges the conventional view that information leakage in concept-based models is inherently undesirable, arguing that in real-world scenarios with incomplete concepts, a form of "benign leakage" is actually necessary for achieving both accuracy and intervenability, and proposes a new training objective to optimize for this beneficial leakage.

Original authors: Mateo Espinosa Zarlenga

Published 2026-06-10
📖 5 min read🧠 Deep dive

Original authors: Mateo Espinosa Zarlenga

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 Idea: Why "Leaking" Might Be a Good Thing

Imagine you are trying to teach a robot to identify different types of birds. You give the robot a list of "concepts" to look for, like "has a red beak," "has blue feathers," or "is small." This is the standard way of building Concept-Based Models (CMs).

The traditional rule in this field has been: "The robot must only look at the list you gave it. If it looks at anything else (like the shape of the tree in the background), it is 'cheating' or 'leaking' information, and that's bad."

This paper argues that this rule is flawed. In the real world, your list of concepts is almost never perfect or complete. If you force the robot to ignore everything except your imperfect list, the robot will become stupid and make mistakes.

The authors say: Sometimes, we need the robot to "leak" a little bit of extra information to be smart and accurate. They call this "Benign Leakage."


The Analogy: The Detective and the Missing Clues

To understand why, let's use a detective analogy.

The Scenario:
You hire a detective (the AI) to solve a crime. You give them a specific list of clues to look for (the "Concepts"): a muddy shoe print, a broken window, and a missing watch.

The "Strict" Approach (No Leakage):
You tell the detective: "You are only allowed to use these three clues. If you see a fingerprint on the glass or a smell of smoke, you must ignore it completely because it's not on your list."

The Problem:
What if the list you gave the detective was incomplete? What if the real key to solving the crime was the "smell of smoke," but you forgot to put it on the list?
If the detective strictly follows your rule, they will fail to solve the crime, even though they are following the rules perfectly. They are accurate to the rules, but useless for the job.

The "Benign Leakage" Approach:
Now, imagine you tell the detective: "Use these three clues as your main guide. But, if you see something else that helps solve the case (like the smoke smell), go ahead and use it too, as long as you can still explain your reasoning using the main clues."

The Result:
The detective solves the crime much more often. They are still using the concepts you gave them, but they aren't paralyzed by the fact that your list was missing a crucial piece of information.

What is "Information Leakage"?

In the paper's technical terms, Information Leakage happens when the AI's internal "concept" (like "red beak") accidentally picks up information about other things (like "is a robin") or the final answer ("is a bird").

  • The Old View: This is a bug. It means the AI is confused and we can't trust its explanations.
  • The New View: This is often a feature. In a world where our lists of concepts are incomplete, the AI needs to grab extra info from the raw data to get the right answer.

The Solution: The "Safety Net" Training

The authors don't just say "let the AI cheat." They propose a specific way to train the AI so that this "cheating" is safe and controlled.

They introduce a training method (called LintL_{int}) that acts like a safety net. Here is how it works:

  1. The Test: During training, the researchers pretend to "fix" the AI's concepts. They say, "Okay, forget what you think the bird looks like. Let's force the concept 'red beak' to be true. Now, can you still guess the bird correctly?"
  2. The Goal: If the AI can still guess correctly even when you force its concepts to be perfect, it means the AI has learned to use the rest of the information (the "leakage") effectively to fill in the gaps.
  3. The Outcome: The AI learns to keep the "leaked" information in a safe place. It knows exactly which part of its brain is looking at the "red beak" and which part is looking at the "smell of smoke."

Why This Matters

The paper challenges three common fears about leakage:

  1. Fear: "Leakage makes the AI un-intervenable."
    • Reality: If trained correctly, you can still change the AI's mind by changing the concepts. The AI will adjust its answer based on your new input, just like a human detective would.
  2. Fear: "Leakage makes the AI un-interpretable."
    • Reality: The authors show that even with leakage, the AI still relies heavily on the concepts you gave it. It doesn't suddenly start guessing randomly; it just uses a little extra help to be accurate.
  3. Fear: "Leakage is always dangerous."
    • Reality: In a perfect world with perfect data, maybe. But in the messy real world, trying to stop all leakage makes the AI too rigid to be useful.

The Bottom Line

The paper argues that we should stop trying to build "pure" concept models that ignore everything else. Instead, we should build models that are honest about their limitations.

If your list of concepts is incomplete (which it almost always is), you need the model to "leak" a little bit of extra information to be accurate. The goal isn't to eliminate the leak; it's to tame it so the model remains accurate, helpful, and able to listen to human feedback.

In short: Don't fire the detective for noticing things you didn't tell them to look for. Instead, teach them how to use those extra clues to solve the case better.

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 →