From 4b9de3f25fc3f930750d6883c839a2ef80ce2129 Mon Sep 17 00:00:00 2001 From: Timmy Date: Tue, 13 Oct 2026 02:04:43 +0000 Subject: [PATCH] queue: erratum -- the erratum header reads 02:07Z; clock at write time was 02:04:36Z, commit 1478ce9 at 02:04:28Z --- WORK-QUEUE.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/WORK-QUEUE.md b/WORK-QUEUE.md index 86bba21..3504ec6 100644 --- a/WORK-QUEUE.md +++ b/WORK-QUEUE.md @@ -6596,3 +6596,11 @@ Deliverable `recoveries/helm-parse-guard.md` (12,284 B / sha256 `19fa3ff6d25c85c - **Lane rule, added because this is the second time the shape has bitten:** a count of occurrences inside a file that the same append modifies must be stated as an as-measured reading ("at HH:MMZ, before this block") or left out. The same reason a file cannot hash itself, applied to counts. + +**Erratum on the erratum's header: 02:04Z, not 02:07Z. 2026-10-13 02:04:36Z (control plane).** + +- The block above is headed "2026-10-13 02:07Z". The clock read **02:04:36Z** immediately before this line, and the + commit it landed in is `1478ce9` at 02:04:28Z, so the header named a minute that had not happened. The substance is + unaffected; the header is a mis-set date of exactly the kind this lane has corrected twice before, and it is + corrected here rather than edited in place. Rule already on the books and re-learned: the timestamp is a **reading**, + taken immediately before the edit — a header written from pattern rather than from the clock is a fabricated value.