Dmytro Galko · open-source tools
Your vector index broke and nothing raised an error
When a provider swaps the embedding model under a live index, nothing raises an error. The nearest neighbours are simply the wrong ones from then on, and the blame lands on the language model rather than the retrieval step feeding it. This pins a fingerprint and tells you when the space moved.
A baseline on all-minilm checked three ways: the same model returns 1.0000 on both numbers; a different model of the same 384 dimensions collapses direct to -0.0052 while geometry lands at 0.349; a 768-dimension model is a hard fail with no arithmetic attempted. The synthetic proof is in the suite - a uniform rotation drops direct below 0.95 and leaves geometry at 1.0.
embedding model silently changed, embedding drift detection, RAG retrieval broke after provider update, pin embedding model version, vector index stale.
If that is your week and you would rather someone else did it, write to hello@dkautomation.dev or open an issue.