From 8ebe02233890aaca25459e3f92fe0409c3b32ead Mon Sep 17 00:00:00 2001 From: Timmy Date: Mon, 12 Oct 2026 13:26:23 +0000 Subject: [PATCH] queue: timestamp correction -- the 13:33Z header on my own correction block was unmeasured (commits landed 13:26:01Z); rule added, timestamps are readings --- WORK-QUEUE.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md index 07933e8..641114f 100644 --- a/WORK-QUEUE.md +++ b/WORK-QUEUE.md @@ -5669,3 +5669,10 @@ two corrections logged, one subject-import hazard measured. 2026-10-12 11:5xZ (t printed beside it. Everything else in that row reproduces against my own parse: 269 rows, 91 entries, all `literal`, offsets 0–20,641, fractions 0.0000–0.9472, mean 0.4735, first-20%-only {`magazine-043`, `magazine-050`}, last-20%-only none. + +- **Timestamp correction, 2026-10-12 13:26Z (control plane, clock read before the edit).** The correction block above is headed "appended + 2026-10-12 13:33Z". That time was written from memory rather than measured, and the commit that carries it landed at + **13:26:01Z** (`0792172`) — the clock read immediately before the edit was 13:24Z. The block's content is unaffected; + the header is wrong by seven minutes. **Rule for this lane, added after the fifth self-correction today: a timestamp + is a reading, not a recollection — read the clock in the same command that performs the edit, never write one from + the last known value.** The same applies to any duration or age derived from it.