<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Temporal Context on Programmer.ie: Modern AI programming</title>
    <link>http://programmer.ie/tags/temporal-context/</link>
    <description>Recent content in Temporal Context on Programmer.ie: Modern AI programming</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 23 Sep 2026 05:00:20 +0100</lastBuildDate>
    <atom:link href="http://programmer.ie/tags/temporal-context/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Context Goes Stale</title>
      <link>http://programmer.ie/books/context/20-chapter/</link>
      <pubDate>Wed, 23 Sep 2026 05:00:20 +0100</pubDate>
      <guid>http://programmer.ie/books/context/20-chapter/</guid>
      <description>&lt;p&gt;The agent reads the project&amp;rsquo;s decision record at repository version C1: backend SQLite, migration failing, README describing the current backend. It plans accordingly. By the time it acts, the repository is at C5. The decision record now says PostgreSQL, the migration passes, the README was rewritten twice. Nothing in the agent&amp;rsquo;s context changed — which is exactly the failure. The captured observation was authoritative, relevant, well-represented, and faithfully preserved. It described a state that no longer exists, and the model configured SQLite with complete confidence. Every chapter before this one asked whether information should enter context. This one asks whether what entered is still true of the world it claims to describe.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
