mlsanityData to 14 Oct 2026

Suggested Is Not Superseded: A Pre-Registered Evaluation of a System-One Model as a Memory-Retirement Gate

arXiv 2610.15710 ↗First posted 11 Oct 2026cs.AIcited by 0

Not on the map. Why?

Abstract (arXiv)

Long-term memory for assistants needs a gate that decides when a new utterance retires an old stored claim. Benchmark labels for this step mark a pair as changed or not, so they cannot tell a gate that acts on established change from one that acts on a hint. We write a task contract that separates the two (SUPERSEDED vs. NEEDS-CONFIRMATION vs. COMPATIBLE), label 500 test pairs built from STALE (change pairs plus same-user controls) with three LLM annotators and two human adjudicators (one author and a second annotator; provenance reported), and evaluate Jev, a typed "System One" decision model, under pre-registered hypotheses. Of the 179 test pairs STALE marks as changed, 72 meet the contract's bar for an established change. Jev never retired a claim on 141 same-conversation non-changes. Its failure is premature retirement: the binary gate retires 39.2% of claims whose change is only suggested. A three-way decision cuts this to 15.5% at a 15.3-point detection cost, which misses our pre-registered 10-point budget, and it lands on the binary gate's own threshold frontier; these verdicts hold under three readings of the gold labels. On a held-out vault scored against a second annotator's labels, a cascade that escalated uncertain cases to a reasoning model and looked best on development data was indistinguishable from simply raising the threshold (premature retirement 26.8% vs. 6.5% on dev). Part of the gap comes from the gold labels: relative to that annotator's reading, LLM-majority gold shares most of its errors with a same-family escalation model, and an identity for binary labels says how much such shared errors hide. The rest is small-sample selection on development data. For builders this means a binary score should not be wired to delete: route suggested changes to pending evidence, and do not trust a cascade selected on development data of this size.

Key facts. No citing papers in the map yet (data through 14 Oct 2026). Builds on 19 of its 30 references that are in the map. First posted on arXiv 11 Oct 2026.

Builds on

19 of 30 references.

References · 19

  1. 2019Sentence-BERT: Sentence Embeddings using Siamese BERT-Networkscited by 9,170
  2. 2023Judging LLM-as-a-Judge with MT-Bench and Chatbot Arenacited by 8,626
  3. 2020MiniLM: Deep Self-Attention Distillation for Task-Agnostic Compression of Pre-Trained Transformerscited by 1,463
  4. 2025A-MEM: Agentic Memory for LLM Agentscited by 1,063
  5. 2023ChatGPT Outperforms Crowd-Workers for Text-Annotation Taskscited by 870
  6. 2024Evaluating Very Long-Term Conversational Memory of LLM Agentscited by 830
  7. 2024LongMemEval: Benchmarking Chat Assistants on Long-Term Interactive Memorycited by 707
  8. 2024LLM Evaluators Recognize and Favor Their Own Generationscited by 686
  9. 2025Evaluating Memory in LLM Agents via Incremental Multi-Turn Interactionscited by 254
  10. 2024Limits to scalable evaluation at the frontier: LLM as Judge won't beat twice the datacited by 51
  11. 2026STALE: Can LLM Agents Know When Their Memories Are No Longer Valid?cited by 50
  12. 2026JEV-as-a-Judge: Accept When Confident, Escalate When Unsurecited by 30
7 more
  1. 2026Jev-Mem: System-One-Controlled Agentic Memory for Efficient AI Agentscited by 14
  2. 2026Evaluating Decision Models for Text Annotation in Computational Social Sciencecited by 11
  3. 2026REFLEX with Jev for Efficient Selective Control in LLM Agentscited by 11
  4. 2026Can Agent Memory Systems Track Evolving State?cited by 7
  5. 2026HAGE: Harnessing Agentic Memory via RL-Driven Weighted Graph Evolutioncited by 6
  6. 2026What Should an Agent Forget? Separating What Is Stored from What Is Usedcited by 1
  7. 2026AnyJev Technical Reportcited by 1

Built on by

Not cited yet.

Similar, not cited

Close in wording, no citation either way

  1. 2026Remember, Verify, or Ask? Cross-Family Evaluation of Memory Commitment in LLM Agents
  2. 2026When Memory Updates but Behavior Does Not: Repairing Implicit Stale Dependencies in Personalized Agent Responses
  3. 2026Defense-in-Depth for LLMs: Evaluating Memory Gates Against Activation-Induced and Memory-Induced Sycophancy
  4. 2026MemTrace: Probing What Final Accuracy Misses in Long-Term Memory
  5. 2026Many Steps into One: Reasoning Contraction and the Limits of Safe Memory Reuse for LLM Agents
  6. 2026MemOps: Benchmarking Lifecycle Memory Operations in Long-Horizon Conversations
  7. 2026Supersede: Diagnosing and Training the Memory-Update Gap in LLM Agents
  8. 2026Calibrating Criterion Revision in LLM Agents: Failure Modes and a Trace-Anchored Protocol