<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Agent Memory on AIBussin — AI applications, systems and books</title>
		<link>https://aibussin.com/tags/agent-memory/</link>
		<description>Recent content in Agent Memory on AIBussin — AI applications, systems and books</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Sat, 08 Aug 2026 17:14:00 +0100</lastBuildDate>
		
			<atom:link href="https://aibussin.com/tags/agent-memory/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Memory and Selective Recall</title>
				<link>https://aibussin.com/books/agents-from-first-principles/08-chapter/</link>
				<pubDate>Sat, 08 Aug 2026 17:14:00 +0100</pubDate>
				<guid>https://aibussin.com/books/agents-from-first-principles/08-chapter/</guid>
				<description>&lt;p&gt;The capability boundary gave the agent a defined action space and a rule for which capabilities are eligible at each step. Runtime state gave it an explicit working representation of what this run has established so far and how it reached that point. Together they govern the current execution, but neither gives information from an earlier run a controlled way to influence this one. There is a family of failures that requires exactly that.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Delta Memory: Cargo-Culting Human Memory with Search</title>
				<link>https://aibussin.com/post/delta/</link>
				<pubDate>Mon, 18 May 2026 11:14:15 +0100</pubDate>
				<guid>https://aibussin.com/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;&#xA;&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>
