<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hybrid-Logical-Clock on Stack Research</title><link>https://stackresearch.org/tags/hybrid-logical-clock/</link><description>Recent content in Hybrid-Logical-Clock 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/hybrid-logical-clock/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;Agent memory that is replayed or audited inherits every time bug the codebase carries. When a derivation step silently calls a &amp;ldquo;now&amp;rdquo; primitive, two replays of the same nominal history can diverge in bytes and in downstream decisions. That failure mode is orthogonal to intent: it is an engineering fact about implicit clocks.&lt;/p&gt;
&lt;p&gt;A parallel issue is representational. Civil calendars and stepped scales—UTC with its leap-second policy—are built for human coordination and Earth rotation, not for &amp;ldquo;same input, same output&amp;rdquo; lineage. The telecommunications and distributed-systems literature documents operational friction from that discontinuity class (&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;). Choosing what to treat as canonical time for append-only history is therefore a design decision with testable consequences.&lt;/p&gt;</description></item></channel></rss>