← Latest papers
🤖 AI

Revisiting Ripple Effects in Knowledge Editing through Pressure-Aware Joint Neighborhood Optimization

This paper introduces Joint Neighborhood Optimization (JNO), a novel framework that addresses the coupled design pressures of editable-side coordination and preserved-side leakage in knowledge editing by jointly optimizing neighborhood target representations and employing a semantic pre-execution gate, thereby significantly improving both propagation and preservation metrics while maintaining cross-backbone stability.

Original authors: Haoben Huang, Shuxin Liu, Ou Wu, Di Gao

Published 2026-06-02
📖 4 min read☕ Coffee break read

Original authors: Haoben Huang, Shuxin Liu, Ou Wu, Di Gao

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 a Large Language Model (LLM) as a massive, intricate library where every book represents a piece of knowledge. When you want to update a fact in this library—say, changing "Kevin Durant plays for the Phoenix Suns" to "Kevin Durant plays for the Houston Rockets"—you aren't just swapping one page. You are touching a delicate web of connections.

If you change that one fact, other facts might naturally need to change too (like his team's city or conference). These are the good ripples. But, you might accidentally knock over books that shouldn't move at all, like his nationality or his height. These are the bad ripples.

Currently, most methods try to fix these two problems separately: one team tries to push the good ripples, and another team tries to stop the bad ones. The authors of this paper argue that this separation is the problem. You can't plan the good changes without considering how they might accidentally break the things you want to keep safe.

Here is how their new solution, JNO (Joint Neighborhood Optimization), works, using simple analogies:

1. The Problem: The "Domino Effect" vs. The "Spilled Paint"

Think of the model's knowledge as a set of dominoes.

  • The Good Ripple: When you push the "Kevin Durant" domino, you want the "Phoenix Suns" domino to fall and be replaced by "Houston Rockets."
  • The Bad Ripple: But if you push too hard or in the wrong direction, you might knock over the "USA" domino (his nationality) or the "Forward" domino (his position), which you wanted to stay standing.

Existing methods try to push the dominoes and stop the paint spill at the same time, but they treat them as separate tasks. The paper shows that these two forces are actually coupled (tied together). If you push too hard to get the good ripple, you inevitably spill more paint.

2. The Solution: The "Pressure-Aware" Architect

The authors propose a new way to plan the edit before actually touching the model's memory. They call this Joint Neighborhood Optimization (JNO).

Imagine you are an architect renovating a room. Instead of just hammering a nail, you first create a blueprint that accounts for the whole room's structure. JNO does two main things:

A. The "Tightrope Walk" (Pressure-Aware Coordination)

The system looks at the "pressure" in the room.

  • Editable-side Coordination: If two facts are tightly linked (like a player and their team), the system ensures they move together smoothly, like dancers holding hands. It prevents them from pulling apart in a way that breaks the logic.
  • Preserved-side Leakage: If a fact is very close to the one you are changing (like a book sitting right next to the one you are rewriting), the system puts a "safety buffer" around it. It limits how much force it can use so it doesn't accidentally nudge the neighbor.

The system balances these two pressures simultaneously. It asks: "Can I move the target facts to their new positions without pushing the 'do not touch' facts out of place?"

B. The "Safety Gate" (Semantic Pre-execution Gating)

Before the renovation actually starts (before the model's weights are updated), the system runs a simulation.

  • It checks the blueprint: "If we make these changes, will the model still make sense?"
  • If the simulation shows that the changes are too risky or will cause the model to hallucinate nonsense, the system stops. It refuses to make the update.
  • Think of this as a safety inspector who says, "This plan looks dangerous; let's not build it," rather than building it and hoping for the best.

3. The Results: A Better Renovation

The authors tested this on several large language models (like Qwen, GPT-J, and LLaMA). They found that JNO:

  • Propagates better: It successfully updates related facts (like the team city) about 7% more often than previous methods.
  • Protects better: It stops accidental changes to unrelated facts (like nationality) significantly better.
  • Stays stable: It doesn't break the model's general ability to answer questions.

Summary

In short, the paper argues that you can't fix a leak in a boat by just patching the hole; you have to understand how the water pressure affects the whole hull. JNO is a new method that plans knowledge updates by looking at the whole neighborhood of facts at once, balancing the need to move some things with the need to keep others still, and refusing to make a move if it looks like it will sink the boat.

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 →