- Rating
- 1
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
This paper presents SlideTrace, a memory framework for cross-project slide personalization. It represents user feedback as structured preference claims with explicit scope, relations, lifecycle states, and supporting evidence. The framework maintains project-level working memory and consolidates selected preferences into long-term memory for reuse in subsequent projects. Experiments with synthetic personas show improved requirement realization and overall scores compared with several memory baselines.
Critical strengths
The paper addresses a meaningful problem: retaining reusable user preferences across projects while preventing temporary or outdated feedback from influencing future generation. Its explicit separation of preference content, applicability, and lifecycle state provides a reasonable approach to this problem.
Critical weaknesses
-
The technical contribution beyond existing personalized memory systems is limited. MemSlides already maintains persistent user profiles, project-level working memory, preference routing, conflict handling, and cross-project consolidation. The main difference in SlideTrace therefore appears to be its more explicit representation and governance of preference claims, rather than the overall memory architecture. While this is a reasonable extension, the paper does not sufficiently establish which additional capabilities it enables or why existing consolidation mechanisms are inadequate. The Append-Only ablation in Table 3 provides some supporting evidence, but it does not directly evaluate the correctness or necessity of individual relation-governed updates.
-
The evaluation does not directly validate the claimed ability to manage evolving and conflicting preferences. A central motivation is that preferences may be refined, contradicted, restricted to particular scopes, or replaced over time. However, the evaluation mainly uses synthetic personas with a fixed preference applicability map and does not separately test these forms of preference evolution. The paper also reports little difference when removing the evidence gate or using the No-Scope variant. Moreover, Section 4.3 describes No-Scope as a generation-time variant constructed from the original frozen store, leaving unclear whether it actually removes scope governance during memory construction and retrieval. Consequently, the experiments do not establish how reliably the proposed system handles the preference-management cases that motivate its design.
-
Table 2 shows that only 23 of 180 held-out requirement slots are matched to claims retrieved and exposed during generation. Although 22 of these 23 requirements are satisfied according to both evaluators, the comparison with non-exposed requirements is observational and subject to selection effects, as the authors acknowledge. The overall score improvements are encouraging, but the analysis does not clearly establish how much of the gain results from explicitly transferred preferences. The small five-task ablation also limits confidence in the relative contributions of the proposed components.
-
The baseline memory states and computational costs require further clarification. In Appendix E, Figure 13 reports 88 active long-term claims for SlideTrace but only 6 active entries for MemSlides, with 83 additional entries marked as superseded. Although these lifecycle labels may have different meanings across systems, the substantial difference raises questions about the effective memory available to each method. Similar total store sizes alone do not establish comparable usable memory. Furthermore, the efficiency analysis in Figure 2 measures memory tokens injected into generation but does not account for the full cost of semantic analysis, verification, and memory updates. These details are important for interpreting both the performance improvements and the claimed efficiency benefits.
Questions for authors
-
What specific preference-update capabilities does SlideTrace provide beyond the profile reconciliation and consolidation mechanisms in MemSlides? Can the authors provide concrete examples of relation-governed updates that existing methods fail to handle?
-
How accurately does SlideTrace identify contradictions, exceptions, temporal updates, and preference scopes? Does the benchmark contain explicit cases that test these operations? In the No-Scope ablation, are scope assignment and retrieval filtering also disabled?
-
Can the authors quantify the contribution of explicitly transferred preferences through a matched removal experiment on held-out tasks? How sensitive are the transfer-trace results to the heuristic claim-matching procedure in Appendix B?
-
Why does the adapted MemSlides baseline retain only 6 active entries after training? How do these states affect retrieval, and what are the total memory-management costs across the compared systems?