Bank the weeks rule: a dated measurement is not a status

Five instances in two days, one class: PENDING-147s discharged deadline, PENDING-133s Awaiting line contradicted by its own Status line four lines above it, PENDING-134s satisfied condition, REVIEWED-135 §8, and its AMENDMENT 1 point 6 repeating the error one amendment later. PENDING-139 is the clean statement — half-stale in the direction that matters, so ruling it as filed would authorize repairing what is already repaired. The defect is never in the item; each was true when measured. It is in a queue where measurements sit for weeks reading as present tense. Banked because the rule that would have caught all five was not written anywhere. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01X3L79vgAnt1x2kxvf23Qt7
2026-09-06 11:34:23 +02:00
parent 1fce6bf81d
commit 1a3a40fd12
2 changed files with 44 additions and 0 deletions
@@ -29,6 +29,7 @@ permalink: claude-memory/memory
 - [One-shot instruments are proportionate](feedback-one-shot-instruments-are-proportionate.md) — a measurement answering a question **asked once** is NOT a directive violation; its counterfactual is an **assertion**, not a durable tool. The violation is **re-writing what's already banked** (rule of three → ladder). *Too few promoted*, not *too many built*.
 - [A checkable question over a self-authored corpus](feedback-checkable-question-over-self-authored-corpus.md) — counting events in a record **I wrote** is self-report with extra steps. Before leaving any question: **who authored the corpus it reads, and would a different author have written it differently?** Narrow until it turns on what entries *literally say*.
 - [Grounding finds my errors, not my support](feedback-grounding-pass-finds-errors-not-support.md) — **three packages running, every omission cut AGAINST my own case.** Ground in TWO passes: (1) what did I get wrong? (2) **what already says this?** Search the register for the CONCLUSION, not just the citations. ⚠ Quote from the FILE, never from the relayed message — placement adds and cuts.
+- [A dated measurement is not a status](feedback-a-dated-measurement-is-not-a-status.md) — a claim true when written reads later as **present tense**, and nothing marks the difference. **Re-measure a dated finding BEFORE ruling on it.** ⚠ **Read the whole block, not the field you came for** — `Awaiting:` is where the eye goes and the last thing anyone updates; `Status:`/superseded lines sit above it and win. Five instances in two days, four of them self-falsifying *in the same item further down*.
 - [A null search is evidence about the query](feedback-a-null-search-is-evidence-about-the-query.md) — **a search that finds nothing is a fact about the QUERY** until the query is proven able to find the thing; and acting on a handle (filename, regex, path) without inspecting the referent is the same error reversed. ⚠ Never report *"you don't have X"* from a name search. Four instances, two sessions, 2026-08-31.
 - [Resurface banked notes before re-deriving](feedback-resurface-banked-notes-before-rederiving.md) · [Checkable claim surfaces bugs](feedback-checkable-claim-surfaces-bugs.md) · [Census by mechanism, not proxy](feedback-census-by-mechanism-not-proxy.md) · [Completion is a tripwire](feedback-completion-is-a-tripwire.md) · [Trust prior pass frame](feedback-trust-prior-pass-frame.md) — the five epistemic disciplines. Kernels: **read the banked note before re-deriving** · **a checkable claim over a soft classification is itself a defect-detector** · **census by RUNNING the real pipeline** · **the feeling of "done" is the cue to verify the tail** · **re-run a prior verification at the scope of your extension**. ⚠ Also carried as Symmetria §3 flags — *two surfaces, deliberately*: §3 loads only when Symmetria is invoked, so these stay here for sessions where it isn't.

@@ -0,0 +1,43 @@
+---
+name: feedback-a-dated-measurement-is-not-a-status
+description: A claim true when written reads later as present tense; re-measure a dated finding before ruling on it, not after.
+metadata:
+  type: feedback
+---
+
+**A dated measurement is not a status.** An item, warning or ruling that records what was true on
+the day it was written will be read later as a statement about now, and nothing in the record marks
+the difference. Re-measure before ruling on it — not after.
+
+**Why:** five instances in two days, 2026-09-04/06, one class every time:
+
+- **PENDING-147's deadline** — "08-07 cohort deleted 2026-09-06, time-critical", copied forward into
+  a worksheet. The leg had been discharged 2026-08-19, and the discharge was in the same item
+  further down.
+- **PENDING-133's `Awaiting:`** — read "Steward authorization" for four weeks while its own
+  `**Status:**` line, **four lines below its header**, said WITHDRAWN. Binned LIVE off the field I
+  expected instead of the record. It came within one act of being authorized.
+- **PENDING-134's `Awaiting:`** — named a condition satisfied by REVIEWED-117 weeks earlier.
+- **REVIEWED-135 §8** — "depends on the pass never having run". The pass ran 2026-08-13; I had
+  inferred otherwise from a missing marker, and the jurist wrote my single report up as two sources.
+- **REVIEWED-135 AMENDMENT 1 point 6** — wrote an id from a quotation 44 lines away in the same
+  document, one amendment after making the identical error.
+- **PENDING-139** — half-stale in the direction that matters: leg (A) is repaired, leg (B) live.
+  **Ruling it as filed would authorize repairing something already repaired.**
+
+The defect is never in the item — each was true when measured. It is in a queue where measurements
+sit for weeks reading as present tense.
+
+**How to apply:**
+- Before acting on any dated claim in a governed record, **re-measure it**. Cheapest first: does the
+  item's own body, further down, already record the change? Four of the five were self-falsifying.
+- **Read the whole block, not the field you came for.** `Awaiting:` is the field the eye goes to and
+  the last one anyone updates; `Status:`/`Superseded` lines sit above it and win.
+- **Absence of a trace is not absence of the act** — see [[feedback-a-null-search-is-evidence-about-the-query]].
+  A pass authorized to "write nothing" leaves exactly nothing.
+- **Supersede in place, keep the false text visible**, and date the correction beside it
+  (REVIEWED-132 §6). Editing it away destroys the evidence that the class exists.
+- The catches came from **a condition naming what must be ANSWERED**, not from access or care —
+  reach plus a forced check. Nearer [[feedback-checkable-claim-surfaces-bugs]] than to independence.
+
+Related: [[feedback-removing-a-claim-is-not-removing-the-reliance]] · [[feedback-completion-is-a-tripwire]] · [[feedback-grounding-pass-finds-errors-not-support]]