- Rating
- 1
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 1
- Soundness
- 1
Read review
Paper summary
This paper proposes ContractFlow, a framework that converts agents’ past task-execution experiences into reusable executable contracts organized as a control graph. Each contract specifies prerequisites, runtime variables, tool actions, and completion criteria, while the graph coordinates dependencies and failure recovery. Execution feedback is used to update relevant contracts and graph relations for subsequent tasks. Experiments on APOLLO, CROSSEP-TOOL, and MemoryArena report improvements over existing experience-memory baselines.
Critical strengths
None
Critical weaknesses
- The paper lacks critical citations. For example, I had never heard of APOLLO or CROSSEP-TOOL, which the authors use, and could not find them through a search. The paper provides no corresponding citations either. The entire paper has only 15 references.
- The overall idea is very similar to prior work, such as AWM and GraphMind: abstracting experience into workflows and updating them after execution. The proposed method is essentially a complex workflow incorporating multiple mechanisms, but the contribution of each mechanism is unclear. I consider the overall novelty and contribution to be rather limited.
- The benchmarks used by the authors have obvious, major problems, making the experimental results unreliable. Shouldn’t they at least use benchmarks such as τ-bench, BFCL, and AutomationBench?
Questions for authors
None