<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ai on Times New Rohan</title>
    <link>https://robrohan.com/tags/ai.html</link>
    <description>Recent content in Ai on Times New Rohan</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 05 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://robrohan.com/tags/ai/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Testing a Spatial Memory Index for Strap</title>
      <link>https://robrohan.com/2026/05/05/octree-memory-strap.html</link>
      <pubDate>Tue, 05 May 2026 00:00:00 +0000</pubDate>
      <guid>https://robrohan.com/2026/05/05/octree-memory-strap.html</guid>
      <description>&lt;p&gt;One of the pieces I still need to build for &lt;a href=&#34;https://therohans.com/strap/&#34;&gt;strap&lt;/a&gt; is a long-term memory store. As I&amp;rsquo;ve written about &lt;a href=&#34;https://robrohan.com/2026/04/26/adventures-local-coding-agent.html&#34;&gt;before&lt;/a&gt;, strap compresses context to work within small token budgets. But context compression only handles what&amp;rsquo;s in the current conversation. The bigger question is how to surface relevant memories from past sessions.&lt;/p&gt;&#xA;&lt;p&gt;The obvious approach is brute-force cosine similarity over sentence embeddings. It works for a small number of stored memories, and it&amp;rsquo;s fast enough. But I got curious whether a spatial index could do better, and whether you could make that index inspectable at the same time.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
