- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper introduces RAS (Refusal Alignment Score), a lightweight metric for screening safety in related open-weight LLM checkpoints. The core idea is that within a model family, degradation in harmful-request refusal correlates with reduced alignment between the target model's activations and refusal directions extracted from an aligned reference. The five-stage SafeVec procedure extracts layer-wise refusal directions from the reference, selects a scoring window, computes alignment on harmful and jailbreak prompts, and calibrates a 0-100 score using behavioral ASR from calibration models.
Critical strengths
S1. The paper addresses a relatively novel topic. Given a reference model (e.g., Qwen) and a large set of its variant checkpoints, the question of how to perform rapid safety audits across these checkpoints is practically motivated and underexplored.
S2. The proposed Refusal Alignment Score enables low-cost safety auditing. By relying on input forward passes rather than response generation and judging, RAS offers a lightweight screening signal that can amortize evaluation cost across many checkpoints.
Critical weaknesses
My main concern with this paper is its practical utility.
W1. The setting is quite restrictive. RAS simultaneously requires (a) white-box access to residual-stream activations, (b) a reference model in the same family, and (c) multiple related checkpoints. Many realistic evaluation scenarios do not satisfy all three conditions at once, which limits the applicability of the method.
W2. The baseline cost being amortized is already modest. Behavioral evaluation on a benchmark like HEx-PHI with a single judge is not expensive in the first place.
W3. Missing comparisons to simple and intuitive baselines. The paper demonstrates correlation between RAS and behavioral safety, but does not compare against cheaper ways of approximating behavioral evaluation itself, such as:
(a) Subsampling the evaluation set: running the full behavioral protocol on only 1%-10% of the safety evaluation prompts;
(b) Capping generation length: performing behavioral evaluation with a very small output token budget (e.g., 10 tokens), since safety-relevant behavior (refusal or compliance) typically manifests at the start of the response.
Both strategies can substantially reduce evaluation cost, may correlate well with final safety scores, and are arguably simpler to deploy than RAS. I encourage the authors to include these baselines so that the contribution of RAS over naive cost-reduction strategies is clearer.
Questions for authors
see weakness