Problem
Search results return wing, room, source_file, and similarity but no timestamp. You can't tell when a drawer was stored without reading it directly. This makes temporal reasoning impossible from search results alone.
Proposal
Add created_at to the search result objects:
{
"text": "Team decided to migrate auth to Clerk...",
"wing": "driftwood",
"room": "decisions",
"source_file": "conversation-2026-04-09",
"similarity": 0.89,
"created_at": "2026-04-09T20:25:23Z"
}If ChromaDB metadata already stores a timestamp, this is just passing it through. If not, it should be added at ingest time.
Why this matters
When the AI retrieves memories, it needs to know if a result is from yesterday or six months ago. A decision from January may have been superseded. Without timestamps in results, every memory looks equally current.
Problem
Search results return
wing,room,source_file, andsimilaritybut no timestamp. You can't tell when a drawer was stored without reading it directly. This makes temporal reasoning impossible from search results alone.Proposal
Add
created_atto the search result objects:{ "text": "Team decided to migrate auth to Clerk...", "wing": "driftwood", "room": "decisions", "source_file": "conversation-2026-04-09", "similarity": 0.89, "created_at": "2026-04-09T20:25:23Z" }If ChromaDB metadata already stores a timestamp, this is just passing it through. If not, it should be added at ingest time.
Why this matters
When the AI retrieves memories, it needs to know if a result is from yesterday or six months ago. A decision from January may have been superseded. Without timestamps in results, every memory looks equally current.