Versioning the Space

Mon, 07 Sep 2026 13:10:00 +0000

Part V — Embedding Spaces Are Not Universal

The upgrade that broke search quietly

Production runs embedding model v1. A better v2 ships. Someone updates the client library. New documents get v2 vectors; the 10 million existing vectors are still v1. Nothing errors. Queries are embedded with v2 and compared against a mix of v1 and v2 vectors.

Recall drops a few points. Nobody notices for a month, because the system still returns ten results and they still look plausible. The v1 and v2 vectors are in different universes (Chapter 16), and half the index is now in the wrong one.

The Embedding Bridge

Mon, 07 Sep 2026 14:20:00 +0000

Part VI — Crossing Embedding Spaces

A map is not a bridge

Chapter 19 produced a matrix W (or an MLP) that translates vectors from space A to space B. Deploying that matrix as “space A and space B are now compatible” is the mistake this chapter prevents.

A map is a function. A bridge is a map plus the record of what it was shown to preserve, for whom, under what conditions — and, crucially, an explicit scope of what it must not be used for.

MLOps on Programmer.ie: Modern AI programming

Versioning the Space

The upgrade that broke search quietly

The Embedding Bridge

A map is not a bridge