<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Representation Alignment on Programmer.ie: Modern AI programming</title>
    <link>http://programmer.ie/tags/representation-alignment/</link>
    <description>Recent content in Representation Alignment on Programmer.ie: Modern AI programming</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 09 Sep 2026 02:00:00 +0000</lastBuildDate>
    <atom:link href="http://programmer.ie/tags/representation-alignment/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Embedding Bridge</title>
      <link>http://programmer.ie/books/embeddings-from-first-principles/20-chapter/</link>
      <pubDate>Mon, 07 Sep 2026 14:20:00 +0000</pubDate>
      <guid>http://programmer.ie/books/embeddings-from-first-principles/20-chapter/</guid>
      <description>&lt;p&gt;&lt;em&gt;Part VI — Crossing Embedding Spaces&lt;/em&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;a-map-is-not-a-bridge&#34;&gt;A map is not a bridge&lt;/h2&gt;&#xA;&lt;p&gt;Chapter 19 produced a matrix &lt;code&gt;W&lt;/code&gt; (or an MLP) that translates vectors from space A to space B. Deploying that matrix as &amp;ldquo;space A and space B are now compatible&amp;rdquo; is the mistake this chapter prevents.&lt;/p&gt;&#xA;&lt;p&gt;A map is a function. A &lt;strong&gt;bridge&lt;/strong&gt; is a map plus the record of &lt;em&gt;what it was shown to preserve, for whom, under what conditions&lt;/em&gt; — and, crucially, an explicit scope of what it must not be used for.&lt;/p&gt;</description>
    </item>
    <item>
      <title>What Should a Translation Preserve?</title>
      <link>http://programmer.ie/books/embeddings-from-first-principles/26-chapter/</link>
      <pubDate>Wed, 09 Sep 2026 02:00:00 +0000</pubDate>
      <guid>http://programmer.ie/books/embeddings-from-first-principles/26-chapter/</guid>
      <description>&lt;p&gt;&lt;em&gt;Research Coda — What Alignment Really Preserves&lt;/em&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;preserve-the-geometry-is-not-a-complete-instruction&#34;&gt;&amp;ldquo;Preserve the geometry&amp;rdquo; is not a complete instruction&lt;/h2&gt;&#xA;&lt;p&gt;A bridge translates vectors from space A into space B.&lt;/p&gt;&#xA;&lt;p&gt;The natural instinct is to say:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;Preserve the source geometry while you translate.&lt;/p&gt;&lt;/blockquote&gt;&#xA;&lt;p&gt;That sounds obviously correct. If two source points are close, keep them close. If two source points are far apart, keep them far apart. Preserve pairwise cosine, distances, neighborhoods.&lt;/p&gt;&#xA;&lt;p&gt;But Chapter 16 established something uncomfortable: different encoders do not merely rotate the same universe. They can disagree on neighborhoods, density, rank order, hard distinctions, and calibration.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
