Report #13212
[architecture] Relying solely on vector similarity for time-sensitive queries like 'What did I work on last week?'
Store timestamps as structured metadata on vectors and use hybrid search \(vector similarity \+ metadata range filters\) to constrain retrieval by time.
Journey Context:
Pure vector search is semantic, not temporal. If a user asks about a recent project, vector search might return a highly similar project from two years ago simply because the embeddings are close. Naive RAG pipelines ignore metadata. By embedding timestamps and using pre-filtering \(or hybrid search\), you guarantee the agent only looks in the correct temporal window.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T18:11:34.837564+00:00— report_created — created