- Rating
- 1
- Confidence
- 2
- Informativeness
- 1
- Presentation
- 1
- Soundness
- 1
Read review
Paper summary
If I understand correctly, this paper proposes REGAP, which updates the state and restricts the action set presented to a frozen language agent when execution feedback is delayed or existing evidence becomes invalid. Experiments on ALFWorld and ScienceWorld evaluate task completion and token usage, reporting improvements over several baselines.
Critical strengths
- The high-level ideas introduced in the introduction appear promising, offering the advantage of improving performance without incurring additional LLM calls.
- The evaluation demonstrates statistical significance, with the proposed method consistently outperforming the baselines.
Critical weaknesses
-
This paper, at least in my reading, has not been prepared with sufficient care to be comprehensible to a human reviewer in this field. While the AI Use Statement asserts that the authors reviewed the content after delegating most of the research to AI, key terminology throughout the manuscript deviates noticeably from standard usage in the community, and many sentences lack precision and clarity. Were this confined to isolated passages, such ambiguities could be resolved through the standard author-reviewer discussion. In its current state, however, I believe the paper requires a fundamental rewrite before meaningful technical engagement is possible. The weaknesses outlined below primarily concern readiness, along with a minor reproducibility issue.
-
The relationship between key terminology and established concepts is unclear. The paper introduces “receipt,” “witness,” “certificate,” “closure,” and “frontier” without sufficiently explaining how they differ from execution feedback, dependencies, condition checks, and task progression. In particular, it is unclear what verifiable information a “certificate” provides beyond a schema-based exclusion indicator.
-
Core operations are insufficiently specified. Section 4 and Algorithm 1 leave receipt recognition, evidence closure, and phase/frontier updates as abstract functions and descriptions, making it difficult to reconstruct the actual procedure. Expressions such as “faithful recognizer” and “current type-consistent closure” describe required correctness properties without adequately specifying the rules that establish them.
-
Several key sentences have ambiguous operational meanings. For example, Section 4.1 states that “A resolved receipt is serialized to its pending request” and that “Destination-sensitive parsing gives terminal destinations precedence over source modifiers,” without concretely explaining request-response matching or parsing precedence. These statements concern implementation-critical behavior, but their inputs, outputs, and applicability conditions remain unclear.
-
The Reproducibility Statement references an anonymous supplement; however, no supplementary material was submitted.
Questions for authors
See weaknesses.