session 2026-08-17: PENDING-142/143/144/145 + REVIEWED-122/123 executed; wake detector rebuilt; 16 trackers stamped; 39 files' frontmatter repaired

Session record, ledger, index rotation and KG appends for the day the
instruments were audited and lost.

Filed: PENDING-142 (open/closed criterion answers an adjacent question) with
three addenda, PENDING-143 (carrier restoring PENDING-121 by hand), PENDING-144
(script-resident substrate claims are checked by nothing), PENDING-145 (a ruling
claims a NUMBER, not a record — PENDING-131's addenda suppressed on arrival, and
the unbuilt fence has never appeared in the open list).

Executed: REVIEWED-122 conds. 6/7/9-as-amended/11 and REVIEWED-123 conds. 1/2/3.
N-now recorded at 60/84 transcripts. Ladder frozen generally; 4 rows queued in
PENDING-141's owed-entries list, two of them earned today (mtime-is-not-content-age;
verify a bulk edit against the pre-change state from git). OWED-4 flagged as a
REWORDING to merge on lift rather than append beside.

Index rotated: prior Active Session demoted verbatim to MEMORY-reference.md,
new one promoted. MEMORY.md 20,242 bytes (83% of the 24.4 KB read limit) —
under budget but the restructuring task remains owed.

KG: 7 lines — 4 drift-patterns, 3 preventions, including the DEGRADED banner
catching its own author's regression and a confound filed against the executor's
own favourable evidence.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Y6t6qx7cpaCu5xGdD36u4

PENDING.md

@@ -3211,6 +3211,15 @@ So **PENDING-138 and this entry are worded to avoid the bare uppercase token**,
 >
 > ⚠ **A CONFOUND THE EXECUTOR OWES AGAINST ITS OWN POSITIVE INSTANCE.** The two cases differ in a variable the discriminator does not name: on 2026-08-17 PENDING-141 was sitting in `MEMORY.md`'s Active Session block, in bold, flagged *"BLOCKED — do not execute"*, and had been read aloud at that session's wake. On 2026-08-01 no equivalent prompt existed for the register split. So the positive instance may record **an index that named the instrument**, not an executor that found it — and the discriminator would then be measuring the memory layer while appearing to measure judgment. That is the same wrong-subject shape as OWED-1, turned on OWED-1's own sibling. **A cleaner test needs a case where the threatened instrument is NOT pre-named in the wake context.** Offered by the party the n=2 flatters, which is the only reason it is worth much.
 
+**OWED-3 — a file's timestamp is not its content's age.** · **Authorizing ruling: NONE — earned 2026-08-17, queued unruled.** · **Ladder claim-class: provenance and re-anchor claims.**
+> **mtime says when a file was last touched; git's last-commit says when it was last *committed*. Neither says when its content was last thought about, and a single mechanical sweep resets both across a whole tree.** Reach for the *earliest* signal that cannot be moved by an ordinary later act — git add-time for existence, the filename's own date for a dated record — and when a bulk operation is in the history, exclude it explicitly before quoting an age.
+>
+> Rule of three, discharged in one day: (1) 191 wrap records dated by mtime, so a CODA appended to the 08-14 record three days later made it look like that session never wrapped; (2) 61 trackers reported at "72.3 days" by mtime **and** by git-last-commit, both reset by `3f9a89b`, a 283-file normalization sweep — three successive staleness estimates were wrong before the fourth excluded it; (3) repairing 20 April–May wrap records moved their mtimes to today and promoted an April session to `Last wrap`, losing the pulling thread and the open question until the DEGRADED banner caught it. ⚠ **The third instance was self-inflicted by the fix for the first**, which is the entry's real warrant.
+
+**OWED-4 — verify a bulk edit against the pre-change state recovered from source control, never against the post-state matching your intent.** · **Authorizing ruling: NONE — earned 2026-08-17, queued unruled.** · ⚠ **This is a REWORDING of the existing `dry-run-first for bulk file operations` entry, not a new one — and rewordings are frozen too under REVIEWED-123 cond. 1.** Merge on lift rather than appending beside it.
+> A dry run shows what the tool *intends*. It cannot show what the tool will do to a file whose shape the tool misreads. On 2026-08-17 a 16-file stamping pass dry-ran clean, applied clean, and silently orphaned the frontmatter of the 3 files whose shape differed — and the post-hoc check reported `malformed: none`, because it asked whether each file *began with frontmatter and a banner* (true) rather than whether the stamp had *preserved the record's keys* (false).
+> **The check that worked was the one that could not be written from intent:** recover each file's pre-change text from git, extract its key set, and assert no key was lost. That control cannot be satisfied by a file the tool mangled, because its subject is the *difference* rather than the result.
+
 ---
 ## PENDING-142 — The open/closed criterion answers "does a REVIEWED header name this id?", not "is this item still awaiting the steward"
 **Date:** 2026-08-17