A Hippocampus for Linear Attention: An Exact Memory for What the Recurrent State Forgets
Abstract: Linear-attention and state-space LLMs compress the prefix into a fixed-size recurrent state, yielding O(1) memory at the cost of a lossy exact memory: when many key--value associations compete, earlier facts are overwritten and needle recall degrades. Inspired by Complementary Learning Systems, we give linear attention a hippocampal complement. HOLA (Hippocampal Linear Attention) keeps the usual delta-rule state as a compressive memory and adds a bounded exact KV cache, forming a semiparametric test-time memory: the state models linearly compressible structure, while the cache stores associations that should not be forced through that state. The cache writes without a learned eviction module, keeping tokens with large beta * ||e||, the prediction residual actually committed to the state; a decoupled RMSNorm-gamma cache read then turns these exact KV pairs into sharp retrieval rather than soft averaging. At 340M parameters trained on 15B SlimPajama tokens, HOLA lowers Wikitext perplexity from 27.32 to 22.92 (-16.1%), below a full-attention Transformer++ (26.88), and improves LAMBADA perplexity from 30.95 to 30.26. It also achieves the best linear in-context retrieval and remains much more robust than GDN or a matched HOLA+recency cache on RULER needle-in-a-haystack recall out to 32k tokens (16x its training length).
Paper Prompts
Sign up for free to create and run prompts on this paper using GPT-5.
Top Community Prompts
Explain it Like I'm 14
Overview
This paper introduces HOLA, a new way to give fast LLMs a better memory. It’s inspired by how the human brain uses two kinds of memory: the neocortex (good at learning general patterns) and the hippocampus (good at storing exact details of specific events). Many efficient LLMs act like the neocortex: they compress everything into a small “state” for speed, but they forget exact facts when there’s a lot to remember. HOLA adds a small, smart “hippocampus-like” memory on top, so the model can keep and precisely recall the most important facts without slowing down much.
Objectives
In simple terms, the paper asks:
- Can we keep the speed and low memory use of linear-attention models while fixing their habit of forgetting exact details?
- Which tokens (pieces of text) should the model store exactly, and how should it look them up later?
- Can this be done with tiny overhead but big gains in performance, especially for long documents?
How HOLA works (with easy analogies)
Think of the model as a student reading a long textbook.
- The student has a small notebook (the “state”) where they summarize what they’ve read. It’s great for patterns and themes, but it can’t hold every detail. Over time, earlier details get overwritten by newer ones.
- HOLA gives the student a small pack of sticky notes (the “exact cache”). The student uses these only for the most surprising or important facts that don’t fit well into the summary notebook. Later, when needed, the student can quickly find and copy the exact fact from a sticky note.
Here’s the approach in everyday language:
- Two memories working together
- Compressed state (the notebook): This is the usual linear-attention memory. It’s fast and small, but lossy (you can’t keep every detail).
- Exact cache (the sticky notes): A tiny, bounded set of exact key–value pairs (think “word → meaning,” “name → phone number”). This holds the details that the small state would forget.
- How the model decides what to keep exactly
- The model already computes how “surprised” it is by each new token. Surprise here means: “How much did this new token force me to change my current summary?”
- HOLA measures surprise by the size of the update the model actually wrote into its state. If a token caused a big change, it was hard to predict and likely important—so it gets a sticky note.
- The cache keeps only the top “w” most surprising tokens so far (for example, w = 64), no matter how far back they appeared. This beats simple “keep the most recent tokens,” because important facts might be far away.
- How the model reads from the cache
- If you have exact copies, you should retrieve them sharply, not blend them into a fuzzy average.
- HOLA “sharpens” lookups so the most relevant stored token pops out clearly. Technically, it uses a special normalization (RMSNorm-γ) on the cache path only, which makes the retrieval strong without destabilizing the rest of the model.
- Final output is a mix: “summary from the notebook” + “exact detail from the sticky notes” when needed.
- Why this is stable and efficient
- The exact cache adds only a tiny number of new learned parameters and a small amount of runtime memory.
- The main model keeps its normal, safe update rules, and the cache’s sharpening is carefully separated so things don’t blow up.
Main findings
The authors trained a 340-million-parameter model on 15 billion tokens and found:
- Lower confusion (perplexity): On the Wikitext dataset, HOLA reduced perplexity from 27.32 to 22.92 (a 16.1% drop). Lower is better, and this even beat a full-attention Transformer at the same scale (26.88).
- Better reading of tricky passages: On LAMBADA (a test of predicting words that require long-range understanding), HOLA improved perplexity from 30.95 to 30.26.
- Stronger exact recall from long contexts: On “needle-in-a-haystack” tests (where you must retrieve a distant, specific token), HOLA stayed accurate out to 32,000 tokens—16 times longer than its training context—while the baseline model’s accuracy fell sharply.
- Best in-class “in-context retrieval” among similar fast models: It pulled exact facts from the text more reliably than other linear-attention models and a recency-only cache.
- The gains hold across sizes: Similar improvements were observed at smaller model scales too.
- Small overhead: The cache adds very little memory and almost no extra learned parameters.
Why this matters: Perplexity measures how “confused” a LLM is—lower perplexity means better predictions. Exactly recalling a distant name, number, or fact is crucial for tasks like reading long documents, code, logs, or stories. HOLA excels at this without giving up efficiency.
Implications and impact
- Practical long-context use: HOLA lets efficient models carry exact details across very long texts, which is useful for document analysis, coding assistants, and any task where a specific earlier fact matters.
- A simple, general design idea: Use the model’s own “surprise” signal (how much it had to change its state) to decide what to keep exactly, instead of relying on recency or adding a complex learned eviction module.
- Strong retrieval with tiny cost: A small, smart cache and a sharper lookup path can recover lots of the exact-memory benefits of full attention—without paying the heavy compute and memory costs.
Key terms in plain words
- Linear attention: A faster version of attention that summarizes the past into a fixed-size state. It’s efficient but can forget exact details when there’s a lot to remember.
- State (or recurrent state): The model’s running summary of what it has seen so far.
- Key–value pair (KV): A stored “question → answer” link, like “What is the capital of France?” → “Paris.”
- Cache: A small storage for exact KV pairs. Think sticky notes for facts you can’t afford to lose.
- Surprise (write magnitude): How much a new token forces the model to change its state. Bigger change = more surprising = more likely to be cached.
- Perplexity: A score of how confused the model is when predicting the next word. Lower is better.
- Needle-in-a-haystack: A test where you must find and use one specific detail hidden in a long passage.
Knowledge Gaps
Knowledge gaps, limitations, and open questions
Below is a focused list of what remains missing, uncertain, or unexplored in the paper, written to guide actionable follow-up research.
- Cache capacity and allocation:
- How does performance trade off with cache size across tasks and lengths? Only (and ) are reported; no sweeps or adaptive allocation across layers/heads are explored.
- Should memory be concentrated in specific layers or heads rather than uniformly per layer? No analysis of layer/head-wise utility or cross-layer redundancy is provided.
- Cross-layer coordination is unstudied: the same token may be stored redundantly across multiple layers; deduplication or learned budget sharing is unexplored.
- Selection signal (surprise-based eviction):
- Generality of across domains and data distributions is not tested (only SlimPajama-15B). Does this criterion remain optimal for code, math, or dialog?
- Sensitivity to value scaling: since depends on in value space, tokens with larger value norms may be disproportionately favored. Normalization or head/value re-scaling strategies are not examined.
- Alternatives to beyond simple ablations (e.g., mutual information, expected future usefulness, gradient-based salience, learned selectors beyond LTE’s CNN) remain untested in matched-memory settings.
- Stability under different backbone gates: the interaction of with GDN’s decay gate is not analyzed; large residuals can arise from small rather than true “surprise.”
- Readout and mixing design:
- The mixing coefficient (cache–state interpolation in ) is not fully specified or analyzed (how it is computed, learned, and distributed across tokens/layers; “gate init −4” is mentioned without details).
- The role, necessity, and impact of the per-head sink token and the “cache gate” are not ablated; their effect on stability and false-positive retrieval remains unclear.
- The sharpened read uses RMSNorm- with fixed ; there is no exploration of alternative kernels, temperature schedules, or regularizers to prevent overreliance on cache (beyond a brief note about “lazy state” with high temperature).
- Robustness of the decoupled normalization: while decoupling avoids destabilizing the delta rule, potential training instabilities, gradient scaling effects, and cross-layer calibration issues introduced by RMSNorm- on the cache path are not examined.
- Scope and comparisons:
- Main 340M results are single-seed; variance across seeds and statistical significance are not reported. Multi-seed confirmation at scale is missing.
- No matched-memory comparison against learned eviction modules (e.g., LTE’s CNN) at 340M; hence the claim that suffices over learned selectors remains unverified at this scale.
- Long-context baselines include a RoPE Transformer++ that collapses beyond 2k; comparisons to length-robust full-attention variants (e.g., ALiBi/YaRN/PI/LongRoPE) are absent.
- Generalization to other efficient backbones (e.g., Mamba/Mamba2, GLA/GSA/KDA) is not empirically validated; HOLA is only instantiated on GDN.
- External-memory or retrieval-augmented LMs as alternatives are not compared under the same compute/data budget.
- Task coverage and failure modes:
- Evaluations emphasize perplexity and synthetic retrieval (RULER, FDA, SWDE); effects on real-world long-context tasks (e.g., long-form QA, code completion, multi-hop reasoning, summarization) are not assessed.
- Multi-needle/multi-hop retrieval remains imperfect; certain RULER cells (e.g., MQ, some MV/MK variants) show only modest gains or near-ties. Error analyses and failure typologies are missing.
- Exact extraction gap to full attention persists (e.g., FDA); no targeted methods are proposed to close it (e.g., adaptive , specialized kernels, or hierarchical caches).
- Length generalization and extreme regimes:
- Despite gains up to 32k ( training length), behavior beyond 32k (e.g., 64k–1M contexts) is not tested; bounded cache capacity suggests degradation in extremely long or needle-dense contexts.
- Impact of training with longer contexts on HOLA vs. GDN is unexplored. Would increasing training context reduce HOLA’s relative advantage or expand it?
- Efficiency and systems aspects:
- Throughput and latency benchmarks are not reported. While memory overhead is small (~5%), the compute overhead of per-layer cache reads (softmax over ) and maintenance of top- heaps are not quantified.
- Online/streaming maintenance of global top- at very long lengths may incur additional bookkeeping; practical engineering trade-offs (CPU/GPU placement, sorting frequency, batching) are unaddressed.
- Training protocol and portability:
- It is unclear whether HOLA’s gains require joint training with the cache. Can the cache be attached post hoc to a pretrained GDN with similar benefits?
- Interactions with regularization, optimizer settings, and training stability when the cache is active are not studied (e.g., does the cache change gradient noise or convergence dynamics?).
- Interpretability and analysis:
- No analysis of which tokens are selected by : Are they semantically salient, rare, or structurally important? Cross-task consistency of selected tokens and heads is unreported.
- The frequency and conditions under which the model actually uses the cache (e.g., distribution of across positions) are not analyzed, leaving the complementarity with the state unquantified.
- Theoretical understanding:
- No formal capacity analysis relating cache size , key dimension , and expected recall under realistic key distributions is provided.
- The semiparametric TMR view is descriptive; there are no error bounds, bias–variance analyses, or theoretical guarantees for -based selection and RMSNorm-sharpened read.
- Safety and robustness:
- Adversarial or noisy contexts: the tendency of to select outliers/noise as “surprising” is untested; robustness to perturbations or adversarial distractors is unknown.
- Privacy/security considerations of exact in-sequence storage are not discussed (even if non-persistent, sensitive spans are temporarily cached verbatim).
- Design space not explored:
- Alternative cache organizations (e.g., hierarchical, per-entity/per-topic, learned hash-based grouping) and approximate nearest-neighbor retrieval (for scalable ) are not considered.
- Mechanisms for “consolidation” (CLS-style) from cache back into the state over time are absent; HOLA reads from cache but does not study transferring cached information into during or after sequences.
These gaps suggest concrete next steps: ablate cache size and placement, benchmark throughput, compare against learned eviction at scale, evaluate on long-form and code tasks, analyze cache usage and selected tokens, extend to other backbones, and develop theory linking , , and recall under realistic distributions.
Practical Applications
Overview
The paper introduces HOLA (Hippocampal Linear Attention), a semiparametric memory for linear-attention/state-space LLMs that augments a fixed-size recurrent “state” with a bounded exact key–value (KV) cache. Two core innovations make the cache effective without learned eviction:
- What to store: keep tokens with the largest delta-rule write magnitude (“surprise”), i.e., tokens that changed the recurrent state most.
- How to read: use a decoupled RMSNorm-γ path for the cache only, producing sharp, near-argmax retrieval without destabilizing the recurrent state update.
At 340M parameters trained on 15B tokens, HOLA improves perplexity and long-context recall (e.g., RULER needles up to 32k tokens), with minimal memory and parameter overhead. Below are practical applications derived from these findings.
Immediate Applications
These uses can be prototyped or shipped now with modest engineering effort, especially when a linear-attention/SSM backbone (e.g., GDN/DeltaNet/Mamba-like) is already in place.
- Long-context chat and document assistants with accurate quoting
- Sectors: software, enterprise productivity, customer support
- What: Deploy HOLA-based LMs to handle lengthy chats, contracts, reports, and logs while recalling exact clauses, IDs, or numbers far back in the context.
- Tools/products/workflows: “Long-document analysis” mode for chatbots; enterprise assistants that highlight and cite exact passages.
- Assumptions/dependencies: Linear-attention backbones for drop-in; tune cache size (e.g., w≈64) and γ; apply PII filters since “surprising” tokens may include sensitive data.
- On-device/offline assistants with extended memory under tight resources
- Sectors: mobile, embedded, consumer devices
- What: Run long-context assistants locally with nearly constant memory (≈5% overhead over GDN, ~31 MB exact-KV state in bf16 at 340M) and robust exact recall.
- Tools/products/workflows: E-reader “deep reader,” email digest on phones, offline dictation with robust name recall.
- Assumptions/dependencies: Linear/SSM model availability for device; cache lifecycle management; careful energy/performance benchmarking.
- Legal and financial document review with precise clause/figure retrieval
- Sectors: legal tech, finance, compliance
- What: Improve precision when extracting or cross-referencing critical terms, thresholds, and dates in long contracts, prospectuses, or filings.
- Tools/products/workflows: Contract clause locator, prospectus checker, redlining assistants that verify exact wording across hundreds of pages.
- Assumptions/dependencies: Evaluate cache capacity under “needle-dense” documents; add audit trails and cite-exact outputs.
- Software engineering copilots that track definitions across large codebases
- Sectors: developer tools
- What: Better recall of distant definitions (APIs, constants, error codes) across multiple files without quadratic memory/compute.
- Tools/products/workflows: IDE plugins using HOLA for open-file contexts; precise jump-to-definition and refactoring suggestions.
- Assumptions/dependencies: Integrate with linear-attention inference servers; tune “surprise” score to retain unique signatures over boilerplate.
- Structured data extraction from long webpages and multi-document bundles
- Sectors: data engineering, web scraping, enterprise search
- What: Improve exact field extraction (e.g., SWDE/FDA-like tasks) in long DOMs or concatenated documents.
- Tools/products/workflows: KV-extraction pipelines with bounded KV caches; validation-by-citation for extracted values.
- Assumptions/dependencies: Cache window/eviction thresholds tuned to page structure; fallback strategies for highly repetitive pages.
- Observability and security log analysis with exact token recall
- Sectors: DevOps, SecOps
- What: Identify and recall exact log lines (hashes, request IDs) buried far back in long streams.
- Tools/products/workflows: HOLA-backed log copilots that can cite the exact originating event; anomaly triage dashboards.
- Assumptions/dependencies: Stream ingestion adapted to blockwise processing with HOLA’s bounded cache; controls to avoid caching secrets.
- Meeting and call transcription assistants with accurate reference retrieval
- Sectors: CX, sales, support
- What: Accurately recall customer IDs, commitments, and action items in multi-hour transcripts.
- Tools/products/workflows: Real-time summarizers that maintain a small “episodic” memory of critical facts; follow-up email generation with verified details.
- Assumptions/dependencies: PII redaction on cache write/read; evaluation of recall vs. window size for long sessions.
- Surprise-driven anomaly flagging in streaming text or multimodal pipelines
- Sectors: operations monitoring, risk
- What: Use the model’s intrinsic (“surprise”) as a lightweight outlier signal to flag tokens/events the recurrent state could not predict.
- Tools/products/workflows: Event-driven alerts when spikes; human-in-the-loop queues.
- Assumptions/dependencies: Calibrate thresholds; false-positive/negative management; domain shift monitoring.
- Academic baselines and diagnostics for efficient-memory modeling
- Sectors: academia, ML R&D
- What: Use HOLA as a baseline for semiparametric test-time memory (state + bounded exact-KV), and as a principled selection signal.
- Tools/products/workflows: Reproducible benchmarks (RULER, passkey), ablations, and teaching materials on CLS-inspired memory architectures.
- Assumptions/dependencies: Open-source implementations; compatibility with linear/SSM labs; standard evaluation protocols.
Long-Term Applications
These opportunities require further research, scaling, and/or systems integration beyond the paper’s 46M–340M experiments.
- Foundation-scale adoption for long-context assistants
- Sectors: cloud AI platforms, enterprise AI
- What: Integrate HOLA into 7B–70B+ models to achieve near-constant-memory long-context inference with strong exact recall.
- Tools/products/workflows: Foundation models offering “Hippocampal mode” for long docs/calls.
- Assumptions/dependencies: Validate scaling behavior at larger sizes and training corpora; tune cache policy for diverse domains; evaluate latency/throughput on multi-GPU inference.
- Persistent and cross-session semiparametric memory
- Sectors: enterprise knowledge management, personal assistants
- What: Extend HOLA with a durable datastore (RETRO/kNN-LM style) to keep exact associations across sessions while maintaining a bounded in-session hippocampal cache.
- Tools/products/workflows: Memory managers that split persistent vs. ephemeral entries, with indexing and TTLs.
- Assumptions/dependencies: Data governance (consent, retention, deletion); PII/security; efficient retrieval infrastructure; learned or hybrid eviction for persistent stores.
- Multimodal “episodic memory” for video, speech, and robotics
- Sectors: autonomous systems, media AI
- What: Apply surprise-driven exact memory to rare audio words, frames, or sensor events requiring precise recall in long sequences (e.g., long-horizon plans).
- Tools/products/workflows: Real-time captioners that remember rare named entities; robots that preserve critical waypoints or instructions.
- Assumptions/dependencies: Adapt to modality-specific states; real-time constraints; safety validation for downstream control.
- Learned-eviction hybrids and adaptive memory budgets
- Sectors: ML infrastructure
- What: Combine with learned eviction (e.g., LTE-like modules) or task-aware priors; dynamically adjust cache size given resource/utilization and task difficulty.
- Tools/products/workflows: Memory controllers that trade throughput vs. recall under SLAs; APIs to expose cache telemetry.
- Assumptions/dependencies: Additional training and inference complexity; careful stability/overfitting checks.
- Compliance-grade assistants for regulated domains
- Sectors: healthcare, finance, legal
- What: Use bounded exact memory to verify, cite, and audit critical facts (e.g., allergies, dosages, covenant thresholds) across long records.
- Tools/products/workflows: “Cite-to-source” outputs with memory provenance; automated checklists with exact-value validation.
- Assumptions/dependencies: HIPAA/GDPR compliance; redaction/consent-aware caching; formal evaluation on domain datasets; harm mitigation for mis-retrieval.
- Energy- and cost-efficient long-context AI standards
- Sectors: policy, sustainability, procurement
- What: Promote sub-quadratic, bounded-memory architectures (like HOLA) for greener long-context inference in public-sector and enterprise RFPs.
- Tools/products/workflows: Benchmarking guidelines for energy per token vs. context length; procurement checklists referencing semiparametric memory.
- Assumptions/dependencies: Transparent reporting of energy/latency; independent benchmarks; alignment with regulatory frameworks.
- OS/hardware support for “hippocampal caches”
- Sectors: systems, accelerators
- What: Provide runtime primitives to manage small, fast KV stores per layer/head, with efficient eviction and inter-block scheduling.
- Tools/products/workflows: CUDA kernels / accelerator firmware optimized for bounded, frequent KV updates; memory pinning and persistence across blocks.
- Assumptions/dependencies: Vendor support; generalized APIs across model families; measurable end-to-end gains.
- Education and assessment on long materials
- Sectors: edtech
- What: Grade long essays or open-book tasks by recalling and verifying exact references in large reading packs.
- Tools/products/workflows: Tutors that track students’ earlier answers and cite exact prior work; proctoring aids that verify quotes.
- Assumptions/dependencies: Fairness and bias audits; pedagogy-aligned rubric design; robust anti-hallucination checks.
Cross-Cutting Assumptions and Dependencies
- Model backbone: HOLA is most natural for delta-rule linear-attention/state-space models (e.g., GDN/DeltaNet). Porting to vanilla Transformers would require architectural adaptation.
- Cache limits: The bounded cache (e.g., w≈64) cannot store all relevant items in very long or needle-dense contexts; some tasks may still favor full attention or external retrieval.
- Stability: Decoupled RMSNorm-γ is critical; applying large norms to the recurrent path destabilizes the delta-rule update.
- Privacy/security: Surprise-based selection may prioritize rare PII (names, IDs). Production systems need cache write/read filters, encryption, TTLs, and audit trails.
- Generalization: Reported gains are validated up to 340M parameters and 32k tokens; additional evidence is needed at larger scales and in specialized domains.
- Evaluation: Benefits are strongest on exact recall and long-context tasks; commonsense benchmarks show parity with strong baselines, not clear superiority.
Glossary
- argmax retrieval: Retrieving the single highest-scoring item rather than averaging over many. "This restores sharp, near-argmax retrieval while preserving the unit-norm keys required for the delta rule's stable state update."
- associative memory: A memory that stores key→value associations to enable retrieval by key. "an online associative memory"
- associative recall: The task of recalling multiple stored associations, often stressing memory capacity. "multi-item associative recall"
- bf16 decoding: Using the bfloat16 numeric format during decoding/inference for memory efficiency. "in bf16 decoding it stores at most"
- Complementary Learning Systems (CLS): A theory positing separate fast episodic (hippocampal) and slow statistical (neocortical) learning systems. "Complementary Learning Systems (CLS) theory~\citep{mcclelland1995cls,kumaran2016cls} argues that the two must be separate"
- delta rule: An online learning rule that updates parameters by writing the prediction residual (error). "the delta rule updates by ``predict, then write the residual'':"
- eviction score: A priority measure used to decide which cached items to keep or discard. "We use this intrinsic write magnitude as the cache's eviction score, retaining tokens that changed the state most rather than tokens that are merely recent."
- exact KV pairs: Uncompressed, verbatim key–value pairs stored for precise retrieval. "a bounded set of exact KV pairs"
- Frobenius norm: A matrix norm equal to the square root of the sum of squares of all entries. "for a rank-1 matrix the Frobenius norm factorizes"
- Gated DeltaNet (GDN): A linear-attention/state-space backbone that augments DeltaNet with a data-dependent decay gate. "Gated DeltaNet (GDN) strengthens DeltaNet with data-dependent decay"
- hippocampal complement: An added exact, episodic memory module analogous to the brain’s hippocampus. "give linear attention a hippocampal complement."
- innovation (Kalman): The residual between observation and prediction in Kalman filtering, used here as the surprise/error signal. "the innovation in the Kalman~\citep{kalman1960} sense"
- kernel estimator (Nadaraya–Watson): A non-parametric regression method that averages targets weighted by a kernel on inputs. "a Nadaraya--Watson kernel estimator"
- key–value cache (KV cache): A store of keys and values used by attention mechanisms to retrieve past context. "replace softmax attention's growing key--value cache with a fixed-size recurrent state "
- L2-normalization: Scaling a vector to have unit Euclidean (L2) norm. "with L2-normalized to unit norm"
- LAMBADA: A benchmark for long-range language modeling and cloze-style prediction. "and improves LAMBADA perplexity from $30.95$ to $30.26$."
- linear attention: An attention mechanism with linear-time/memory complexity via a fixed-size recurrent state. "Linear attention is precisely such a ``neocortex'': a superb compressor, but a leaky exact memory."
- LMS (Widrow–Hoff): The Least Mean Squares learning rule, closely related to the delta rule. "the Widrow--Hoff/LMS rule~\citep{widrow1960}"
- m_t (write magnitude): The scalar size of the committed residual update; used as a surprise signal for caching. "What to store: the write magnitude $$ is ``surprise''"</li> <li><strong>neocortex (analogy)</strong>: The generalizing, compressive component contrasted with exact episodic memory. "Linear attention is precisely such a ``neocortex'': a superb compressor, but a leaky exact memory."</li> <li><strong>needle-in-a-haystack (NIAH)</strong>: Long-context retrieval tasks requiring exact recall of a specific distant item. "needle-in-a-haystack recall out to 32k tokens"</li> <li><strong>non-parametric estimator</strong>: A model that relies directly on stored data points rather than a fixed set of parameters. "full attention is an unbounded non-parametric estimator over all prefix tokens"</li> <li><strong>parametric estimator</strong>: A model summarized by a fixed set of parameters (e.g., a recurrent state) rather than stored examples. "pure GDN is the parametric estimator $q S_t$"</li> <li><strong>perplexity</strong>: A standard measure of language-model uncertainty; lower is better. "lowers Wikitext perplexity from $27.3222.92-16.1\%$)"</li> <li><strong>rank-1 update</strong>: An update that adds an outer product of two vectors, changing matrix rank by at most one. "(\text{rank-1})"</li> <li><strong>RMSNorm-γ</strong>: Root Mean Square normalization with a learnable scale parameter γ. "A simple fix is to use Qwen3-style RMSNorm-$\gamma$ \citep{yang2025qwen3} on the cache path only"</li> <li><strong>RoPE (Rotary Positional Embeddings)</strong>: A positional encoding method enabling rotation-based relative positions. "this RoPE checkpoint is not a length-extrapolating baseline"</li> <li><strong>RULER</strong>: A benchmark suite for evaluating long-context capabilities and retrieval. "We evaluate on the official RULER benchmark \citep{hsieh2024ruler}"</li> <li><strong>selective forgetting</strong>: Controlled decay of the recurrent state to forget older information. "adds a data-dependent decay gate $\alpha_t\in(0,1]$ (selective forgetting)"</li> <li><strong>semiparametric test-time memory regression</strong>: A framework combining a parametric state with a bounded non-parametric memory at inference time. "We formalize this complement as semiparametric test-time memory regression"</li> <li><strong>softmax attention</strong>: Standard attention that weights values by a softmax over dot-product logits, retaining all tokens. "full softmax attention --- which keeps every token exactly, at $O(T)O(T^2)$ compute --- remains the gold standard."</li> <li><strong>state-space models (SSMs)</strong>: Sequence models that evolve hidden states via linear dynamical systems. "state-space models \citep{gu2023mamba,dao2024mamba2}"</li> <li><strong>temperature (softmax)</strong>: A factor controlling the sharpness of softmax distributions. "fix $\tau{=}1$"</li> <li><strong>test-time memory regression (TMR)</strong>: Formalization of memory read/write as estimating a mapping from queries to values during inference. "Definition 1 (test-time memory regression)."</li> <li><strong>unit-L2 normalization</strong>: Ensuring vectors have unit L2 norm for stability in state updates. "the $q,kS$ remain unit-L2-normalized."</li> <li><strong>write strength β_t</strong>: A gating coefficient determining how strongly a token updates the state. "write strength $\beta_t\in[0,1]$"
- teacher forcing: Feeding ground-truth tokens during evaluation/training to probe behaviors. "teacher-force the answer tokens after the query"
Collections
Sign up for free to add this paper to one or more collections.