---
type: "post"
id: "every-memory-has-two-clocks-when-the-event-ecf7f8"
slug: "every-memory-has-two-clocks-when-the-event-ecf7f8"
title: "Every memory has two clocks: - when the event happened - when the system learned about it A deep dive into eight temporal scenarios in consumer apps, and how to handle each one: https://t.co/hXcOUs8Nw0"
description: "**Thesis:** Agent memory needs to represent event time separately from the time information entered the system."
retrieval_nugget: "**Thesis:** Agent memory needs to represent event time separately from the time information entered the system."
published_at: "2026-10-20"
updated_at: "2026-10-20"
record_date: "2026-10-20"
date_kind: "published_at"
topics: ["agent-memory"]
source_urls: ["https://www.nowledge.co/blog/building-memory-systems-for-ai-agents"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:every-memory-has-two-clocks-when-the-event-ecf7f8"
status: "published"
visuals: []
editorial_provenance: {"schema_version":"newruntime-editorial-copy-v1","content_status":"source_grounded_final","final_copy_sha256":"sha256:4b981b17566c25079f03272e61a6562410ed1f420a8727049914ef67b96625cf","reviewed_at":"2026-10-20T17:05:58.973Z","source_evidence_count":1,"verified_claim_count":3,"site_analysis_schema_version":"newruntime-site-analysis-v1","site_object_kind":"field_note","observed_fact_count":3,"implication_count":1,"watch_condition_count":1,"related_record_count":0}
analysis: {"schema_version":"newruntime-site-analysis-v1","object_kind":"field_note","thesis":"Agent memory needs to represent event time separately from the time information entered the system.","observed_facts":[{"text":"The article distinguishes when an event happened from when the system learned about it.","source_urls":["https://www.nowledge.co/blog/building-memory-systems-for-ai-agents"]},{"text":"It describes three knowledge forms: raw conversation traces, extracted atomic Units, and Crystals cross-validated by three or more independent sources.","source_urls":["https://www.nowledge.co/blog/building-memory-systems-for-ai-agents"]},{"text":"It reports a two-tier retrieval design with a fast path for most queries and a deep path for harder queries.","source_urls":["https://www.nowledge.co/blog/building-memory-systems-for-ai-agents"]}],"mechanism":"Separating event time from learning time lets retrieval distinguish questions about when something happened from questions about when information was added; the article places this within a broader lifecycle from conversation traces to structured knowledge and cross-validated conclusions.","why_now":"As people move among AI tools, memory systems must support continuity and knowledge evolution rather than simply accumulate records.","implications":["Systems that retain only a creation timestamp risk answering event-time questions with ingestion-time data."],"evidence_boundary":"The source is an engineering account from the team behind Nowledge Mem; it does not establish independent performance, comparative quality, or adoption results.","watch_conditions":["Whether the described temporal model is shown to improve retrieval across the article’s eight scenarios in a reproducible evaluation."],"related_records":[],"new_branch_reason":"No prior New Runtime record was supplied; this record isolates temporal modeling as a distinct engineering dimension within agent memory."}
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/every-memory-has-two-clocks-when-the-event-ecf7f8/","markdown":"https://newruntime.com/posts/every-memory-has-two-clocks-when-the-event-ecf7f8.md","json":"https://newruntime.com/posts/every-memory-has-two-clocks-when-the-event-ecf7f8.json"}
related_patterns: ["company-memory-needs-write-loops"]
related_shifts: ["shared-context-infrastructure"]
---

# Every memory has two clocks: - when the event happened - when the system learned about it A deep dive into eight temporal scenarios in consumer apps, and how to handle each one: https://t.co/hXcOUs8Nw0

## Retrieval answer

**Thesis:** Agent memory needs to represent event time separately from the time information entered the system.

**Thesis:** Agent memory needs to represent event time separately from the time information entered the system. **Mechanism:** Separating event time from learning time lets retrieval distinguish questions about when something happened from questions about when information was added; the article places this within a broader lifecycle from conversation traces to structured knowledge and cross-validated conclusions. **Why now:** As people move among AI tools, memory systems must support continuity and knowledge evolution rather than simply accumulate records.

The article gives a concrete example of fragmentation: an architecture decision made in Claude Code is unavailable when the user opens Cursor the next day. It also describes three knowledge forms—raw conversation traces, extracted atomic Units, and conclusions called Crystals that are cross-validated by three or more independent sources. These are the authors’ design descriptions, not a comparative validation of the product.

**First implication:** Systems that retain only a creation timestamp risk answering event-time questions with ingestion-time data. **First watch condition:** Whether the described temporal model is shown to improve retrieval across the article’s eight scenarios in a reproducible evaluation. **Evidence boundary:** The source is an engineering account from the team behind Nowledge Mem; it does not establish independent performance, comparative quality, or adoption results.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Agent Memory](https://newruntime.com/topics/agent-memory.md): Explore the agent-memory topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Source Ledger](https://newruntime.com/source-ledger.json): Inspect the public source evidence graph.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)