From 9f2a178a9e95f5db60e8fac039a5dccabeef8d32 Mon Sep 17 00:00:00 2001
From: Jeuner <62662523+Jeuners@users.noreply.github.com>
Date: Thu, 7 May 2026 13:50:09 +0200
Subject: [PATCH] Add observation on timestamps and LLMs

Added a new observation regarding timestamps and LLMs, emphasizing their interpretability and impact on system stability.
---
 README.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/README.md b/README.md
index 1094132..d95a9ba 100644
--- a/README.md
+++ b/README.md
@@ -37,6 +37,9 @@ Distributed systems literature treats time as a coordination problem to be solve
 > nicht weil die Clocks falsch laufen, sondern weil Timestamps für LLMs kein 
 > neutrales Metadatum sind. Sie sind interpretierbarer Inhalt.
 
+This observation is the point of departure for the framework developed in this paper.
+*(In short: as memory grew, agents began interpreting timestamps rather than using them — reconstructing timelines, losing focus, destabilising the system. Timestamps, it turned out, are not neutral metadata for an LLM. They are interpretable content.)*
+
 The conventional view treats time in distributed systems as a coordination challenge. Lamport's logical clocks [^1], Mattern's vector clocks [^2], and Spanner's TrueTime [^3] all approach the problem with the same implicit assumption: there is a real, objective time, and the engineering challenge is to approximate it consistently across participating nodes. The assumption is sound for distributed databases, where nodes are computationally homogeneous and clock divergence is bounded by network latency and physical drift.
 
 The assumption breaks for autonomous LLM-based agents.