- Rating
- 1
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 1
- Soundness
- 1
Read review
Paper summary
This paper proposes meta-faithfulness as a criterion for evaluating chain-of-thought faithfulness detectors: predictions should remain invariant under faithfulness-preserving transformations and respond appropriately to faithfulness-altering transformations. It introduces the FaithShift evaluation protocol, theoretical results concerning detector limitations and selective risk, and SIFT, a trajectory-based detector combining hidden-state features, invariance training, and abstention. The paper ultimately emphasizes an empirical diagnosis—that stochasticity dominates distribution-shift sensitivity—and reports that simple ensembling substantially narrows SIFT’s advantage.
Critical strengths
The audit-of-auditors perspective is well motivated. Evaluating preservation invariance jointly with alteration sensitivity and coverage is a useful way to assess faithfulness detectors beyond in-distribution AUROC. Requiring alteration sensitivity also addresses the trivial solution of obtaining perfect stability by always returning the same prediction.
Critical weaknesses
- Internal inconsistencies undermine the central empirical conclusions.
Equation (8) defines MFS as coverage multiplied by a harmonic mean bounded by one, so MFS cannot exceed coverage. Yet Table 1 reports SIFT’s MFS as 0.72 at coverage 0.49; substituting the reported IVR and AS gives approximately 0.404. This discrepancy affects the principal comparisons and ablations.
The claim that over 80% of instability is stochastic is likewise unsupported by Table 1: the seed-repeat component is approximately 30% for four baselines and 27% for SIFT; the 82% figure applies only to attribution-consistency. Moreover, Appendix G redefines raw IVR as the union of seed-induced and transformation-induced disagreements, rather than the transformation disagreement defined in Eq. (6). The ensemble conclusions are also inconsistent: Table 8 reports 0.76 versus 0.71, a margin of 0.05, while the text describes 0.01. Finally, does not establish equivalence. These issues prevent a reliable assessment of either SIFT’s advantage or the proposed stochasticity diagnosis.
- The remaining contributions do not sufficiently establish the claimed verification capability.
The theoretical results have limited implications for SIFT: Theorem 4.5 is conditional on identical observations, Theorem 4.6 relies on local sensitivity and independence assumptions, and Theorem 4.7 requires calibration samples from the evaluation distribution. None establishes that SIFT’s descriptors identify causal faithfulness or remain certified under unseen shifts. The multi-feature bound in Theorem N.1 also incorrectly uses an upper bound on score perturbation to derive an IVR lower bound; orthogonal perturbations provide a counterexample.
FaithShift’s construct validity remains unclear. Answer sensitivity to CoT scrambling does not establish mechanism preservation across a transformed pair. Alteration sensitivity is supported by only three pairs each for cue injection and cue verbalization, while the reported pooled AS differs between the main table and limitations.
Conflicting architecture descriptions and insufficiently specified API access to Claude-3/GPT-4o hidden states further limit the interpretability and reproducibility of the cross-model results.
Questions for authors
-
Metric definitions and reporting: Which implementation of MFS generated the tables, and how can MFS=0.72 coexist with coverage=0.49? Please reconcile the reported components using the existing predictions. Please also clarify the inconsistent AS values and whether “transfer gap” denotes an average or worst-axis gap, including the definitions used for the preregistered hypotheses.
-
Stochasticity decomposition: Is the primary IVR the transformation-disagreement statistic in Eq. (6), or the union statistic in Appendix G? What aggregation supports the suite-wide 80% conclusion? Please specify whether the varied randomness belongs to backbone generation, feature extraction, detector training, or inference.
-
Ensemble comparison: Which configurations and operating points underlie Table 8, the matched-coverage comparison, and Appendix H? Please reconcile their reported differences and identify the comparator associated with . If equivalence was not tested, could the conclusion be limited to the absence of a statistically detected difference?
-
FaithShift construction and audit validity: Please reconcile 750 base items with the description of 250 items from each of four domains, and provide the existing verified-pair counts used for AS. What exactly does the scrambling audit establish, and why is it interpreted as mechanism preservation rather than intervention sensitivity?
-
Theoretical contribution and correctness: What conclusion specific to SIFT follows from Theorem 4.5? How do the Appendix K diagnostics support the assumptions of Theorem 4.6? Please address the orthogonal-perturbation counterexample to Theorem N.1 and correct or restrict the bound.
-
Certification and risk curves: Which distribution supplies the calibration data, and is target-specific calibration used for each shift? How is dependence among traces from the same base item handled in certification? Please also reconcile Table 3 with Figure 9 and explain why Proposition M.10, concerning optimal coverage as allowed risk changes, justifies smoothing risk as a function of coverage.
-
Implementation and cross-model evaluation: Which SIFT architecture generated the main results? How were trajectories aligned across models, and what target data were used for alignment or calibration? For the cached Claude-3/GPT-4o hidden states described in Appendix P, please identify the API endpoint/version and returned features, and clarify how the eight-model evaluation relates to the two-backbone trace construction.
To the Program Chairs and Area Chairs, Concern Regarding Reviewer K9bc's Review (Submission 32732)
Dear PC and AC,
We request a human-level review of our paper. The Pangram report (link) flagged 94% as AI-generated, but we do not trust this review. Pangram itself notes false positives (~1 in 10,000), limited confidence on short/formulaic text, and segment-based scoring that mislabels hybrid human-AI editing. We ask that reviewers assess the substantive content and author contributions directly, rather than relying on this automated 94% figure.
Sincerely,
The Authors