# CLEAR: Continuous Latent Adapter Routing for Utility-Preserving LLM Safety Alignment

Source: [arXiv](https://arxiv.org/abs/2608.21278v1)  
Feed7 permalink: https://feed7.dev/p/2608-21278v1-0ozp13x  
Published: 2026-08-21T16:36:10.000Z  
Trust: Needs Review (needs_review)

## Why Included

CLEAR conditionally activates a safety adapter instead of applying safety tuning to every prompt, reducing harmful completions while limiting benign-task degradation.

## Source Summary

**CLEAR** uses a hidden-state gate to vary the strength of a safety LoRA while keeping the backbone frozen. On Llama-3-8B-Instruct, HarmBench attack success fell from **32.3% to 0.5%**, with up to **7.1 points** more GSM8K accuracy than global SFT or LoRA.

## Practical Implication

For builders serving specialized models, conditional adapter routing is worth evaluating when global safety tuning damages benign tasks. Test the gate, adapter, and untouched backbone as separate failure surfaces across both adversarial and ordinary workloads.

## Agent-Ready Context

**CLEAR** uses a hidden-state gate to vary the strength of a safety LoRA while keeping the backbone frozen. On Llama-3-8B-Instruct, HarmBench attack success fell from **32.3% to 0.5%**, with up to **7.1 points** more GSM8K accuracy than global SFT or LoRA.

For builders serving specialized models, conditional adapter routing is worth evaluating when global safety tuning damages benign tasks. Test the gate, adapter, and untouched backbone as separate failure surfaces across both adversarial and ordinary workloads.

The results come from selected safety and utility benchmarks on **Llama-3-8B-Instruct**. They do not establish production robustness, routing reliability under distribution shift, or behavior on other model families.

## Connected Context

Feed7 judgment across 551 accumulated Signals:

CLEAR narrows safety alignment from a global model rewrite to a conditional internal intervention: benign utility can be preserved by routing a frozen backbone through a safety adapter only as strongly as needed. This complements frozen-model reliability mechanisms but adds a new routing surface whose behavior must be evaluated as part of the deployment configuration; the single-model benchmark does not resolve production robustness or false refusals.

- [You Only Pass Once: Answering and Abstaining Together in a Single Forward Pass of a Frozen Language Model](https://feed7.dev/p/2608-14465v1-0tpy8xd) — Both preserve a frozen backbone while applying internal interventions; YOPO’s finding that one intervention can corrupt another probe reinforces the need to test CLEAR’s gate and adapter as interacting failure surfaces.
- [Opaque Epistemic Mediation: How LLM Deployment Configurations Shape the Validation of Pseudo-Science](https://feed7.dev/p/2607-22513v1-0yf6na5) — Its deployment-dependent behavior finding makes CLEAR’s gate, adapter, interface, and serving configuration part of the versioned system rather than treating the backbone identifier as sufficient.
- [Announcements](https://feed7.dev/p/fable-safeguards-jailbreak-framework-05x4d7q) — Fable 5’s wider false-positive margin supplies a practical utility cost that conditional safety routing is intended to reduce, while also showing that refusal behavior must be tested on legitimate workloads.

## Context Map

- Layer: model
- Domains: security
- Topics: model-selection, agent-reliability

## Uncertainty

- The results come from selected safety and utility benchmarks on **Llama-3-8B-Instruct**. They do not establish production robustness, routing reliability under distribution shift, or behavior on other model families.

## 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.