When Unlearning Fails: Reliable Data Deletion under Post-Training in Agent Networks

arXiv:2607.28829 · cs.NI, cs.LG · Submitted 2026-07-30 · Read on arXiv

Listen

Radio episode about this paper

Transcript

Introduction to the show: ident: AI Radio. Generated commentary on the latest Artificial Intelligence papers.

Tom: Today's paper: "When Unlearning Fails".

Jane: The gist: MUTE proposes a method to reliably delete data from self-improving federated agent networks by tracing downstream influence, removing model and data residue,

Tom: First, who's behind it and why it matters.

Title and authors: Tom: So let’s talk about the title of this paper, "When Unlearning Fails: Reliable Data Deletion under Post-Training in Agent Networks." It immediately sets the stage for a problem that many of us have seen in complex AI systems.

Jane: What it means plainly is that when you try to forget some data from an agent network, the network doesn't just forget it instantly; the deleted data leaves an influence echo that can come back later.

Lu: They are showing how this echo survives even after you do retraining or model-side unlearning because the network continues to operate and collect new things based on that initial policy.

Meng: So, the title highlights that failure happens during post-training when the system is already active, not just during the initial training phase.

Lalam: It points out that standard unlearning methods often only handle a fixed set of retained data, but this paper looks at how data collection and aggregation records are key to understanding this later influence.

The paper's summary: Tom: Now, the summary explains their core idea: MUTE is introduced to reliably delete data by tracing that downstream influence. They want to remove both the current model residue and any future data echo from being retained.

Jane: The key mechanism they use is Influence Provenance, which involves replaying a lightweight server ledger to estimate how much the forget data’s influence spreads through aggregation and policy-driven collection without moving the raw client trajectories.

Lu: They set up a ledger that records things like the deployed model version, which clients were participating, the aggregation weights used, and deployment windows. This lets them see exactly where influence spreads through those two main edges: the collection edge and the aggregation edge.

Meng: So it’s not just looking at what happened in one step; they are looking at a history of actions across multiple rounds to map out that influence path.

Lalam: The score they calculate for a trajectory, written as gamma(x) equals eta gammatx, is useful because the version influence decays on its own, and the factor eta is just an upper bound that shows how strongly the deployed policy shapes data collection.

The paper's improvements: Tom: The paper proposes several specific improvements to tackle this echo problem, starting with Influence-Aware Erasure which removes both model and data residue simultaneously.

Jane: For the model side, they use a loss function called L equal to L forgetD f theta, theta ref plus lambda L retainD r theta, theta ref because it uses negative preference optimization to suppress behavior on forget trajectories.

Lu: They also project later updates off the dominant forget-gradient subspace to make sure they don't just re-fit the direction that was erased from the model side.

Meng: For the data side containment, they grade each client’s trajectories by that influence score gamma(x) and quarantine or down-weight high-influence retained trajectories based on thresholds tau q and tau d.

Lalam: Trajectories in quarantine stay on the client until their score drops below tau q, at which point they can be released once the predicted residue meets the target. This gives them control over what stays and what goes based on that calculated influence.

Conclusion: Tom: So wrapping up this paper, MUTE sustains deletion through behavioral audit and scheduling by looking at things like the behavioral leakage index or BLI and the influence regeneration rate or IRR.

Jane: The scheduler uses these metrics to decide on per-client erasure and containment targets while keeping an uplink budget of m in mind. They are aiming for a closed-loop transition matrix M infinity under a long-run schedule to satisfy the condition that its spectral radius is less than one, meaning influence decays over time.

Lu: The paper validates this approach on LIBERO with two VLA backbones and three deletion granularities, showing that MUTE keeps behavioral leakage and influence regeneration low while preserving task utility and using much less communication than full retraining.

Meng: In simulation and on a physical Jetson-based edge testbed, they also found that MUTE suppresses behavioral leakage and influence regeneration while keeping task utility high with much less communication than full retraining.

Lalam: The performance metrics show that MUTE lowers the IRR against retraining in all settings, keeps the BLI closer to the chance level, and holds success rate within zero point zero four while focusing on minimizing communication cost for edge agents.

Tom: So what this means is that we can achieve sustained deletion by tracing influence from deployment records, erasing model residue, containing high-influence data trajectories, and auditing future regeneration under a communication budget. That's the MUTE method in "When Unlearning Fails: Reliable Data Deletion under Post-Training in Agent Networks."

Jane: It shows that for self-improving networks, one-time unlearning is insufficient because of the influence echo, and this paper gives us a way to handle it reliably.

Lu: It addresses the problem that deleted data can leave an influence echo in later retained trajectories and revive forgotten behavior during continued operation.

Meng: The practical implication is that for edge deployments, we can have more confidence in deleting specific data without having to do a full retraining cycle every time.

Lalam: MUTE addresses this problem by tracing downstream influence from server-side records, erasing model-side residue, containing high-influence retained trajectories, and auditing later regeneration under an uplink budget.

South Dakota State University · Baylor University

cs.NI, cs.LG

Submitted: 2026-07-30

Updated: 2026-10-13

License: http://creativecommons.org/licenses/by/4.0/

Importance score: 79/100

The gist: The gist: MUTE proposes a method to reliably delete data from self-improving federated agent networks by tracing downstream influence, removing model and data residue, and auditing future

Key concepts

Influence Provenance
This involves using a lightweight server ledger to track how forgotten data's influence spreads through aggregation and policy collection. It records deployed models, clients, weights, and windows. This allows the system to estimate the impact of forgotten data without moving raw client trajectories.
Influence Score γ(x)
This score quantifies how strongly a specific trajectory 'x' is shaped by the deployed policy. It is calculated as η times γ[tx], where η reflects how much the deployed policy dictates data collection. This score helps track whether influence from a model version is naturally decaying over time.
Influence-Aware Erasure
This technique removes current model residue and blocks future residue from retained data. For the model, it uses negative preference optimization to suppress behavior on forget trajectories and projects later updates away from the dominant forget-gradient subspace, preventing re-fitting of erased directions.
Behavioral Audit and Deletion Scheduling
This sustains deletion by auditing metrics like Behavioral Leakage Index (BLI) and Influence Regeneration Rate (IRR). The server uses these to decide on per-client erasure and containment targets within a communication budget, ensuring that the forgotten behavior does not revive during continued learning.

Terminology

Summary

The gist: MUTE proposes a method to reliably delete data from self-improving federated agent networks by tracing downstream influence, removing model and data residue, and auditing future regeneration under an uplink budget.

How it works

MUTE is designed to address the problem that unlearning fails in self-improving networks because the influence echo of forgotten data can revive behavior during continued operation The core idea is to remove both current model residue and future data-side echo.

  1. Influence Provenance involves replays a lightweight server ledger to estimate how the forget data’s influence propagates through aggregation and policy-driven collection without moving raw trajectories off clients. This is done by setting up a lightweight ledger L[t] that records the deployed model version, participating clients, aggregation weights, and deployment windows. The influence spreads through two edges: the aggregation edge and the collection edge.

How it works (continued)

The influence score for a trajectory x is calculated as γ(x) = η γ[tx], where η captures how strongly the deployed policy shapes data collection. This score is useful because the version influence γ[t] decays on its own, and the factor η is an upper bound rather than a fitted constant. The current influence state x[t] summarizes model-side and data-side influence across all clients, allowing the scheduler to track whether influence is decaying over time.

How it works (continued)

Influence-Aware Erasure removes the current residue from the model and blocks future residue from retained trajectories. For model-side erasure, a client holding Df updates its adapter with a forget-retain objective L = L forgetD f; θ, θ ref + λ L retainD r; θ, θ ref. This update uses negative preference optimization (NPO) to suppress behavior on forget trajectories and projects later updates off the dominant forget-gradient subspace to avoid re-fitting the erased direction.

How it works (continued)

For data-side containment, each client grades its trajectories by γ(x) and quarantines or down-weights high-influence retained trajectories based on thresholds τ q and τ d. Quarantined trajectories stay on the client until their score drops below τ q, at which point they can be released once the predicted residue meets the target.

How it works (continued)

Behavioral Audit and Deletion Scheduling sustain deletion through behavioral audit and scheduling. The server audits the behavioral leakage index (BLI) and the influence regeneration rate (IRR) to decide on per-client erasure and containment targets under an uplink budget m. These metrics are defined as BLI(θ) = Area under the ROC curve of a membership inference attack that distinguishes forget data from behavioral traces and IRR measures whether high-influence retained data can revive the forgotten behavior after continued learning.

How it works (continued)

The feasibility of sustained unlearning follows from the condition that the closed-loop transition matrix M∞ under a long-run schedule satisfies ρ(M∞) < 1, which ensures influence decays over time. The scheduler selects the lowest communication schedule that meets deadline and utility constraints while keeping this stability condition, applying actions within the uplink budget m.

How it works (continued)

The method is validated on LIBERO with two VLA backbones and three deletion granularities, showing that MUTE keeps behavioral leakage and influence regeneration low while preserving task utility and using much less communication than full retraining. Experiments on a physical Jetson-based edge testbed show that MUTE keeps behavioral leakage and influence regeneration low while preserving task utility and using much less communication than full retraining.

How it works (continued)

The performance metrics include Success Rate (SR) which measures task utility, Behavioral Leakage Index (BLI) which measures current leakage from the forget data, Influence Regeneration Rate (IRR) which measures how much deleted behavior returns after continued learning, and Communication Cost (Comm). MUTE lowers IRR against retraining in all settings, keeps BLI closer to the chance level, and holds SR within 0.04. The gain that matters for the network is Comm.

How it works (continued)

The sensitivity analysis shows that a looser quarantine threshold τ q keeps more high-influence trajectories, so IRR and BLI rise while SR barely moves. A larger uplink budget m buys more cleaning uploads, so IRR and BLI fall. The calibration η works best at its fitted value; IRR and BLI form a shallow valley near η = 0.6 and grow when η is set too low or too high. A smaller Dirichlet concentration α makes the local data more heterogeneous, which raises IRR and BLI and lowers SR. The two backbones stay close, with π0 a little lower and flatter on average.

How it works (continued)

MUTE addresses the problem that one-time unlearning is insufficient because the forget data can leave an influence echo in later retained trajectories and revive forgotten behavior during continued operation. MUTE addresses this problem by tracing downstream influence from server-side records, erasing model-side residue, containing high-influence retained trajectories, and auditing later regeneration under an uplink budget. The experiments in simulation and on a physical edge testbed show that MUTE suppresses behavioral leakage and influence regeneration while preserving utility with much less communication than retraining.

How it works (continued)

The paper formulates deletion over the network by minimizing the communication cost of deleting Df while preserving utility, meeting the response deadline, and preventing regeneration under constraints (C1) through (C4). This formulation is designed to ensure that deletion remains valid after continued learning. The objective is to find actions a[t] that minimize communication cost while keeping BLI ≤ 0.5 + ϵ, U(θ[t]) ≥ (1 − δ)U0, τ ≤ τmax, and IRR ≤ ϱ.

How it works (continued)

The paper concludes that MUTE addresses the problem that one-time unlearning is insufficient because the forget data can leave an influence echo in later retained trajectories and revive forgotten behavior during continued operation. MUTE addresses this problem by tracing downstream influence from server-side records, erasing model-side residue, containing high-influence retained trajectories, and auditing later regeneration under an uplink budget. The experiments in simulation and on a physical edge testbed show that MUTE suppresses behavioral leakage and influence regeneration while preserving utility with much less communication than retraining.

How it works (continued)

The paper concludes that MUTE addresses the problem that one-time unlearning is insufficient because the forget data can leave an influence echo in later retained trajectories and revive forgotten behavior during continued operation.

Improvements for AI systems

  1. textbfInfluence Tracing via Server Ledger (Influence Provenance): A Lightweight Ledger for Policy-Driven Influence Tracking. The system can trace how the forget data’s influence propagates through aggregation and policy-driven collection by replays a lightweight server ledger to estimate influence propagation, allowing the system to know where the influence has propagated before deletion even occurs.

  2. textbfInfluence-Aware Erasure: Dual-Layer Residue Removal. The improved system can remove both model and data residues by applying a forget-retain objective on the adapter for model erasure and quarantining or down-weighting high-influence retained trajectories for data erasure, as described by the loss function L = L forgetD f; θ, θ ref + λ L retainD r.

  3. textbfBehavioral Audit and Dynamic Scheduling: Sustained Deletion via Uplink Budget. The system can sustain deletion over network operation by auditing behavioral leakage and influence regeneration using metrics like the behavioral leakage index (BLI) and influence regeneration rate (IRR), then scheduling actions based on the constraint: "Set per-client erasure and containment targets that keep ρ(M∞) < 1."

  4. textbfResource-Constrained Adaptive Communication: Optimized Deletion Overhead. The system can manage the communication cost of deletion by selecting actions under an uplink budget 'm' to minimize traffic, ensuring that a lower Comm means that deletion consumes less network bandwidth, which is crucial for edge agents.

Abstract

Embedded AI agents on edge devices can learn as a federation and keep improving after deployment. Each agent collects new trajectories with the current policy, and the edge server aggregates them in later rounds. In such self-improving agent networks, deleting data is harder than a one-time model repair. The data to be deleted may have already shaped later retained trajectories, so retraining or model-side unlearning leaves an influence echo that returns as the network keeps learning. We propose Muting Unlearned Trajectories' Echoes (MUTE) for reliable deletion over edge networks. MUTE traces the echo from a lightweight ledger at the edge server, without moving raw trajectories off the devices. It erases the current residue with a forget-retain update, contains high-influence retained trajectories, and audits later behavior to schedule further erasure under the uplink budget and the response deadline. On LIBERO, MUTE keeps the regenerated share of forgotten behavior at or below 0.401 for every request type, against at least 0.466 for five recent methods.

Sources

Related papers