Skip to main content
Back to blog
Engineering
8 min read·Dec 2025

Temporal Supersession: Tracking Facts That Change Over Time

"My meeting with Sarah is on Thursday" becomes stale the moment the meeting passes. Here's how Hypermemory's fact graph tracks current state vs. historical state without explicit updates.

Temporal Supersession: Tracking Facts That Change Over Time

In long-running AI agents, memory staleness has become the frontier research problem of 2026. An agent recalls that a user expressed a preference two years ago — but that preference is no longer valid. The memory is confidently wrong, not just outdated. Distinguishing between still-valid historical context and genuinely superseded facts is harder than it appears, and the 2026 research community is treating it as a first-class problem: recent work on systems like MemMachine explicitly frames the goal as 'ground-truth-preserving memory' — ensuring that updates to facts don't silently corrupt the historical record that earlier decisions depended on.

Temporal supersession is the mechanism for tracking which facts are still current. When a user reschedules a meeting ('My meeting with Sarah is now on Friday instead of Thursday'), the new fact doesn't erase the old one—it supersedes it. The historical fact remains (useful for 'When was the original date?' questions) but becomes marked as non-current. The new fact becomes the canonical answer to 'When is my meeting?' When new information contradicts existing memories, the system prioritizes recency while maintaining the full record of previous states — letting agents distinguish between outdated and current information without losing provenance. Zep's Graphiti engine formalizes this as a bi-temporal model: every fact node carries `valid_at` and `invalid_at` timestamps with explicit validity intervals, so 'Kendra loves Adidas shoes (as of March 2026)' is not a string but a bounded fact. Graphiti runs on Neo4j, FalkorDB, and Amazon Neptune; the Apache 2.0 Graphiti MCP Server v1.0 shipped in November 2025. Independent LongMemEval evaluations quantified the architectural payoff: Zep with GPT-4o scored 63.8% vs. Mem0's baseline 49.0% — a 15-point gap that directly reflects bi-temporal modeling's advantage over flat vector storage. (Mem0's April 2026 token-efficient algorithm update subsequently gained +29.6 percentage points specifically on temporal queries, narrowing the gap — but the underlying structural advantage of explicit temporal fact modeling remains.)

Hypermemory's fact graph implements temporal supersession by storing facts with their creation timestamp and supersession chain. When a fact is updated, the system creates a new fact node and links it to the old one with a 'supersedes' relationship. Queries for current state filter to the most recent unsuperseded facts. Queries for historical state or temporal reasoning ('What was the original date?') can traverse the chain.

The challenge becomes harder in multi-agent systems or long-memory scenarios. If an agent hasn't interacted with the user for six months, should it assume preferences are still valid? How confident can we be that a two-year-old preference is still accurate? The research community in 2026 is actively exploring staleness detection heuristics: confidence scoring based on how often facts are reaffirmed, automatic preference decay models, and explicit user signals ('This is still true'/'This has changed'). LinkedIn's production Cognitive Memory Agent validates this direction at enterprise scale — their system evaluates each incoming fact against existing memory using a write-time curation loop before committing, preventing stale contradictions from ever entering the store. A Mem0 production study of 50,000 real-world sessions quantifies exactly what happens without this curation: benchmark accuracy collapsed from 91.6% to 49% after just 30 days of live usage as entity contradictions and stale facts accumulated. MemMachine (arXiv:2604.04853, April 2026) addresses a related risk by storing raw conversational episodes rather than LLM-extracted facts, with a planned roadmap for confidence-scored staleness retirement — prioritizing frequently accessed memories and gracefully retiring stale ones.

AWS AgentCore Memory (GA October 2025) takes a complementary approach: source attribution on every stored fact, contradiction detection at write time, and periodic consolidation passes that merge redundant memories. A March 2026 update added streaming LTM notifications via Amazon Kinesis, eliminating polling and enabling event-driven downstream filtering by `eventTime`. A May 2026 release added metadata support — up to 10 indexed keys per memory resource (STRING, NUMBER, STRING_LIST types) with range-query operators — letting agents issue date-range queries against the memory store without relying solely on semantic similarity. Cloudflare launched Agent Memory in April 2026 private beta — a managed service with a two-pass extraction pipeline (a full pass using Llama 4 Scout for extraction and Nemotron 3 for synthesis, plus a detail pass for concrete values like names and version numbers). Retrieval runs five channels in parallel (full-text, exact fact-key lookup, raw message, direct vector, and HyDE vector) fused with RRF, with recency as a tiebreaker. Shared memory profiles let knowledge learned by one agent be immediately available across an entire team. The pattern of write-time curation — validating each incoming fact against the existing store before committing — is now an industry standard across AWS, Cloudflare, Mem0, and LinkedIn's CMA.

Staleness is now formally classified as one of four open research problems in AI agent memory — alongside privacy governance, consent frameworks, and cross-session identity resolution. The RankSquire Memory Fidelity Curve quantifies the production impact mathematically: Production Accuracy ≈ Benchmark − (0.22 × Staleness_Rate) − (0.15 × log₁₀(Entities)), making staleness the single largest correction factor between benchmark numbers and live production performance. For now, Hypermemory's approach is pragmatic: mark facts with their provenance and recency, surface current facts with higher priority, and give the agent visibility into when facts were last updated. A sophisticated agent can use this metadata to avoid confidently applying stale information. The agent that says 'I found a reference to this preference from two years ago—should I assume it's still valid?' is far better than one that silently applies obsolete context.

As memory systems scale to weeks and months of agent operation, temporal supersession becomes non-negotiable. It's not enough to remember; you have to remember which version of the truth is current.

A

Adrian

Hypermemory · Support