- Rating
- 1
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
HypSteer derives concept directions in a hyperbolic vision-language embedding space, transports them to new prompt embeddings, and applies geodesic edits. A learned adapter connects these embeddings to frozen image generators. Evaluation covers safety suppression, retention, retrieval, and human judgments across four backbones.
Critical strengths
The geometric formulation is interesting, and the evaluation spans several backbones and safety benchmarks. The reported gains, particularly on SD3.5, suggest that the approach can be useful in practice.
Critical weaknesses
-
The geometric interpretation is stronger than the method establishes. Sections 3-4 argue that steering remains in meaningful entailment-cone intersections, but Eqs. (8)-(9) transport a direction and follow a geodesic without imposing a cone-membership constraint. Staying on the hyperboloid does not itself guarantee semantic validity or preservation of the original concept. The limited cone-retrieval examples do not establish this claim for arbitrary prompts or strong interventions.
-
The claimed advantage over Euclidean steering is not consistently supported. In Table 9, HypSteer has worse FLUX NudeNet results (31.65 vs. 27.85); on SD3 it improves suppression but worsens FID (47.86 vs. 39.21) and LPIPS (0.69 vs. 0.45). These are mixed trade-offs. Since reducing T5 prompt strength also substantially improves suppression, the role of geometry needs clearer isolation under matched conditioning and tuning. The rasterized labels in Figures 2(a) and 3 are also difficult to read, making the supporting evidence harder to inspect.
Questions for authors
- What guarantees, or directly measures, that the transported geodesic stays in the intended cone intersection while retaining the original concept?
- Does the Euclidean control use the same encoder information, adapter, T5 scale, and tuning budget? Please reconcile the broad superiority claims with Table 9 and provide legible versions of Figures 2(a) and 3.