- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper investigates Dynamic Residual Decay (DRD), a phenomenon in which historical information continues to influence multi-agent decisions even after its positive utility for the current task has declined. To address this issue, the authors propose the Cross-Lifecycle Graph (CLG), which combines forward invalidation propagation and backward demand tracing to identify dependencies requiring recomputation while preserving reusable historical information. The paper evaluates DRD across four models and three benchmarks, including TravelPlanner, ScienceWorld, and MARBLE. End-to-end recovery experiments show that CLG achieves a task-normalized utility of 0.9781, compared with 0.9485 for Global Rerun, while reducing model calls by 39.79%, token consumption by 29.95%, and execution time by 33.86%. Additional experiments examine the effects of task drift, dependency quality, and demand scope on recovery performance.
Critical strengths
- Meaningful problem formulation. The paper identifies the mismatch between historical influence and current-task utility in dynamic multi-agent systems, offering a useful perspective on information reuse.
- Promising efficiency improvements. CLG combines forward invalidation and backward demand tracing to avoid unnecessary recomputation, achieving substantial reductions in model calls, tokens, and execution time.
Critical weaknesses
- Limited methodological novelty. CLG mainly relies on established graph reachability and dependency-slicing techniques. Its distinction from conventional demand-aware incremental computation is insufficiently demonstrated.
- Limited robustness and generalizability. End-to-end experiments cover only two models, with inconsistent utility improvements. Recovery performance also deteriorates substantially under incomplete dependency records.
Questions for authors
Q1. What is the key algorithmic novelty of CLG compared with conventional demand-aware incremental computation? Q2. How does CLG ensure reliable recovery when dependency records are incomplete or inaccurate? Q3. Why is end-to-end evaluation limited to two models, and what explains the performance degradation on MARBLE–GLM? Q4. Are graph construction and dependency-tracking overhead included in the reported efficiency results, and can actual energy savings be quantified? Q5. How well do the constructed cross-lifecycle task sequences represent naturally evolving, long-running multi-agent workflows?