- Rating
- 3
- Confidence
- 2
- Informativeness
- 3
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The authors highlight architectural leakage in per-timestep sequence models. The authors propose Future-Perturbation Score (FPS) as a detector, introduce label-only scores that quantify what a leaked bit is worth on monotone early-warning labels, and run a matched causal/non-causal audit across four architecture variants on PhysioNet 2019.
Critical strengths
- I thought the introduction and related works were very well written. To the point and clear.
- The details in the main paper and appendix is appreciated. I especially liked how the authors included the exact code implementation differences between different architectures in the paper.
Critical weaknesses
- Although the intro and related works were well written, I thought the methodology and results were quite choppy sometimes, reading more like a log.
- The authors mention this, but i think a key weakness is the paper's investigation comprises of one benchmark.
- I thought the scope of the paper is a bit too large and tried to fit in too many experiments in the main paper.
Questions for authors
- Have the authors tried running FPS on any published open-source sepsis or early-warning models that report per-timestep metrics?
- Did any of the causal models improve meaningfully when given the same observation indicators that drove part of the routed model’s gain?
Thank you for the review. We agree with much of it; the disagreement is mostly about what the paper claims.
We agree that any path from future inputs to a per-timestep output that must be issued online is a bug, that future information helps whenever the label depends on it, and that a one-bit channel being enough is a property of the label. We also agree that running the model in streaming fashion is the reference check. The paper does not present the two-run test as new. Section 2 cites Fonseca (2026), who perturbs only future data, and Saggese & Smith (2025), who compare batch with streaming execution, and says FPS is that two-run test applied to trained sequence models. A prefix replay is a streaming check at one cut, and the checklist recommends it.
The contribution is the benchmark of which checks miss which leaks and the measurement of how much these leaks are worth.
The leaks are not written as future access. In the case-study model the leak is a router context averaged over the whole record. The released challenge entry that fails combines a bidirectional LSTM with per-record min–max scaling, backward fill and a softmax over the time axis (we did not ablate which part leaks). Such a model is scored causally by the official challenge harness, which replays prefixes, and still inflates an offline whole-record evaluation.
The shortcuts used instead of a full streaming run miss some of them. On 14 synthetic leaks with causal twins (Table 1), a shuffle-only test catches 4, a shift-only test 10, and a truncation that zero-pads the future instead of cropping it catches 13. The one it misses reads the tensor length, so a check that masks rather than crops would likely not see it either. The prefix replay catches all 14 by construction. We flag FPS > 1e-6 to allow for round-off, and there are no false positives: all 125 causal checkpoints we scored give exactly 0 in float64, as you say they should (float32 does not; Appendix A).
On this benchmark the size is large enough to change conclusions. Pairs that differ in one line of code gain +6.2 to +19.2 AUROC on all twenty splits, and the gap survives per-patient scoring, the challenge utility and training on one PhysioNet2019 hospital and testing on the other (3 splits each way). The routed model that started this was reported at +14 AUROC over its causal baseline. With causal context and matched augmentation it gives −0.3 at five seeds and −0.65 at twenty.
The label-only score is a tool. We agree the one-bit result follows from the label. The oracle score is computed from labels alone, in minutes on a CPU, so anyone can check how exposed their own label is before training a model. What a real leak delivers is what the inputs reveal: on this benchmark a bit predicted from whole-record summaries of the inputs reaches 0.86, above every causal model we trained (the best, with the observation indicators as inputs, reaches 0.82).
A field-wide study would make a stronger paper, and we did not do one. Our evidence is narrower: the case-study model, and four released PhysioNet/CinC 2019 entries with trained weights (a selection we could run as released, not a screen). One of the four, run once on the whole record as an offline per-timestep evaluation runs it, fails and scores 4.5 AUROC points above its own prefix loop (0.673 against 0.628, Table 5). Its official score is not affected. We do not infer a failure rate from this, and we could not extend the screen before the discussion closes.
We agree about the abstract. For a final version we would replace it with a shorter one along these lines:
"Per-timestep sequence models can read future inputs through their architecture even when the split and the features are clean, for example through a bidirectional layer, unmasked attention, symmetric padding or a context pooled over the whole record. A prefix replay detects this: run the model on the record cropped at step k and compare its outputs up to k with those of the full run; a causal model gives identical outputs in float64. On 14 synthetic leaks, cheaper checks such as shuffling or zero-padding the future miss some. On PhysioNet 2019 sepsis prediction, causal and non-causal models that differ in one line of code differ by 6 to 19 AUROC points on all twenty splits, and one of four released challenge entries, evaluated offline on whole records, scores 4.5 points above its own prefix loop. A routed additive model reported at +14 AUROC loses its gain once the leak is removed; a causal design that reads its measurement history gives +1.7, most of it without the router."
Whether an empirical audit of this kind is enough for ICLR is a fair question, and it is yours to judge. We would only ask that the paper be read as one: the fact that future access helps and the two-run test are not what it claims, and the benchmark of checks and the measurements are.