- Rating
- 3
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
STAMP learns a cross-session interface for the existing recurrent states of frozen Qwen3.5 backbones. Learned write tokens and write-only LoRA prepare the terminal state, a low-rank carrier maps it to the next session's initializer, and norm-controlled carry supports repeated updates. Source context and attention KV caches are removed before answering. On the static evaluation, macro F1 improves over backbone-matched Metis by 6.15 points at 4B and 12.19 points at 27B. The paper also reports 2/4/8-write trajectories, ten-segment component and geometry diagnostics, multi-state reading, and post-write SVD compression. The reported results establish state-only memory construction from supplied relevant evidence more directly than retention of complete interaction histories for unknown future questions.
Critical strengths
S1. A concrete adaptation interface that reuses the backbone's own recurrent states. Unlike the dedicated memory pathway of Metis, STAMP writes into and reads from the existing recurrent matrices of a frozen backbone, and under source-excluded answering it improves macro F1 over backbone-matched Metis at both scales (+6.15 at 4B, +12.19 at 27B). This is a potentially useful, low-footprint way to make native state persist across independent calls.
S2. Candid disclosure of the evaluation's limits. The paper states gold-evidence conditioning, overlap between evaluation suites, growing LoCoMo endpoint question sets, repeated-write interference, and the storage/compression trade-off. Together with retrained ablations and carrier-only results, this makes the evidence easy to scope correctly.
Critical weaknesses
W1. The main evidence does not cover complete interaction memory, and retention is not separated from acquisition. Section 5 and Appendix B reset memory per LoCoMo question and write its annotated evidence sessions; LongMemEval merges each question's gold evidence into a packet. This is a valid memory-construction setting, not a leakage allegation, but the future question has already determined which history must be stored. The 2/4/8-write trajectories and ten-segment diagnostics still do not evaluate writing an entire conversation once and answering previously unknown queries. In Table 3, STAMP-27B LongMemEval F1 falls from 29.55 after two writes to 15.82 after eight, below Metis-27B's 17.33; at 4B the eight-write scores are 13.29 versus 17.24. Gains on three of four suites do not establish uniformly stronger long-term retention, and LoCoMo's growing endpoint question sets are a confound the authors acknowledge. Either a bounded complete-history evaluation with an unchanged fact set and age-stratified retention is needed, or the abstract and conclusions should be narrowed to supplied-evidence compression and recall.
W2. Architectural and resource advantages, and the carrier/stabilization mechanism, are not isolated. The Aux.=0 column excludes STAMP's 48/144 MiB native states (disclosed in the caption), so total persistent bytes should be shown; the 16-soft-token baseline uses only 0.078 MiB and is not capacity-matched. Metis checkpoints, training data, supervision and tuning budgets are not documented, and there is no direct state-carry or simple normalization/scaling baseline trained with the same QA supervision. Appendix C.1 removes deployment stabilization together with the transformation, so the carrier's own contribution is not separable; default SLERP is not the best setting in Figure 4, and Table 7's static PersonalMem carrier-only score (18.61) exceeds the full model's (17.01). Eq. 11 states an intent to preserve general capabilities, but no memory-on/off general-task results or preservation-loss ablation are reported.
Questions for authors
- How much does performance change when the complete conversation is written once and all subsequent questions are answered, compared with gold-evidence conditioning? If this cannot be run, will the abstract be narrowed to supplied-evidence recall?
- What are the results for simple state carry/normalization and for Metis under matched QA training, total persistent state bytes, and write/read budgets?
- What remains of the carrier's benefit once stabilization is separated, and how sensitive are age-stratified retention and later writes to the first state's norm?
- Does the KL preservation loss (Eq. 11) measurably protect general capabilities, and how much memory-induced behavioral drift remains?
Thank you for your clarification and additional experiments. Your new results help address many of my concerns. However, I still think the design choices—in particular, the role and effect of each component (native recurrent state, learned write, and adapter)—are not well validated/clarified due to insufficient controlled comparisons. I hope this can be more thoroughly justified in the revision.
Overall, I believe the strengths outweigh the weaknesses, so I will raise my score to Weak Accept.