<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Replay on Stack Research</title><link>https://stackresearch.org/tags/replay/</link><description>Recent content in Replay on Stack Research</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 15 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://stackresearch.org/tags/replay/index.xml" rel="self" type="application/rss+xml"/><item><title>Memory Lineage Physical Time: TAI Mechanism and Heliocentric Coordinate</title><link>https://stackresearch.org/research/memory-lineage-physical-time-tai-and-heliocentric-coordinate/</link><pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate><guid>https://stackresearch.org/research/memory-lineage-physical-time-tai-and-heliocentric-coordinate/</guid><description>&lt;h2 id="why-this-matters-now"&gt;Why this matters now&lt;/h2&gt;
&lt;p&gt;Replay an agent&amp;rsquo;s memory and you replay its time bugs too. A hidden call to the clock returns a fresh value on every run, so two replays of one history no longer match—different bytes, and sometimes different decisions.&lt;/p&gt;
&lt;p&gt;UTC makes this worse. It was built for people and the turning Earth, and it can add or drop a leap second. Distributed-systems work has long flagged the trouble those jumps cause (&lt;a href="https://www.itu.int/hub/2023/05/synchronization-and-the-impact-of-utc-discontinuities/"&gt;ITU, &amp;ldquo;Synchronization and the impact of UTC discontinuities,&amp;rdquo; 2023&lt;/a&gt;). Which time you treat as the record is a design choice you can test.&lt;/p&gt;</description></item></channel></rss>