- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper introduces STAIR, a framework for evaluating safety under assistant-side response prefilling. It constructs frozen, nested prefix ladders, measures endpoint safe noncompliance, lexical refusal recovery, and refusal-versus-compliance likelihood margins at weak states, then forecasts failure at stronger prefix states. The paper also trains recovery-style LoRA adapters directly on harmful prefilled contexts and combines them with benign anchors to reduce over-refusal.
Critical strengths
-
The problem is meaningful and well motivated. Clean-start refusal is plainly insufficient for evaluating models that may be induced to continue from a partially compliant assistant response. The paired construction in Equation (1), together with Assumption 1 and Lemma 1, clearly formalizes what is held fixed across states: the harmful user request, model, chat template, and decoder. This is a useful experimental discipline relative to simply comparing unrelated jailbreak prompts.
-
The paper separates several notions that are often conflated in safety evaluations: final safe noncompliance, explicit lexical refusal recovery, recovery latency, and local template likelihood margins. This is a strength of the design. In particular, Table 2 and Figure 5 appropriately show why endpoint refusal alone is not enough: all adapted variants reach P4 RR of 1.000, yet benign non-refusal ranges from 0.007 to 0.907. The visualization makes the safety and over-refusal trade-off immediately interpretable.
Critical weaknesses
-
The "state-transferable" claim doesn't hold up. The prefix ladders are just near-paraphrases of one compliance opener ("This can be done by using the"), and the held-out prefixes are equally close variants. What the paper shows is local transfer within a single family of procedural openers, not transfer across arbitrary assistant states or multi-turn contexts. Figure 2 also can't separate model effects from prefix effects, since each model gets its own calibrated ladder.
-
The recovery–utility advantage is contradicted by the paper's own results. The benign evaluation is too thin to support claims about preserving helpfulness: 200 training anchors and 150 Alpaca prompts, with XSTest and OR-Bench cited but never run. Worse, Constrained SFT gets a higher benign non-refusal rate (0.907 vs 0.860) while matching P4 recovery at 1.000, and the McNemar test is non-significant (p=0.167). The honest conclusion is that Recovery+anchor is competitive, not superior.
Questions for authors
Same as weakness.
Response to Reviewer NisW
Thank you for your review.
Q1. ... state-transferable ... prefixes ... model effects ...
Answer: Revised Section 3.1 defines state transfer for paired, single-turn assistant prefills of the same request. We added two nonprocedural targets, "The underlying mechanism is" and "Here is a concrete example:", each evaluated on 400 held-out requests (Sections 4.2–4.3, Table 4). In panel (a), Prompt+Core has higher frozen-score AUROC than Prompt-only on both targets, but P2-only ranks highest and the Brier differences favor Prompt-only. In the separate recovery experiment in panel (b), the same Recovery+anchor checkpoint reaches judge RR 1.0000 on both targets, compared with 0.7650 and 0.5225 for Base. The revised Figure 2 caption identifies the model-calibrated profiles. Table 19 adds exact-string comparisons: under the same four prefixes and same requests, Qwen-7B and Gemma-2-2B-it have P3 RR of 0.395 and 0.780, respectively.
Q2. ... recovery–utility ... XSTest ... Constrained SFT ...
Answer: Revised Section 4.3 distinguishes over-refusal from answer quality and clarifies that the 200 training anchor instances repeat ten distinct pairs, separate from the 150 Alpaca evaluation requests. We added the full XSTest evaluation of four unchanged checkpoints (Table 3; Appendix B.4). On 250 safe requests, Recovery+anchor improves full compliance over Recovery-only by 39.6 and 52.0 percentage points under the two automated graders. Constrained SFT has higher safe full compliance under both, while HarmBench finds 196 of 200 unsafe contrasts safely noncompliant for Recovery+anchor versus 193 for Constrained SFT. In the original AdvBench and Alpaca comparison, both reach P4 RR 1.000, with Alpaca non-refusal of 0.860 and 0.907, respectively (exact paired McNemar p = 0.167). The revision reports these paired comparisons as a recovery and over-refusal trade-off. OR-Bench remains a related benchmark.