What happens when a published scientific paper is handed to an AI system designed specifically to behave like an unusually persistent reviewer?
We recently tried this with our paper, A benchmarking framework for comparative evaluation of low-complexity region detection tools in the human proteome, published in Scientific Reports. The study compared eight low-complexity region, or LCR, detection approaches under 13 configurations across 20,610 representative human proteins. It examined length, protein coverage, amino-acid composition, entropy, purity, method consensus, pairwise overlap, sequence-complexity landscapes, and operational sensitivity and specificity.
We submitted the paper to Google's Deep Review.
What came back was not the familiar generic AI review consisting of “clarify the novelty,” “improve the discussion,” and “add more validation.” Deep Review produced a long technical audit containing specific mathematical, computational, graphical, methodological, and textual criticisms. Its high-level assessment was actually rather positive about the scale of the benchmark, the consensus analysis, probabilistic treatment of LCR sequence space, and the availability of code and processed data. But it then identified several potentially serious weaknesses.
The interesting question is not whether Deep Review found many things to criticize. A sufficiently energetic reviewer can always do that.
The interesting question is: how many of those criticisms survive scrutiny?
I therefore audited the audit. I compared the Deep Review comments with the article, inspected the figures, checked the publicly available analysis scripts, and compared some of the methodological claims with the original literature.
The conclusion is more interesting than either “AI reviewing is amazing” or “AI reviewers hallucinate.”
Deep Review is remarkably good at forensic consistency checking. It is less reliable when it moves from detecting an inconsistency to declaring what that inconsistency necessarily means biologically or methodologically.
That pattern is also strikingly consistent with what has been reported from earlier deployments of Deep Review's predecessor, Google's Paper Assistant Tool.
Deep Review is not just another chatbot prompt
Deep Review grew out of Google's Paper Assistant Tool, or PAT, which was deployed as an optional pre-submission reviewer at STOC, ICML, NeurIPS, and ICLR. Google reports that the system has now been used on more than 16,000 manuscripts. The stated aim is not to replace scientific judgment but to perform labor-intensive checks of logical consistency, technical claims, mathematical statements, and supporting evidence.
The author feedback from the earlier PAT experiments is illuminating. More than 90% of surveyed authors at STOC and ICML described the feedback as very or mostly helpful, and more than 90% said they would use it again. Yet only 55.8% of STOC respondents and 64.8% of ICML respondents said the feedback was mostly or completely grounded.
Those numbers describe our experience surprisingly well.
The review contains some excellent catches. It also contains several comments that are better regarded as hypotheses to investigate rather than verdicts.
Google itself explicitly acknowledges this limitation. Earlier users reported occasional hallucinations, incorrect challenges to valid arguments, and difficulties interpreting figures and complex notation. The ICLR instructions similarly warn authors that PAT may flag correct statements as erroneous or miss real flaws, and that authors remain responsible for verifying every criticism.
With that in mind, how did it perform on our paper?
Auditing the individual criticisms
The table below gives my assessment of each substantive criticism.
| Deep Review criticism | Assessment | My evaluation |
|---|
| 1. The Abstract says high-consensus LCRs are “longer,” although consensus analysis examines motif composition, entropy and purity, not length. | ✅ Valid | This is one of the cleanest catches. Figure 2 analyses motif composition, Shannon entropy and purity as consensus increases. It does not show length versus consensus. The Abstract and Discussion therefore extend the result beyond the analysis actually presented. The paper does indeed describe consensus regions as “longer” despite the corresponding consensus analysis not establishing this. |
| 2. “Residue-centric” and “protein-centric” metrics are partly misclassified in the Abstract. | ✅ Valid | Coverage is calculated as the fraction of each protein covered by LCRs and is naturally a protein-level summary. LCR count per protein is explicitly protein-centric. Amino-acid composition and entropy are calculated from LCR sequences themselves. Deep Review is correct that the terminology should be reorganized. |
| 3. CAST, SIMPLE, GBSC and LCD-Composer were omitted. | ⚠️ Fair criticism, not a methodological error | No benchmark can contain every available program. Eight approaches and 13 modes already constitute a substantial comparison. However, because the paper invokes PlaToLoCo and broad algorithmic diversity, explaining why these other tools were excluded would improve the study. The criticism becomes too strong if interpreted as meaning the benchmark is invalid because they are absent. |
| 4. The Introduction does not make the gap relative to PlaToLoCo and existing databases sufficiently explicit. | ✅ Valid presentation criticism | The paper describes previous resources and then moves rapidly to the new benchmark. Explaining explicitly that aggregation servers are not quantitative proteome-wide benchmarks would make the novelty sharper. This does not change the results, but it would improve the argument. |
| 5. The paper says coordinates were standardized to a 1-based BED-like format and then processed by BEDTools, which expects 0-based starts. | ✅ Valid and important | This was Deep Review's strongest technical catch. The manuscript explicitly says the common files are 1-based. BEDTools documentation states that BED starts are zero-based and ends are one-based. More importantly, inspection of our public code confirms the concern. seq_parser.py deliberately outputs start + 1 as a 1-based inclusive coordinate, while downstream scripts pass these coordinates into BEDTools. complexity_plot.py also performs Python slicing as sequence[start:end], despite receiving those 1-based coordinates. Thus, a nominal 20-residue window can become a 19-residue extracted sequence. This is a real coordinate-convention problem and should be corrected and the affected analyses regenerated. |
| 6. The operational TPR/FPR reference favors homorepeat-like LCRs and disadvantages multi-residue repeat detectors. | ✅/⚠️ Core criticism valid; wording somewhat overstated | The reference definition strongly favors low mutation and high single-residue dominance. The paper itself clearly says this is an internal operational reference rather than biological ground truth. That caveat is important. Deep Review is nevertheless correct that such a definition is inherently better aligned with some classes of LCR than others. This matters especially because T-REKS is specifically designed for tandem repeats, including degenerate multi-residue repeats. However, the review says a perfect dipeptide with exactly 50% representation is necessarily classified as negative. That is true under the manuscript's written Y > 50% rule, but not under the public code, which uses Y >= 50%. Thus the bias is real, but one of Deep Review's illustrative examples overstates it. |
| 7. Calling Dotplot the best-performing detector may partly reflect similarity between the detector and the operational reference. | ✅ Valid caution | When “truth” is operationally defined using particular compositional and repetitiveness features, performance means agreement with that definition. The paper acknowledges this in the Methods and Figure 6 caption, but later language such as “best-performing,” “real LCRs,” and “correct detection” occasionally slides back toward biological accuracy. The AlcoR paper itself notes that there is no computable universal gold standard for LCR detection, illustrating why this distinction matters. |
| 8. DisProt and missing PDB residues are problematic as a negative/background class for LCRs. | ⚠️ Substantively important, but Deep Review goes further than can be proved from the manuscript alone | LCRs and intrinsic disorder overlap but are not identical. Experimental work has explicitly shown differing structural and amino-acid preferences between LCRs and disordered regions. Therefore, treating disorder as the simple biological complement of low complexity would indeed be inappropriate. In our paper, these datasets were intended as biological anchors/backgrounds rather than a claim that all IDRs are non-LCRs. The review is right to ask whether overlapping LCR coordinates were removed and how class membership was handled. But its claim that label contamination definitely occurred requires inspection of the exact boundary-generation data workflow. It is a valid question, not yet a demonstrated fatal error. |
| 9. Changing the number of positive consensus regions with increasing k changes class priors in the GAM/posterior analysis. | ✅ Valid statistical concern | If the positive class shrinks as consensus becomes more stringent while the background remains fixed, raw posterior probabilities are affected by prevalence as well as changes in feature-space geometry. Comparing probability thresholds across k therefore requires either class balancing, weighting, calibration, or an explicit statement that these are prevalence-dependent empirical posteriors. Deep Review is right here. |
| 10. The held-out ROC description is ambiguous. | ✅ Valid | The paper says ROC analysis was performed on held-out data and then refers specifically to coordinates of IDRs and missing residues. But TPR requires positive as well as negative cases. The train/test construction needs to be stated much more precisely. This is a reporting problem even if the underlying implementation used an appropriate split. |
| 11. Tool versions and exact parameter configurations are under-specified in the manuscript. | ✅ Mostly valid | The repository contains considerably more information than the article itself, and many scripts reveal exact settings. That mitigates the reproducibility problem. But a benchmarking paper should ideally summarize all 13 configurations, software versions, command-line flags, and key thresholds in one table. Deep Review's recommendation is sensible. |
12. The example ACDEFEGEIE should have 40% rather than 60% minimal mutation if dipeptide periodicity is considered. | ⚠️ Deep Review identifies a real conceptual problem, but its exact correction is not fully justified | Inspection of the public implementation is revealing. The code does not actually compute the mathematically minimal number of substitutions required to transform a sequence into any possible periodic sequence. Instead, it searches exact k-mers already occurring at least twice and estimates the uncovered fraction using their non-overlapping counts. Under that implementation, the reported 60% can arise. So Deep Review's assertion that the software must return 40% assumes a more rigorous definition than the code implements. The deeper criticism is actually stronger: the manuscript's phrase “minimal mutational distance to a perfect repeat” does not accurately describe what the current algorithm computes. |
| 13. Exact 50% boundaries are unassigned because the text uses strict inequalities. | ✅ Valid for the manuscript, not for the implementation | The written definitions leave X = 50 and Y = 50 ambiguous. Deep Review correctly catches that. But the public classification.py uses mutation <= 50 and dominance >= 50, so the implementation does assign boundary values. This is therefore primarily a methods-text/code inconsistency, rather than an unclassified-data bug. |
| 14. fLPS and fLPS 2.0 default and strict modes are repeatedly confused in the Results. | ✅ Strongly valid | This is probably the most impressive manuscript-level catch. Figure 1 visually shows broad, high-coverage behavior for the default fLPS modes, while the strict modes are substantially narrower. Figure 7 similarly shows the highest TPR/FPR combination for the default modes, not the strict modes. Yet the Results repeatedly attribute those patterns to the strict variants. This needs correction throughout. |
| 15. The interpretation of the fLPS purity-retention curves is reversed. | ✅ Valid | Figure 3 shows the strict fLPS curves remaining above the default curves over much of the moderate-purity range. A curve that remains high as the purity threshold increases indicates a larger fraction of that method's calls surviving the threshold. The text says the strict versions have lower retention and uses this to infer greater stringency, which is not the correct reading of the plotted relative-retention curves. |
| 16. AlcoR and XSTREAM are described inconsistently as conservative, compositionally sharp, heterogeneous and high-entropy. | ✅/⚠️ Mostly valid, with one important nuance | There are genuine narrative inconsistencies. AlcoR is called “less selective” in one place and “conservative” shortly afterward. It is also described as favoring sharply biased LCRs although the entropy and complexity-space analyses emphasize heterogeneous predictions. However, Deep Review slightly overstates the contradiction when comparing pooled amino-acid composition with within-region Shannon entropy. A method can produce a dataset globally enriched for one residue while individual detected regions remain fairly heterogeneous. These metrics are related but not identical. |
| 17. The direction of the consensus trajectory contradicts itself across supplementary analyses. | ✅ Unambiguously valid | One paragraph says increasing consensus produces increasing mutation tolerance and decreasing compositional dominance. Another says increasing consensus produces lower mutation and higher dominance. Both cannot describe the same directional trend. Figure 2 supports decreasing entropy and increasing purity with consensus, so the former description almost certainly has its direction reversed. |
| 18. The paper gives opposite descriptions of whether DisProt or PDB-derived boundaries are more restrictive. | ✅ Unambiguously valid | The manuscript first says DisProt boundaries extend further into high-mutation space and PDB-derived boundaries are more restrictive, then shortly afterwards says DisProt boundaries are consistently more restrictive than PDB-derived boundaries. Deep Review is correct: this is a direct textual contradiction, not a matter of interpretation. |
| 19. High TPR together with near-unity FPR for default fLPS makes “high sensitivity” potentially misleading. | ✅ Valid and important | A detector that labels nearly everything positive can achieve both high TPR and high FPR. Figure 7 makes this trade-off very clear. Reporting TPR and FPR separately is legitimate, but describing such a detector as especially effective without emphasizing discrimination is misleading. A quantity such as Youden's J, balanced accuracy, precision/recall, MCC, or residue-level ROC/PR analysis would make the trade-off clearer. |
| 20. Several Figure 6 trend descriptions do not match the plotted curves. | ✅ Valid | Deep Review went beyond broad interpretation here and actually checked directions of individual trends. The figure supports several of its observations, including declines that are described in the text as increases or near-constant behavior. |
| 21. Several Jaccard values are interpreted incorrectly. | ✅ Strongly valid | The clearest example is the statement that strict modes overlap less, followed by an example in which 0.1235 is compared with 0.099 even though 0.1235 is larger. The text also describes 0.9462 as involving “strict modes” even though that value corresponds to the two default fLPS generations. Figure 4 confirms the numerical mismatch. |
| 22. Figure legends, scales and some visual elements are difficult to read or incompletely described. | ✅ Mostly valid, but editorial rather than fundamental | Several legends and axes are indeed cramped. Figure 5 uses tiny discrete labels rather than intuitively readable percentage axes, and Figure 6 could be scaled more consistently. These issues matter for reproducibility and interpretation but do not themselves invalidate the analyses. |
| 23. The Discussion groups SEG strict, T-REKS and XSTREAM together as choices for “compositionally pure” or tandem-repeat-like sequences. | ✅ Valid | This sentence combines two distinct goals. SEG strict and LCRFinder fit the “compositionally pure/homorepetitive” description better, whereas T-REKS and XSTREAM are specifically repeat-oriented and can detect compositionally heterogeneous tandem structures. T-REKS was explicitly developed for tandem repeats, including degenerate repeat architecture. The practical recommendation should separate these use cases. |
| 24. The >50 aa length and >20% protein-coverage thresholds recommended for functional prioritization are not directly demonstrated by the consensus analysis. | ✅ Valid | These cutoffs correspond conveniently to bins used elsewhere in the study, but Figure 2 does not demonstrate that consensus LCRs exceeding these thresholds are especially enriched for lower entropy or higher purity. The recommendation is reasonable as a hypothesis, but it should be described as heuristic rather than empirically established by the present analyses. |
| 25. The discussion overstates how closely PlaToLoCo overlaps the benchmarked tool set and incorrectly places LCD-Composer in the context of emerging ML methods. | ⚠️ Partly valid | The broader suggestion to discuss omitted methods is useful. The manuscript's wording around PlaToLoCo can be made more precise. LCD-Composer is composition-based rather than a machine-learning method, although the manuscript does actually say this immediately after mentioning emerging ML approaches. So this is more an issue of paragraph construction than a major factual error. |
| 26. Reference 29 is inappropriate support for the claim that experimentally curated disorder represents regulated, evolutionarily maintained architecture. | ✅ Valid | Wootton and Federhen's SEG work concerns local sequence complexity, not experimental evidence for the evolutionary maintenance of intrinsic disorder. A reference specifically addressing IDR evolution and functional constraint would be more appropriate. |
| 27. Minor terminology, acronym, typo and reference corrections. | ✅ Mostly valid | These are largely good copy-editing catches. In particular, T-REKS is indeed named for “Tandem REpeats in sequences with a K-meanS based algorithm,” not the expansion given in the manuscript. The AlcoR paper is titled alignment-free simulation, mapping, and visualization of low-complexity regions, so the manuscript's invented expansion of “AlcoR” should also be corrected. Other spacing, naming, citation-format and reference-list comments are mostly straightforward editorial corrections. |
The most consequential thing Deep Review found
For me, the most important result of this exercise is not one of the many textual contradictions.
It is the coordinate issue.
The paper states that outputs were standardized in a 1-based BED-like format. Deep Review correctly noted that BEDTools interprets BED coordinates with zero-based starts.
Initially, that could have been dismissed as an AI reviewer making an assumption about what the scripts actually did.
But the public code confirms the mismatch.
seq_parser.py explicitly converts windows into 1-based inclusive coordinates. Downstream sequence extraction then uses Python's zero-based slicing convention. The confusion-matrix script subsequently passes interval files directly to BEDTools. This means the issue is not merely terminological. At least some sequences and interval lengths are shifted or shortened by one residue.
For long LCRs this may have a small quantitative effect. For very short motifs it can matter appreciably. More importantly, the operational reference itself is generated from short sliding windows, so a one-residue change can alter amino-acid dominance, entropy, and repeat statistics.
This is exactly the kind of error for which an automated reviewer can be unusually useful. Human reviewers tend to concentrate on whether the conceptual analysis makes sense. A machine can relentlessly notice that “1-based” appears on page 3 and “BEDTools” appears on page 4 and ask whether those two statements are compatible.
That is a real contribution.
Where Deep Review is too confident
The review is less convincing when it moves from:
“This design may favor one class of sequences”
to:
“Therefore this tool is systematically penalized and this ranking is circular.”
The first statement is demonstrable from the operational definition. The second requires quantitative testing.
For example, the positive reference strongly emphasizes high single-amino-acid dominance. That undeniably makes it a particular definition of LCR rather than a neutral biological truth. The paper itself explicitly acknowledges that limitation.
Deep Review is therefore correct to say that TPR and FPR must be interpreted as agreement with the operational reference.
But demonstrating how much that definition changes the ranking of T-REKS, XSTREAM, AlcoR or fLPS would require repeating the benchmark under alternative definitions.
That would actually make an excellent follow-up analysis:
use several operational ground truths,
include the long-tandem-repeat region,
include curated compositional-bias annotations,
include experimentally characterized functional LCRs,
and ask how stable tool rankings are across reference definitions.
That is a better scientific response than simply accepting or rejecting the AI criticism.
The reference-set criticism cuts to the heart of the field
Deep Review's criticism of the operational reference is especially interesting because it touches a fundamental problem in LCR research: there is no universally accepted biological gold standard for low complexity.
Even the AlcoR publication explicitly notes that no computable gold standard for LCR detection is available because the true boundaries are not known.
This means any benchmark must choose some operational definition, simulated data, curated annotations, consensus standard, or biological proxy.
Every choice has a lens.
Our mistake is therefore not that we used an operational definition. Some operational reference is necessary.
The point requiring greater care is what we infer from it.
“Tool A agrees most closely with this operational LCR definition” is defensible.
“Tool A is the most accurate LCR detector” is much harder to establish.
Deep Review is right to insist on that distinction.
Deep Review was exceptionally good at finding contradictions
The review's strongest performance is almost forensic.
It found that one paragraph says increasing consensus moves sequences toward higher mutation and lower dominance, while another says the opposite.
It found that the text says DisProt boundaries are less restrictive than PDB boundaries and later says precisely the opposite.
It found that Figure 7 shows default fLPS variants with the highest TPR/FPR values while the prose attributes this to the strict variants.
It checked numerical values in the Jaccard matrix against sentences interpreting those values and noticed that the stated example literally has the inequality backwards.
These are mundane errors compared with inventing a new biological mechanism, but they matter. They are also exactly the kind of errors that can survive several rounds of human reading because readers understand the intended narrative and unconsciously repair inconsistencies while reading.
An AI has no such courtesy. It can be gloriously literal.
But it also demonstrates the classic AI-review failure mode
The ACDEFEGEIE criticism is a good example.
Deep Review reasons that if “mutation percentage” truly means the minimum number of substitutions required to make the sequence periodic, an alternating repeat can be created with fewer changes than a homopolymer, so the manuscript's 60% example must be wrong.
Mathematically, that interpretation is sensible.
But the public code reveals that the implemented algorithm does something narrower. It searches for exact k-mers already repeated within the sequence and calculates a coverage-like quantity. Under that algorithm the 60% value can arise.
So Deep Review has found a genuine problem, but not exactly the problem it claims to have found.
The problem is that the prose gives the reader a stronger mathematical definition than the software implements.
This distinction is crucial. AI reviewers are very capable of constructing a logically consistent interpretation of ambiguous prose and then criticizing the paper for violating that interpretation. Sometimes the paper is wrong. Sometimes the description is merely ambiguous. Sometimes the model's interpretation is not the intended one.
A human expert still has to separate those cases.
How does this compare with other experiences of Deep Review?
Quite closely.
Google's own PAT study reports an intriguing combination: around 91–93% of authors rated the feedback very or mostly helpful, but only 56–65% judged it mostly or completely grounded.
That is almost the signature of the review we received.
It is highly useful even though not every criticism is correct.
That sounds paradoxical until one recognizes what a tool like this is good for. It functions less like a judge issuing a ruling and more like a very energetic colleague covering the manuscript in sticky notes.
You investigate the sticky notes.
Some reveal errors.
Some reveal ambiguities.
Some reveal that the reviewer misunderstood you, which may itself mean the text needs clarification.
And some can simply be discarded.
There is also some early independent evidence supporting this picture. In one recent informal evaluation, Deep Review correctly identified a serious pseudoreplication problem in a biomedical study and independently found textual inconsistencies in doses and injection sites. But on another paper it missed image-related concerns raised elsewhere and even stated that the images were consistent with their descriptions.
That is only an anecdotal test, but it mirrors the broader pattern.
Deep Review appears strongest when the evidence for an error is encoded in text, equations, numerical tables, methods or internal consistency. It is less trustworthy when the task requires subtle visual interpretation, domain-specific causal judgment or deciding whether an unconventional scientific choice is actually wrong.
Interestingly, Google's earlier STOC deployment reported the same weakness: users could identify useful insights but also occasional hallucinations, and the system sometimes struggled with figures and complex notation.
Does the review mean the paper is fundamentally flawed?
No.
That would itself be an overreading of the Deep Review report.
The central descriptive result of the paper remains valuable: different LCR algorithms detect strikingly different portions of protein sequence space, and consensus increases compositional simplicity. Deep Review itself recognized the scale, systematic framework, consensus analysis and open-science components as strengths.
But several conclusions need to be disentangled from the operational reference used to derive TPR and FPR.
Several figure interpretations need correcting.
The fLPS default/strict labels need a systematic textual audit.
The consensus-direction and DisProt/PDB contradictions need correction.
The coordinate convention deserves a rerun of analyses that depend on interval extraction and BEDTools.
And some claims in the Abstract and Discussion should be narrowed to what was actually measured.
That is not a collapse of the study. It is what a rigorous post-publication technical audit is supposed to accomplish.
Perhaps the most valuable lesson is about reproducibility
One unexpected benefit of the exercise is that the public code made it possible to adjudicate the AI reviewer.
Without the repository, the 1-based/0-based issue would remain an accusation.
With the code, we can inspect it.
Without the implementation of mutation percentage, we would have to choose between the manuscript and Deep Review's mathematical interpretation.
With the code, we can see that both descriptions miss part of the story.
Open science therefore does more than make a study reproducible. It makes criticism reproducible.
That may become increasingly important as AI-generated reviews become common.
The future scientific conversation may involve three layers:
the paper,
the AI critique,
and the evidence needed to audit the critique.
So, how good was Deep Review on this paper?
My assessment is that this was an impressively high-value review, but it should not be treated as an authoritative peer-review verdict.
Most of its internal-consistency criticisms are valid.
The coordinate issue is both valid and important.
The default-versus-strict fLPS confusion is real.
The contradictory descriptions of consensus trajectories and DisProt/PDB boundaries are real.
Several Jaccard interpretations are demonstrably wrong in the prose.
Its concern about reference-set neutrality is scientifically well founded.
Its call for stronger parameter reporting is reasonable.
Where it becomes less reliable is in assigning consequences. It sometimes treats “this benchmark favors a particular operational definition” as equivalent to “this tool has been unfairly penalized.” The former follows logically; the latter needs an alternative analysis. It sometimes interprets ambiguous methodology in one particular mathematical way and then declares the manuscript wrong for not following that interpretation. And some of its requested additional tools and validation datasets are valuable extensions rather than requirements for the original study.
That distinction matters enormously.
AI review may be most useful before human review, not instead of it
Google describes Deep Review as a tool that handles cognitively expensive verification while leaving higher-level judgments to people. Based on this exercise, that seems like the right division of labor.
A human reviewer should spend precious attention asking:
Is the biological question important?
Does the operational definition make sense for the stated purpose?
Are the conclusions interesting?
What would actually change our understanding of low-complexity protein sequence?
Deep Review can spend its silicon patience checking:
Did Figure 7 actually show what paragraph 3 says?
Is 0.1235 really smaller than 0.099?
Does “1-based BED” make sense with BEDTools?
Did we call the same algorithm conservative on page 8 and less selective on page 9?
Did the Abstract claim a length result that was never plotted?
That is not a small contribution.
It is exactly the sort of painstaking second-pass review that humans are notoriously bad at sustaining across a long technical manuscript.
But the final scientific judgment still belongs to someone who understands what the paper is trying to discover.
A final thought
The most interesting outcome of this experiment is that Deep Review did not simply tell us whether our paper was “good” or “bad.”
It produced testable criticisms.
Some survived immediately.
Some became stronger after inspecting the code.
Some became weaker.
Some exposed deficiencies in the writing rather than the underlying analysis.
And a few turned out to depend on assumptions made by the AI reviewer itself.
That is probably the productive way to think about AI scientific review.
Not as an oracle.
Not as a replacement referee.
Not even necessarily as a referee at all.
It is closer to a tireless adversarial reader with an enormous memory and no embarrassment about checking whether one sentence on page 18 contradicts a caption on page 11.
Used that way, it is extremely useful.
The important rule is simple:
Deep Review should generate the questions. Science still has to determine the answers.