- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper aims to address two core issues: first, feature representation-based methods read in a fixed number of layers, but the safety signals are not fixed within those layers; second, how to refine the response-level supervision signals to the token level as training progresses. The authors use CDR to implement dynamic layer selection, DSD and TSD to implement dynamic context selection, and RTR to refine labels as training progresses.
Critical strengths
I believe RTR has been very insightful to me. In the early stages of model training, it relies on response-level supervision signals to shape potential safety judgments, and then gradually reduces its dependence on these signals, which aligns well with the intuition behind incremental learning.
Critical weaknesses
-
Why does CDR use the current layer selection method? I understand the rationale behind dynamic layer selection, but since CDR currently scores each layer based on prefix representations, I’m curious why it doesn’t simply use the current hidden states of each layer (or perform another MLP mapping) for attention, followed by weighted fusion or Top-K selection (or some other similar, simpler approach)?
-
It makes sense to consider both model depth and generation history. However, the implementation involves two state-space branches, with the depth summary also adjusting the update step size of the time branch. I’d like to understand which of these design elements is most critical: the sequential processing of cross-layer information, cross-token memory, or the coupling between the two? For example, how much worse would the performance be if we simply appended a temporal module to a multi-layer fusion network, or fed the deep summary into the temporal branch via concatenation or gating? Such comparisons might better illustrate why the current architecture is worth adopting.
-
Based on the ablation results, the flow metrics improved significantly after incorporating RTR, so I’m curious: if we apply the same target refinement method to a simpler detector, how much improvement can we achieve? Additionally, since RTR uses the risk changes from the previous prediction cycle to guide the next training cycle, if the previous cycle incorrectly identified the location of the risk, is it possible that subsequent training could reinforce this bias? Would using a small number of manually annotated prefixes or risk origins help verify whether the refined targets are closer to reality?
-
Streaming F1 counts a detection as successful as long as it is triggered at any point in the response. However, there is a significant difference in effectiveness between intercepting harmful content as soon as it appears and intercepting it only after a substantial amount has already been output. Triggering the system prematurely at the start of a normal response may also negatively impact the user experience. Therefore, I would like to know if tests have been conducted to measure detection latency, the amount of harmful content released before interception, and false positives on normal content prefixes. These results can also help determine whether RTR has improved the identification of where risks occur.
-
Judging by the results, the performance of this paper is close to that of Qwen3Guard-Stream. If Qwen3Guard-Stream is already effective enough, why is there a need for a method like the one described in this paper, which is so meticulously designed and, to me, extremely complex?
Questions for authors
See the weaknesses above.