I read this as a careful, self-critical characterization paper rather than a 'we beat IBM' paper, and that honesty is its best feature. The science that survives scrutiny is narrow: one MIP-corroborated code at roughly twice the Gross encoding rate, plus a clean negative result that the highest-rate code is not deployable on a naive schedule. I would accept after revision, mainly because the significance is real but the title and abstract promise more breadth than the verified evidence delivers.
- The paper is intellectually honest in a way that is rare for search-driven results: it leads with its own negative implication (the headline code sits below usable pseudothreshold) instead of burying it.
- It correctly identifies that the popular k d^2/n figure of merit is misleading under realistic circuit noise and offers a concrete, more honest alternative (S/w), which is a genuine conceptual contribution beyond the codes themselves.
- The distinction between what is exact ([[192,8,24]]) and what is heuristic (everything else) is maintained throughout, so a careful reader is never misled about the strength of each claim.
- The title says 'Codes' and the abstract advertises up to 4.41x, but only one code (~2.0x) has a defensible distance; a reader skimming will overestimate the result. I would retitle or reframe so the MIP-anchored ~2.0x code is clearly the headline and the rest are explicitly exploratory.
- Three of seven codes carry an admitted, unresolved prior-art risk (the cyclic Z_84/Z_90/Z_99 cases). Listing them in the main catalog before checking the GB tables sits awkwardly with the paper's otherwise scrupulous tone; I would resolve or relegate them.
- The 'primary finding' (pseudothreshold falls with stabilizer weight) rests on four codes at three weights, with a confound the authors themselves name. Calling it the primary finding is a stretch; I would frame it as a motivating observation pending the L1 ablation and denser weight sweep.
- Significance for the reader is gated almost entirely on future work (an FT schedule for weight-8+ checks); the paper should be clearer up front that nothing here is near-term deployable, so practitioners calibrate expectations.