- Rating
- 3(+1)
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper introduces MemHub, a shared latent-memory interface that enables heterogeneous LLMs to exchange persistent memory artifacts without pairwise training. Each model independently trains a Writer–Reader adapter pair against a fixed public anchor. This allows zero-shot cross-model reading and independent onboarding of new models. The authors validate the approach across multiple model families, independently rebuilt hubs, distribution shifts, and downstream tasks.
Critical strengths
-
Independent cross-model interoperability. The fixed-anchor design enables independently trained heterogeneous LLMs to exchange reusable latent memories without pairwise alignment or retraining existing members.
-
Strong experimental and mechanistic validation. The paper's evaluation covers complete directed pairs among nine models, distribution shifts, independent training runs, and alternative anchor configurations. The geometric and functional anchoring ablations and the representation-alignment analysis provide useful insight into why interoperability emerges.
Critical weaknesses
-
Practical advantages over persistent text memory remain insufficiently established. The reported 21–33× latency improvement primarily compares against live text generation, whereas the stored-text results show substantially smaller advantages and occasionally lower first-token latency for text.
-
The generality of reusable memory transfer is not yet fully demonstrated. The strongest results come from partitioned multi-hop QA, while the non-QA experiments require additional Reader training and exhibit larger cross-model performance gaps, particularly on classification and summarization.
Questions for authors
I'm intended to increase my score if below questions are well justified.
-
In Table 1, the Empty baseline already shows a fairly large improvement over Half. How much of the reported 96.1% recovery actually comes from the transferred memory itself?
-
The speedup over live text communication is impressive, but the advantage over re-reading stored text seems much smaller. Would MemHub still have a clear advantage over storing a short text summary in advance?
-
Most of the main experiments focus on multi-hop QA with split contexts. How well would MemHub work when the same stored memory needs to answer different questions or preserve more detailed information?
Dear Reviewers, This is a gentle reminder that the discussion deadlines are approaching. Please make sure to engage with the authors and address any outstanding questions or concerns before the discussion period closes. Best regards, AC