<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Resumability on Programmer.ie: Modern AI programming</title>
    <link>http://programmer.ie/tags/resumability/</link>
    <description>Recent content in Resumability on Programmer.ie: Modern AI programming</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 14 Sep 2026 05:00:16 +0100</lastBuildDate>
    <atom:link href="http://programmer.ie/tags/resumability/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Externalize Working Memory</title>
      <link>http://programmer.ie/books/applied-ai/16-chapter/</link>
      <pubDate>Mon, 14 Sep 2026 05:00:16 +0100</pubDate>
      <guid>http://programmer.ie/books/applied-ai/16-chapter/</guid>
      <description>&lt;p&gt;&lt;em&gt;Part 3 — Give Intelligence a Runtime&lt;/em&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-step-that-didnt-finish&#34;&gt;The step that didn&amp;rsquo;t finish&lt;/h2&gt;&#xA;&lt;p&gt;A process was reviewing a paragraph. It had compiled its context, recorded the call&amp;rsquo;s manifest, and sent the request. While the provider was still working on it, the process died.&lt;/p&gt;&#xA;&lt;p&gt;The standard recovery is familiar: restart, find the step that didn&amp;rsquo;t finish, and run it again. Someone did exactly that in this chapter&amp;rsquo;s experiment, on a copy of the dead process&amp;rsquo;s files, and the step re-ran to completion.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
