44 x 32

LAPSE: 1,397 matched pairs, 11 model configurations, three installed memory pipelines

Memory Consolidation Flattens the Temporal Shape of User Facts

Sugam Panthi, Muhaiminul Yeamin, Siyan Luo, and Rabab Abdelfattah

The University of Southern Mississippi. LAPSE asks whether a memory writer keeps the cue that says a user's fact is still going on, or stores it as a fact that simply holds.

The problem

A memory can keep your fact and lose that it is still happening

A user says "I am driving a Peugeot." A writer stores The user drives a Peugeot. The object and the relation survive. The cue that the activity is ongoing does not. Months later the assistant has less evidence for deciding whether the fact still holds. We call that transformation aspectual flattening.

1 · SOURCE UTTERANCE “I’m working at Corvida Analytics.” progressive an ongoing event, the fact may stop holding 2 · STORED MEMORY User works at Corvida Analytics as of August 27, 2026 simple present a standing fact memory writer aspect flattened Write-time test Was the source’s temporal form preserved in the memory? 244 of 381 pairs: no separate tests no mediation Read-time test Did the later action use the form that survived the write? every reader says less persistent
One observed pipeline specimen: the writer replaces progressive working with simple-present works and keeps a date anchor. Data: paper Figure 1.

Method: matched pairs differing only in temporal form

Change the tense, hold everything else fixed

Form
progressive against its simple-present match; the lexical head is fixed.
Frame
lodging, workplace, vehicle, class, household, equipment, role, project.
Carrier
one main verb plus five alternatives, so the result cannot rest on one wording.
Gap
six elapsed-time bins from a timestamp; fresh and boundary are positive controls.
Task
memory write, guided write, memory use, validity question, send-or-check choice.
Destructive
the rewrite removes ongoingness or invents an unsupported durable fact; paraphrase and politeness do not count.
Labels
the destructive group: coerced-stative removes ongoingness, manufacture invents a durable fact.

45,000 requests; protocol frozen before outcomes were opened. Data: paper Table 1.

Core result: 381 confirmatory matched pairs, three prospectively fixed writers

Writers erase the progressive, and never the reverse

SIMPLE ONLY PROGRESSIVE ONLY DeepSeek V4 Flash 128 matched pairs, adjusted p = 1.5 × 10⁻³¹ 104 0 GPT-5.6 Luna 128 matched pairs, adjusted p = 3.3 × 10⁻²⁴ 79 0 GLM-5.2 125 matched pairs, adjusted p = 4.3 × 10⁻¹⁹ 61 0

244 : 0 of 381 matched pairs destroyed on the progressive side, against the reverse

FLATTENING BY WHAT THE FACT IS ABOUT DeepSeek V4 Flash GPT-5.6 Luna GLM-5.2 0 25 50 75 100 Vehicle Workplace Equipment Affiliate role Class Lodging Household Project Progressive-minus-simple destruction (pp)

Every writer, every tested carrier, the same-lexeme subset, and eight further configurations show the same direction. Across all 11 configurations 807 usable pairs lose only the progressive and two show the reverse. Leaving out any one frame preserves the result. An exhaustive placebo audit over 4,263,744 cells flags seven benign matches. Data: paper Tables 2, 9, and 10.

Installed pipelines: mem0 2.0.19, Graphiti 0.30.1, Letta 0.16.8

Shipping memory systems lose the same cue

mem0 2.0.19 stored all 128, flattened 49 49/128 38% Graphiti 0.30.1 flattened 15 of 32 grid progressives 15/32 47% Letta 0.16.8 kept a progressive verb in only 3 29/32 91% Ongoing facts stored, then flattened

mem0 flattened 49 of 128 ongoing facts and added progressive wording to none of the 128 controls. The loss is not confined to grammar: it also removed "for now" from 91 of 128 notes and "at the moment" from 104 of 128.

Graphiti writes valid_at for all 287 stored edges whatever the source form and never sets invalid_at. Data: paper Section 7.1, Appendix D.

The write-read boundary: seven writers, three readers

An instruction moves the write, not the tested action

baseline instruction helps instruction hurts 0 25 50 75 100 GPT-5.6 Luna 3.1 Qwen3-8B 0.0 DeepSeek V4 Flash 57.5 GLM-5.2 38.6 Mistral Small 3.2 46.5 GPT-OSS-20B 75.0 OLMo-2-32B 100.0 Progressive destruction (%)

The prospectively fixed downstream task showed no effect: readers use the fact on 97% to 100% of stale memories, so it cannot show that better storage helps later.

Reader, dated-note testPersistenceField fillsp
DeepSeek, official -31.5 26 : 3 1.5 × 10⁻⁵
GLM, OpenRouter -18.5 17 : 3 .003
Luna, OpenRouter -16.1 23 : 15 .26

In an exploratory dated-note test every reader rates a stale progressive 16 to 32 points less likely to still hold, but only two change whether they fill the field. Data: paper Figure 3.

Takeaway

Store temporal form as evidence, not as style

  1. Temporal form is evidence, not style. A progressive verb says the fact may stop holding; normalizing it deletes that.
  2. Keep form in its own field. Store the normalized fact, the temporal form, and the observation time separately.
  3. Do not trust a preservation instruction alone. It nearly fixes two writers and makes GPT-OSS and OLMo worse.
  4. Audit the installed pipeline, not the model. mem0, Graphiti, and Letta each flatten through unmodified write paths.
  5. A saturated task hides the cost. Readers proceed on almost every stale fact, so good downstream numbers prove nothing about storage.

TL;DR

What we did

LAPSE sends matched user statements that differ only in temporal form to the same memory-writing instruction, holding topic, predicate, carrier verb, and elapsed time identical, then scores what the writer stored and what a later reader did with it.

What we found

Across three prospectively fixed writers, 244 of 381 matched pairs lose only the progressive form and not one loses only the simple present. The same asymmetry appears in eight further configurations and in mem0, Graphiti, and Letta. Readers rate a flattened fact more likely to still hold.

What you should do

Keep the normalized fact, the temporal form, and the observation time in separate fields, and let a later rule decide expiry. A preservation instruction is not a repair: it nearly fixes two writers and makes two others worse. Audit the pipeline you ship, not the model.

QR code linking to this poster online at spanthi.com

This poster online

+ and − zoom, 0 fits, scroll pans, ⌘/ctrl + wheel zooms, Esc or X closes