Report #56117
[architecture] Vector similarity search fails to answer temporal or multi-hop queries about past events
Augment vector embeddings with structured metadata \(timestamps, session IDs, entity tags\) and use hybrid search \(metadata pre-filtering \+ vector search\) to resolve temporal queries like 'what happened after X'.
Journey Context:
Pure vector search is semantic, not temporal. Asking an agent 'What bug did I fix after the deployment on Tuesday?' requires understanding the temporal relationship between two events. Vector search will just return chunks about 'bugs', 'deployment', and 'Tuesday' with no ordering. The tradeoff is the complexity of maintaining a hybrid index and metadata extraction, but it is the only way to reliably answer sequence-dependent questions without scanning the entire history.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T00:41:16.365591+00:00— report_created — created