- Rating
- 1
- Confidence
- 2
- Informativeness
- 1
- Presentation
- 1
- Soundness
- 2
Read review
Paper summary
Attempting to theoretically analyse the impacts of structural stability on safety.
Critical strengths
Theoretically, this work could be interesting. The authors are exploring the foundational mechanisms of how networks work, and are attempting to construct a theoretical framework around interesting concepts. The work contains some mathematical sophistry.
Critical weaknesses
When assessing a paper, I look at two primary avenues - how interesting is the core idea (and how well is it explored), and how well the work is presented. Unfortunately, I must say that to me, any ability to appreciate the work is hamstrung by the way the authors presentation. The work is littered with undefined terms and other writing issues (see below), and I must ask who this work is actually written for? Because I must admit that as someone from the AML community, I find this work almost impenetrable - not due to the mathematical detail, but rather the comprehensive lack of detail and descriptions in the authors presentation. This reads as a paper that was written either for a very specific audience or specifically for the authors themselves, with no regard to how it would be interpreted by the broader community. Which is a problem, because an idea should be broadly accessible.
I will also state that, and this may speak to my biases, but I find myself unconvinced by completely theoretical works at this point in time - especially when AI tools were used to "refine the conceptual framework...clarify limitations, and edit the manuscript". Without some level of experimentally testable hypothesis, I cannot be certain that the LLM that was involved in generating these theories was actually correct. And I have no way to calibrate the impact of the theoretical assumptions made by the authors.
It could be argued that peer review is the exact place for testing such things, and that reviewers should be doing this. However, this is offloading responsibility onto reviewers. I do not think that reviewers should be just skimming over papers and treating all results as true, but there is an element of reciprocity that is required within the peer reviewed process, and unfortunately, it's difficult to establish this for theory only papers.
With that said, my judgement is based strictly upon the content invested, rather than my concerns regarding reciprocity for theory-papers. However, I would suggest to the authors that there's value in attempting to experimentally elucidate theoretical contributions, at least on a toy-model level.
Writing issues
-
Abstract is....a lot. 9 sentences, 21 lines, including 1 sentence that runs 6 lines long. This is not aligned with the general accepted practice and style of papers at venues like ICLR. This comment is not presented to gatekeep, but rather to indicate that I view the deviation from standards of practice to be indicative of a style of writing that values density and verbosity over clarity.
-
Undefined terms - "same benign functionality but contradictory security policies" , the security policies aren't defined.
- "strong variants"
- "Multi-task supermasks and universal tickets"
- "robust tickets, Trojan tickets, and unsafe/safety tickets"
- "security-domain representations....the safety direction"
- "security decisions"
- "benign error"
-
Even the contributions are doing so much heavy lifting - they're explaining content, without defining parameters, without any of the associated context. Who is this meant for?
-
"Structural security distance" is treated as a proper noun with the introduction of the acronym, so it should have all leading letters capitalized.
-
Citation style issues. See for example Li & Kim's Superficial Safety Alignment Hypothesis .. (Li & Kim, 2026) would usually be presented as Li & Kim's (2026).
-
|. | isn't defined for the L_0 norm in Eqn 3, or at least it's only implicitly defined as the "number of active mask coordinates".
-
Parameters are often undefined - see for example the ranges in Theorem 3. There's no justification as to why these ranges exist?
-
Theoretical results are presented without the context to explain them. Theorems 6 & 7 and Prop 5 are given a 5 line framing (lines 281-285), but the framing is strictly focused on the "what", not the "why". There's no context here for anyone to understand why holding these theorems in their heads would be at all useful. The same goes for the entirety of Section 6.
Questions for authors
-
Why is the hamming distance an appropriate measure for security distance?
-
What parts of this work would be amenable to experimental validation?
Rebuttal
Thank you for the detailed feedback. We recognize that the original manuscript's presentation makes the contribution unnecessarily difficult to follow. We have rewritten the abstract and introduction, reduced specialized terminology, and added a worked example and experimental results to make the theoretical findings more accessible. We also moved some less central results to the appendix.
Hamming distance. Hamming distance counts the number of binary structural decisions required to move between two subnetworks of the same parent. This is directly relevant for parameter pruning or disabling predefined components, such as neurons, attention heads, or adapters. It is not intended as a universal measure of security risk. An important finding of our work is precisely that proximity between feasible policies, distance from a deployed model, and distance to an arbitrary security violation are different quantities.
Experimental validation. We have conducted an exploratory experiment on Qwen2.5-1.5B-Instruct comparing rank-one activation projection with binary gating of actual MLP intermediate neurons. Directional projection reduced detected refusals from 12/12 to 3/12 harmful prompts, whereas disabling 128 selected MLP neurons left 11/12 refusals. This demonstrates different behavioral effects under the two intervention classes. Still, it does not establish the minimum number of required edits or prove preservation of benign functionality.
Presentation and interpretation. The revised manuscript explains the main theoretical results before introducing their formal statements, provides a concrete illustration of the structural-distance separation, and adds a computable certification example. We have also clarified the assumptions and limitations of the results, particularly the distinction between prescribed unsafe policies and arbitrary security violations.