<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Representation Geometry on Nalar</title>
    <link>https://nalar.dev/tags/representation-geometry/</link>
    <description>Recent content in Representation Geometry on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 16 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/representation-geometry/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Measure Embedding Anisotropy Before Vector Retrieval</title>
      <link>https://nalar.dev/measure-embedding-anisotropy-before-vector-retrieval/</link>
      <pubDate>Wed, 16 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/measure-embedding-anisotropy-before-vector-retrieval/</guid>
      <description>&lt;p&gt;Cosine similarity is often treated as a local comparison between one query embedding and one candidate. That interpretation becomes less informative when most vectors occupy a narrow set of directions. Unrelated items can then share a substantial common component, compressing the range of angles that retrieval uses to separate candidates.&lt;/p&gt;&#xA;&lt;p&gt;This directional concentration is commonly described as embedding anisotropy. It is a property of a vector distribution, not a defect implied by any single similarity score. For developers, the practical issue is that a fixed cosine value has no universal meaning. Its usefulness depends partly on the geometry of the embedding population in which it was produced.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
