David F GliddenandClaude Opus 5
1a3a40fd12
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
2.9 KiB
2.9 KiB
name, description, metadata
| name | description | metadata | ||
|---|---|---|---|---|
| feedback-a-dated-measurement-is-not-a-status | A claim true when written reads later as present tense; re-measure a dated finding before ruling on it, not after. |
|
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:/Supersededlines 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