- Rating
- 1
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 1
- Soundness
- 1
Read review
Paper summary
The paper studies provenance tracking for persistent-memory LLM agents using model-declared parent identifiers. It compares global write blocking, exposure-based blocking, and lineage-based blocking across synthetic tasks. While lineage-based filtering preserves more writes, the main operational evaluation shows little meaningful improvement. A separate controlled-reuse experiment reports large gains when relevant memory is explicitly retained and retrieved.
Critical strengths
The paper makes a useful distinction between memory exposure, recorded ancestry, and downstream behavior. The attempt to evaluate these stages separately is understandable, and the experiments include controlled comparisons and a content ablation.
Critical weaknesses
In general, the paper is extremely difficult to read. I feel this is a more like an ai-generated tech report, than a research paper, there is no clear research gap, research contribution, and the paper presentation needs significant improvements.
The main mechanism is essentially provenance tracking through explicitly declared parent IDs. The proposed policy ordering follows directly from the definitions, and it is unclear what substantial technical contribution is made beyond existing provenance and information-flow tracking approaches.
Both studies also lack descriptions and hard to follow. Study 2, the more natural operational evaluation, shows little improvement in task success or invalid-event rates. The large gains in Study 3 come from a constructed setting where one policy retains a task-relevant record, the other removes it, and the agent is subsequently required to use that information. This demonstrates the benefit of retaining useful information, but provides limited evidence that the proposed approach improves realistic persistent-memory agents.
Questions for authors
- What is the technical novelty over existing provenance tracking and lineage-based enforcement methods such as MemLineage?
- Why should Study 3 be considered evidence of practical utility when the downstream task is explicitly constructed to depend on the record preserved by one policy?
- How would the approach handle incomplete or incorrect parent declarations, especially when an agent incorporates information without reporting its source?