{
  "id": 17869754,
  "title": "Your AI Agent's Memory Needs Two Clocks",
  "url": "https://urgent.news/2026/11/02/your-ai-agents-memory-needs-two-clocks",
  "topic": "ai",
  "section": "AI",
  "published": "2026-11-02T22:41:39.000Z",
  "source": {
    "name": "HackerNoon",
    "slug": "hackernoon",
    "url": "https://hackernoon.com/your-ai-agents-memory-needs-two-clocks?source=rss"
  },
  "original_language": "en",
  "account": "Consumer agents, such as fitness coach apps or journaling tools, run for years with the same user, collecting thousands of small facts. These facts often have limited relevance or evolve over time. For example, a race scheduled for next Sunday, a trial set to end in January, or a trip taken last week. However, most setups only store the date the user mentioned the fact and when the system recorded it, without indicating when the event actually occurred. This leads to outdated information being retained indefinitely, even after the original event has passed.\n\nTo address this issue, two \"clocks\" are needed to track independent timelines: event time and write time. Event time represents when the event actually happened (e.g., Sam ran a race on June 14, 2025), while write time is when the system learned about the event (e.g., during a user's chat session or later data import).\n\nBy tracking both timelines, the system can resolve discrepancies and provide accurate information. For instance, if Sam wrote \"I ran my first 10K last weekend\" in June 2025, the system should store the original event time and update the phrase to reflect the current date, such as \"Sam ran a 10K this week.\" This approach allows for continuous updates and accurate responses based on the actual occurrence of events.",
  "summary": "Agent memory goes stale because it tracks when a fact was stored and not when it happened. A practical guide to bitemporal memory: event time and write time.",
  "key_points": [
    "Two clocks needed: event time and write time",
    "Event time represents actual event occurrence",
    "Write time records when system learned about event"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}