<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Retrieval Traces on Programmer.ie: Modern AI programming</title>
    <link>http://programmer.ie/tags/retrieval-traces/</link>
    <description>Recent content in Retrieval Traces on Programmer.ie: Modern AI programming</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 14 Sep 2026 05:00:05 +0100</lastBuildDate>
    <atom:link href="http://programmer.ie/tags/retrieval-traces/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Pathways Through Memory</title>
      <link>http://programmer.ie/books/memory/05-chapter/</link>
      <pubDate>Mon, 14 Sep 2026 05:00:05 +0100</pubDate>
      <guid>http://programmer.ie/books/memory/05-chapter/</guid>
      <description>&lt;p&gt;Chapter 4 set out to give the system a map. Instead of reconstructing meaning from raw passages at every query, it keeps interpretation: entities, relationships, claims, communities, each traceable back to the artifact it came from. Whether that map pays for itself is Chapter 4&amp;rsquo;s own question and Chapter 4&amp;rsquo;s own experiment; nothing here assumes its verdict.&lt;/p&gt;&#xA;&lt;p&gt;This chapter asks a question that arises either way. Suppose the map exists. A map is a structure to search. Remembering is not a search — or at least, human remembering does not feel like one. Something occurs to you, and something else follows from it, and the thing you needed arrives three steps later by a route you did not plan.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
