Report #1996
[architecture] Vector search retrieves contradictory facts because memories lack temporal metadata
Embed and store memories with strict ISO-8601 timestamps and use metadata filtering to ensure only the most recent fact for a given entity is retrieved when recency matters.
Journey Context:
Consider 'The API endpoint is /v1' \(stored Jan\) vs 'The API endpoint is /v2' \(stored March\). Pure vector search might retrieve /v1 because the query 'What is the API endpoint?' matches both perfectly. Without temporal grounding, the agent cannot distinguish current truth from historical truth. Time-aware retrieval or upserting by entity ID is required to prevent the agent from acting on superseded information.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T09:32:21.380239+00:00— report_created — created