<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Memory Attribution on Programmer.ie: Modern AI programming</title>
    <link>http://programmer.ie/tags/memory-attribution/</link>
    <description>Recent content in Memory Attribution on Programmer.ie: Modern AI programming</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 18 May 2026 11:14:15 +0100</lastBuildDate>
    <atom:link href="http://programmer.ie/tags/memory-attribution/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Delta Memory: Cargo-Culting Human Memory with Search</title>
      <link>http://programmer.ie/post/delta/</link>
      <pubDate>Mon, 18 May 2026 11:14:15 +0100</pubDate>
      <guid>http://programmer.ie/post/delta/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;AI systems today have no idea why their own memory changes, that’s the problem we are trying to solve in this post.&lt;/p&gt;&lt;/blockquote&gt;&#xA;&lt;h2 id=&#34;summary&#34;&gt;Summary&lt;/h2&gt;&#xA;&lt;p&gt;Most AI memory systems start from a practical place: retrieval. Retrieval is useful, scalable, and often the right tool for the job. But if we want systems that interact with humans in more human‑like ways, we need a different analogy, not storage, but &lt;strong&gt;thinking&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Humans don’t store perfect records. We don’t retrieve exact text or replay video files. What we call “memory” is a shifting landscape of associations, impressions, weights, and patterns. When you recall something, you’re not pulling a file from disk, you’re running a &lt;strong&gt;search&lt;/strong&gt; across your internal world, shaped by everything you’ve lived through.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
