In this analysis
Document-level confidence is hard to investigate; claim-level findings let a reader inspect the evidence and decide which part of an argument needs revision.
The Deep Review release raises a useful design question for automated checking: what should a review finding point to? A broad verdict on a document is less actionable than an inspectable relationship between a claim and the evidence offered for it.
The dated path
-
2026-01-14: ICML Paper Assistant Tool pilot.
-
2026-06-26: Towards Automating Scientific Review with Google’s Paper Assistant Tool.
-
2026-10-14: Google publicly releases Deep Review.
The document is a container, not a single proposition
A technical report can contain correct observations, unsupported conclusions and ambiguous definitions at the same time. Treating the whole report as one confidence-bearing object obscures this structure. Our retrospective argument is that useful review assistance needs a finer unit of attention. A finding should identify the claim being questioned, the relevant passage and the reason the available support may be insufficient. That makes the criticism separable from the reviewer’s overall impression of the writing.
Evidence links make disagreement productive
An author can respond differently to a missing premise, a numerical inconsistency and an unsupported generalization. A vague request to improve rigor does not expose those alternatives. Linking a finding to its evidence lets both sides investigate the same object. The generated finding still needs checking, but the work becomes bounded. This is a proposed design principle inferred from the review problem, not a claim that the public tool guarantees every form of claim extraction or evidence verification discussed here.
A counterfactual with the same conclusion
Imagine two reviews both saying that a result is insufficiently supported. One gives only the verdict; the other identifies the dependency between an assumption and a conclusion. Ask independent readers to determine whether the criticism is valid and what revision would address it. The second format can be more useful even when both reviews reach the same headline judgment. The relevant measure is whether a reader can verify and act on the finding without reconstructing the entire document from scratch.
Why versioning becomes part of review quality
A claim can move or change when an author revises a manuscript. A finding therefore needs a connection to the draft it examined, not merely a page number detached from history. Infrastructure should preserve that connection through exports and collaborative workflows. The earlier PAT pilots and later public release form context for this need, while not proving that automated feedback replaces scientific judgment. The historical lesson is that a useful review system organizes inspectable disagreements. It should make the path from criticism to evidence clearer rather than hide that path behind a document-wide score.
Technical background
Related engineering context: Document boundaries; Evidence metrics.