- Rating
- 1
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
The paper proposes µWM, a hand-designed compact memory for wearable assistants that stores typed state instead of raw event logs: per-entity counters, first/latest timestamps, action/place conditional tables, a weighted temporal coreset, and a dormant tier, all packed into a fixed byte layout under a nominal 16 KiB cap. Queries are answered by deterministic readers, and a "query-loss" heuristic drives which precision to shed when the budget is exceeded. The engineering is unusually concrete — field widths are specified to the byte (Tables 6–7), update procedures are given as pseudocode, and the evaluation protocol uses a frozen design/confirmation split with paired, video-clustered bootstrap intervals. This is the paper's real strength: it is a careful systems measurement paper.
Critical strengths
S1: The protocol discipline is better than the norm for this sub-area. S2: Byte accounting is auditable. S3: Negative and inconvenient results are disclosed. S4: The costs of the alternative are measured, not asserted.
Critical weaknesses
The problem is that the paper does not present itself as a systems measurement paper. It presents itself as a new memory paradigm ("world memory", "theoretical boundaries", "first wearable world memory") whose empirical claims are stronger than the evidence. Three examples, all checkable inside the paper. First, Section 1 states µWM matches "the fidelity of recent memory systems requiring over 122.6× larger storage", yet Table 2 reports those systems at 100.00% and µWM at 86.90%. Second, no published memory system is ever run at µWM's budget; the "equal-budget control" is the authors' own joint table, allocated only four cells at 13.35 KiB — an allocation no competent engineer would defend as the best use of 13 KiB. Third, the accuracy numbers that anchor the abstract are produced with Qwen2.5-VL-7B in the loop, while the paper's selling point is deterministic on-device readers with no language model.
Beyond framing, there is a scale problem. The motivating scenario is a wearable running for weeks; the longest stream evaluated is 21,594 events (roughly six hours at one event per second), and the only "long-horizon" test is a synthetic 32× tiling of ≤1.3k-event ALFRED trajectories over a 29-noun vocabulary that fits entirely in the 64-slot state. In that test the memory never has to evict anything, so "full accuracy" is a property of arithmetic, not of memory design. Meanwhile the deployed footprint on hardware is 33–46 KiB, not the 16 KiB the paper keeps claiming, on a 320 KiB-SRAM Cortex-M7 that is five times larger than every wearable in Table 1.
Questions for authors
- In Table 2, SeCom/A-Mem/HippoRAG 2 are at 100.00% and µWM at 86.90%. What precisely does "matching the fidelity of recent memory systems requiring over 122.6× larger storage" (Section 1) mean given that table?
- Why does the 13.35 KiB joint table allocate only 2–4 cells, and why do the 2-cell and 4-cell variants consume identical bytes? How many (action, place) records fit in 13,670 bytes at your record width, and what accuracy does that configuration reach?
- Which numbers in the paper are produced by deterministic readers alone, and which require Qwen2.5-VL-7B? Please give the reader-only column for all fourteen families.
- In the 32× ALFRED experiment, how many distinct nouns and distinct (action, place) conjunctions appear, and does the state ever demote, merge, or evict? If not, what does the experiment test beyond Proposition 1?
- What is the operational definition of F_S(t) in the allocation loss? What does the device compare against when no raw log exists?
- Which budget is the paper's design point — 13.38 KiB, 16 KiB, 28.3 KiB, or 33–46 KiB? What would the system look like on a 64 KB-SRAM device with no DTCM?
- What event rate and measurement method produced 153–173 mW, and what is the energy per ingested event compared with buffering events to flash?
- Where does the 3.1-second mean duration come from, and was it estimated on data that overlaps the evaluation set?