Memory & Retrieval•Study date: September 28, 2026•Printable brief ↗Living Paper

Published by Sean Carr

Semantic Memory Living Paper: An Empirical Synthesis Across Session Memory Evaluations

A synthesis of eight session-memory question sets, diagnostic reanalyses and planner reruns: structured event extraction, retrieval anchoring, sealed holdouts with source-access limitations, and zero-token deterministic routing.

Where this shows up in MeshTen: selfmem, our engineering agent memory system powering multi-session continuity and deterministic query routing.
Executive Brief

At a Glance

LongMemEval Token Drop

82.8% Fewer Tokens

On 100 questions over ~115k-token histories, structured events matched full context (88/100) using 19.5k vs 113.6k tokens.

Bank Slice 2 Accuracy Gain

46/50 vs 35/50

On Bank Slice 2, H scored 46/50 versus B0 35/50 (exact McNemar test, p = 0.0034).

Planner Tokens Eliminated

152,239 -> 0 Tokens

The October 2 run recorded 152,239 planner tokens versus zero, with both arms scoring 135/180. The October 3 unlimited-planner rerun scored 141/180 versus 142/180 and measured pointer p50 latency of 8.8s versus 0.67s.

Pointer Lookup Latency

8.8s -> 0.67s

Deterministic routing accelerated p50 pointer lookup from 8.8 s to 0.67 s compared to a Gemini planner with its time limit lifted.

Empirical Findings TableScroll table →
Telemetry MetricMeasured ValueContext & Observability
LongMemEval Token Drop82.8% Fewer TokensOn 100 questions over ~115k-token histories, structured events matched full context (88/100) using 19.5k vs 113.6k tokens.
Bank Slice 2 Accuracy Gain46/50 vs 35/50On Bank Slice 2, H scored 46/50 versus B0 35/50 (exact McNemar test, p = 0.0034).
Planner Tokens Eliminated152,239 -> 0 TokensThe October 2 run recorded 152,239 planner tokens versus zero, with both arms scoring 135/180. The October 3 unlimited-planner rerun scored 141/180 versus 142/180 and measured pointer p50 latency of 8.8s versus 0.67s.
Pointer Lookup Latency8.8s -> 0.67sDeterministic routing accelerated p50 pointer lookup from 8.8 s to 0.67 s compared to a Gemini planner with its time limit lifted.
Transcript Retrieval Gap92% vs 70%On Bank Slice 2, H scored 46/50 versus B0 35/50 (exact McNemar test, p = 0.0034).
Confounded Log Slice 186% vs 94%In Bank Slice 1, raw grep beat memory (47/50 vs 43/50, McNemar p = 0.22) because 43/50 gold answers lived in handoff logs.
Error Noise Floor8.0% (16 / 200)Pareto analysis of 200 holdout questions identified 10 bad gold answers and 6 ambiguous questions forming an unreachable noise floor.
Pre-Retrieval LLM Triage0 / 6 RecallA lightweight model caught 0 of 6 ambiguous questions. Rules written after inspecting the benchmark flagged all 6 ambiguous questions and falsely flagged 19/158 H-correct questions (12%). This was an in-sample result.

Executive Summary & Core Finding

This living paper (v1) synthesizes eight session-memory question sets, diagnostic reanalyses and planner reruns. Data collected September 28 to October 3, 2026; synthesized October 2026. On sealed Bank Slice 2, H scored 46/50 versus B0 35/50 (exact McNemar test, p = 0.0034). B0 was a notes, handoff-log and memory-file grep baseline without raw transcripts. The arms had different source access, so observed gains include corpus availability. The October 2 run recorded 152,239 planner tokens versus zero, with both arms scoring 135/180. The October 3 unlimited-planner rerun scored 141/180 versus 142/180 and measured pointer p50 latency of 8.8s versus 0.67s. On these reused question sets, deterministic routing reduced pointer latency, with no detected accuracy difference.

Method

1

Consolidated benchmark battery: A synthesis of eight session-memory question sets, diagnostic reanalyses and planner reruns across frozen development and holdout splits (P0, P1, P2, Holdout-80, Holdout-P7, Pareto, Triage, Bank-S1, Bank-S2, and Detplan-2).

2

Corpus scale: Indexed 778 initial engineering sessions (2.80M stripped tokens) yielding 6,758 semantic events, expanding to 1,282 sessions during subsequent holdout waves.

3

Evaluation arms: Arm M (unaugmented semantic event memory), Arm C (semantic memory with verified citation spans), Arm H (hybrid hints-to-grep steering), Arm B0 (a notes, handoff-log and memory-file grep baseline without raw transcripts), and Arm DU (deterministic query routing).

4

Authoring, verification and judging protocols varied by study. Session-memory evaluations used Opus; LongMemEval used Sonnet. The triage prediction was hash-locked rather than git committed.

5

Later evaluations used mechanically sealed stages; earlier exploratory runs lacked those guarantees.

Empirical Telemetry

What We Measured

Telemetry across eight session-memory question sets, diagnostic reanalyses, and planner reruns

LongMemEval Token Drop

82.8% Fewer Tokens

On 100 questions over ~115k-token histories, structured events matched full context (88/100) using 19.5k vs 113.6k tokens.

Bank Slice 2 Accuracy Gain

46/50 vs 35/50

On Bank Slice 2, H scored 46/50 versus B0 35/50 (exact McNemar test, p = 0.0034).

Planner Tokens Eliminated

152,239 -> 0 Tokens

The October 2 run recorded 152,239 planner tokens versus zero, with both arms scoring 135/180. The October 3 unlimited-planner rerun scored 141/180 versus 142/180 and measured pointer p50 latency of 8.8s versus 0.67s.

Pointer Lookup Latency

8.8s -> 0.67s

Deterministic routing accelerated p50 pointer lookup from 8.8 s to 0.67 s compared to a Gemini planner with its time limit lifted.

Transcript Retrieval Gap

92% vs 70%

On Bank Slice 2, H scored 46/50 versus B0 35/50 (exact McNemar test, p = 0.0034).

Confounded Log Slice 1

86% vs 94%

In Bank Slice 1, raw grep beat memory (47/50 vs 43/50, McNemar p = 0.22) because 43/50 gold answers lived in handoff logs.

Error Noise Floor

8.0% (16 / 200)

Pareto analysis of 200 holdout questions identified 10 bad gold answers and 6 ambiguous questions forming an unreachable noise floor.

Pre-Retrieval LLM Triage

0 / 6 Recall

A lightweight model caught 0 of 6 ambiguous questions. Rules written after inspecting the benchmark flagged all 6 ambiguous questions and falsely flagged 19/158 H-correct questions (12%). This was an in-sample result.

Experimental Notes & Observability Details

  • Changelog v1 (October 2026): Initial synthesis uniting selfmem findings across eight session-memory question sets, diagnostic reanalyses and planner reruns with links to five existing lab memory articles.
  • In session memory, H consumed about 12% more median tokens (median 129k vs 115k tokens per question in P7H); the gain is accuracy, not token reduction.
Interpretation & Working Hypotheses

What We Think It Suggests

  • Semantic event extraction solves different problems depending on conversational structure. On long conversation histories (LongMemEval), structured events yield massive prompt token reductions (82.8%). Across hundreds of disparate developer sessions, structured memory functions primarily as a precision anchor; memory reduced some historical-recall errors in these evaluations.
  • A confident incorrect memory hint is worse than no hint. In our Pareto evaluation, memory hints contributed to 28.6% of misses because the answering model anchored on the hint rather than verifying the source. The Pareto analysis estimated that pointer-only hints could recover 8 to 9 misses; that estimate was not measured on the original questions.
  • Benchmark design and source access affect interpretation. In sealed Bank Slice 1, B0 scored 47/50 versus H 43/50 (McNemar p = 0.22); 43/50 gold answers cited handoff logs. On sealed Bank Slice 2, H scored 46/50 versus B0 35/50 (exact McNemar test, p = 0.0034). B0 was a notes, handoff-log and memory-file grep baseline without raw transcripts. The arms had different source access, so observed gains include corpus availability.
  • On these reused question sets, deterministic routing reduced pointer latency, with no detected accuracy difference.
  • Rules written after inspecting the benchmark flagged all 6 ambiguous questions and falsely flagged 19/158 H-correct questions (12%). This was an in-sample result.
Methodology Boundaries

Limits

  • Single developer organization corpus: Benchmarks reflect MeshTen software engineering sessions; organizations with different project naming or logging conventions may observe differing noise floors.
  • Model family specificity: Answering agents utilized Gemini and Claude models; smaller open-weight models may exhibit different sensitivity to memory hint formats.
  • Ingestion compute investment: Structured event extraction requires upfront compute during session finalization; it is inefficient for ephemeral conversations queried only once.

Detailed Analysis & Field Observations

In autonomous software engineering, agents frequently need to know what happened in earlier sessions: which design was selected, why a library was replaced, what instruction the operator gave, or what error occurred three weeks ago. When context windows span millions of tokens, a common assumption is that agents can simply grep through raw session logs on demand. In empirical testing across eight session-memory question sets, diagnostic reanalyses and planner reruns, we measured where that assumption holds, where it fails, and what structured semantic memory actually accomplishes.

This living paper (version 1) consolidates our experimental campaign across selfmem, integrating findings from our five previously published memory studies: semantic-memory-83-percent-fewer-tokens, session-memory-recall, benchmark-confinement-tax, speculative-prefetch-agent-recall, and deconstructing-agent-retrieval-latency. Data collected September 28 to October 3, 2026; synthesized October 2026.

Our earliest baseline, P0, indexed 778 sessions into 6,758 events. These exploratory evaluations lacked mechanical confinement; their accuracy scores are omitted from public reporting.

In P1, we introduced hybrid hints-to-grep (Arm H), where memory surfaces candidate session pointers, timestamps and line excerpts to guide a targeted grep pass.

In P2 and Holdout-80, we observed hint anchoring: the answering model sometimes relied on an intermediate narrative summary instead of inspecting subsequent turns. A pooled Pareto analysis attributed 28.6% of 42 misses to hint anchoring. The analysis estimated that pointer-only hints could recover 8 to 9 misses; that estimate was not measured on the original questions.

In Holdout-P7, memory was restricted to factual pointers rather than narrative conclusions. G lacked access to the Codex source store. These exploratory results do not provide a confined accuracy comparison.

Later evaluations used mechanically sealed stages; earlier exploratory runs lacked those guarantees. In session memory, H consumed about 12% more median tokens than the baseline. Unlike single-document benchmarks where semantic memory reduces prompt tokens by ~83%, session memory recall is an accuracy intervention, not a token reduction mechanism.

In sealed Bank Slice 1, H scored 43/50 versus B0 47/50 (McNemar p = 0.22). Of 50 gold answers, 43 cited structured session handoff logs available to B0. In sealed Bank Slice 2, every gold answer cites a raw transcript, and 17/50 cite only transcripts. On sealed Bank Slice 2, H scored 46/50 versus B0 35/50 (exact McNemar test, p = 0.0034). B0 was a notes, handoff-log and memory-file grep baseline without raw transcripts. The arms had different source access, so observed gains include corpus availability. B0 performed poorly on these categories: 0/6 which-session, 1/6 operator statements and 1/5 cross-model.

Finally, in DETPLAN-EVAL-2 (180 questions pooled across P7H, Bank Slice 1, and Bank Slice 2), we tested whether an unconstrained LLM query planner could surpass deterministic query routing. The October 2 run recorded 152,239 planner tokens versus zero, with both arms scoring 135/180. The October 3 unlimited-planner rerun scored 141/180 versus 142/180 and measured pointer p50 latency of 8.8s versus 0.67s. On these reused question sets, deterministic routing reduced pointer latency, with no detected accuracy difference.