# Forgetting Only What Matters: Layer-Selective Unlearning toward Robust LLMs

Source: [arXiv](https://arxiv.org/abs/2609.10439v1)  
Feed7 permalink: https://feed7.dev/p/2609-10439v1-1ob3vkf  
Published: 2026-09-09T16:50:41.000Z  
Trust: Needs Review (needs_review)

## Why Included

FOM-UL targets model layers that affect unwanted memories while sparing retained knowledge, and reports that forgetting survives 8-bit and 4-bit quantization better than baselines.

## Source Summary

FOM-UL scores transformer layers by influence on the forget set versus sensitivity to the retain set, then updates only the strongest candidates. Across **TOFU**, **KnowUnDo**, and **MUSE-style** evaluations, it reports less residual memorization while keeping utility near the original model.

## Practical Implication

Teams that must remove sensitive or copyrighted training content should evaluate unlearning after every deployment transformation. The method specifically tests **8-bit and 4-bit quantization**, where low-bit rounding can otherwise undo small, diffuse parameter changes, plus adversarial prompts that try to recover forgotten content.

## Agent-Ready Context

FOM-UL scores transformer layers by influence on the forget set versus sensitivity to the retain set, then updates only the strongest candidates. Across **TOFU**, **KnowUnDo**, and **MUSE-style** evaluations, it reports less residual memorization while keeping utility near the original model.

Teams that must remove sensitive or copyrighted training content should evaluate unlearning after every deployment transformation. The method specifically tests **8-bit and 4-bit quantization**, where low-bit rounding can otherwise undo small, diffuse parameter changes, plus adversarial prompts that try to recover forgotten content.

This is empirical suppression, not proof of deletion. The paper explicitly offers no formal erasure guarantee, so builders should not treat lower benchmark recovery as evidence that targeted data can never be extracted.

## Connected Context

Feed7 judgment across 732 accumulated Signals:

This narrows utility-preserving unlearning to the layers most influential for forgetting and explicitly makes post-quantization recovery testing part of the deployment workflow. It supports targeted intervention over diffuse updates for this objective, but only demonstrates resistance to tested recovery methods; it does not convert empirical suppression into a deletion guarantee.

- [The Structure of Quantization Damage in LLMs: Why the Next Bit Should Be Spent Globally](https://feed7.dev/p/2609-01587v1-1kd5xo7) — Quantization damage was found to be broadly distributed, whereas FOM-UL concentrates unlearning updates in selected layers; together they show that layer selectivity is objective-dependent and must be retested after quantization.
- [p-e-w/heretic](https://feed7.dev/p/heretic-0ne3rbq) — Both modify selected model behavior while trying to preserve general utility, but their aims oppose each other: FOM-UL suppresses targeted memorization, while Heretic removes refusal behavior and can weaken safety controls.
- [CLEAR: Continuous Latent Adapter Routing for Utility-Preserving LLM Safety Alignment](https://feed7.dev/p/2608-21278v1-0ozp13x) — CLEAR and FOM-UL both seek limited behavioral change without rewriting the entire model, but CLEAR conditionally routes safety behavior at inference while FOM-UL permanently updates selected parameters.
- [The Implications of Linguistic Illegibility for LLM Security](https://feed7.dev/p/2609-02852v1-09xc04l) — The limits of language-based monitoring reinforce FOM-UL’s warning that observed non-recovery cannot prove erasure; external containment and data controls remain necessary.

## Context Map

- Layer: model
- Domains: security
- Topics: open-models, agent-reliability

## Uncertainty

- This is empirical suppression, not proof of deletion. The paper explicitly offers no formal erasure guarantee, so builders should not treat lower benchmark recovery as evidence that targeted data can never be extracted.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.