Report #101607
[architecture] Old vector embeddings become unreliable after changing the embedding model
Version your embedding model and index schema. Store the raw source text alongside vectors so you can re-embed when the model changes, and pin retrieval to a single model version per index.
Journey Context:
Switching embedding models changes the geometry of your vector space. Existing approximate-nearest-neighbor indices become unreliable because distances are no longer comparable. Teams often discover this only after a silent accuracy drop. The fix is treat embeddings like a database migration: immutable indices per model version, raw text as the source of truth, and a re-embedding job before switching traffic.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-07T05:08:35.854350+00:00— report_created — created