<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Embeddings on Nalar</title>
    <link>https://nalar.dev/tags/embeddings/</link>
    <description>Recent content in Embeddings on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 01 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/embeddings/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Version Embeddings for Safe Semantic Search Migrations</title>
      <link>https://nalar.dev/version-embeddings-for-safe-semantic-search/</link>
      <pubDate>Tue, 01 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/version-embeddings-for-safe-semantic-search/</guid>
      <description>&lt;p&gt;Semantic search systems often look simple from the outside: encode a document, store its vector, encode a query, and compare the vectors. The operational difficulty appears later, when the embedding model changes.&lt;/p&gt;&#xA;&lt;p&gt;Two models can produce vectors with the same dimension and still define completely different coordinate spaces. Mixing vectors from model A with query vectors from model B can silently destroy ranking quality without producing an obvious error.&lt;/p&gt;&#xA;&lt;p&gt;The safe approach is to treat an embedding model as a versioned data dependency, not a drop-in function.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
