session 2026-08-26: PENDING-163/164/165 + five amendments; prior-art search built

Session record: the record did not contain the decision.

Filed: PENDING-163 (+3 amendments), PENDING-164 (jurist-drafted, placed verbatim,
+ executor addendum and build record), PENDING-165 (+1 amendment). Rulings
REVIEWED-130 and REVIEWED-131 placed by the steward.

Built: preserve-transcripts.py (PENDING-147 (i), 43 transcripts read-back proved),
two pre-commit fixes, the hook-directory allowlist in governance-drift-check.py,
and prior-art.py + the prior_art MCP tool (PENDING-164 (c)+(d)).

The finding: a steward decision that rewrote seventeen commits of history
(chamber-library 0677e8a, retiring LFS) is absent from the entire authorization
record, so both AI parties independently recommended adopting the mechanism it
retired. governance_search over 313 items returns one hit; grep over the raw files
returns zero before today.

Six self-referential instrument failures and three false zeroes, one of which was
caught before it was believed — and the only reason was that the jurist
pre-specified what the instrument had to return.

MEMORY.md rotated (prior Active Session demoted verbatim, checked for carried
claims first). 6 KG lines incl. one genuine transfer: the 2026-08-25 lesson about
declaring a limit rather than manufacturing a column fired unprompted on a
different instrument in a different item. One skill-harvest proposal, whose subject
is that today's own build ignored the routing table measurement it had open.

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

claude/governance/thread-query-log.jsonl

@@ -1,3 +1,4 @@
 {"date": "2026-08-24", "thread": "the turning exists but has never run in anger; whether the container should be shaped like the work — Darwin's chapters — rather than the session's thread", "terms": ["turning", "exists", "never", "anger", "whether", "container", "should", "shaped", "like", "work", "darwin's", "chapters", "rather", "session's", "thread"], "candidates": 868, "returned": [{"path": "~/Library/Mobile Documents/iCloud~md~obsidian/Documents/David, root-and-branch/08. Notes/Books.app highlights/Surviving an Eating Disorder.md", "date": "2025-04-20", "matched": ["turning", "exists", "never", "anger", "whether", "should", "like", "work", "rather", "thread"]}, {"path": "~/Library/Mobile Documents/iCloud~md~obsidian/Documents/David, root-and-branch/00. Compass/00b. Constellations/Animal Rationis Capax/99. Archives—Previous Iterations/99. The Chamber/00. Core Foundation/complete-amphitheatre/hybrid/turing-beyond-test.md", "date": "1953-01-01", "matched": ["never", "whether", "like", "work"]}, {"path": "~/Library/Mobile Documents/iCloud~md~obsidian/Documents/David, root-and-branch/08. Notes/Books.app highlights/Concerning the Spiritual in Art.md", "date": "2025-04-20", "matched": ["turning", "exists", "never", "whether", "should", "like", "work", "rather"]}, {"path": "~/Library/Mobile Documents/iCloud~md~obsidian/Documents/David, root-and-branch/00. Compass/00b. Constellations/Animal Rationis Capax/99. Archives—Previous Iterations/99. The Chamber/00. Core Foundation/complete-amphitheatre/weil-attention-gravity.md", "date": "1942-01-01", "matched": ["exists", "like", "work"]}, {"path": "~/Library/Mobile Documents/iCloud~md~obsidian/Documents/David, root-and-branch/08. Notes/Books.app highlights/The Longing for Less.md", "date": "2025-04-20", "matched": ["exists", "never", "whether", "should", "shaped", "like", "work", "rather"]}]}
 {"date": "2026-08-25", "thread": "the beacon, NIST randomness pulse, the Fool derivation run once, last act of the Fool before the fence resumes", "terms": ["beacon", "nist", "randomness", "pulse", "fool", "derivation", "once", "last", "fence", "resumes"], "candidates": 178, "returned": [{"path": "~/Library/Mobile Documents/iCloud~md~obsidian/Documents/David, root-and-branch/08. Notes/Books.app highlights/The Longing for Less.md", "date": "2025-04-20", "matched": ["randomness", "once", "last"]}, {"path": "~/Library/Mobile Documents/iCloud~md~obsidian/Documents/David, root-and-branch/08. Notes/Books.app highlights/The Lord of the Rings [Illustrated by the author, 2021].md", "date": "2025-04-20", "matched": ["fool", "once", "last"]}, {"path": "~/Library/Mobile Documents/iCloud~md~obsidian/Documents/David, root-and-branch/08. Notes/Books.app highlights/Mythos  A Retelling of the Myths of Ancient Greece.md", "date": "2025-04-20", "matched": ["fool", "once", "last"]}, {"path": "~/Library/Mobile Documents/iCloud~md~obsidian/Documents/David, root-and-branch/00. Compass/00b. Constellations/Animal Rationis Capax/Mid-longform articles/Vespers for the Living - Monteverdi with Jordi Savall.md", "date": "2025-06-08", "matched": ["pulse", "once", "last"]}, {"path": "~/Library/Mobile Documents/iCloud~md~obsidian/Documents/David, root-and-branch/03. People/Arthur Boynton Glidden Jr..md", "date": "2025-10-23", "matched": ["once", "last", "fence"]}]}
 {"date": "2026-08-25", "thread": "wire Tarbuckle the fool: status line body, 20-minute mumble tick, seam voice at wake and wrap", "terms": ["wire", "tarbuckle", "fool", "status", "line", "body", "minute", "mumble", "tick", "seam", "voice", "wake", "wrap"], "candidates": 640, "returned": [{"path": "~/Library/Mobile Documents/iCloud~md~obsidian/Documents/David, root-and-branch/08. Notes/Reflections/The Bark Came Off It — Seamus Heaney.md", "date": "2012-01-01", "matched": ["status", "line", "body", "seam"]}, {"path": "~/.claude/projects/-Users-davidglidden/memory/session-ledger-2026-04-18.md", "date": "2026-04-18", "matched": ["wire", "status", "line", "body", "minute", "voice", "wake", "wrap"]}, {"path": "~/.claude/projects/-Users-davidglidden/memory/session-ledger-2026-04-27.md", "date": "2026-04-27", "matched": ["wire", "fool", "status", "line", "body", "voice", "wake", "wrap"]}, {"path": "~/.claude/projects/-Users-davidglidden/memory/session-ledger-2026-05-30.md", "date": "2026-05-30", "matched": ["wire", "status", "body", "seam", "voice", "wake", "wrap"]}, {"path": "~/.claude/projects/-Users-davidglidden/memory/session-2026-05-01-to-2026-05-02-arc-compositional-arc-and-body-block-sidenote-architecture.md", "date": "2026-05-01", "matched": ["status", "line", "body", "voice", "wake", "wrap"]}]}
+{"date": "2026-08-26", "thread": "the §5 regrade gate — the control on the jurist's step 2 result is already degraded and decays with every exposure; blind grading, contaminated control, whether to run it or record it as degraded", "terms": ["regrade", "gate", "control", "jurist's", "step", "result", "already", "degraded", "decays", "every", "exposure", "blind", "grading", "contaminated", "whether", "record"], "candidates": 689, "returned": [{"path": "~/Library/Mobile Documents/iCloud~md~obsidian/Documents/David, root-and-branch/00. Compass/00b. Constellations/Animal Rationis Capax/99. Archives—Previous Iterations/99. The Chamber/00. Core Foundation/complete-amphitheatre/hermetic/ibn-arabi-artificial-divine-intelligence.md", "date": "1230-01-01", "matched": ["every", "blind", "whether"]}, {"path": "~/Library/Mobile Documents/iCloud~md~obsidian/Documents/David, root-and-branch/08. Notes/Books.app highlights/The Subtle Art of Not Giving a F*ck  A Counterintuitive Approach to Living a Good Life.md", "date": "2025-04-20", "matched": ["control", "step", "result", "already", "every", "blind", "whether", "record"]}, {"path": "~/.claude/projects/-Users-davidglidden/memory/session-ledger-2026-07-04.md", "date": "2026-07-04", "matched": ["gate", "jurist's", "step", "result", "already", "every", "blind", "grading", "contaminated", "record"]}, {"path": "~/Library/Mobile Documents/iCloud~md~obsidian/Documents/David, root-and-branch/08. Notes/Books.app highlights/Concerning the Spiritual in Art.md", "date": "2025-04-20", "matched": ["step", "result", "already", "every", "blind", "whether"]}, {"path": "~/Library/Mobile Documents/iCloud~md~obsidian/Documents/David, root-and-branch/08. Notes/Books.app highlights/The Shape of a Pocket.md", "date": "2025-04-20", "matched": ["control", "step", "result", "already", "every", "blind", "whether", "record"]}]}

claude/memory/MEMORY-reference.md

@@ -107,6 +107,19 @@ Split out of [MEMORY.md](MEMORY.md) on 2026-07-06 to keep the wake-loaded index
 
 ## Archived (2026-08-20 — the fence, the vault spec and Trial 09 held; demoted on promote at the 2026-08-20 wrap)
 
+<!-- demoted from MEMORY.md at the 2026-08-26 wrap -->
+## Active Session
+> 🔑 **TARBUCKLE IS WIRED — five surfaces, 125 controls** (`6f0ccde` `3df5e4f` `7a9dbf2` `acdbc09` `8a0e5c4` `cfbaded`). body · mumble · wake seam · wrap seam · `! tarbuckle`. §13.1 spec written LAST, per §12 — and four filed claims did not survive the substrate, which is why.
+> ⚠ **THE SESSION'S CENTRAL FINDING — PENDING-160, filed at the jurist's direction.** Five instruments, five passing control suites, **five failures on first real use.** Controls verify that code does what was written; **nothing verifies that what was written survives contact** with a model, a shell, or a corpus containing its own reader. ⚠ **Not a bad day — the class is months old**: `governance-mcp.py`'s own docstrings record it three times on 2026-07-28.
+> ⚠ **A FALSE PREMISE REACHED A PLACED RULING.** REVIEWED-129: *"the jurist has no substrate access"* — false (`governance-mcp.py`, 14 enumerated files) — **and the same sentence said "PENDING-82, still open", closed since 2026-08-08.** Third instance in one day of *a conclusion keeping its reasoning after that reasoning is falsified*. Draft correction at `claude/governance/REVIEWED-129-AMENDMENT-1-draft-for-placement.md` — **JOINS, never replaces.**
+> ⚖ **PENDING-151 RAN BOTH HALVES.** Step 1 (executor, mechanical): 9 pairs, **19,479 words exact**, and a confound in its own pre-registered measure — Claude longer **9/9**. Step 2 (jurist, unblinded): **A 4 · C 3 · B 0 — the null did not appear**, criterion amended mid-read on the executor's own length header. ⚠ **The surplus half of the question is unanswerable from this corpus.**
+> ⚠ **THE WRAP SEAM FAILED, WAS DIAGNOSED, FIXED, FIRED, AND WAS THEN REJECTED — all after the wrap.** The heartbeat proved the `Stop` hook was firing all along, so the silent-net prediction was **right that it would fail and wrong about why**. The detector sought the steward *typing* `/wrap-up`; the wrap arrived as prose + a Skill call. ⚠ **The earlier, correct fix is what blinded it.** PENDING-160's sixth and sharpest instance.
+> ⚠ **PENDING-162 `[ESCALATE]` — the executor breached REVIEWED-128 condition 3** within seven hours, reading the rejection log for content while diagnosing. **Conditions 1 and 2 were made structural; only 3 was left to care.** ⚠ It surfaced the clustering signal (2 seam rejections, 10 and 11 words vs a cap of 9) that the fortnight was meant to arbitrate — **not acted on, and must not be.**
+> 📌 **STEWARD OWES:** place the REVIEWED-129 amendment · rule PENDING-160 · **restart Claude Desktop** or `governance_pair` is absent · the §5 regrade ruling.
+> ✅ **DISCHARGED 2026-08-26 — the agreed first act, done.** The false `STEWARD OWES: place REVIEWED-127` line in `MEMORY-reference.md` is corrected (`7a92460`), **struck rather than deleted** so instance six keeps its evidence, and the `STATE-CLAIM` block carries `resolved:` with that pointer. ⚠ **This is one marked claim corrected in the very next session — evidence for expressibility, NOT for adoption**, which is the open question (REVIEWED-127 C2). The 57 unmarked claims are untouched.
+
+- [Session 2026-08-25 evening — Tarbuckle wired, and the gap controls cannot see](session-2026-08-25-tarbuckle-wired-and-the-contact-gap.md) — five surfaces built and every one failed on first real use; PENDING-151 step 1 + step 2 both run. **NEXT: the §5 regrade gate — the control is already degraded and decays with every exposure.**
+
 <!-- demoted from MEMORY.md at the 2026-08-25 evening wrap -->
 ## Active Session
 > 🔑 **THE BEACON FIRED AND THE DERIVATION RAN — ONCE, 2026-08-25T12:00Z** (`5694b92`). Peak **SUCCESSION 96** · dump **ABSENCE 8** · AIM 75 · SCALE 60 · STAKE 29. Seed `6ea9383b…f05d`. Announced by the trigger built the night before — **its first real firing, not a rehearsal.** Verified at execution, not relayed: selftest **16/16** (record said 12), provenance re-derived from git, seed recomputed independently, value asserted uppercase *at the call* — the step the 08-22 dry run silently bypassed. **DO NOT REGENERATE ANYTHING; both doors are ruled shut.**

claude/memory/MEMORY.md

@@ -72,16 +72,16 @@ permalink: claude-memory/memory
 - Chamber-typography — *tracker not yet established*; moves live in per-session memories (2026-05-11 →) + `project-chamber-cruft-restoration.md` + `project-chamber-typography-mining-plan-2026-05-15.md`.
 
 ## Active Session
-> 🔑 **TARBUCKLE IS WIRED — five surfaces, 125 controls** (`6f0ccde` `3df5e4f` `7a9dbf2` `acdbc09` `8a0e5c4` `cfbaded`). body · mumble · wake seam · wrap seam · `! tarbuckle`. §13.1 spec written LAST, per §12 — and four filed claims did not survive the substrate, which is why.
+> 🔑 **THE RECORD DID NOT CONTAIN THE DECISION — PENDING-164, and it is the day's finding.** On 2026-06-05 the steward adopted LFS in chamber-library, retired it, and **rewrote seventeen commits** to undo it (`0677e8a`); `400c054` built the per-repo exemption. **Neither appears anywhere in PENDING/PENDING-archive/REVIEWED.** Twelve weeks later BOTH AI parties independently recommended adopting LFS. `governance_search('LFS')`: **1 hit, PENDING-163 itself.** Grep over raw files: **0 before today.** ⚠ **The symptom is two parties missing prior art; the disease is that the record does not contain the decision, so only the party with a filesystem could find it — and the jurist has none** (`repo_activity` caps at 100 commits, five weeks short).
-> ⚠ **THE SESSION'S CENTRAL FINDING — PENDING-160, filed at the jurist's direction.** Five instruments, five passing control suites, **five failures on first real use.** Controls verify that code does what was written; **nothing verifies that what was written survives contact** with a model, a shell, or a corpus containing its own reader. ⚠ **Not a bad day — the class is months old**: `governance-mcp.py`'s own docstrings record it three times on 2026-07-28.
+> ✅ **BUILT: `prior-art.py` + `prior_art` MCP tool** (PENDING-164 (c)+(d), REVIEWED-131) — commit-message search across owned repos, **no count window**, register-mention count beside it. **One implementation, two surfaces.** On `LFS` returns 20 commits incl. `0677e8a` + `95760ff`. ⚠ **The positive control FORCED the enumeration to be computed from remotes** — copied from `REPOS`, `95760ff` (in dotfiles) was unreachable. **Had it existed that morning, one command would have returned the whole refutation.**
-> ⚠ **A FALSE PREMISE REACHED A PLACED RULING.** REVIEWED-129: *"the jurist has no substrate access"* — false (`governance-mcp.py`, 14 enumerated files) — **and the same sentence said "PENDING-82, still open", closed since 2026-08-08.** Third instance in one day of *a conclusion keeping its reasoning after that reasoning is falsified*. Draft correction at `claude/governance/REVIEWED-129-AMENDMENT-1-draft-for-placement.md` — **JOINS, never replaces.**
+> ⚠ **THE CENSUS'S SECOND HALF IS NOT MECHANICAL — and the backlog is NOT counted.** 661 candidates → 270 narrowed (243 outside dotfiles). Grepping verbs is mechanical; identifying *which mechanism* a commit decided about is interpretation. **Limit declared, not faked** (PENDING-151 step 1's shape). **270 unclassified, a few hours of reading, unscheduled and unclaimed.**
-> ⚖ **PENDING-151 RAN BOTH HALVES.** Step 1 (executor, mechanical): 9 pairs, **19,479 words exact**, and a confound in its own pre-registered measure — Claude longer **9/9**. Step 2 (jurist, unblinded): **A 4 · C 3 · B 0 — the null did not appear**, criterion amended mid-read on the executor's own length header. ⚠ **The surplus half of the question is unanswerable from this corpus.**
+> ⚠ **SIX SELF-REFERENTIAL INSTRUMENT FAILURES, THREE FALSE ZEROES.** `git lfs install --local` wrote into the **global** hook dir twice (2nd triggered by measuring LFS) · the whitespace census **returned a clean zero having measured nothing** (zsh newline splitting) · **the new hook-allowlist controls registered AFTER the tally, so a failure would have printed nothing** — the check against blind checks, blind to itself · `prior-art.py` returned zero for everything (`find` exits 1 on unreadable `Library` dirs while printing all 37 repos). 🔑 **The last was the ONLY false zero caught before it was believed, and the sole reason is that the jurist PRE-SPECIFIED what it must return.** The others were luck. **The difference is not care.**
-> ⚠ **THE WRAP SEAM FAILED, WAS DIAGNOSED, FIXED, FIRED, AND WAS THEN REJECTED — all after the wrap.** The heartbeat proved the `Stop` hook was firing all along, so the silent-net prediction was **right that it would fail and wrong about why**. The detector sought the steward *typing* `/wrap-up`; the wrap arrived as prose + a Skill call. ⚠ **The earlier, correct fix is what blinded it.** PENDING-160's sixth and sharpest instance.
+> ✅ **PENDING-147 (i) DISCHARGED — 43 transcripts, 115 MB, at `~/_Dev/claude-transcript-archive`**, read-back PASS, re-runnable instrument. ⚠ **NOT git-tracked and NOT backed up** — no Time Machine destination exists on this machine. Living outside the pruned path is what stopped the clock; git was never the load-bearing part.
-> ⚠ **PENDING-162 `[ESCALATE]` — the executor breached REVIEWED-128 condition 3** within seven hours, reading the rejection log for content while diagnosing. **Conditions 1 and 2 were made structural; only 3 was left to care.** ⚠ It surfaced the clustering signal (2 seam rejections, 10 and 11 words vs a cap of 9) that the fortnight was meant to arbitrate — **not acted on, and must not be.**
+> ⚠ **THE HOOK WAS BROKEN TWO WAYS.** Line 45 word-split on paths, so **a 17 MB file with a space in its name passed the 5 MB ceiling entirely** (`ecee76b`; 10 such files exist and could only have entered through it). And its message recommended LFS, which cannot satisfy it (`2408032`, **jurist-drafted — two edits I would have shipped wrong**). PENDING-165: git-lfs **launders** shims into the governed dir — `066a47a` COMMITTED them, tracked four weeks. (d) allowlist + (b) narrow gitignore built; ⚠ **my (d) was blind to that very occurrence** — the jurist caught it, on **my own standard**.
-> 📌 **STEWARD OWES:** place the REVIEWED-129 amendment · rule PENDING-160 · **restart Claude Desktop** or `governance_pair` is absent · the §5 regrade ruling.
+> 📌 **STEWARD OWES:** **move the pre-LFS snapshot** to the MemPalace drive (⚠ **move, don't `migrate export`**; must carry `.git/lfs/objects`, 552 obj / 975 MB; **399/399 resolve locally**; read back at destination) · place the REVIEWED-129 amendment · rule PENDING-160 · **restart Claude Desktop — now also gates `prior_art`**, else the tool built to close the jurist's blindness is built-and-inert · the §5 regrade ruling.
-> ✅ **DISCHARGED 2026-08-26 — the agreed first act, done.** The false `STEWARD OWES: place REVIEWED-127` line in `MEMORY-reference.md` is corrected (`7a92460`), **struck rather than deleted** so instance six keeps its evidence, and the `STATE-CLAIM` block carries `resolved:` with that pointer. ⚠ **This is one marked claim corrected in the very next session — evidence for expressibility, NOT for adoption**, which is the open question (REVIEWED-127 C2). The 57 unmarked claims are untouched.
+> ⚠ **THE §5 REGRADE GATE WAS THIS SESSION'S INHERITED THREAD AND WAS NEVER TOUCHED.** Recorded as untouched rather than quietly dropped.
 
-- [Session 2026-08-25 evening — Tarbuckle wired, and the gap controls cannot see](session-2026-08-25-tarbuckle-wired-and-the-contact-gap.md) — five surfaces built and every one failed on first real use; PENDING-151 step 1 + step 2 both run. **NEXT: the §5 regrade gate — the control is already degraded and decays with every exposure.**
+- [Session 2026-08-26 — the record did not contain the decision](session-2026-08-26-the-record-did-not-contain-the-decision.md) — two chores opened a four-round jurist exchange that found the record's gap; PENDING-163/164/165 + five amendments; REVIEWED-130/131. **NEXT: the 270 uncounted candidates — the instruments are done, the backlog is not.**
 
 ## Historical reference → MEMORY-reference.md
 Older archived-session pointers and the stable reference layer (steward profile · project-state detail · L1/L2/Chamber inventories · legacy pending-work · reference-file list) live in [MEMORY-reference.md](MEMORY-reference.md) — consult on demand; not loaded at wake. Recent cross-session trajectory comes from the Active Session entry above + the recent `session-*.md` files (wake §2.b.1).

claude/memory/knowledge-graph.jsonl

@@ -731,3 +731,9 @@
 {"subject": "declaring a limit instead of manufacturing the column", "predicate": "prevention", "object": "STOPPED STEP 1 FROM BECOMING STEP 2 IN DISGUISE. PENDING-151's pre-registration asked for terms, entities AND propositions. Propositions cannot be extracted mechanically \u2014 it requires reading for claims \u2014 and the only reader available at step 1 was the party barred from judging. Building that column with a model would have been the forbidden judgement wearing the permitted step's clothes. Declaring it absent kept the routing intact, and the jurist then judged propositions itself from the raw pairs.", "valid_from": "2026-08-25", "valid_to": null, "confidence": 0.95, "source_file": "session-2026-08-25-tarbuckle-wired-and-the-contact-gap.md", "extracted_at": "2026-08-25"}
 {"subject": "the steward's mandated commensurability check", "predicate": "prevention", "object": "FOUND A COLLISION IN THE DIRECTION NOBODY WAS LOOKING. The check was ordered for any periodicity tier 3 introduced; a seam is aperiodic, so the answer looked trivially empty. Running it anyway surfaced that the mumble's clock file PERSISTS ACROSS SESSIONS, so any gap over the interval left a tick already due at the moment of waking \u2014 the fool would have spoken twice into the same seam. An instrument aimed at one thing caught another because it was actually run.", "valid_from": "2026-08-25", "valid_to": null, "confidence": 0.95, "source_file": "session-2026-08-25-tarbuckle-wired-and-the-contact-gap.md", "extracted_at": "2026-08-25"}
 {"subject": "chamber-v1 archive", "predicate": "has-property", "object": "9 complete formation pairs, 6 sessions, 3 protocol axes, 19479 words raw+submitted, 33 real content files. '55 files' is the AppleDouble-inclusive count and is unstable across days. Claude arm longer in 9 of 9 pairs, 1.41x-3.40x \u2014 formation and length are perfectly confounded, so the surplus half of PENDING-151's question is unanswerable from this corpus.", "valid_from": "2026-08-25", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-25-tarbuckle-wired-and-the-contact-gap.md", "extracted_at": "2026-08-25"}
+{"subject": "claude-code", "predicate": "drift-pattern", "object": "A POLICY QUESTION MANUFACTURED BY MY OWN ERROR. PENDING-163 went to the steward as a decision between two options because the item claimed option (ii) 'widens what may be committed everywhere'. It does not: git cat-file -s reads the STAGED blob, so an LFS-tracked file measures 133 bytes and a plain one still measures 17MB and is still refused. The claim was false by a category, it made one option look safer and the other costlier than either was, and the steward's time was spent on a fork that did not exist. Not a judgement call under uncertainty — a confident wrong claim that generated a decision.", "valid_from": "2026-08-27", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-26-the-record-did-not-contain-the-decision.md", "extracted_at": "2026-08-27"}
+{"subject": "claude-code", "predicate": "drift-pattern", "object": "DID NOT CHECK PRIOR ART, AND WAS THE ONLY PARTY WHO COULD. Both AI parties recommended adopting Git LFS twelve weeks after the steward had tried it, documented why it failed, and rewritten seventeen commits to undo it. The jurist COULD NOT have found it — repo_activity caps at 100 commits, five weeks short of 0677e8a — so 'search prior art before proposing' is not a rule it can follow. The executor has a filesystem and did not look until the string 'pre-lfs-export' appeared in an unrelated directory listing. The asymmetry is structural; the failure to use it was not.", "valid_from": "2026-08-27", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-26-the-record-did-not-contain-the-decision.md", "extracted_at": "2026-08-27"}
+{"subject": "claude-code", "predicate": "drift-pattern", "object": "THE CHECK AGAINST BLIND CHECKS WAS BLIND TO ITSELF. Five new controls for the hook-allowlist registered AFTER failed_controls is computed (line 846 vs 702): all ran, none counted, the tally still read 48/48, and a failure among them would have printed NOTHING. Built in the same hour as, and as the fix for, the class 'a check that passes because it could not run' — immediately after the jurist had caught the previous blindness in the same item. Caught only by comparing the printed tally against the number of controls I knew I had added.", "valid_from": "2026-08-27", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-26-the-record-did-not-contain-the-decision.md", "extracted_at": "2026-08-27"}
+{"subject": "claude-code", "predicate": "drift-pattern", "object": "THREE FALSE ZEROES IN ONE DAY, EACH FROM A DIFFERENT MECHANISM. (1) A zsh loop over a newline-joined string iterated once and printed 'NONE' having measured nothing. (2) sh() discarded stdout on non-zero exit, and find over $HOME exits 1 from unreadable Library dirs WHILE printing all 37 repos, so every prior-art search returned zero. (3) The uncounted controls above. A clean zero is the most dangerous output an instrument produces, because it is indistinguishable from a real negative and carries the same confidence.", "valid_from": "2026-08-27", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-26-the-record-did-not-contain-the-decision.md", "extracted_at": "2026-08-27"}
+{"subject": "the jurist pre-specifying what an instrument MUST return", "predicate": "prevention", "object": "STOPPED A FALSE ZERO FROM BEING BELIEVED — the only one of three that day caught before it was acted on. The jurist specified, before prior-art.py was written, that its positive control must return 0677e8a and 95760ff or it measured nothing. Its first run returned zero for every term (find exits 1 on unreadable dirs; stdout was being discarded), and the control failed loudly instead of the tool reporting 'no prior art' forever. The other two false zeroes that day were caught by luck — an echoed cd error, and a tally that looked one short. The difference between them is not care; it is that someone external named the expected output in advance.", "valid_from": "2026-08-27", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-26-the-record-did-not-contain-the-decision.md", "extracted_at": "2026-08-27"}
+{"subject": "declaring a limit instead of manufacturing the column (banked 2026-08-25, PENDING-151 step 1)", "predicate": "prevention", "object": "STOPPED A DIFFERENT INSTRUMENT FROM FAKING ITS SECOND HALF, TWELVE DAYS LATER AND IN ANOTHER ITEM. PENDING-164's census has two halves: grep adoption/retirement verbs (mechanical), then check each hit against the register (requires reading each commit to identify WHICH mechanism it decided about — interpretation). The verb grep returned 661, narrowed to 270. The lesson from PENDING-151 — where propositions could not be extracted mechanically and the column was declared absent rather than built with a model — fired here unprompted: the census reports 270 UNCLASSIFIED candidates and states that the backlog is not censused. This is transfer, not repetition: different item, different instrument, same shape.", "valid_from": "2026-08-27", "valid_to": null, "confidence": 0.95, "source_file": "session-2026-08-26-the-record-did-not-contain-the-decision.md", "extracted_at": "2026-08-27"}

claude/memory/session-2026-08-26-the-record-did-not-contain-the-decision.md

@@ -0,0 +1,169 @@
+---
+name: Session 2026-08-26 — the record did not contain the decision
+description: "Two steward tasks (preserve the transcripts, correct the false STEWARD OWES line) opened a four-round exchange with the jurist that produced the day's real finding: a steward decision consequential enough to rewrite seventeen commits of history was absent from the ENTIRE authorization record, so both AI parties independently recommended a mechanism that had been tried and retired twelve weeks earlier. PENDING-163/164/165 filed with five amendments; REVIEWED-130 and REVIEWED-131 placed; prior-art search built as (c)+(d). Six self-referential instrument failures, three false zeroes, two caught by controls. PULLING THREAD: the 270 uncounted census candidates — the backlog of decisions that never reached the record, whose base rate today showed is not low."
+type: project
+metadata:
+  node_type: memory
+  type: project
+  modified: 2026-08-26
+---
+
+# Session 2026-08-26 — the record did not contain the decision
+
+## PAST — what moved, and why
+
+### The two asked-for tasks (both done inside the first hour)
+
+**Transcripts preserved** (PENDING-147 option (i)) — 43 files, 115 MB, to
+`~/_Dev/claude-transcript-archive`, read-back PASS. Built as a re-runnable instrument
+(`scripts/preserve-transcripts.py`) rather than a one-shot, because the retention window keeps
+moving. **All 43, not the 23 the item scoped** — the files expiring soonest are the older ones
+and they are the only residual baseline material. ⚠ **The option bundles a second act its own
+no-ruling justification does not license** (*"re-express the trigger"* changes an instrument a
+placed ruling leans on, inside the REVIEWED-123 freeze). Split; only the copy done.
+
+⚠ **Git refused it three times** — dotfiles' 5 MB hook, the same hook globally in a dedicated
+repo, then Git LFS, which the hook itself recommends. **No guard was bypassed.** The honest
+read: git was never the load-bearing part; living outside the pruned path is what stopped the
+clock, and the real gap is that **no Time Machine destination is configured on this machine**.
+
+**The false `STEWARD OWES: place REVIEWED-127` line corrected** (`7a92460`) — verified at
+`REVIEWED.md:2218` first rather than inheriting yesterday's claim. **Struck, not deleted**: the
+line is the evidence for instance six. `resolved:` set with a commit pointer, form derived from
+the parser, which is why the correction commit had to come first. Verified end-to-end by
+re-running: `1 of 3 NOW FALSE` → `2 tracked, none falsified`.
+
+### Then the cascade — four rounds with the jurist, and the day's actual finding
+
+**PENDING-163** (the hook recommends Git LFS but measures the working-tree file, so its own
+advice cannot satisfy it) went to the steward as a policy question. **It should not have.** The
+jurist showed the item **overstated option (ii)'s cost by a category** — `git cat-file -s` reads
+the *staged blob*, so (ii) admits only deliberately LFS-tracked files, not large files generally.
+That mis-sizing is what manufactured the "policy question."
+
+Then, checking something unrelated, the string `pre-lfs-export` appeared in a directory listing:
+
+> **`0677e8a`, 2026-06-05** — *"retire LFS — corpus is plain text in git proper … the Gitea
+> remote carries no LFS endpoint, so pointers made the remote a non-backup."* Seventeen commits
+> of history rewritten to undo it. **`400c054`** then built the per-repo hook exemption that
+> option (iii) was proposing to invent.
+
+⚠ **Both AI parties had spent the afternoon reasoning toward a mechanism the steward had tried,
+documented and retired twelve weeks earlier.** `governance_search('LFS')` over 313 items: **one
+hit — PENDING-163 itself.** Grep over the raw files, independently: **zero mentions before
+today.** Two instruments sharing no code, same answer.
+
+**PENDING-164** (the jurist's item, placed verbatim): the symptom is two parties missing prior
+art; **the disease is that the record where such a decision is supposed to be findable does not
+contain it**, so the only party who could have found it is the one with a filesystem. The jurist
+*could not* — `repo_activity` caps at 100 commits, a floor five weeks short of `0677e8a`.
+
+**PENDING-165** (the hook laundering): git-lfs writes four shims into `core.hooksPath`, which
+here is the **global** directory for 37 repos. The jurist asked the decidable question — is a
+*governed* hook overwritten? **No.** But `066a47a` (2026-03-20) **committed the shims into
+dotfiles** and they sat tracked for four weeks. **Not overwriting — laundering.** REVIEWED-105's
+converse: an ungoverned hook that looks governed.
+
+### What was built
+
+| | |
+|---|---|
+| `preserve-transcripts.py` | PENDING-147 (i); idempotent, read-back proved |
+| pre-commit line-45 `[FIX]` (`ecee76b`) | unquoted `$( )` word-split on paths; a 17 MB file with a space in its name passed the ceiling entirely |
+| pre-commit message (`2408032`) | stops recommending LFS; **jurist-drafted, two edits I would have shipped wrong** |
+| drift-check hook allowlist | PENDING-165 (d) — declares contents, **never consults tracked-ness** |
+| `.gitignore`, four names | PENDING-165 (b), deliberately narrow |
+| `prior-art.py` + `prior_art` MCP tool | PENDING-164 (c)+(d), **one implementation, two surfaces** |
+
+## PRESENT — how it stands
+
+**The mood.** A day that began with two small chores and ended having found that the
+authorization record does not contain the decisions the system makes. Four rounds with the
+jurist, each of which improved the item and two of which reversed my recommendation. The
+correction traffic ran in every direction — which is the doctrine working, and the first day
+it has been legible as such.
+
+**⚠ Six self-referential instrument failures, and three false zeroes.**
+1. `git lfs install --local` wrote into the **global** hook dir (`--local` overridden by
+   `core.hooksPath`), twice — the second time triggered by the measurement of LFS itself.
+2. The whitespace census **returned a clean zero having measured nothing** (zsh does not
+   word-split on newlines). Caught by an echoed `cd` error, not by design.
+3. The new hook-allowlist controls registered **after** `failed_controls` is computed — all
+   five ran, none counted, **a failure would have printed nothing.** The check against blind
+   checks, blind to itself.
+4. `prior-art.py`'s first run returned **zero for everything** — `sh()` discarded stdout on
+   non-zero exit, and `find` over `$HOME` exits 1 from unreadable `Library` dirs *while printing
+   all 37 repos*. **Caught by the jurist's pre-specified positive control.**
+5. Extending the read-only guarantee found `str.replace()` false-flagged as a mutation — which
+   is *why* the guarantee had never been extended past one file.
+6. `wake-digest.py` was a delegate outside the read-only proof **since before today**.
+
+⚠ **The one that matters: #4 is the first false zero of the day caught BEFORE it was believed,
+and the only reason is that the jurist pre-specified what the instrument must return.** #2 was
+caught by luck. The difference between them is not care.
+
+**Confidence to recalibrate.**
+- ⚠ **I put a policy question to the steward that was an artefact of my own error.** Not a bad
+  call under uncertainty — a wrong claim, stated confidently, that manufactured a decision.
+- ⚠ **I did not check prior art before filing**, and I was the only party who could.
+- ⚠ **PENDING-165 (d) as I filed it was blind to the only occurrence that did damage.** The
+  jurist caught it; the standard it failed (*which failure class can this green check see*) is
+  **my own**, and I did not apply it to my own filing.
+- ⚠ **`prior-art.py` (d) is a CLI requiring executor recall** — the measured routing table puts
+  that at **~10% retrieval**. Built and not wired. See §1.6.
+
+**What held.** Reported `thread-query`'s null honestly. Did not open the rejection log.
+Substrate-checked PENDING-147 (i) as unbuilt rather than reading its own recommendation.
+Refused three chances to bypass the pre-commit guard. Applied the *non-defect-as-defect* flag
+before filing PENDING-163. Verified the steward's REVIEWED-130 placement content-faithful
+(5,889 chars, identical) before committing it.
+
+**Instruments:** 4 built · 4 carrying controls written before first execution · **K = 0
+duplications**. ⚠ The K=0 is weaker than it looks: `prior-art.py` (c) and (d) were built as one
+implementation *specifically to avoid* computing the same value on two sides of a boundary —
+that was a deliberate avoidance, not an absence of temptation.
+
+## FUTURE — what pulls
+
+**The pulling thread: the 270 uncounted census candidates — the backlog of decisions that never
+reached the record. Today showed the base rate is not low, and nothing recovers the backlog.**
+
+PENDING-164 (c) and (d) prevent the *next* loss. Neither recovers what is already lost. The
+census's mechanical half ran (661 candidates, narrowed to 270, 243 outside dotfiles); its
+interpretive half — *which mechanism did this commit decide about, and is it in the register* —
+**is not mechanical and was declared as a limit rather than faked.** ⚠ **Two instances surfaced
+today and NEITHER WAS SOUGHT.** That is evidence about the base rate, not about luck.
+
+**Actionable resumption point (as of wrap — re-judge against what changed):**
+
+1. **⚠ First, and steward-dated:** move `~/_Dev/chamber-library.pre-lfs-export-20260605` to the
+   decommissioned-MemPalace drive. **Move, do not `git lfs migrate export`** — rewriting commits
+   destroys the exact-preservation property that is the snapshot's only purpose. **Must carry
+   `.git/lfs/objects`, 552 objects / 975 MB.** Verified 2026-08-26: **399/399 resolve locally,
+   0 remote-only**, so a whole-directory copy is complete and only a whole-directory copy is.
+   **Read back at the destination.** Then PENDING-165 (c) is free.
+2. **The classification pass:** 270 candidates, a few hours of reading. Unscheduled, unclaimed.
+   ⚠ Do not let the instrument's existence stand in for the count.
+3. **Wire (d) into a ritual** or accept ~10% (§1.6 proposal).
+4. ⚠ **The §5 regrade gate was this session's inherited thread and was never touched.** It is
+   the steward's and jurist's to settle; recorded as untouched rather than quietly dropped.
+
+**Other horizons.** *Steward's:* place the REVIEWED-129 amendment · rule PENDING-160 · restart
+Claude Desktop (⚠ **now also gates `prior_art`** — the tool built to close the jurist's blindness
+is absent until then, which would make it built-and-inert). *Dated:* **2026-09-08 carries two
+obligations** — the mumble rate report and the rejection log's deletion.
+
+**Pause statement.** I am about to be away from this. What I want to find still pulling is the
+**backlog**, not the instruments — because the instruments are done and satisfying, and the
+count is not, and the temptation across a pause is to treat a built tool as a discharged
+obligation.
+
+**Literal question for next-Claude** *(checkable; it turns on the record, not on introspection)*:
+
+**Was `prior-art.py` run before the next `[PROPOSAL]` or `[HARDENING]` that names a mechanism —
+and if not, what fired instead?** Check `git log` for the next such item filed after 2026-08-26,
+then check whether anything in the session record shows a prior-art run preceding it. ⚠ This is
+PENDING-164 (d)'s own falsifier turned on the instrument built today: the routing table measured
+**0% retrieval for capabilities requiring executor recall**, and (d) shipped as exactly that. If
+it did not fire, the finding is not "I forgot" — it is that **the routing table predicted this
+and the build ignored it**, which is a design defect, not a discipline one.

claude/memory/skill-harvest-register.md

@@ -565,3 +565,13 @@ floor question in the executor's favour.
 ⚠ **Caught by doing it, not by inspection.** The trap was noticed only while writing the
 rotation code and asking what happened to the line. Nothing in `/wrap-up` would have surfaced
 it, which is the argument for the step.
+
+## Proposed 2026-08-26 wrap — awaiting steward
+
+| # | kind | target | proposal | firing moment | routing |
+|---|---|---|---|---|---|
+| — | patch | `governance-drift-check.py` (detector, **not** a skill) | **PENDING-164 (d) shipped as a CLI requiring executor recall — the exact class the routing table measures at ~10%, and at 0% for the 53 skills needing recall.** `prior-art.py` exists and works; nothing makes it fire. Proposed: the drift-check reports any `PENDING-*` item filed since its last run whose title or summary names a term with **commit history and zero prior register mentions** — the asymmetry `prior_art` already computes. ⚠ **Honest limits, stated before building:** (a) it fires **after** filing, not before — but before the steward rules, which is where the LFS error actually cost something; (b) extracting "the mechanism named by this item" is the same interpretive step that defeated the census, so a keyword heuristic will over- and under-fire; (c) it therefore catches the *loud* case (a named tool) and not the quiet one. **Filed as a detector because the alternative is a discipline the routing table already measured at ~10%, and today's build ignored that measurement while the item recording it was open in the same session.** | **at every `governance-drift-check.py` run** — i.e. every wake, already a ritual | mechanical detector (the strong tier) |
+
+⚠ **Why this is a `[PROPOSAL]` and not the FIX lane.** It adds a *required check* to a governed instrument rather than changing what that instrument records, and the first clause of the classification test — "what the executor may do without asking" — is arguable either way. The lane's own instruction is *when in doubt, propose*. It also touches `governance-drift-check.py`, which REVIEWED-95's falsifier leans on; the ladder trial is frozen under REVIEWED-123 and **adding a reporting section is not obviously outside that freeze's spirit even though it is outside its letter.** That doubt alone routes it here.
+
+⚠ **The self-referential note, since it is the point.** This proposal exists because the executor built (d) as a recall-dependent CLI **on the same day, in the same item, as the register line recording that recall-dependent capabilities fire at ~0%.** The measurement was in front of me and the build ignored it. That is not a discipline failure to be fixed with more care — it is the routing table's own thesis, demonstrated at its own expense.