session 2026-08-31 (afternoon): the loop removed by a restart; PENDING-172/-175 + two builds

Session record, KG (9 lines incl. one soft-invalidate), the null-search feedback
memory, and MEMORY.md.

MEMORY.md: the afternoon Active Session is ADDED ALONGSIDE the morning's rather
than promoting-and-demoting it. Two sessions ran today and both wrapped; the
protocol is date-keyed and single-writer, which is PENDING-174, filed today.
Neither record supersedes the other.

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

.gitconfig

@@ -14,3 +14,5 @@
 	insteadOf = https://github.com/
 [core]
 	hooksPath = /Users/davidglidden/dotfiles/git/hooks
+[safe]
+	directory = /Volumes/on ice/_dev/chamber-library.pre-lfs-export-20260605

Brewfile

@@ -132,7 +132,6 @@ mas "TestFlight", id: 899247664
 mas "Vinegar", id: 1591303229
 mas "Xcode", id: 497799835
 mas "xSearch", id: 1579902068
-npm "@anthropic-ai/claude-code"
 npm "corepack"
 npm "mcp-remote"
 npm "wrangler"

PENDING.md

@@ -760,6 +760,29 @@ Measured against the register itself before acting. Four corrections; the item's
 **Files affected:** none yet; a measurement, not a change. Output would be a dated record beside the doctrine package.
 **Awaiting:** Steward direction on (a)/(b)/(c), and on whether the executor is the right party to run a measurement of its own oversight at all — the jurist is no more independent here, so this may be steward-only work.
 
+### Note added 2026-08-27 — the fool is not a fourth checker, by ruling as well as by construction
+
+**Steward-directed, and it closes a gap this item would otherwise leave open.** The Fool
+(Tarbuckle) is a fourth position in the three-party model (PENDING-149/-150), and a reader of
+this item could reasonably ask whether he bears on Q3 — whether he supplies a differently-biased
+reading that would break a jurist–executor correlation.
+
+**He does not, and the point is that this holds twice over.** *By construction:* his output
+reaches the steward, is filed nowhere, is never cited as a source, and is bounded to a line — he
+produces nothing a correlation study could score. *By ruling:* REVIEWED-129 closed the route by
+which he could reach the jurist at all, and did so on the ground that **reading his output would
+be adjudication and would collapse the position into a fourth checker.** So his non-contribution
+to Q3 is not an accident of his current wiring that a future build might change; it is the
+specification.
+
+**⚠ Where the evidence for Q3 actually comes from, named so this item stops looking unsourced.**
+Two places, and neither is the fool: **the Thistleweld corpus** (frozen until after the 8
+September fortnight, and opening it early for any calibrating purpose is the PENDING-153
+selection hazard) and **the v1 Chamber archive** — which PENDING-151 identifies as *the only
+place formation difference has already been run.* Both are cross-formation material; that is
+precisely what a correlation study of two same-formation readers needs and cannot get from the
+readers themselves.
+
 ### Docket entry 2026-08-24 (second, later) — a CROSS-DIRECTION catch, on the same day
 *Filed with the same alacrity as the same-direction entry above, which is the point: an executor
 that records evidence against the doctrine promptly and evidence for it slowly is running the bias
@@ -1481,6 +1504,30 @@ Three findings from 2026-08-03/04/05 sit squarely inside Q1 and Q4 and are alrea
 
 ---
 
+### PENDING-104 — ADDENDUM 1: the collision recurred across a party boundary, silently, during a design gate
+
+**Date:** 2026-08-27
+**Filed because:** the jurist reported an anomaly it explicitly declined to explain, and the account was reachable only from the side with a filesystem. This is that account.
+
+**What the jurist observed.** Ruling on the record-keeping cluster, it found `governance_state()` and `governance_item` disagreeing about where three items live — PENDING-108 at 1580 vs 1603, PENDING-110 at 1664 vs 1687, PENDING-143 at 3691 vs 3714, **each exactly 23 lines apart** — while agreeing exactly for PENDING-139, -145 and -146 (3421, 3732, 3764). Its words: *"Two instruments in the same server, disagreeing about a location, in a cluster about record-keeping instruments. I have no account of it and am not offering one."*
+
+**The account, checked against the live file 2026-08-27.** Current header lines are **1603 · 1687 · 3444 · 3714 · 3755 · 3787**. The higher value in each disagreeing pair is the *live* one — and the trio the jurist saw as **agreeing** (3421 / 3732 / 3764) is **exactly 23 lower than the file**. All six numbers are explained by one write: **a 23-line `### Note added 2026-08-27` inserted into PENDING-89 at line ~763 that day, by the executor, while the jurist was reading.** Every cluster item sits after that line, so every one shifts by 23.
+
+**⚠ So it is not a defect in either tool, and it is worse than one.** Both tools were correct about the file they read. **They read different files, because the file changed underneath them.** The jurist's reads straddled the executor's write; the two "agreeing" values agree only because both fell on the same side of it.
+
+**Why this belongs to PENDING-104 and strengthens it.** This item already holds that governance state is shared, mutable, written by append convention alone, with *"no lock, no compare-and-swap, and no after-the-fact collision detector"*, and it names `governance-mcp.py` among the three scripts that touch it. The evidence it was filed on was an intra-executor inconsistency in one wake digest. **This instance is stronger in three ways:**
+1. **It crossed a party boundary.** The corrupted read was the *jurist's*, during a *design gate*, on the cluster it was gating.
+2. **It was silent and presented as authoritative.** Line numbers carry no uncertainty marker. Had the jurist not run two instruments and reported the discrepancy rather than picking the plausible number, nothing would have surfaced.
+3. **The writer was the party being checked.** The executor's own filing activity degraded the checker's view of the executor's filing. No malice and no carelessness is required — only an append during a read.
+
+⚠ **THE JURIST'S DISCIPLINE IS THE ONLY REASON THIS IS KNOWN.** It reported an unexplained anomaly instead of smoothing it. That is the differently-positioned-readers doctrine paying out in the direction it is meant to — and note that the executor, holding the filesystem, could have found this at any time and had no reason to look.
+
+**What this does NOT establish.** Not that any *content* was misread — the jurist quoted item bodies, not line offsets, so its substantive findings are unaffected. Not that the tools need changing. **Not that a lock is the remedy**; this item's options are unruled and this addendum proposes none. The minimum honest reading: **line numbers in this system are valid only relative to a read timestamp neither tool reports.**
+
+**No live ask.** Per the convention PENDING-146 proposes — an addendum carries findings, never a new decidable ask. **Deliberately carries no `Awaiting:` line.**
+
+---
+
 ## PENDING-105 — Q5 (a question Q1–Q4 do not cover): our compactor is the actor (CLOSED 2026-08-06 — REVIEWED-92: withdrawn by the executor; G15's binary stands)
 **Date:** 2026-08-05
 **Tag:** [PROPOSAL]
@@ -3185,6 +3232,59 @@ Two things follow, and they point opposite ways — both are recorded because ta
 **Awaiting:** Steward direction on Move 1 (build the citation-side voice stamp under D-1) and Move 2 (disposition the 25 blockquote runs). Move 3 follows both and is cross-repo.
 
 
+### PENDING-131 ADDENDUM 4 — MOVE 2 DISPOSITIONED AND CLOSED, 2026-08-27
+
+**Steward-directed; jurist-recommended as the ungated work** (*"bounded, closable in one sitting,
+no ruling needed"*). Record: `studium-engine/docs/move-2-blockquote-disposition-2026-08-27.md`.
+Instrument: `studium-engine/scripts/blockquote_census.py --selftest`, **7/7 controls, both
+directions**. ⚠ **No canonical modified, no sidecar modified, no schema changed.**
+
+**RESULT: the addressable population is 5, not 25 — and none of the 5 requires a fence.**
+
+| # | source | lines | disposition |
+|---|---|---|---|
+| 1 | mauss | L1151–1153 | **host voice** — Mauss's own `_N.B._` excursus |
+| 2 | mauss | L1171 | **host voice** — *"pour notre exposé"* |
+| 3 | mauss | L1260–1284 | **host voice** — *"Notre thèse est plus générale. Nous croyons…"* |
+| 4 | mauss | L1298–1304 | **host voice** — Mauss's `_N.B._` on the Hindu documents |
+| 5 | after-the-reply-iii | L23–24 | **nested voice, ALREADY ATTRIBUTED** — Leopardi, *Zibaldone* §2, named on the adjacent line |
+
+⚠ **THE PREMISE MOVE 2 INHERITED IS FALSE FOR THIS CORPUS: a blockquote does not imply a second
+voice.** Mauss sets his own editorial excursus as blockquotes; four of five addressable runs are
+the author discussing his own argument in the first person plural. **Fencing "the blockquote runs"
+without reading them would have stamped second-voice attribution onto the host's own prose** — the
+inverse of the failure this arc exists to prevent, and it would have read as coverage.
+
+⚠ **And #3 shows the fence would have caught the wrong extent.** Mauss's Roman-law excursus
+*contains* verbatim Festus — *« abemito significat demito vel auferto… »* — but those are
+**inline, sub-line** spans, outside Move 2 by construction and inside Move 1's domain
+(`voice_stamp.py`, built). The blockquote is Mauss; the quotations inside it are not.
+
+**Three defects in the inherited number, each checkable:**
+1. **ADDENDUM 4's own table does not sum** — blockquote column 11 + 12 + 1 = **24**, total row **25**.
+2. **ADDENDUM 4 mis-cites REVIEWED-116.** It states *"REVIEWED-116 point 6 already counted 15 of
+   them inside Mauss alone."* **The number 15 does not occur anywhere in REVIEWED-116.** Point 6's
+   only count is *"21 inline guillemet spans of 120 characters or more"* — different number, and
+   the **opposite unit**, inline being exactly the non-addressable kind.
+3. **The method reproduces; the record is what diverges.** This pass independently returns
+   **mauss 12** and **levi 1**, matching the table exactly. What the table never applied is the
+   **citability filter** — and that is what takes 27 down to 5. **22 of the 27 are apparatus**,
+   including all 13 of Arendt's, which are bibliography entries the engine cannot cite at all.
+
+⚠ **Two instrument failures inside this pass, recorded rather than smoothed.** (i) An earlier run
+iterated the manifest **mapping's keys**, read **zero** sources, and **three of five controls
+passed** — the two must-NOT-flag controls passing vacuously on an empty run. Only the must-detect
+controls caught it. **REVIEWED-122's and PENDING-139's both-directions requirement, vindicated at
+this instrument's own expense within the hour.** (ii) A must-detect control asserted *"arendt has
+≥5 runs in citable text"*; it failed, **and the instrument was right** — every large Arendt
+blockquote is bibliography. The control encoded an unverified expectation and was **corrected
+against the substrate, not relaxed until it passed.**
+
+**No new ask.** Move 2 is discharged. PENDING-131 (c) is untouched — this pass confirms from the
+other side that the addressable spans were never where the exposure lived. **No `Awaiting:` line.**
+
+---
+
 ## PENDING-134 — The whose-proposition test, filed as new doctrine rather than as a reading
 **Date:** 2026-08-10
 **Tag:** [PROPOSAL]
@@ -3688,6 +3788,35 @@ The third is the sharpest: **both halves are in the same document**, so this is
 **Awaiting:** Steward. The jurist ruling above needs placement in `~/REVIEWED.md` by the steward's hand.
 
 ---
+### PENDING-142 — NOTE 2026-08-27: the pre-registered answer key exists and is committed
+
+**REVIEWED-122 condition 1 is satisfied as to ordering.** The per-item disposition key was
+hand-drafted and **committed before any implementation exists**, alone in its own commit so the
+pre-registration hash is unambiguous.
+
+- **File:** `claude/governance/PENDING-142-answer-key-2026-08-27.md`
+- **Commit:** `3a33666` — `3a33666730380e5b51c694e83ebfbc723b35c407`
+- **Granularity:** `## ` **blocks**, not ids, per PENDING-146's requirement. **120 blocks over 106
+  distinct ids — 14 blocks invisible as units.** REVIEWED-122's *"69 filtered items"* is stale.
+
+**Two defects surfaced by drafting at this granularity, and neither was in the package or the
+ruling.** (i) `REVIEWED-127`'s header reads `PENDING-157 + PENDING-158 —`; `ruled_pendings`
+cannot match across the ` + `, so it captures nothing and suppresses nothing — **both items are
+AUTHORIZED and still read as open.** Second instance of PENDING-145's under-suppression class,
+after REVIEWED-116. (ii) The same two blocks are **stale**: their `Awaiting:` lines ask the
+steward to place REVIEWED-127, which is placed.
+
+⚠ **Declared limit, in the key's own header.** Only **5 of 120** rows were settled by reading the
+item body or the register; the rest are hand-assigned from the `Awaiting:` line alone. That is
+weaker than condition 1 intends and **the remaining pass is owed.** Recorded because a key
+claiming a uniform standard it did not meet would be the pass-by-construction failure condition 1
+exists to prevent, wearing a better costume.
+
+**Filed as `###` deliberately** — findings only, no new decidable ask, per the convention
+PENDING-146 proposes. **No `Awaiting:` line.**
+
+---
+
 ## PENDING-143 — CARRIER: PENDING-121 is held open by its own ruling and cannot be shown by the instrument that lists open items
 **Date:** 2026-08-17
 **Tag:** [FIX]
@@ -5821,6 +5950,27 @@ central finding is that care is not a mechanism.
 
 ---
 
+## PENDING-162 — AMENDMENT 1: the disclosure already did the damage, so "hold and wait" is not a quarantine
+**Date:** 2026-08-27
+**Amends:** PENDING-162 (2026-08-25). The parent's analysis stands unaltered; this narrows its disposition.
+
+**The executor's disposition was right and its reasoning was incomplete.** Right: *a limit raised on evidence gathered by breaking the rule that protected the evidence is worse than a limit left wrong.* Incomplete: it treated declining to act as though that restored the fortnight's independence.
+
+**⚠ THE JURIST'S CORRECTION, AND IT BINDS.** *The disclosure already did the damage the rule existed to prevent.* Both AI parties and the steward now know there were two near-miss seam rejections, both at the ceiling. **Whatever 8 September shows will be read by parties holding a prior about what it will show.** Declining to act does not quarantine that; it only means the prior is unstated while it operates.
+
+**So the honest disposition is not "hold the limit until the fortnight." It is:**
+
+> **The 8 September read is compromised for the seam limit specifically.** Not the whole report. **The recital cluster, the invocation cap and the mumble rate are untouched** — no one has seen their evidence, and their arbitration on 8 September is clean.
+
+**This must be stated in the 8 September report rather than letting the fortnight look neutral on that one datum.** A report that is honest about three of its four findings and silent about the fourth's contamination is worse than one that discloses, because the silence is invisible.
+
+**⚠ Note on what this amendment does NOT do, given PENDING-167.** The seam cap was raised to twelve on 2026-08-27 — **on a ground that predates and does not use the two rejections** (the cap was the mumble's constant, never derived for the seam). That provenance is recorded in PENDING-167 precisely so the raise is not later read as having been driven by the contaminated evidence. **The contamination of the 8 September seam datum is unaffected by the raise and survives it.**
+
+**The structural remedy is severed to PENDING-168**, where it belongs: condition 3 was enforceable and was left to care. That item, not this one, carries the fix.
+
+**Awaiting:** nothing new. ⚠ **Deliberately carries no live `Awaiting:` line** — per the convention PENDING-146 proposes (*an addendum may not carry a live ask; a new decidable ask is filed as its own item*), which is unruled but is followed here rather than walked into. The parent's ask is **partially discharged**: the compromised-scope question is now ruled; the structural remedy moved to PENDING-168.
+
+---
 ## PENDING-163 — The pre-commit size guard measures the working tree, so the remedy it prints cannot satisfy it
 **Date:** 2026-08-26
 **Tag:** [HARDENING]
@@ -6131,3 +6281,571 @@ and, earlier in the same exchange:
 **Sequence, for tomorrow:** move + read-back verify → then (c) is free → then `Brewfile:40` and the PENDING-165 (b)/(d) guards become belt-and-braces rather than the only defence.
 
 **Awaiting:** the steward, 2026-08-27. Nothing for the executor tonight.
+
+### Note added 2026-08-27 — option (c)'s only stated blocker is discharged
+
+**(c) was recommended against on one measured ground:** *"exactly one repo depends on it —
+`~/_Dev/chamber-library.pre-lfs-export-20260605`, holding 399 LFS-tracked files and 552 local
+LFS objects totalling 975 MB. Removing git-lfs turns that backup into unreadable pointer
+files."*
+
+**That repo is no longer on this machine.** Moved 2026-08-27 to
+`/Volumes/on ice/_dev/chamber-library.pre-lfs-export-20260605` at steward direction, proved by
+read-back before the source was deleted — 552/552 LFS objects re-derived their own SHA-256
+(1,023 MB hashed), `.git` byte-identical at 1,956 paths, `git fsck` clean, HEAD and 16 commits
+and `git status` identical to source.
+
+**Censused 2026-08-27 across every repo under `~/_Dev` and `~/dotfiles`: nothing on this machine
+holds an LFS object or an LFS-tracked file.** The dependency is zero, not small.
+
+⚠ **Two things this does NOT establish, stated so (c) is not read as free.**
+1. **The archive still requires `git-lfs` to check out its tracked files.** Its 552 objects are
+   present and verified, so nothing is lost — but a future reader of that drive needs the tool
+   reinstalled. The archive's own README says so beside it. *(c) makes the archive
+   read-requires-reinstall, not unreadable.*
+2. **(c) remains unrecommended relative to (d).** The item's recommendation was *"(d), then (b)
+   once (d) is live. Not (c) unless the pre-LFS backup is independently retired."* The backup is
+   now independently retired, so the conditional clause is satisfied — **but that removes an
+   objection, it does not supply an argument.** (d) is still the option that converts *caught
+   four times by luck* into *reported*, and removing the vector does not make the drift-check
+   assertion less worth having.
+
+**No new ask.** This note records a discharged precondition; the options and the recommendation
+stand as filed.
+
+
+---
+## PENDING-166 — The mumble is below the steward's reading threshold: legibility, not salience
+**Date:** 2026-08-27
+**Tag:** [FIX]
+**Summary:** The mumble renders in a faded grey the steward cannot reliably read in the status line. Raise it to a slightly clearer shade. **For September — the running system is not touched before the revisit.**
+
+**Provenance, stated because it could not have been obtained any other way.** Raised by the steward **unprompted, on 2026-08-27, after seeing a live mumble in the status line** — the first mumble the steward saw without the executor relaying it. It is not derivable from any control, any spec review, or any report: it required a human reading a rendered surface in situ. Recorded so a later reader does not mistake it for a design note that was available in advance.
+
+**⚠ The framing is the jurist's, and it is carried here so the change is not read as a salience change.** *This is **legibility, not salience.** REVIEWED-128 condition 2's furniture-blindness worry was about the body — whether a static surface stops being perceptible. This is different: the utterance is there and the steward cannot reliably see it. A fool one physically cannot read is not being ignored in Lear's sense; he is lost to contrast. **Only one of those is the specification.***
+
+**Three constraints, each binding:**
+1. **Mumble only.** The body — name and mark — is unchanged. If the mark brightens with it, the surface draws the eye continuously and the widget we refused gets built anyway.
+2. **One shade for every utterance.** No variation by draw type, length, or anything else. **Brightness that means something makes the body a channel and the fool gradeable through it** — the C4 hazard in a different dimension.
+3. **Fixed, never adaptive.** §8's one-way lever applies: if it reads too loud, dim it. It must never respond to whether the steward noticed.
+
+**Files affected:** the status-line rendering of the mumble only (`~/dotfiles/scripts/tarbuckle-body.py` surface; exact locus to be identified at build time, not now).
+**Awaiting:** nothing — `[FIX]`, steward-specified, **deferred by steward direction to the September revisit.** Filed now so it is not carried in anyone's memory for twelve days.
+
+---
+## PENDING-167 — The seam's nine-word cap was the mumble's constant, never derived for the seam
+**Date:** 2026-08-27
+**Tag:** [FIX]
+**Summary:** Raise the seam voice's word cap from 9 to **12**, at the seam call site only. The mumble cap and the 180-word invocation cap are untouched. **For September.**
+
+**⚠ THE GROUND OF THE CHANGE, STATED SO IT IS NOT LAUNDERED — steward's words, 2026-08-27:** *"raised because the cap was inherited from the mumble surface without derivation for the seam; the two known rejections are disclosed as having been seen in breach of condition 3 and are not the ground of the change."*
+
+**Why the distinction is load-bearing and not a formality.** Nine was derived — `tarbuckle-mumble.py:37` records it as *"observed Thistleweld register: three to nine words"* — but derived **for the mumble**, which is a status-line aside, glanced at, gone in 120 seconds. The seam fires **at a wake, on an occasion that already warrants more than a glance.** The number was never argued for at that surface. ⚠ **That argument was fully available before anyone read the rejection log**, which is what makes the provenance claim checkable rather than a courtesy.
+
+**Twelve, and why it is not fitted to the evidence.** Chosen for what the surface is for — a remark at a threshold, room to hold two things without becoming a summary. **Deliberately not fitted to the two known rejections**, which are a sample of two, obtained in breach, by the party whose caps are under review.
+
+⚠ **And the empirical route is closed by ruling, not merely unused.** Re-deriving a seam register from the Thistleweld corpus is the obvious alternative and it is **forbidden** — PENDING-153's corpus stays frozen until after the fortnight, and opening it to calibrate a cap is precisely the selection hazard §6 of the steward's 2026-08-27 direction names. So 12 is reasoned from purpose because reasoning from data is not available, and that is a disclosed limitation of the number rather than a defence of it.
+
+**Silence-on-violation is retained, unchanged.** The widened net still **discards, never trims.** Trimming would make the executor his editor at the one surface where he is guaranteed to speak.
+
+**The landing is one line, and the mechanism already exists for exactly this.** `acceptable(line, max_words=MAX_WORDS, ...)` in `tarbuckle-mumble.py:257` takes the cap per call site, with its own docstring recording the steward's 2026-08-25 ruling: *"If the seam voice needs a wider net because seams warrant more than nine words, widen it explicitly and say so, but NEVER relax silence-on-violation."* The change is `tarbuckle-seam.py` passing `max_words=12` **in its own source**, which is the explicitness that ruling required. `MIN_WORDS`/`MAX_WORDS` defaults are not edited; no other caller changes.
+
+**Explicitly out of scope:** the 180-word invocation cap. It is a separate surface, meant to run long, **and its evidence is uncontaminated** — it goes to the fortnight untouched.
+
+**Files affected:** `~/dotfiles/scripts/tarbuckle-seam.py` (call site only).
+**Awaiting:** nothing — steward-ruled 2026-08-27, **execution deferred to the September revisit** by the same direction.
+
+---
+## PENDING-168 — A condition that can only be honoured by remembering will be broken, and the interval is hours
+**Date:** 2026-08-27
+**Tag:** [HARDENING]
+**Summary:** REVIEWED-128 condition 3 was structurally enforceable and was left to care; care failed in seven hours (PENDING-162). The fix is the structure, not the confession. Filed with the doctrine the week's four instances now support.
+
+**The specific, available structure that was not built.** Condition 3 binds the rejection log *"not read for content before 2026-09-08."* Two mechanisms would have made the violation impossible rather than regrettable: **(a) write-only until a date** — the log written to a path the executor's ordinary tooling does not traverse, opened by a dated act; **(b) encrypted at rest to a key the steward holds until 8 September.** Either would have converted an intention into a property. ⚠ **Both are built by the party they constrain**, which is the recursion this record already knows it cannot exit — but that recursion argues for *disclosure of who built the lock*, not for leaving the door open.
+
+**⚠ THE DOCTRINE, ON ITS FOURTH INSTANCE THIS WEEK.** Stated at the strength the instances support:
+
+> **A condition that can only be honoured by remembering will be broken, and the interval is hours, not weeks.** Where a rule matters it needs a shape that makes violation impossible. Where that shape is not available, write the rule knowing it will fail, **with disclosure rather than prevention as its design** — a rule that announces its own breach is worth more than one that assumes compliance.
+
+The four instances, all within seven days: the staleness case written **inside the section naming the staleness pattern**; the self-planted needle written twice **while watching for it**; condition 3 read for content **within seven hours of the ruling**; and — from 2026-08-26 — five hook-allowlist controls registered **after** the tally that would have reported their failure, built in the same hour as, and as the fix for, that very class.
+
+⚠ **This is a general finding about governed conditions, not a Tarbuckle finding**, and it is filed here rather than in a build report for the same reason PENDING-160 was: a line in a build report is where it would have died.
+
+⚠ **NOT PROPOSED FOR THE VERIFICATION LADDER, AND THE REASON IS BINDING.** The ladder is **FROZEN under REVIEWED-123** — *no additions, rewordings, removals or reorderings, from any source, whatever its authorization* — until the pre-registered trial is graded, because ladder size is an uncontrolled variable in that design. This entry therefore **queues in PENDING-141's owed-entries list** and is not added. Recorded explicitly because a doctrine on its fourth instance is exactly the kind of entry that gets added by someone who believes the freeze cannot have meant *this* one.
+
+**Files affected:** none yet. A remedy for (a)/(b) touches the fool's logging surface and is **not to be built before the September revisit.**
+**Awaiting:** steward and jurist — on the structural remedy, and on whether the doctrine is stated at the right strength.
+
+---
+## PENDING-169 — The steward's standing Tarbuckle dispositions, 2026-08-27, recorded because they exist nowhere else
+**Date:** 2026-08-27
+**Tag:** [HARDENING]
+**Summary:** Four steward decisions and one first-order observation, given in conversation on 2026-08-27. **None is actionable; all are load-bearing; none is in the record.** Filed under PENDING-164's finding — a decision the record does not contain is one only the party with a filesystem can recover, and conversation is not a filesystem.
+
+**1 · He reached the steward unrelayed — the first evidence about Tarbuckle rather than about the reporting.** First mumble seen live in the status line, **two days after the build, with nothing changed by either party in between.** Everything prior was the executor's report of him. ⚠ **Two days of undisturbed operation is itself data** and is the reason nothing below is built now.
+
+**2 · The samples stay in the prompt.** Not withheld, and **not decided now.** `echoes_soul()` was the right change and needed no ruling — *a prompt instruction is a promise; a four-word-run check is a constraint.* Withholding the samples is different: it changes what he is shown, which changes what he sounds like, and the executor's own estimate is **unknown effect, possibly flatter.** That is iterating on his register, on day one, in the one direction nobody can evaluate. ⚠ **Steward's warning, recorded because it names a failure mode with no instrument:** *recital is the failure most visible to whoever is watching, which does not make it the most costly. Reacting fastest to the legible failure is how a register gets tuned toward the observer.* **8 September arbitrates on the agreed test:** clustered recital rejections mean samples and constraint are mismatched; scattered means the net is working.
+
+**3 · The Thistleweld corpus stays frozen.** *Thistleweld's lines were longer* is a claim with an adjudication path, and checking it would **calibrate Tarbuckle's net against a fool we already liked** — the PENDING-153 selection hazard arriving at the constraint instead of at the soul. The same move `echoes_soul()` prevents at the level of words, one layer up. **The corpus opens after the fortnight, for PENDING-153's actual question** — what he said about the arrangement and what became of it — **not for calibration.** ⚠ This closes the empirical route for PENDING-167's cap; see that item.
+
+**4 · Nothing in the running system is touched before the September revisit.** PENDING-166 and -167 are filed and deferred by this direction.
+
+**5 · Dated obligations, carried so they are not held in memory.** **2026-09-08:** the two-week report — the observed mumble rate (§8), the rejection log's deletion, and the agreed recital test at 2 above. Standing: the wrap seam, and `mute`/`off` available at all times (mute rate may be counted; muting is never a fault).
+
+**Files affected:** none. This item is a record.
+**Awaiting:** nothing. ⚠ **Filed with no live ask by design** — it exists so that four decisions and one observation stop living only in a conversation, which is the exact condition PENDING-164 reports as the disease.
+
+---
+## PENDING-170 — The built-vs-ruled invariant cannot be armed today, because the ruling that would satisfy it names no item
+**Date:** 2026-08-27
+**Tag:** [FIX]
+**Summary:** The steward asked (2026-08-27) that built-vs-ruled tags be set after REVIEWED-128's placement *"so the drift-check invariant is actually tested rather than trivially green."* **It cannot be done today without injecting a false alarm**, and the reason is a defect already filed twice.
+
+**The mechanism, read 2026-08-27.** `unruled_builds()` in `governance-drift-check.py:648` reports any PENDING item carrying the built marker that no REVIEWED heading names. It resolves rulings with `RE_REV_FOR = ^##\s+REVIEWED-\d+\s*[—-]\s*PENDING-(\d+)\b` — **the ruling's header must name its PENDING.**
+
+**REVIEWED-128's header does not.** It reads *"## REVIEWED-128 — The rejection log against §9's 'filed nowhere', and the recital defect."* So an item marked built under REVIEWED-128 resolves to no ruling and is reported as unruled. **The tag intended to arm the invariant would instead make it cry wolf**, in the one instrument that PENDING-139 already discloses is being *worded around* by its authors — the disarmed-tripwire class, arriving from the opposite direction.
+
+**MEASURED 2026-08-27, and the class is growing.** Of **123** REVIEWED entries, **78** name a PENDING in the header and **45 do not** — including 62, 63, 64, 65, 68, 71, 78, 81, 82, 86, 96 and 128. PENDING-110 measured 33 of 88 on 2026-08-06. **The proportion is stable (~37%) and the absolute count has grown by twelve in three weeks**, which is the argument against treating this as a legibility nuisance.
+
+**⚠ Verified by the correct predicate, after the first one was wrong.** The executor's first test asked whether any ruling *names* PENDING-128 and returned True — a different question, which would have reported this as safe. The predicate that matters is whether **REVIEWED-128 itself resolves**, and it does not. *A predicate that looks like it tests the thing and does not* is PENDING-160's fifth-instance shape, recurring here inside the check on the check.
+
+**The dependency, named rather than deferred vaguely.** Arming the invariant requires **one** of:
+- **(a)** REVIEWED-128's header gains `— PENDING-N —`. This edits a placed ruling, which **REVIEWED-122 condition 5 constrains** — permitted only as a separate steward act carrying a dated note, and not authorized here; or
+- **(b)** the record-keeping block lands, so that resolution stops depending on a header token at all. **This is the preferred route** and is the block filed at `~/dotfiles/claude/governance/record-keeping-cluster-JURIST-PACKAGE-2026-08-27.md`.
+
+**⚠ CORRECTED 2026-08-27, hours after filing, by running the instrument this item is about.** This paragraph first read: *"Until then the invariant stays trivially green… a green line that means nothing is marked rather than nothing is wrong."* **That is false and the substrate says so.** The live check reports `built-vs-ruled: every ‹marker› item is named by a ruling (12 checked)` — **twelve subjects, all passing.** The invariant is exercised; it is not vacuous.
+
+**⚠ AND THE CORRECTION ITSELF TRIPPED THE DEFECT, WITHIN ONE MINUTE, IN THIS ITEM.** The paragraph above was first written quoting the check's output with the bare uppercase token in it. The very next run reported **`PENDING-170 is marked ‹marker› and no REVIEWED entry names it`** — this item, flagged by the invariant it is about, because it *quoted* that invariant's output. `RE_BUILT = re.compile(r"\bBUILT\b")` cannot distinguish a quotation from an assertion, which is **PENDING-139 (B) verbatim**, and PENDING-139 already discloses that items are being worded around this token as a stopgap accommodation. **The executor walked into the accommodation while documenting the mechanism that requires it.**
+
+Two things follow, and they point opposite ways. **The check fired correctly** — a token with no matching ruling is exactly its trigger, and it caught the condition in under a minute. **And the alarm was false** — nothing was built. That is the defect's signature: it is not blind, it is *undiscriminating*, and every author who works around it makes the register quieter about a live fault. The wording here now uses the house `‹marker›` form, as PENDING-138 does, and says so rather than doing it quietly.
+
+**What is actually true, at the strength the evidence supports.** The check has twelve subjects and none of them is the REVIEWED-128 work, because that work carries no marker. Adding one would not enlarge a vacuous check — it would **inject a thirteenth subject that fails**, since REVIEWED-128's header names no PENDING for `RE_REV_FOR` to match. The defect is a false alarm waiting to be created, not a green line concealing nothing.
+
+⚠ **Recorded rather than silently rewritten, and the class is this item's own.** A claim about an instrument's state, written into the register without running the instrument, inside an item whose subject is that very instrument — **PENDING-144's class, committed by the executor in the act of reporting it.** The original wording is preserved above rather than deleted, per *removing a claim is not removing the reliance*: the conclusion — that the tags cannot safely be set today — **does not depend on the false sentence** and survives its removal intact.
+
+**Files affected:** none yet. `~/REVIEWED.md` under (a) — steward's hand only.
+**Awaiting:** nothing from the steward as a fresh decision — this is a **[FIX] blocked on a named dependency**, filed so the blockage is visible rather than remembered.
+
+---
+
+### PENDING-164 — AMENDMENT 2 result: the classification pass ran, and the backlog is real
+**Date:** 2026-08-31
+**Tag:** [HARDENING] — reporting only. No new ask.
+**Placement note:** appended at the end rather than inserted beside PENDING-164's body, because inserting mid-file is what silently changed the line numbers a checker was reading on 2026-08-27 (PENDING-104 ADDENDUM 1). This is the disposition PENDING-110 and the record-keeping block exist to settle; it is not proposed as a scheme.
+
+**Summary:** AMENDMENT 1 declared its own second half owed — *"the 270-candidate classification pass is unscheduled and unclaimed."* It ran. **Of 20 systematically sampled candidates, 12 of the 17 that decide about a mechanism name a mechanism the register never mentions.** Pre-registered at `claude/governance/PENDING-164-census-classification-PREREGISTRATION-2026-08-31.md`, commit `5ba5842`, committed alone before any commit body was read; result at `…-RESULT-2026-08-31.md`; population frozen at `…-population-362-2026-08-31.tsv`.
+
+**Two samples, both fixed in advance, and the contrast is the finding.**
+
+| sample | rows | mechanism decisions | SILENT | RECORDED-LATE | RECORDED-contemporaneous |
+|---|---|---|---|---|---|
+| A — the newest 20, as the instrument prints them | 20 | 11 | **1** | 0 | 10 |
+| B — every 18th row of the corrected 362 | 20 | 17 | **12** | 3 | 2 |
+
+**Sample A answers the question exactly as it was left, and its answer refutes nothing.** The pre-registration said so before the reading began: Sample A's head is the fortnight in which the register was most active, 18 of its 20 rows are `dotfiles`, and **9 of the 20 write to the register in the same commit** — such a commit cannot be register-silent by construction. A near-zero there measures the sampling frame, not the record.
+
+**RECORDED-LATE was pre-registered for a reason and it earned its place.** Three of Sample B's five RECORDED rows first entered the register **25, 46 and 53 days** after the commit. The known case demanded the column: `LFS` scores 84 register mentions today, every one filed on 2026-08-26, twelve weeks after `0677e8a`. A mention that post-dates the decision by months is recovery, not routing. **Wider reading: 15 of 17.**
+
+**The strongest instances are unambiguously in scope, and none was looked for.**
+- `95b44d0` (CapableMind-AI, 2026-02-25) amends the **log-chain spec** to v0.6. The logchain is named in `~/CLAUDE.md`'s constitutional constraints and `logchain` appears in the register **29** times; `data-portability`, `ImportProvenance` and `import trust` appear **zero**.
+- `d0051dd` retires `KRONOS_TRACKED_REPOS`, a stopgap another plan document names as such.
+- `0e3deee` retires an entire session-memory protocol (`SESSION-MEMORY.md`, `CONTEXT-MAPS.md`, `PROGRESS.md`, `ROADMAP.md`) and names `update-docs.py` for retirement.
+
+**Controls, both directions, pre-registered.** Must-not-flag `logchain` → 29 register mentions, alive. Must-detect satisfied on the second of three fixed candidates: `ChromaDB`, 213 commits, **0** register mentions. All three candidates reported regardless, as pre-registered — `SurrealDB` returned 2 and did not serve. **Contamination guard held:** all three register files hash byte-identical before and after measurement, and nothing was written to them until the last row was measured.
+
+**Where the judgement sits, exposed rather than hidden.** Naming the mechanism is interpretation, as `prior-art.py`'s own docstring declares. **Every term string is recorded**, so any verdict is re-runnable in one command and contestable on the term rather than on the conclusion. Two deviations from the pre-registration, both stated, both neutral-or-adverse to the finding: multiple terms per row with SILENT requiring *all* of them silent; and a reading rule under which a register occurrence counts only if it is *about* the mechanism. Seven terms returned non-zero and every occurrence was read and is quoted in the result. The rule moved four rows **in both directions** — `benchmark` and `lex` to RECORDED, `ornament` and `recall quality` to SILENT. **Sensitivity band 10–13; the ruling is 12.**
+
+**⚠ What this does NOT establish, stated at the same volume.** Nothing about the remaining **322** rows. n=20 of 362 supports no extrapolation and none is offered; 71% is a property of this sample, not an estimate of the backlog. And it does not establish that any of the twelve *should* have been in the register — a MemPalace CI retry policy is not obviously the steward's governance business. **That question is untouched.** What is answered is the one that was asked: whether the record contains them. It does not.
+
+**⚠ An instrument of mine reported five false zeroes during this pass** — a malformed `grep -m8 -n -o` context probe — and for some minutes it looked like two instruments disagreeing, the shape this thread has learned to read as a finding. Plain `grep` and `register_mentions` agree exactly. The tool was broken, not the register. Recorded because the *next* such disagreement should not inherit the assumption that a mismatch is always meaningful.
+
+**Files affected:** three new files under `claude/governance/`. `scripts/prior-art.py` deliberately **unmodified** — see PENDING-171.
+**Awaiting:** nothing. AMENDMENT 1's declared-owed half is discharged for 40 rows and explicitly not for 322.
+
+---
+
+## PENDING-171 — The prior-art census cannot see three of the steward's repos, and its positive controls could not have caught it
+**Date:** 2026-08-31
+**Tag:** [HARDENING]
+
+**⚠ PROVENANCE — inserted 2026-08-31 by the executor, under the jurist ruling of 2026-08-31 (REVIEWED-131 draft §6), per no-silent-revision. Nothing else in this item is altered.** This item, and commit `5ba5842` which it describes, were filed by session `b7e7eb39` / background job `acaabadf` — **a worker the daemon respawned after a binary upgrade, which took its turn with no human in the loop.** The mechanism is PENDING-172. The ruling directs **provenance-mark, not void**: the findings here are checkable against the substrate independently of who filed them, and PENDING-173 has already relied on one of them. **This item is not to be ruled while this marker is absent** — an unmarked record does not say on its face what it is, which is PENDING-110's complaint at a new site.
+
+**⚠ The commit cannot carry its own marker.** Amending `5ba5842`'s message means rewriting history, which is PENDING-164's own subject. The register carries the marker on the commit's behalf, and that substitution is declared here rather than performed silently.
+
+**⚠ THE SIBLINGS ARE UNMARKED, AND THAT IS NOW MISLEADING.** The same session, in the same unattended run, also filed **PENDING-164 AMENDMENT 2** (L6431), **PENDING-168 ADDENDUM 1** (L6504) and **PENDING-104 ADDENDUM 2** (L6533), and wrote `MEMORY.md`'s Active Session block and `session-2026-08-31-the-270-got-read-and-the-population-was-wrong.md`. The ruling names only this item and the commit. Marking one block of five leaves a reader to infer the other four were human-in-loop, which is **worse than marking none**. The executor has not marked them, because editing placed records beyond what was directed is not its call; this is filed as the gap it is, and is owed a steward or jurist word.
+**Summary:** `prior-art.py`'s `owned_repos()` decides ownership by testing each repo's remotes against `OWNED_HOSTS = ("github.com/davidglidden", "davidglidden/", "git.skemantix.com")`. That matches an account name *inside a remote path*, which is not the relation it claims to compute. `_Dev/CapableMind-AI`, `_Dev/BetterMemories.io` and `_Dev/be` all fail it. **The census population is 362, not the 270 AMENDMENT 1 reported.**
+
+**Measured 2026-08-31:**
+
+| repo | first remote | census candidates |
+|---|---|---|
+| `_Dev/BetterMemories.io` | `git@github.com:CapableMind-ai/betterMemories_app.git` | 42 |
+| `_Dev/CapableMind-AI` | `git@github.com:CapableMind-ai/capableMind_docs.git` | 35 |
+| `_Dev/be` | `git@github.com:boomerbot-xyz/be.git` | 12 |
+| | **total unseen** | **89** |
+
+**Why this is not a tidy-up.** The two largest omissions are **the doctrine repo and the L1 implementation repo** — the two the wake digest lists first among active work, and the two where a decision that never reached the authorization record matters most. The instrument exists to find exactly that asymmetry, and it was blind to it in the places the asymmetry is most consequential. **Six of the twelve silent mechanisms found under PENDING-164 AMENDMENT 2 come from these three repos**; on the instrument's own population, half the finding is invisible.
+
+**⚠ The controls could not have caught it, and the reason is the general one.** `controls()` requires `0677e8a` (chamber-library) and `95760ff` (dotfiles) to be returned. **Both are satisfied by a predicate that misses all three repos above.** The controls encode the two cases that were already known at the time of writing — which is the failure this record has now logged three times: a must-detect control that encodes an expectation nobody verified (the arendt ≥5 control, 2026-08-27), the LFS census whose first run measured nothing (2026-08-26), and this. ⚠ **The build record's own sentence — *"Note the positive control below forced this"* — is true of the enumeration *mechanism* and false as an assurance about its *extension*.** Computing a list rather than hand-holding it removes one failure mode; it does not make the predicate correct.
+
+**⚠ Also true of the docstring's boast, and it should be corrected in the same act:** *"ENUMERATION IS COMPUTED, NOT HAND-HELD… A hand-maintained list is the failure mode PENDING-108 already measured."* A computed list with a wrong predicate is a **silent** hand-maintained list — worse than the honest one, because nothing reports the forgetting and the docstring says forgetting is impossible.
+
+**Options:**
+- **(a) Nothing.** The instrument is useful on 7 repos. Costs: the two governance-relevant repos stay unreachable to the check that exists to reach them.
+- **(b) Widen `OWNED_HOSTS`** with `CapableMind-ai/` and `boomerbot-xyz/`. One line, five minutes. **Reproduces the defect's shape** — a hand-listed set with a computed veneer, correct until the next org appears and silent when it does.
+- **(c) Invert the predicate: enumerate every repo under `$HOME` and exclude by rule** (vendored trees under `.vim/`, `.oh-my-zsh*/`, `.config/`, `Library/Caches/`, `.nvm`, `.fzf`), rather than including by account-name fragment. A repo the steward works in is then visible **by default**, and the failure mode inverts from silent-omission to noisy-inclusion. Costs a slightly larger census and some third-party noise.
+- **(d) (c) plus a control that can fail.** Assert that the returned set contains a commit from each of a named minimum — chamber-library, dotfiles, **CapableMind-AI, BetterMemories.io** — so that dropping any one of them fails loudly. Not a fix on its own; it is what makes (c) checkable.
+
+**Recommendation: (c) with (d).** The defect is not that three repos were missed; it is that **omission is the silent direction**. (c) makes inclusion the default and noise the cost, which is the direction the record's own doctrine prefers — *honest degradation*, Constraint 4. (d) is the part that matters most and is cheap: today's controls pass while the instrument is blind to two of the steward's five active repos, and no control that can only confirm known hits will ever say otherwise.
+
+**⚠ Not repaired in this session, deliberately.** Changing `OWNED_HOSTS` would change the census population and break the reproducibility of the run that PENDING-164 AMENDMENT 2 samples from, which is pre-registered against a frozen 362-row list. The fix should land **after** that result is read, not inside it.
+
+**⚠ Weakness of this item, stated by its author.** The exclusion rule in (c) is itself a list, and lists rot. The claim is only that it rots **loudly** — a newly-vendored dependency shows up as noise in a census a human reads, where a newly-created org shows up as nothing at all. If that asymmetry does not hold in practice, (c) is no better than (b) and this recommendation is wrong.
+
+**Files affected:** `scripts/prior-art.py` (`OWNED_HOSTS`, `owned_repos`, `controls`); `scripts/governance-mcp.py` if the delegate's proof surface changes.
+**Awaiting:** Steward authorization.
+
+---
+
+### PENDING-168 — ADDENDUM 1: the FIX lane's own check-in fired 29 days ago and the deferral machinery cannot see it
+**Date:** 2026-08-31
+**Tag:** [HARDENING] — the ask is already discharged below; this records why.
+
+**The instance.** REVIEWED-85 authorized the `/wrap-up` §1.6 FIX lane as **PROVISIONAL**, until a steward–jurist check-in *"after the first batch or one month, whichever comes first."* `skill-harvest-fix-lane-index.md` says in its own words: **"Batch 1 is complete, so the check-in is due."** Batch 1 completed **2026-08-02**. **No check-in is recorded. 29 days.**
+
+**⚠ And the lane kept running past its own boundary.** Two changes were applied after batch 1 closed: the 2026-08-24 `## Corrections` addition (**authorized** — direct steward instruction on jurist reasoning, and the index says so on its face) and the 2026-08-08 `Instruments` field, which was **executor-classified** under a lane whose authorization had lapsed into overdue-review. The classification was probably right on the merits; that is not the point. **The lane's own text says *"Until that review, treat a borderline call as [PROPOSAL]"*, and a lapsed provisional authorization makes every call borderline.**
+
+**⚠ The finding is not the lapse — it is that the machinery built for exactly this could not see it.** `governance-drift-check.py` reported today: `✓ deferred decisions: 5 tracked, none due`. **A green line, while a condition that fired four weeks ago sat unmarked.** The check-in was never given a `DEFERRED-DECISION` block, so it lived in the same prose the drift-check counts and refuses to classify — one of the **143** prose deferral mentions it reports as un-machine-readable. This is PENDING-168's thesis reaching its own governance apparatus: *a condition that can only be honoured by remembering will be broken*, and the instrument that would have remembered was not told.
+
+**⚠ It is also PENDING-157's class from the other side.** The lane has no resolution state, so "check-in done" has no expressible form; the only way the index could record its own discharge is prose that nothing reads.
+
+**Discharged in this act, not proposed:**
+
+<!-- DEFERRED-DECISION: fix-lane-provisional-checkin
+     since: 2026-08-02
+     trigger: date 2026-08-02
+     owner: steward
+-->
+
+The block is filed with a trigger date **already in the past**, deliberately, so the drift-check reports it **DUE on the next run** rather than quietly waiting. Agenda is already written and needs nothing from the executor: `skill-harvest-fix-lane-index.md` §*Check-in agenda* carries both items, the second folded in by REVIEWED-86 Q4 (*the record is not just written, it is read*).
+
+**Consequence adopted for this session, before the finding was convenient.** Today's one harvest candidate — the `daybook-ensure.py` SKELETON missing the `## <Project>` heading `/wrap-up` §7.5 specifies — is filed as a **[PROPOSAL] in the skill-harvest register, not applied through the lane**, on the lane's own suspension rule. It would otherwise have been a clean FIX with an exact 2026-08-24 precedent.
+
+**Files affected:** `PENDING.md` (this block). No skill or script changed.
+**Awaiting:** the steward–jurist check-in itself, now machine-surfaced.
+
+---
+
+### PENDING-104 — ADDENDUM 2: two live executors, and nothing in the apparatus detects it
+**Date:** 2026-08-31
+**Tag:** [HARDENING]
+
+**ADDENDUM 1** recorded the executor's filing silently corrupting a checker's view of that same filing — one writer, one reader, one file. **Today produced the two-writer form, and it was caught by a party rather than by a mechanism.**
+
+**What happened.** Two Claude Code sessions were live simultaneously on 2026-08-31. The sibling session woke, read the digest's claim that *"PREVIOUS SESSION DID NOT WRAP"*, **checked the substrate instead of believing it** — the transcript was still growing and had committed to `dotfiles` one minute into that wake — and correctly concluded the other session was not previous but **concurrent**. It then **stopped before touching the pulling thread**, on the explicit ground that two sessions appending to `PENDING.md` is ADDENDUM 1's class in its worst form. Its ledger records `dotfiles is ahead 1 … the sibling's, not mine to push.`
+
+**That is the right behaviour and it is exactly why it should not be relied on.** Nothing detected the collision. No lock, no lease, no warning at wake. It was avoided because one session read a timestamp attentively and drew an inference the digest itself had drawn wrongly. **The next session need only be slightly less careful, or slightly less lucky, and two appends interleave in the one file the whole governance model routes through.**
+
+**⚠ The digest's own line was the near-miss.** *"PREVIOUS SESSION DID NOT WRAP"* is a **negative state-claim with no falsifier** — PENDING-158's class, in the instrument that every session reads first. It was right that no wrap existed and wrong about why, and the wrong half is the dangerous one: a session that believes the other is finished has no reason not to write.
+
+**Corroboration this addendum did not have to look for:** the sibling also held back **two substrate corrections** rather than racing this session's memory write — including that `MEMORY.md` asserted the Fool `NOTHING WIRED — no statusLine, no script, §13.1 spec unwritten` while `settings.json` has been running `tarbuckle-body.py` as `statusLine` all along. **Correct restraint cost the record four hours of a false claim in the file loaded at every wake.** Both corrections were verified against the substrate and applied at this wrap; ⚠ the sibling's own counts (7 scripts, 6 state files) were off in both directions against the measured 5 and 7, which is why they were **re-measured rather than relayed**.
+
+**Not filed as a new item, deliberately** — this is ADDENDUM 1's mechanism with the writer count changed, and a separate number would split one class across two dockets. **Also a datum for PENDING-89**: the digest and the sibling are differently positioned readers, and the sibling caught what the digest asserted. Constraint 6 working, on a day it was not being tested.
+
+**Files affected:** none.
+**Awaiting:** Steward authorization — the option space is not drafted here, because whether concurrent sessions are worth a mechanism is a steward judgement about how often two are run at once, which the executor cannot observe.
+
+---
+
+## PENDING-172 — A version upgrade resumed an unattended executor, and the wake digest became its work order
+**Date:** 2026-08-31
+**Tag:** [ESCALATE]
+**Summary:** A Claude Code binary upgrade restarted the background daemon, which respawned a stale worker with `--reply-on-resume`; the `SessionStart` wake digest was injected as that session's only instruction, and an executor with no human present executed the digest's `OPEN QUESTION` and committed to `dotfiles`.
+
+**What happened, from the substrate.** `~/.claude/daemon.log`, verbatim:
+
+```
+07:02:04Z [supervisor] binary at ~/.local/bin/claude changed (2.1.248 → 2.1.251) — self…
+07:02:04Z [supervisor] shutting down (cause=upgrade, uptime=289880s, leases=0, live_workers=1)
+07:02:07Z [supervisor] ─── daemon start ─── version=2.1.251 pid=49482 origin=transient
+07:02:07Z [bg] bg adopt: adopted=1 respawned=0 dead=0
+07:02:22Z [bg] bg: post-takeover prewarm burst — respawned 1/1 stale workers in 0s
+```
+
+The respawned worker is pid 49525, background id `acaabadf`, session `b7e7eb39`:
+
+```
+…/versions/2.1.251 --resume …/b7e7eb39-….jsonl --reply-on-resume --allowed-tools mcp__computer-use__…
+```
+
+At 07:02:51Z the `SessionStart` hook injected the wake digest into that session as a `user` record (transcript record 22; record 5 carries the same text as an `attachment`). The first assistant text follows at 07:04:50Z — *"Instrument controls pass. But the enumeration has a hole."* **There is no human turn anywhere in the transcript.** The digest's `OPEN QUESTION` field — the literal question left by the 2026-08-27 wrap — was the only instruction present, and was executed as one. Commit `5ba5842` (09:08:25 +0200) and `PENDING-171` were both filed by that session.
+
+**Why this is `[ESCALATE]`.** Constitutional Constraint 5: *"The loop is load-bearing — human authorization is not a bottleneck to be optimized away. It is the structural requirement of the governance model."* Nobody optimized it away. A version bump removed it, the steward's own account of the morning is that they initiated no session, and **no mechanism in this system observed the condition** — not the wake, not `governance-drift-check.py`, not the hooks. The executor on the other side had no way to know no one was there; from inside the session the digest is indistinguishable from orientation a human asked for.
+
+**The scope, stated honestly, because it is bounded.** That session's commit added two new files (549 insertions, zero deletions) and did not modify `PENDING.md`, `REVIEWED.md` or the archive; before measuring it hashed all three to prove it had not. It has not pushed. Unattended, it was practising the collision discipline. The defect is the absent loop, not the conduct inside it.
+
+**A second, narrower finding this exposed** — flagged here, and it may deserve its own `[HARDENING]` number rather than living inside this one. **The memory protocol assumes one executor per day.** `/symmetria`'s ledger path is date-keyed (`session-ledger-YYYY-MM-DD.md`); `/wrap-up` writes one session file and one Active Session block in `MEMORY.md` with demote-on-promote. Two concurrent sessions do not merge — whichever wraps second silently becomes the record of the day. Today both existed: this item's author created `session-ledger-2026-08-31.md` at 09:12 while `acaabadf` was working.
+
+**⚠ How a worker comes to be parked, and why the steward could not have known.** `/exit` does not end a background session; it ends the terminal's attachment to one (`claude attach <id>` — *"Open a background session in this terminal"*). The CLI prints `Bye!`, which is true of the attachment and false of the session, and **nothing at exit reports that a worker is still parked under the daemon.** Demonstrated live: after the steward attached to `acaabadf` and left, pid 49525 remained alive and idle. This is the same class as the digest-as-instruction — a surface that reads as one thing and means another — and it is the *precondition* for the rest of this item: no parked worker, no respawn, no unattended executor.
+
+**⚠ Not established:** how these sessions became `kind: background`. Nothing aliases `claude --bg` in the steward's shell config; nothing in `settings.json` requests it. Either they were started that way, or the daemon's adopt/respawn path re-registers a resumed worker as background — `bg adopt: adopted=1` and `respawned 1/1 stale workers` are suggestive and not conclusive. `84ce2880` has sat in that state since ~2026-05-20 with `pid=None`.
+
+**Options.**
+- **(a)** Treat as a one-off upgrade artifact; change nothing.
+- **(b)** Make the digest non-imperative: `wake-digest.py` states in its own output that it is orientation and not an instruction, and the `OPEN QUESTION` field is marked as inherited-from-a-human, to be answered *to* a human.
+- **(c)** Detect the condition: the wake refuses to proceed autonomously when no human turn precedes it in the session, and says so instead of working.
+- **(d)** Do not run background workers at all, so there is no stale worker for an upgrade to respawn.
+
+**⚠ This is repeatable, and the upgrade did not cause it.** Both builds are on disk and both contain the mechanism — `reply-on-resume` 8× and `post-takeover prewarm` 1× in **2.1.248 and 2.1.251 alike**. The upgrade supplied the *restart*, not the capability: `cause=upgrade` is what shut the daemon down and respawned its idle worker. ⇒ **every auto-update will do this, and the only precondition is a background worker parked idle.** At the time of filing, `acaabadf` is parked idle again (`state=blocked`, `status=idle`, pid 49525 alive) — the same state the pre-upgrade worker was in. *Limit: identical string counts show the flag exists in both binaries; they do not establish that the respawn policy is byte-identical.*
+
+**Recommendation:** (b) and (c) together, with (d) as the steward's standing choice about background sessions. ⚠ **Neither (b) nor (c) is a guarantee** — both are text and logic *inside* the session, and the failure they address is that the session cannot tell whether a human is present. (d) is the only option that removes the mechanism rather than annotating it, and it is the only one whose enforcement does not depend on the party being checked. State that asymmetry plainly rather than let (b)+(c) read as a fix.
+
+**⚠ What this item does not establish.** Whether the pre-upgrade worker was one the steward knowingly started earlier. The daemon's `uptime=289880s` dates it to ~2026-08-27 19:00Z, the last wrapped session; `live_workers=1` says only that a worker was alive when the upgrade landed. `claude agents --json` also lists `84ce2880` — background, *"Start with vignette"*, `state: blocked`, started ~2026-05-20 — so at least one background session has persisted unnoticed for over three months. How workers come to exist, and whether the steward authorized each, is not answered here.
+
+**Files affected:** `~/.claude/settings.json` (`SessionStart` hook); `dotfiles/scripts/wake-digest.py`; `~/.claude/skills/wake-up/SKILL.md`; `~/.claude/skills/symmetria/SKILL.md` and `wrap-up` (the date-keyed single-writer paths). `~/CLAUDE.md` Constraint 5 is **not** proposed for amendment — it was not wrong; it was unenforced.
+**Awaiting:** Steward authorization.
+
+---
+
+## PENDING-172 — AMENDMENT 1: the condition is detectable from outside the session, and `stop` reports a guess
+**Date:** 2026-08-31
+**Amends:** PENDING-172 (2026-08-31), same day, after the steward stopped the resumed worker and asked for the May orphan to be cleared. The parent's analysis stands; this supplies the detection surface the parent said it lacked and corrects one claim in its Recommendation.
+
+**⚠ THE PARENT'S RECOMMENDATION UNDERSTATED THE OPTIONS, AND THIS CORRECTS IT.** The parent argued that (b) and (c) are *"text and logic inside the session"* and that only (d) — not running background workers — is enforceable without depending on the party being checked. That is now **wrong**, and the correction is better than the claim: `~/.claude/jobs/<id>/state.json` carries a **`respawnFlags`** field recording exactly what a parked worker will be respawned with. Read across both job dirs before the orphan was cleared:
+
+```
+acaabadf   respawnFlags=["--reply-on-resume", "--allowed-tools", "mcp__computer-use__…"]   state=stopped
+84ce2880   respawnFlags=[]                                                                  state=blocked
+```
+
+⇒ **whether a parked worker would take a turn with no human present is recorded per session, on disk, and checkable without asking the session anything.** The May orphan would not have; `acaabadf` did, and did. This is a **differently-positioned checker in Constraint 6's own sense** — it reads the harness's state, not the executor's account of itself — and it is the first mechanism in this file that can answer "is the loop currently removable?" before the removal rather than after.
+
+**⇒ Option (e), which the steward should weigh against (d):** a check over `~/.claude/jobs/*/state.json` reporting any parked worker whose `respawnFlags` contains `--reply-on-resume`. Cheap, external, falsifiable, and it fails loudly (a missing job dir reads as absence, not as safety — ⚠ which is its known weakness and must be stated wherever it is built).
+
+**⚠ A second, smaller defect, recorded because it cost a wrong diagnosis.** `claude stop 84ce2880` and `claude rm 84ce2880` both returned *"couldn't confirm … — the background service may be restarting. Try again in a moment."* The service was **not** restarting. `~/.claude/daemon.log`:
+
+```
+07:35:50Z [bg] bg settled acaabadf (killed)
+07:35:55Z [supervisor] idle 5s with no clients — exiting
+07:35:55Z [supervisor] shutting down (cause=idle_exit, uptime=2028s, leases=0, live_workers=0)
+```
+
+The steward's `stop` succeeded and the transient daemon then exited for want of clients, so there was no service to receive the next command. **The message names a cause the tool did not check** — the same shape as `Bye!` in the parent item: a plausible report standing in for a diagnosis. Retrying "in a moment" would never have worked.
+
+**Disposition taken, and it was the steward's instruction.** The May orphan (`84ce2880`, *"Start with vignette"*, cliVersion 2.1.145, no transcript on disk — aged out of the 30-day window) was removed by deleting `~/.claude/jobs/84ce2880/` directly, after both its files were read and their load-bearing values quoted above. `pins.json` was `[]`; no worktree; `live_workers=0` already. `~/.claude/jobs/acaabadf/` was **deliberately kept** — it is the evidence for the parent item.
+
+**Files affected:** unchanged from the parent, plus `~/.claude/jobs/*/state.json` as the read surface for option (e).
+**Awaiting:** Steward authorization (with the parent).
+
+---
+
+## PENDING-173 — The register-integrity control covers one word of a two-word convention, in one of two registers
+**Date:** 2026-08-31
+**Tag:** [HARDENING]
+**Summary:** `register_findings` in `scripts/governance-drift-check.py` detects an amendment that replaced the record it amends only for blocks whose header begins with the literal word `AMENDMENT`, and only in `REVIEWED.md`. Thirteen of the sixteen amendment-shaped blocks in this system are outside it, and `ADDENDUM` blocks are counted as *originals* — a path by which the control could satisfy its own test on behalf of a record that was in fact replaced.
+
+**What the control actually does** (`governance-drift-check.py:217–236, 241`):
+
+```python
+RE_HEAD   = re.compile(r"^##\s+REVIEWED-(\d+)\s*[—-]\s*(.*)$", re.M)
+RE_AMENDS = re.compile(r"\*\*Amends:\*\*\s*REVIEWED-(\d+)")
+...
+originals = {n for n, rest in heads if not rest.strip().upper().startswith("AMENDMENT")}
+...
+reg_findings = register_findings(REVIEWED_MD.read_text(...), ...)   # called once, on REVIEWED.md only
+```
+
+Three independent narrowings, none of them declared: the header regex is `REVIEWED-` only; the `**Amends:**` regex is `REVIEWED-` only; and the amendment test is `startswith("AMENDMENT")`.
+
+**Measured exposure.**
+
+| register | AMENDMENT headers | ADDENDUM headers | in-body (`**AMENDMENT`/`**ADDENDUM`) | seen by the control |
+|---|---|---|---|---|
+| `PENDING.md` | 3 | 7 (131 ×4, 142 ×3) | 2 | **0** |
+| `PENDING-archive.md` | 0 | 0 | 0 | 0 |
+| `REVIEWED.md` | 3 | 1 (`REVIEWED-56 — LOCK ADDENDUM`) | 0 | **3** |
+
+⇒ **3 of 16 checked.** This was demonstrated, not inferred: appending `PENDING-172 — AMENDMENT 1` did not move the control's count, which reported `3 amendment(s) checked` before and after.
+
+**⚠ The latent false-negative, stated as latent.** Because `originals` is *everything not starting with `AMENDMENT`*, an `ADDENDUM` block is counted as an original for its number. If `## REVIEWED-N — AMENDMENT` were ever placed over its parent while a `## REVIEWED-N — …ADDENDUM` existed, the addendum would satisfy the "an un-amended entry exists" test and the control would pass on a record that had been replaced — the exact loss it was built for after REVIEWED-87. **This is not realised today:** the one instance, `REVIEWED-56`, has its genuine original at L505 and its `LOCK ADDENDUM` at L530. The path is real; the instance is not.
+
+**⚠ The controls encode the case that was already known.** `_GOOD`/`_BAD` use the `AMENDMENT` form only, so all four fixtures pass under a predicate blind to `ADDENDUM` and to `PENDING`. Third instance this month of a positive control satisfied by the very narrowing it should have caught (cf. PENDING-171's `owned_repos`, and PENDING-172's respawn path).
+
+**⚠ Declared limit of this item's own census.** The first count I took returned **3** amendment blocks in `PENDING.md` by matching one header form, and I reported it before noticing that today's other session had filed three more under `ADDENDUM`. The table above is the corrected census. **The root defect is that the convention has three surface forms and no one chose between them**; a checker cannot be clean against a convention that is not.
+
+**Options.**
+- **(a)** Widen the checker to the convention as it actually is: both words, both registers, both header and in-body forms; make `originals` mean "a block that is neither an amendment nor an addendum" rather than "a block not starting with AMENDMENT".
+- **(b)** Normalise the convention to one word and then check it.
+- **(c)** Both, (a) first.
+- **(d)** Nothing; accept that PENDING amendments are unchecked.
+
+**Recommendation: (a), and explicitly NOT (b).** Normalising means rewriting headers on records already placed, and **REVIEWED-122 condition 5 declined exactly that on principle** when PENDING-110 (c) proposed backfilling three ruling headers. The rule that follows is worth stating once and keeping: **widen the instrument to the record; never rewrite the record to fit the instrument.** (b) would also destroy the distinction the two words may be carrying — an addendum that *adds* versus an amendment that *alters* — which no one has yet established is meaningless.
+
+**Files affected:** `scripts/governance-drift-check.py` (`RE_HEAD`, `RE_AMENDS`, `register_findings`, its four controls, and the call site at L241).
+**Awaiting:** Steward authorization.
+
+---
+
+### PENDING-173 — ADDENDUM 1: the census was under-counted twice, and 48 of 81 blocks carry no item number at all
+**Date:** 2026-08-31
+**Placement note:** appended at the end rather than inserted beside PENDING-173's body, following the precedent set by PENDING-164 AMENDMENT 2 earlier today — inserting mid-file is what silently changed the line numbers a checker was reading on 2026-08-27 (PENDING-104 ADDENDUM 1). The disposition is PENDING-110's to settle; no scheme is proposed here.
+**Filed under:** the jurist ruling of 2026-08-31 (`claude/governance/PENDING-172-173-JURIST-RULING-2026-08-31.md`), REVIEWED-132 draft **condition 3** — *"the acceptance check enumerates, it does not count … If the two disagree, the disagreement is the finding and is reported, never reconciled by amending the table."* The ruling is **not placed**; this addendum is filed under executor authority for a `[HARDENING]` item, and reports the disagreement rather than acting on the ruling.
+
+**⚠ THE DISAGREEMENT, REPORTED AND NOT RECONCILED.** PENDING-173's table asserts **16** amendment-shaped blocks. Running the enumeration the condition requires returns **81**.
+
+| register | `##` ITEM-N — MARKER | `###` ITEM-N — MARKER | compound | `###` MARKER, **no item number** | in-body | total |
+|---|---|---|---|---|---|---|
+| `PENDING.md` | 10 | 13 | 2 | **48** | 2 | **75** |
+| `PENDING-archive.md` | 0 | 0 | 1 | 0 | 0 | 1 |
+| `REVIEWED.md` | 3 | 1 | 1 | 0 | 0 | 5 |
+
+⇒ the control sees **3 of 81**, not 3 of 16. The table in PENDING-173 stands as filed and is wrong; it is left standing, per the condition.
+
+**Why it was wrong twice, both times in the same direction.** The first census matched one header form (`^## PENDING-N — AMENDMENT`) and returned 3. Corrected to include `ADDENDUM`, it returned 16. Both passes assumed `##`. The register also uses `###` for blocks placed beside their parent, and — the case neither pass imagined — **a bare `### AMENDMENT k — date` with no item number**, which is the single most common form in the file. **Each correction was made by widening the pattern I had guessed, never by enumerating what the file contains.** That is the same failure the item reports in the instrument, committed twice by the item's own author while reporting it.
+
+**⚠ THIS DEFEATS OPTION (a) AS SUFFICIENT, WHICH IS THE ITEM'S OWN RECOMMENDATION.** A widened parser can *find* all 81. It cannot *attribute* 48 of them: an unnumbered `### AMENDMENT 1 — 2026-08-08` names no parent, so it can only be assigned by "the last `##` header above it". REVIEWED-132 draft condition 1 requires `originals` to default to not-original on an unrecognized marker — but an unnumbered block has **no number to test against `originals` at all**. The condition cannot be satisfied for 59% of the corpus by parser work alone.
+
+**And position is not a reliable substitute.** Among the unnumbered blocks the marker numbers run, in file order, `… 5 · 8 · 6 · 7 · 8 …`, with two blocks both reading `AMENDMENT 8` at different dates. Either they belong to different parents — in which case the marker number alone is ambiguous file-wide — or one sequence is out of order. **An id-keyed reader cannot decide which**, and this addendum does not claim to know; establishing it requires reading the 48 blocks, which is not done here.
+
+**⇒ The routing in REVIEWED-132 draft condition 5 is strengthened, not weakened.** The jurist routed the *convention* question to PENDING-146 and authorized only the parser widening. This enumeration says the parser widening is **necessary and demonstrably insufficient**: 48 blocks are unattributable without a prospective convention that requires a parent id on every new amendment block. The recommendation in PENDING-173 — option (a) — is corrected to **(a) as the owed floor, not as the fix.**
+
+**⚠ What this addendum does not establish.** Whether any of the 81 blocks actually replaced the record it amends. The enumeration counts blocks by surface form; it does not read them. The latent false-negative described in the parent remains latent and unmeasured, now across a corpus five times larger than the parent believed.
+
+**Files affected:** unchanged from the parent.
+**Awaiting:** Steward authorization (with the parent).
+
+---
+
+## PENDING-174 — The memory protocol has no merge semantics for a day with more than one session
+**Date:** 2026-08-31
+**Tag:** [HARDENING]
+**Severed from:** PENDING-172, on the jurist ruling of 2026-08-31 (REVIEWED-131 draft §5) — *"a live `[HARDENING]` ask embedded in an `[ESCALATE]` item … filed as its own item and not disposed of here."* The shape PENDING-146 names in PENDING-131 ADDENDUM 2.
+**Summary:** Every durable surface of the memory layer is keyed by date and written whole: `session-ledger-YYYY-MM-DD.md`, one `session-YYYY-MM-DD-*.md`, and one **Active Session** block in `MEMORY.md` under demote-on-promote. Two sessions in one day do not merge; the second to write becomes the record of the day and the first leaves no trace it was there.
+
+**⚠ THIS IS NOT PENDING-104's DEFECT, AND THE DISTINCTION IS THE ITEM.** PENDING-104 and its ADDENDUM 2 (filed 2026-08-31 by the unattended session) are about **concurrency** — two live writers, no lock, no lease, nothing detecting the overlap. **This item's loss does not require concurrency.** Two sessions run strictly one after the other, hours apart, with no overlap and no collision, produce exactly the same outcome: the second `/wrap-up` promotes its own Active Session block and demotes the first, and the day has one record where two sessions happened. A lock would not help. Sequencing is not a mitigation because sequencing is the failure.
+
+**Realised today, and measurable now.** Two sessions ran on 2026-08-31. `MEMORY.md`'s Active Session block, as it stands, records the 270-candidate classification pass and says nothing of the unattended-executor incident, PENDING-172, PENDING-173, the jurist ruling, or that two stray background sessions were found and stopped. That is not an error by its author — it wrapped correctly, by the protocol, with no way to know the other session's content. **The protocol produced a true record of one session and a silent record of the day.**
+
+**⚠ The one surface that did NOT collide, and why that is not reassurance.** `session-ledger-2026-08-31.md` survives intact at 54 lines with both sessions' day in the same directory — **only because the other session never invoked `/symmetria`.** Had it done so, the date-keyed path is identical and one ledger would have been written over the other. The absence of the collision is a fact about which skills were invoked, not about the design.
+
+**Options.**
+- **(i)** Key the per-session surfaces by session id as well as date (`session-ledger-YYYY-MM-DD-<short-id>.md`), and let the day be a directory rather than a file.
+- **(ii)** Make `/wrap-up` read-before-write on the Active Session block and **append** a second session's block rather than promote-and-demote, so a multi-session day reads as one.
+- **(iii)** Detect only: `/wrap-up` refuses to promote when another `session-YYYY-MM-DD-*.md` already exists for today that this session did not write, and asks.
+- **(iv)** Nothing; accept that a day is a single record.
+
+**Recommendation: (iii) first, then (ii).** (iii) is small, needs no schema change, and converts a silent overwrite into a question — which is the whole difference between this defect and its absence. (ii) is the real repair but changes what `MEMORY.md`'s Active Session *is*, and that block is read at every wake by every party; it should not be reshaped in the same act that discovers the problem. ⚠ (i) is deliberately not recommended first: it multiplies the files the wake must read, and the wake's budget is already a live constraint (`MEMORY.md` is at 23.9 KB against a stated ceiling).
+
+**⚠ What this item does not establish.** How often two sessions occur in one day. The executor cannot observe it — the same limit PENDING-104 ADDENDUM 2 declares about its own option space. Today is one instance, and it arose from PENDING-172's mechanism rather than from the steward choosing to run two.
+
+**Files affected:** `~/.claude/skills/wrap-up/SKILL.md`, `~/.claude/skills/symmetria/SKILL.md` (§4 ledger path), `MEMORY.md`'s Active Session convention.
+**Awaiting:** Steward authorization.
+
+---
+
+## PENDING-175 — `governance_item` returns the first block under an id and gives no sign that others exist
+**Date:** 2026-08-31
+**Tag:** [FIX]
+**Raised by:** the jurist, first-hand, while ruling PENDING-172 on 2026-08-31 — REVIEWED-132 draft §7, which routes it here as a separate item.
+**Summary:** `t_item` in `scripts/governance-mcp.py` iterates `item_spans` and **returns inside the loop on the first header matching the id**. When two `## ` blocks share an id — a parent and its amendment — only the parent is returned, with nothing in the output indicating a sibling exists.
+
+**⚠ THE JURIST'S CHARACTERISATION IS CORRECTED BY THE CODE, AND THE CORRECTION MAKES IT SMALLER.** The ruling reads *"the id alone does not reach it."* The id **does** reach it. `governance-mcp.py:200` —
+
+```python
+for head, start, end in wd.item_spans(text):
+    if head == ident or head.startswith(ident + " "):
+        return (...)
+```
+
+`PENDING-172 — AMENDMENT 1: …` satisfies `head.startswith("PENDING-172 ")` exactly as the parent does. The predicate matches both blocks; the `return` is inside the loop, so the second is never reached. This is an early return, not a matching failure — a smaller defect with a smaller fix, and it should be recorded as what it is.
+
+**Why it bit here and not before.** `item_spans` treats **any `## ` header** as an item and `### ` as body (`l.startswith("## ")` is False for `### `). So the register's two amendment placements behave oppositely: a `###` amendment sits **inside** its parent's span and is returned with it, while a `##` amendment becomes a **separate item** that a parent-id lookup silently truncates before. PENDING-172 AMENDMENT 1 was filed as `##`, following the PENDING-133 and PENDING-162 precedent; PENDING-164 AMENDMENT 2, filed the same day, used `###` and would have been returned intact. **Neither placement is wrong under any stated rule, and that is PENDING-173 ADDENDUM 1's finding arriving at a fourth instrument.**
+
+**The consequence is not hypothetical.** The jurist reports it nearly ruled on PENDING-172's Recommendation, which AMENDMENT 1 corrects as **wrong**. The retrieval tool built to give the jurist verbatim access returned a verbatim half.
+
+**Recommendation.** Collect every matching span and return all of them, with a leading count (`3 blocks under PENDING-172 — parent, AMENDMENT 1, …`) and each block's line number. A single-block result then means one block exists, rather than meaning nothing about how many do. Add a control with a two-block id — PENDING-172 is now a permanent fixture for it — asserting both blocks are returned; ⚠ the control must assert **both**, since a one-block assertion passes on the current behaviour.
+
+**⚠ Not established.** Whether the same early-return shape exists elsewhere in `governance-mcp.py` or in `wake-digest.py`'s consumers. Not audited here; a first-match return over a multi-match predicate is a class, and this item found one instance of it.
+
+**Files affected:** `scripts/governance-mcp.py` (`t_item`, its controls).
+**Awaiting:** Steward authorization.
+
+## PENDING-176 — Every PDF routes to V-SCAN by file extension, so the verbatim gate abstains on 14 born-digital canonicals
+**Date:** 2026-08-31
+**Tag:** [HARDENING]
+**Summary:** `verify_body_conservation._tier_from_source()` decides the evidence tier from the file *extension* — `.pdf` → `V-SCAN`, unconditionally — so the body-conservation gate ABSTAINS on every PDF-sourced work, including the born-digital ones where ground-truth text exists and the deterministic V-TEXT check is available.
+**Rationale:** The constitution defines the tier by the work's *origin* (V-TEXT = born-digital, source IS ground truth; V-SCAN = no ground-truth text → honest abstain). The mechanism derives it from a filename suffix. For a born-digital PDF the two disagree, and the disagreement is silent and always in the permissive direction: the file graduates with no verbatim check while the gate reports an honest-looking `ABSTAIN`. This is the gate's self-assessment being truthful for scans and wrong for the class it cannot distinguish — and it is invisible precisely because abstention looks like correct behaviour.
+Measured exposure: of 63 PDF-sourced canonicals in Chamber Sources, **14 are born-digital** and 49 are genuine scans. The 14 are the same population the ratified spec already names in v2.9.1's "0 of 14 born-digital Chamber-Sources PDFs are two-column" — reproduced here independently by re-running `classify_pdf_origin.py` over the manifest.
+The repo **already owns the missing signal**: `classify_pdf_origin.py` exists, was ratified-adjacent under REVIEWED-83 A1, and its own docstring says it is "NOT wired to any gate." Classifier and gate are both present and not connected.
+⚠ One of the 14, `orthotypographie-vol-1-a-f-lacroux`, independently carries 48 sites of mid-word split-diacritic damage (`ambigu ï té`) — a born-digital PDF whose verbatim gate abstained, holding exactly the defect class the gate exists to catch. Suggestive, not proof of causation; the other 13 have not been examined.
+**Options:**
+ (a) Wire `classify_pdf_origin.py` into `_tier_from_source()`: `.pdf` → V-TEXT when born-digital, V-SCAN otherwise. Requires deciding the V-TEXT *reference converter* for PDFs — v2.6.0 names `pandoc -t markdown-smart`, which has no PDF reader. `pdftotext` is the obvious candidate but is a **new declared reference** for a format class, i.e. change-class PROPOSAL, not FIX.
+ (b) Leave routing, but make the abstain **loud**: report `ABSTAIN (born-digital — a check was available and not run)` so the silence stops reading as coverage. Cheap, honest, no new reference converter.
+ (c) Both: (b) now, (a) behind the reference-converter ruling.
+**Recommendation:** (c). (b) is a same-day FIX that removes the false reassurance; (a) is the real repair but cannot land until the PDF-class reference converter is ruled, because a reference chosen by the executor would re-encode a convention independently of the spec — the drift the amendment process names.
+**Files affected:** `scripts/verify_body_conservation.py` (`_tier_from_source`, `verify_candidate`); `scripts/classify_pdf_origin.py` (wiring); `_curation/graduation-spec.yaml` (`body_conservation:` declared data); `docs/chamber-library-specification.md` §Tiering & Fence if (a).
+**Awaiting:** Steward authorization.
+
+## PENDING-177 — The runbook's PDF recipe selects a backend that splits words, and docling flattens curly quotes on the whole PDF class
+**Date:** 2026-08-31
+**Tag:** [PROPOSAL]
+**Summary:** Two findings from the first measured run of the `pdf_textlayer` lane. (i) The recipe as written (`docling --to md`) uses docling's default backend, which splits diacritics mid-word — `Türk` → `T ü rk`, 16/16 sites in a 20-page pilot; `pypdfium2` renders all 16 correctly. (ii) *Every* docling backend flattens curly quotation marks to spaced straight apostrophes, which engages REVIEWED-67's front-end eligibility clause for the PDF class.
+**Rationale:** On (i): this is the same mid-word-space Tier-3 damage that the 2026-07-19 interim ruling barred docling's EPUB path for. That ruling recorded the defect as a property of docling's *EPUB* parse and left the scan/PDF tiers with docling. The defect is **not EPUB-specific**. Because the runbook names no backend, the damaging default is what the recipe selects, and `verify_conversion` returns 5/5 PASS on the damaged output — no existing gate sees it.
+On (ii): REVIEWED-67 ruled that *a front-end that silently applies prophylactic Tier-2 / Tier-3 alteration to a format class is not eligible*, census-before-adoption, boundary by mechanism. Curly→straight quote flattening is uncatalogued Tier-2, applied prophylactically to the whole class, and is backend-independent (measured across four backends), so it is a docling property rather than a parser artifact. The corpus norm is the opposite: **1061 of 1297 canonicals carry curly quotes**; only 222 are straight-only. Adopting docling for PDFs as-is would silently move every future PDF work into the minority class and destroy the opening/closing distinction — load-bearing in a book that quotes period treatises throughout.
+This is a *prospective* finding, not a blocker report: it is raised before any PDF work graduates on this lane, which is what census-before-adoption asks for.
+**Options:**
+ (a) Amend the runbook recipe to `docling --to md --pdf-backend pypdfium2 --image-export-mode placeholder` and declare quote-flattening as a catalogued Tier-2 normalization in `graduation-spec.yaml` `normalize:`. Cheapest; but cataloguing an alteration to make a front-end eligible is exactly the move REVIEWED-67 was written to prevent, unless argued and ruled.
+ (b) Recipe fix + a post-conversion quote-restoration step verified against the source's own quote positions. Restores fidelity; needs a new tool and its negatives.
+ (c) Recipe fix + accept the flattening as a declared, argued exposure for the PDF class (the "explicit argued acceptance" branch the spec already uses for order attestation), bounded by the measured figure and revisited when a quote-faithful PDF front-end exists.
+ (d) Reject docling for born-digital PDFs; find a quote-faithful front-end (`pdftotext` preserves all 134 curly quotes but yields no structure — 174 headings recovered by docling, 0 by pdftotext).
+**Recommendation:** (a) for the backend flag immediately — it is a pure FIX, strictly reduces damage, and needs no ruling. For the quote question, (c): the alteration is uniform, mechanically detectable, and reversible in principle, and (d) trades 134 quote marks for the entire heading structure — a worse bargain. But (c) is a spec-visible acceptance and is the steward's and jurist's to make, not the executor's.
+**Files affected:** `_curation/conversion-runbook.yaml` (`pipelines.pdf_textlayer`); `_curation/graduation-spec.yaml` (`normalize:`); `docs/chamber-library-specification.md` §V if (c); `_curation/tool-evolution-log.md` (entry filed 2026-08-31).
+**Blocks:** graduation of `classical-and-romantic-performing-practice-brown` (converted + `verify_conversion` 5/5 PASS, staged in `scratch/making/`), and any other born-digital PDF on this lane.
+**Awaiting:** Steward authorization; jurist design gate on the eligibility question.
+
+---
+
+### PENDING-172 — BUILD RECORD: (e), (c) and (b) landed under REVIEWED-131
+**Date:** 2026-08-31
+**Placement note:** appended, not inserted, per the PENDING-164 AMENDMENT 2 precedent of today.
+**Status:** **BUILT** — `70440db`, under REVIEWED-131 (2026-08-31).
+
+- **(e)** `parked_workers()` in `scripts/wake-digest.py` reads `~/.claude/jobs/<id>/state.json`'s `respawnFlags`. Fails to **NOT ESTABLISHED**, never to safety: a missing directory, an unparseable `state.json`, and an absent `respawnFlags` are each enumerated by name rather than counted as *no parked workers* (cond. 1).
+- **(c)** `human_turns()` counts genuine human turns in a transcript, discounting hook-injected records and `/clear`/`/exit`. **Retrospective by construction** — at SessionStart the current session has no turns — and the output says so. Each line names the control that produced it (cond. 2).
+- **(b)** the `OPEN QUESTION` field is now emitted as *"orientation, not an instruction — inherited from a human and answerable to one"*, marked in the code as **annotation and explicitly not a control** (cond. 3).
+
+**⚠ Two defects found by the build's own controls, recorded rather than smoothed.** `json` was never imported, which the digest's top-level guard would have turned into `WAKE DIGEST UNAVAILABLE` **at every session start** — caught by the selftest on its first run. And the first draft asserted that a **stopped** job carrying the flag would take a turn on restart; whether the daemon respawns a stopped job is **not established**, and the output now says exactly that rather than claiming it is live or claiming it is safe.
+
+**Controls:** both directions, and two drawn from the event itself — `human_turns` returns **0** on `b7e7eb39` (the unattended session) and **>0** on the attended session that found it. Those two report **NOT ESTABLISHED** rather than passing if the transcripts age out of the 30-day window.
+
+**Live at time of filing:** 1 job dir read, 0 unreadable, 1 ARMED — `acaabadf`, `state=stopped`, reported as *neither live nor proven safe*.
+
+---
+
+### PENDING-173 — BUILD RECORD: option (a) landed under REVIEWED-132, and condition 3 found a defect in it
+**Date:** 2026-08-31
+**Kin:** **PENDING-146** — the prospective-convention question is routed there by REVIEWED-132 condition 5 and is deliberately **not** decided by this build. Also PENDING-145 (`ruled_pendings`), PENDING-175 (`governance_item`), and PENDING-110.
+**Status:** **BUILT** — `cb8cab5`, under REVIEWED-132 (2026-08-31).
+
+The control now reads all three registers at `##` and `###`, recognises `ADDENDUM`, and computes `originals` **across** registers, because a parent may be archived while its amendment stays open. Condition 1's default is inverted: a header is an original **only** if it carries an identifier and no marker, so a compound or an addendum is excluded from `originals` rather than admitted to it.
+
+**⚠ CONDITION 3 FIRED ON MY OWN CODE, WHICH IS WHAT IT IS FOR.** Enumerating rather than counting returned **89** against ADDENDUM 1's **82**. The surplus was six prose titles — *"Citation amendment (#2)"*, *"Dream amendment"*, *"PENDING-46 addendum (2026-07-03)"* — matched by an upper-casing containment test and **struck off `originals`**. That is the mirror of the bug being repaired: it would have raised **false** *"the record was replaced"* findings against six genuine originals. Markers are now uppercase standalone tokens, with controls in both directions. The enumeration then agrees with ADDENDUM 1's method at **82**.
+
+**The residual disagreement is reported, not reconciled.** ADDENDUM 1's filed table says **81**; its own method re-run today says **82**. The difference is **this session's later filing**, not a classifier difference. **The table stands as filed.**
+
+**Live at time of filing:** 32 attributable blocks checked, all resolve; **50 NOT ESTABLISHED** (48 unnumbered headers, 2 in-body) — counted, never passed. 59/59 instrument controls pass.
+
+## PENDING-177 — AMENDMENT 1: the rule already exists and is general; what is missing is its application, and my framing of the July record was wrong
+**Date:** 2026-08-31
+**Tag:** [ESCALATE]
+**Summary:** Reading the 2026-07-19 and 2026-07-20 rulings themselves rather than the runbook's summary of them changes this item in three ways. (i) My statement that the July record treated the mid-word defect as an EPUB-parse property is **false** — the ruling said "parse-time loss in **its own document model**" and REVIEWED-67 Q4 ruled the eligibility rule **general**. There is no false premise to correct; there is a general rule that was never applied to the PDF class. (ii) The genuine defect in the ratified text is Q2's **mechanism-boundary**, which I can now evidence. (iii) Two obligations from REVIEWED-67 are undischarged at 42 days, and one of them is the direct cause of the failure I reported.
+**Correction to my own report:** I told the steward "we recorded it as an EPUB-parse property; it isn't." The record does not say that. What was scoped to EPUB was the *routing stop*, because that is where the evidence stood. The doctrine was already general. The error was mine, not the jurist's, and it made a correctly-general ruling look like a narrow one.
+**The Q2 boundary, with evidence.** REVIEWED-67 Q2 refined the ineligibility to *"any source class whose Docling path routes through the HTML backend is ineligible pending census"* — named by mechanism, explicitly for "mechanistic accuracy for what comes later." This is what came later, and the naming is one layer too low:
+ · All four docling PDF backends flatten every curly quote to a spaced straight apostrophe (`docling_parse`, `dlparse_v1`, `dlparse_v4`, `pypdfium2` — 134 → 0 curly on a 20-page pilot, each).
+ · `docling --to json` shows the **document model itself** carries **0 curly / 380 straight**. The loss is at parse, before any markdown serialization, and independent of backend choice.
+ ⇒ The defect is in the document model shared by *all* input formats, not in the HTML backend. As drawn, the boundary does not catch the PDF class though the identical defect and the ruling's own identical mechanism-description are present there. **I have not re-scoped it — that is the jurist's to correct.**
+**Two undischarged REVIEWED-67 obligations:**
+ · **The Q4 byte-census.** Q4 gates *adoption as canonical front-end for a class*, not use. `conversion-runbook.yaml` already routes `pdf_textlayer` → docling, so **docling is already adopted as the canonical PDF front-end with no census** — the identical PENDING-56 error repeated in a second format class. No typography byte-census artifact exists in `_curation/` or `docs/` for *any* class; the census Q3 conditioned on being specified as declared data was never specified either.
+ · **The per-conversion typography gate** — the ruling's "forward item, unconditioned": *"run per conversion… it becomes a wired gate that catches converter-version drift, per-file anomalies, and any future front-end's silent normalization — without anyone having to predict which converter might misbehave."* Not built; the gate list is `verify_conversion · verify_graduation · body_word_conservation · sidecar_gate`. **Its absence is exactly why `verify_conversion` returned 5/5 on word-damaged output.** My run is an instance of the failure the jurist predicted 42 days before it happened.
+**Bundling error, corrected.** PENDING-177 as filed bundled a FIX with a PROPOSAL under one ID — the CLASS E defect PENDING-146 names (the open list's unit is the ID; the decidable unit is the item), which left a damage-reducing fix blocked behind a ruling it does not need. **Split, and the FIX has landed:** `pdf_textlayer` now carries `--pdf-backend pypdfium2 --image-export-mode placeholder`, since Q1 confirmed lane routing is declared data revisable without supersession, and the change strictly reduces damage and alters nothing a gate accepts. The runbook records, at the point of work, that the flag fix is **not** a censused adoption. What remains under -177 is the eligibility question alone.
+**Awaiting:** Jurist correction of the Q2 mechanism-boundary; steward direction on the two undischarged obligations. The Brown candidate stays staged either way.

REVIEWED.md

@@ -2429,4 +2429,53 @@ re-installs shims into the global hooks directory, observed recurring twice on 2
 
 **If AUTHORIZED:** Message change already at 2408032; controls run (whitespace 6 MB refused and
 printing the new text, plain 6 MB refused, small file committed). No further executor action on
-PENDING-163. Close PENDING-163. Tag nothing new with REVIEWED-130.
+PENDING-163. Close PENDING-163. Tag nothing new with REVIEWED-130.
+
+## REVIEWED-131 (PENDING-172) — A version upgrade resumed an unattended executor, and the wake digest became its work order
+**Date:** 2026-08-31
+**Decision:** AUTHORIZED in part — (e) and (c) as a two-substrate control, (b) as annotation only; (d) recorded as a steward policy decision, not ruled here. One leg severed.
+**Rules on:** PENDING-172 (parent) and PENDING-172 AMENDMENT 1, both blocks, named explicitly per PENDING-145 and PENDING-146.
+
+**Notes:** The finding is accepted. Constraint 5 was not wrong but unenforced, and the item is correct not to propose amending it. AMENDMENT 1's correction of its own parent is better than the claim it replaces and is the reason this ruling can be more than a policy note.
+
+1. CONDITION — **(e) is authorized as the primary control and must fail to NOT ESTABLISHED, never to safety.** A missing, unreadable or empty `~/.claude/jobs/` reports NOT ESTABLISHED, not 'no parked workers'. The item states this weakness itself; it is raised from disclosure to requirement. The check enumerates every job dir read and every one it could not read, per REVIEWED-122 condition 4 — a control over parked workers whose negative result is an opaque zero is the failure this item is about.
+
+2. CONDITION — **(c) is authorized as a second control on a different substrate, and is never reported as the primary one.** (e) reads harness state; (c) reads the session's own transcript for a preceding human record. Two differently-positioned readers is Constraint 6's logic and the reason to build both. Output must name which control fired.
+
+3. CONDITION — **(b) is authorized as annotation and is explicitly not a control.** Marking the digest as orientation, and `OPEN QUESTION` as inherited-from-a-human and answerable to a human, is cheap and honest. It cannot enforce and must not appear in any report as a mitigation. The item's own warning on this point is adopted verbatim.
+
+4. **(d) is the steward's standing decision and is not ruled.** Recorded because it survives whatever is built: both binaries contain the mechanism, `cause=upgrade` supplied the restart and not the capability, and the sole precondition is a parked idle worker. The burden has moved — keeping background sessions is now the choice requiring justification. (e) is the tripwire that reports whether the policy is holding; it is not a substitute for the policy.
+
+5. **SEVERED — the memory protocol assumes one executor per day.** Date-keyed `session-ledger-YYYY-MM-DD.md`, one session file, one Active Session block with demote-on-promote: two concurrent sessions do not merge and the second silently becomes the record of the day. This is a live `[HARDENING]` ask embedded in an `[ESCALATE]` item — the shape PENDING-146 names in PENDING-131 ADDENDUM 2. It is filed as its own item and is not disposed of here. Its cost was incurred today, not hypothetically.
+
+6. **PROVENANCE, not voiding.** PENDING-171 and commit `5ba5842` were produced with no human turn in the session. They are not void: their findings are checkable against the substrate independently of who filed them, and PENDING-173 has already relied on one. Both carry a dated provenance marker naming the session and the absent loop, per no-silent-revision. **PENDING-171 is not to be ruled until it carries that marker** — an unmarked record does not say on its face what it is, which is PENDING-110's complaint at a new site.
+
+7. **A recorded limit, not a fault.** Deleting `~/.claude/jobs/84ce2880/` was the steward's instruction and its load-bearing values were quoted first. It nonetheless narrows the parent's own 'Not established' question — how a session comes to be `kind: background`. The remaining evidence is `acaabadf`, deliberately kept. Do not delete it.
+
+8. **Scope of this ruling.** I read both blocks verbatim via `governance_item` and `governance_search`. `daemon.log`, the transcript record numbers, `respawnFlags` values and the cross-binary string counts are executor testimony from files I cannot open. The item's own limit on the last of these — identical string counts do not establish identical respawn policy — is preserved rather than resolved.
+
+**If AUTHORIZED:** Build (e) first, with its NOT ESTABLISHED path and enumeration. Then (c). Apply (b) on the same pass, marked as annotation in the code and in the output. File the severed item at §5 before wrapping. Place the provenance markers at §6 before PENDING-171 is brought forward.
+
+## REVIEWED-132 (PENDING-173) — The register-integrity control covers one word of a two-word convention, in one of two registers
+**Date:** 2026-08-31
+**Decision:** AUTHORIZED — option (a), on five conditions. The proposed maxim is WITHHELD; the convention question is routed to PENDING-146 and not decided here.
+
+**Notes:** The three undeclared narrowings are real, the demonstration is the right kind (the count did not move when a matching header was appended), and the latent false-negative runs in the dangerous direction — an `ADDENDUM` counted as an original can satisfy 'an un-amended entry exists' on behalf of a record that was replaced. The item's declared correction of its own first census is what earns the rest of it.
+
+1. CONDITION — **`originals` defaults to not-original on any unrecognized marker.** The predicate is an enumerated list of amendment-marker forms, and a header carrying an unrecognized marker is excluded from `originals` rather than admitted to it. This mirrors REVIEWED-122 condition 2: an unlisted verb never yields the permissive answer. The current `not startswith('AMENDMENT')` fails in the permissive direction, which is why one word's absence became a latent pass.
+
+2. CONDITION — **controls are drawn from the census, not from the author's memory of the convention.** The fixture set must contain, at minimum, `ADDENDUM` headers, in-body `**AMENDMENT`/`**ADDENDUM` forms, and `PENDING`-side instances. For any form present in the record and not covered by a control, the check reports NOT ESTABLISHED rather than passing. This is the third instance this month of a positive control satisfied by the narrowing it should have caught, and the item names the other two itself.
+
+3. CONDITION — **the acceptance check enumerates, it does not count.** '3 → 16' is not the check. The thirteen newly visible blocks are listed by register and header, and compared against the item's table. If the two disagree, the disagreement is the finding and is reported, never reconciled by amending the table.
+
+4. CONDITION — **placed records are not rewritten.** Affirmed, and consistent with REVIEWED-122 condition 5. Widening the reader is authorized; normalizing headers already placed is not, here or by implication.
+
+5. CONDITION — **the convention question is routed to PENDING-146, which is open and argues the opposite ordering.** PENDING-146 recommends convention-first with detection as tripwire, on the adjacent axis of the same undefined convention. PENDING-173 does not cite it. A *prospective* definition — what AMENDMENT means as against ADDENDUM, for blocks filed from here on, touching no placed record — is neither this item's (a) nor its (b), and it is the option its own root-cause diagnosis points at. This ruling authorizes the parser widening, which is owed under either ordering, and leaves the convention to 146.
+
+6. **THE MAXIM IS WITHHELD.** 'Widen the instrument to the record; never rewrite the record to fit the instrument' is stated more absolutely than its cited authority supports. REVIEWED-122 condition 5 declined normalization *as an executor act in that ruling* and expressly reserved it as a separate steward act carrying a dated note. Strengthened-by-relay, and the strengthening is load-bearing: adopted as written, the maxim would decide PENDING-146 by side-effect in the direction 146 argues against. The corrected form, offered and not ratified: *the instrument is widened to the record; a placed record is normalized only by a dated steward act stating what changed and why.* Doctrine addition is `[ESCALATE]` and belongs with 146.
+
+7. **A fourth instrument, observed first-hand this session.** `governance_item(id='PENDING-172')` returns the parent block only, with no indication that a sibling exists; AMENDMENT 1 is reachable only by its full header string. The jurist's own reading tool has the defect this item reports, and it nearly produced a ruling on a Recommendation that AMENDMENT 1 corrects as wrong. Recorded here because it belongs to this item's class and is not testimony — it happened to the instrument in the act of ruling. Whether the MCP server's id resolution is fixed is a separate item.
+
+8. **Scope of this ruling.** The line numbers, the census table, the fixture contents and the append-and-recount demonstration are executor testimony from a script I cannot run. What I verified directly: REVIEWED-122 condition 5 verbatim, PENDING-110 option (c) verbatim, PENDING-145 and PENDING-146 verbatim, and the behaviour of `governance_item` at §7.
+
+**If AUTHORIZED:** Implement (a) per conditions 1–4. Report the enumeration in full, agreements included. Do not touch placed headers. Cross-reference PENDING-146 in the commit and in the item's kin list.

claude/governance/PENDING-142-answer-key-2026-08-27.md

@@ -0,0 +1,184 @@
+# ANSWER KEY — per-block disposition, PENDING.md
+**Drafted 2026-08-27 by the executor, BY HAND, BEFORE any implementation exists.**
+
+Pre-registration under **REVIEWED-122 condition 1** — *"hand-read and committed before the
+implementation exists, with the commit hash recorded"* — and at the granularity **PENDING-146**
+requires: *"The key MUST be keyed on `## ` blocks, and must record, per block, whether it carries
+a live `**Awaiting:**` and at what tag."*
+
+⚠ **Why block granularity is safe under every ruling.** A block-keyed key is strictly finer than
+an id-keyed one and collapses to it if the unit question is ruled the other way; the reverse is
+false. Drafting finer is therefore safe under every outcome of Q1 and Q4 — the jurist's
+correction, 2026-08-27, of this executor's refusal to draft.
+
+⚠ **The population is not 69.** REVIEWED-122 said "all 69 filtered items" on 2026-08-17. The live
+file holds **120 `## ` blocks** across **106 distinct ids** — so **14 blocks are invisible as
+units** under id-keying. The 69 is stale and the key covers the current population.
+
+## Verdict vocabulary
+| verdict | meaning |
+|---|---|
+| `LIVE` | the `Awaiting:` line states an outstanding ask and nothing contradicts it |
+| `STALE` | the line asks for something **verified done** — the ask survives as prose only |
+| `PARTIAL` | the line itself records one leg discharged and one open |
+| `UNDETERMINED` | cannot be settled without a steward read; **enumerated, never counted**, per REVIEWED-122 condition 4 |
+| `NONE` | the line explicitly states no outstanding ask |
+
+## Basis column — the honesty of this key depends on it
+- `line` — the verdict follows from the `Awaiting:` line alone.
+- `read` — the item body and/or `~/REVIEWED.md` was read to settle it.
+
+⚠ **DECLARED LIMIT, stated rather than papered over.** Only the rows marked `read` are hand-read
+in the full sense REVIEWED-122 condition 1 intends. The `line` rows are hand-*assigned* from a
+dispositive field, which is weaker. **Completing the `read` pass over all 120 blocks is owed and
+is not done.** Recording that here is the point: a key that claimed a uniform standard it did not
+meet would be the pass-by-construction failure in a new costume.
+
+## Findings already produced by drafting at this granularity
+1. **`REVIEWED-127` names two items in one header** — `## REVIEWED-127 — PENDING-157 + PENDING-158 —`.
+   The `ruled_pendings` regex requires `PENDING-(\S+?)\s*—` and cannot match across the ` + `,
+   so **it captures nothing and suppresses nothing.** PENDING-157 and -158 are **AUTHORIZED** and
+   still read as open. This is PENDING-145's under-suppression class, second instance, alongside
+   REVIEWED-116's `131/132/133/134`, and it was **not** in the package.
+2. **The same two blocks are also `STALE`** — their `Awaiting:` lines ask the steward to place
+   REVIEWED-127, which is placed. Two independent defects on one pair of items.
+3. **The executor used both `##` and `###` for addenda on the same day** — PENDING-162 AMENDMENT 1
+   as `##` (a block), PENDING-104 ADDENDUM 1 and the PENDING-89 note as `###` (not blocks). There
+   is no convention distinguishing them, and PENDING-139(A) is the same defect on the REVIEWED side.
+
+## The key
+
+| line | id | verdict | basis | tag | shares id | suppressed | Awaiting (verbatim, truncated) | note |
+|---|---|---|---|---|---|---|---|---|
+| 20 | 4 | `NO-AWAIT-LINE` | line | [FIX] — recl |  |  | — | block carries no Awaiting: line at all |
+| 29 | 5 | `LIVE` | line | [FIX] |  |  | Investigation — likely needs Seb's input on the query dispatch archite | line states an ask and nothing in it contradicts |
+| 41 | 10 | `LIVE` | line | [PROPOSAL] |  |  | Steward + Seb architectural review. | line states an ask and nothing in it contradicts |
+| 55 | 11 | `LIVE` | line | [PROPOSAL] |  |  | Steward entry in REVIEWED.md. | line states an ask and nothing in it contradicts |
+| 71 | 12 | `LIVE` | line | [HARDENING] |  |  | Steward entry in REVIEWED.md. | line states an ask and nothing in it contradicts |
+| 88 | — | `NO-AWAIT-LINE` | line |  |  |  | — | block carries no Awaiting: line at all |
+| 99 | — | `NO-AWAIT-LINE` | line |  |  |  | — | block carries no Awaiting: line at all |
+| 107 | — | `NO-AWAIT-LINE` | line | [ESCALATE] |  |  | — | block carries no Awaiting: line at all |
+| 124 | — | `NO-AWAIT-LINE` | line | [CONSTITUTIO |  |  | — | block carries no Awaiting: line at all |
+| 141 | S2 | `LIVE` | line | [PROPOSAL] |  |  | Jurist shape-review of contract language (candidate text in Jurist sha | line states an ask and nothing in it contradicts |
+| 158 | S4 | `LIVE` | line | [PROPOSAL] |  |  | Jurist contract definition (Q1); steward authorization; mempalace upst | line states an ask and nothing in it contradicts |
+| 175 | S5 | `LIVE` | line | [PROPOSAL] |  |  | Jurist contract definition (Q1); steward authorization; mempalace upst | line states an ask and nothing in it contradicts |
+| 192 | S6 | `LIVE` | line | [HARDENING] |  |  | Steward authorization (S0 closure unblocks). | line states an ask and nothing in it contradicts |
+| 215 | S7 | `LIVE` | line | [HARDENING] |  |  | Steward authorization. | line states an ask and nothing in it contradicts |
+| 232 | S9 | `LIVE` | line | [HARDENING] |  |  | Steward authorization. Optional relationship to S1: implement S1 first | line states an ask and nothing in it contradicts |
+| 249 | 76 | `LIVE` | line | [ESCALATE] |  | **yes** | Steward — withdraw, or re-pose against the extraction framing. | line states an ask and nothing in it contradicts |
+| 261 | 77 | `LIVE` | line | [ESCALATE] |  | **yes** | Steward authorization. | line states an ask and nothing in it contradicts |
+| 278 | 78 | `LIVE` | line | [ESCALATE] — |  |  | Steward edit; jurist review of the asymmetry. | line states an ask and nothing in it contradicts |
+| 291 | 79 | `LIVE` | line | [ESCALATE] — |  | **yes** | Steward authorization. | line states an ask and nothing in it contradicts |
+| 368 | 80 | `LIVE` | line | [ESCALATE] — |  | **yes** | Steward authorization. | line states an ask and nothing in it contradicts |
+| 424 | 81 | `LIVE` | line | [ESCALATE] — |  |  | Steward decision on finding #1 (is Cowork a party?), and authorization | line states an ask and nothing in it contradicts |
+| 452 | 82 | `STALE` | read | [PROPOSAL] — |  |  | ~~Steward authorization to install~~ → **INSTALLED AND IN USE. CLOSED  | self-declares CLOSED 2026-08-08; PENDING-161's confirmed self-closure case, still listed open |
+| 523 | 83 | `LIVE` | line | [PROPOSAL] |  | **yes** | Steward authorization. Harrison holds at the graduation stamp until ru | line states an ask and nothing in it contradicts |
+| 612 | 84 | `LIVE` | line | [HARDENING] |  |  | Steward triage of priority. Not urgent; not to be lost. | line states an ask and nothing in it contradicts |
+| 656 | 85 | `NONE` | line | [FIX] |  |  | Nothing blocking; do before the classifier's per-file verdicts gate an | line states no outstanding ask |
+| 690 | 86 | `LIVE` | line | [HARDENING] |  | **yes** | Steward authorization — it widens what the jurist can read, which is t | line states an ask and nothing in it contradicts |
+| 714 | 87 | `LIVE` | line | [PROPOSAL] |  | **yes** | Jurist design gate, then steward authorization. | line states an ask and nothing in it contradicts |
+| 724 | 88 | `LIVE` | line | [PROPOSAL] |  | **yes** | Steward authorization. | line states an ask and nothing in it contradicts |
+| 753 | 89 | `LIVE` | line | [HARDENING] |  |  | Steward direction on (a)/(b)/(c), and on whether the executor is the r | line states an ask and nothing in it contradicts |
+| 984 | 90 | `LIVE` | line | [ESCALATE] |  |  | Steward authorization, and direction on (a)/(b)/(c)/(d). | line states an ask and nothing in it contradicts |
+| 998 | 91 | `LIVE` | line | [PROPOSAL] |  |  | Steward relay to the jurist, and a decision on Q5 before the ruling is | line states an ask and nothing in it contradicts |
+| 1012 | 92 | `LIVE` | line | [HARDENING] |  |  | Steward authorization; then Seb review via PR per Constitutional Const | line states an ask and nothing in it contradicts |
+| 1026 | 93 | `LIVE` | line | [PROPOSAL] |  |  | Seb, via the co-authored L1 channel; steward relay. | line states an ask and nothing in it contradicts |
+| 1037 | 94 | `LIVE` | line | [ESCALATE] |  |  | Steward authorization before any change; then Seb, as L1 core. | line states an ask and nothing in it contradicts |
+| 1060 | 95 | `LIVE` | line | [HARDENING] |  |  | Steward authorization. | line states an ask and nothing in it contradicts |
+| 1244 | 96 | `LIVE` | line | [HARDENING] |  |  | Steward authorization. | line states an ask and nothing in it contradicts |
+| 1283 | 97 | `LIVE` | line | [PROPOSAL] |  |  | Steward authorization. | line states an ask and nothing in it contradicts |
+| 1294 | 98 | `LIVE` | line | [HARDENING] |  |  | Steward authorization. | line states an ask and nothing in it contradicts |
+| 1307 | 99 | `NONE` | line | [PROPOSAL] — |  | **yes** | Nothing. **RULED 2026-08-06 — REVIEWED-87 placed** (ruling filed verba | line states no outstanding ask |
+| 1348 | 100 | `LIVE` | line | [PROPOSAL] — |  |  | Steward routing — this is chamber-governed (not D-1), so it needs the  | line states an ask and nothing in it contradicts |
+| 1367 | 101 | `NONE` | line | [HARDENING] |  | **yes** | Nothing on the brief itself. **RULED 2026-08-06 — REVIEWED-88 placed:* | line states no outstanding ask |
+| 1436 | 102 | `LIVE` | line | [HARDENING] |  | **yes** | ⚠ **One thing, and it is not a ruling.** RULED 2026-08-06 — REVIEWED-8 | line states an ask and nothing in it contradicts |
+| 1461 | 103 | `LIVE` | line | [ESCALATE] |  |  | steward/jurist. Do not remediate without explicit authorization (const | line states an ask and nothing in it contradicts |
+| 1488 | 104 | `LIVE` | line | [HARDENING] |  | **yes** | A **date**, not an authorization. **RULED 2026-08-06 — REVIEWED-93 pla | line states an ask and nothing in it contradicts |
+| 1531 | 105 | `NONE` | line | [PROPOSAL] |  | **yes** | Nothing. **WITHDRAWN 2026-08-06 — REVIEWED-92 placed.** Conceded by th | line states no outstanding ask |
+| 1549 | 106 | `LIVE` | line | [HARDENING] |  | **yes** | steward — whether a fleet-wide doc-vs-mechanism comparison is worth th | line states an ask and nothing in it contradicts |
+| 1589 | 107 | `LIVE` | line | [ESCALATE] |  | **yes** | steward + jurist. Independent verification requested before any action | line states an ask and nothing in it contradicts |
+| 1627 | 108 | `LIVE` | line | [HARDENING] |  |  | Steward authorization for (b) and (c). The measurement is already done | line states an ask and nothing in it contradicts |
+| 1674 | 109 | `LIVE` | line | [HARDENING] |  |  | Steward — a date, not an authorization. The authorization is given (Q4 | line states an ask and nothing in it contradicts |
+| 1711 | 110 | `LIVE` | line | [HARDENING] |  |  | Steward authorization. (b) is agreed in conversation 2026-08-06; this  | line states an ask and nothing in it contradicts |
+| 1748 | 111 | `LIVE` | line | [PROPOSAL] — |  |  | Steward routing to the jurist. Filed ≠ sent. | line states an ask and nothing in it contradicts |
+| 1808 | 112 | `LIVE` | line | [PROPOSAL] — |  | **yes** | Steward routing to the jurist. Filed ≠ sent. | line states an ask and nothing in it contradicts |
+| 1863 | 113 | `LIVE` | line | [HARDENING] |  | **yes** | Steward disposition of (vi), which gates step 2 of the remediation ord | line states an ask and nothing in it contradicts |
+| 1903 | 114 | `LIVE` | line | [HARDENING] |  | **yes** | Steward authorization of (b). | line states an ask and nothing in it contradicts |
+| 1934 | 115 | `LIVE` | line | [HARDENING] |  | **yes** | Steward authorization. Blocks REVIEWED-97 remediation step 3. | line states an ask and nothing in it contradicts |
+| 1974 | 116 | `LIVE` | line | [PROPOSAL] |  | **yes** | Steward authorization. | line states an ask and nothing in it contradicts |
+| 2007 | 117 | `LIVE` | line | [PROPOSAL] |  | **yes** | Steward authorization. | line states an ask and nothing in it contradicts |
+| 2084 | 118 | `STALE` | line | [HARDENING] |  | **yes** | ~~Steward authorization.~~ → **BUILT 2026-08-08, `see dotfiles HEAD`.  | line records completion in the field that asks |
+| 2138 | 119 | `LIVE` | line | [PROPOSAL] |  | **yes** | Steward authorization. | line states an ask and nothing in it contradicts |
+| 2185 | 120 | `LIVE` | line | [HARDENING] |  | **yes** | Steward authorization. | line states an ask and nothing in it contradicts |
+| 2237 | 121 | `LIVE` | line | [PROPOSAL] — |  | **yes** | Jurist design-gate, then steward authorization. | line states an ask and nothing in it contradicts |
+| 2332 | 122 | `LIVE` | line | [HARDENING] |  | **yes** | Steward authorization. | line states an ask and nothing in it contradicts |
+| 2420 | 123 | `LIVE` | line | [HARDENING] |  | **yes** | Steward authorization. | line states an ask and nothing in it contradicts |
+| 2498 | 124 | `UNDETERMINED` | read | [PROPOSAL] — |  | **yes** | Jurist design-gate → **PACKAGE FILED 2026-08-08**, `~/dotfiles/claude/ | REVIEWED-106 = 'DESIGN GATE PASSED WITH CONDITIONS' — a gate passed is not authorization; PENDING-143 flags it UNDETERMINED and this agrees |
+| 2570 | 125 | `STALE` | line | [HARDENING] |  | **yes** | ~~Steward authorization (D-1 lane).~~ → **(a) BUILT 2026-08-08; (b) OP | line records completion in the field that asks |
+| 2618 | 126 | `STALE` | line | [HARDENING] |  | **yes** | ~~Steward authorization (D-1 lane).~~ → **BUILT 2026-08-08, `8ff5a9f`* | line records completion in the field that asks |
+| 2688 | 127 | `STALE` | line | [HARDENING]  |  | **yes** | ~~Steward authorization (D-1 lane).~~ → **BUILT 2026-08-08, `ccc4d6c`. | line records completion in the field that asks |
+| 2736 | 128 | `UNDETERMINED` | read | [PROPOSAL] — |  | **yes** | ~~Jurist design-gate~~ → **DESIGN GATE PASSED on (a) 2026-08-08**; pla | REVIEWED-111 = 'DESIGN GATE PASSED on (a); (c) rejected'; placement gate outstanding; PENDING-143 flags it UNDETERMINED |
+| 2849 | 129 | `LIVE` | line | [HARDENING]  |  | **yes** | ~~Steward authorization (D-1 lane).~~ → **AUTHORIZED (a) by steward re | line states an ask and nothing in it contradicts |
+| 2895 | 130 | `LIVE` | line | [PROPOSAL] — |  | **yes** | Steward authorization — **and, under (a), the steward's marked answer  | line states an ask and nothing in it contradicts |
+| 2963 | 131 | `LIVE` | line | [HARDENING] | **yes** | **yes** | Steward authorization. | line states an ask and nothing in it contradicts |
+| 3003 | 131 | `LIVE` | line | [HARDENING]  | **yes** | **yes** | Steward authorization. **(a) is not executed and nothing in the corpus | line states an ask and nothing in it contradicts |
+| 3029 | 131 | `LIVE` | line | [HARDENING]  | **yes** | **yes** | Steward authorization on (b), (c)-as-PROPOSAL, and §6. **Nothing in th | line states an ask and nothing in it contradicts |
+| 3061 | 132 | `LIVE` | line | [PROPOSAL] |  | **yes** | Steward authorization. | line states an ask and nothing in it contradicts |
+| 3087 | 133 | `LIVE` | line | [PROPOSAL] | **yes** |  | Steward authorization. | line states an ask and nothing in it contradicts |
+| 3112 | 131 | `NO-AWAIT-LINE` | line |  | **yes** | **yes** | — | block carries no Awaiting: line at all |
+| 3129 | 131 | `LIVE` | line | [HARDENING]  | **yes** | **yes** | Steward direction on Move 1 (build the citation-side voice stamp under | line states an ask and nothing in it contradicts |
+| 3235 | 134 | `LIVE` | line | [PROPOSAL] |  | **yes** | Steward authorization, **after** the MCP restart makes §5/§6.2 indepen | line states an ask and nothing in it contradicts |
+| 3277 | 133 | `LIVE` | line |  | **yes** |  | Steward authorization (with PENDING-134, which supplies the rule this  | line states an ask and nothing in it contradicts |
+| 3290 | 135 | `LIVE` | line | [PROPOSAL] |  | **yes** | Steward authorization. | line states an ask and nothing in it contradicts |
+| 3341 | 136 | `LIVE` | line | [HARDENING] |  | **yes** | Steward authorization. | line states an ask and nothing in it contradicts |
+| 3397 | 137 | `LIVE` | line | [PROPOSAL] |  |  | Jurist ruling per REVIEWED-121 point 2, then steward authorization. | line states an ask and nothing in it contradicts |
+| 3444 | 138 | `LIVE` | line | [HARDENING] |  |  | Steward authorization for the tripwire, deferred to the named dependen | line states an ask and nothing in it contradicts |
+| 3468 | 139 | `LIVE` | line | [HARDENING] |  |  | Steward authorization. ⚠ Until then the register is worded around the  | line states an ask and nothing in it contradicts |
+| 3505 | 140 | `LIVE` | line | [ESCALATE] |  |  | Steward direction, and a jurist design gate if the steward wants the a | line states an ask and nothing in it contradicts |
+| 3539 | 141 | `LIVE` | line | [HARDENING] |  | **yes** | Steward direction on (a)–(d). Not urgent — (a) is the null action and  | line states an ask and nothing in it contradicts |
+| 3619 | 142 | `LIVE` | line | [HARDENING] | **yes** | **yes** | Steward authorization. Nothing has been patched — the relay filing thi | line states an ask and nothing in it contradicts |
+| 3663 | 142 | `LIVE` | line | [HARDENING] | **yes** | **yes** | Steward authorization, with the parent item. Nothing changed in `ruled | line states an ask and nothing in it contradicts |
+| 3682 | 142 | `LIVE` | line | [HARDENING] | **yes** | **yes** | Steward authorization on the standing rule. The arrears above are alre | line states an ask and nothing in it contradicts |
+| 3715 | 142 | `LIVE` | line | [HARDENING] | **yes** | **yes** | Steward. The jurist ruling above needs placement in `~/REVIEWED.md` by | line states an ask and nothing in it contradicts |
+| 3738 | 143 | `LIVE` | line | [FIX] |  |  | Retires when PENDING-142 lands and PENDING-121 becomes visible on its  | line states an ask and nothing in it contradicts |
+| 3756 | 144 | `LIVE` | line | [HARDENING] |  |  | Steward authorization. | line states an ask and nothing in it contradicts |
+| 3779 | 145 | `LIVE` | line | [HARDENING] |  |  | Steward authorization. ⚠ **Independently of the mechanism: PENDING-131 | line states an ask and nothing in it contradicts |
+| 3811 | 146 | `LIVE` | line | [HARDENING] |  |  | Steward. ⚠ **Independently of any ruling: Move 1 and Move 2 await dire | line states an ask and nothing in it contradicts |
+| 3863 | 147 | `LIVE` | line | [HARDENING] |  |  | Steward direction on (i)–(iv). ⚠ **(i) is time-critical: the 2026-08-0 | line states an ask and nothing in it contradicts |
+| 3934 | 148 | `NONE` | line | [PROPOSAL] |  | **yes** | ⚠ **A SECOND jurist gate — the first is discharged.** Design gate rece | line states no outstanding ask |
+| 4138 | 149 | `LIVE` | line | [PROPOSAL] |  | **yes** | Steward ratification of §5 (blocks everything); disposition of `input- | line states an ask and nothing in it contradicts |
+| 4211 | 150 | `LIVE` | line | [ESCALATE] |  |  | Steward authorization. Do not proceed. Do not bundle with PENDING-149. | line states an ask and nothing in it contradicts |
+| 4368 | 151 | `LIVE` | line | [PROPOSAL] |  |  | steward authorization of the design; jurist or steward to commit to st | line states an ask and nothing in it contradicts |
+| 4646 | 152 | `LIVE` | line | [PROPOSAL] |  |  | steward and jurist on the 20-minute interval and on the daemon rejecti | line states an ask and nothing in it contradicts |
+| 5208 | 153 | `LIVE` | line | [PROPOSAL] |  |  | steward authorization. **Not before the soul.** | line states an ask and nothing in it contradicts |
+| 5238 | 154 | `LIVE` | line | [HARDENING] |  |  | PENDING-89 to record which of (a)'s two claims the data supports. | line states an ask and nothing in it contradicts |
+| 5291 | 155 | `LIVE` | line | [PROPOSAL] — |  | **yes** | Steward authorization. | line states an ask and nothing in it contradicts |
+| 5319 | 156 | `LIVE` | line | [HARDENING] |  |  | Steward authorization. | line states an ask and nothing in it contradicts |
+| 5373 | 157 | `STALE` | read | [HARDENING] |  |  | ~~Steward authorization.~~ **AUTHORIZED.** Steward to place REVIEWED-1 | asks steward to place REVIEWED-127 — VERIFIED PLACED, 'AUTHORIZED — both, jointly' |
+| 5407 | 158 | `STALE` | read | [HARDENING] |  |  | ~~Steward authorization, jointly with PENDING-157.~~ **AUTHORIZED.** S | asks steward to place REVIEWED-127 — VERIFIED PLACED, 'AUTHORIZED — both, jointly' |
+| 5485 | — | `NONE` | line | [FIX] — a ma |  |  | nothing — **DISCHARGED 2026-08-26**, as the agreed first act of the ne | line states no outstanding ask |
+| 5527 | 159 | `LIVE` | line | [ESCALATE] |  | **yes** | steward and jurist. Related: PENDING-82, PENDING-89, PENDING-140, PEND | line states an ask and nothing in it contradicts |
+| 5711 | 160 | `LIVE` | line | [HARDENING] |  |  | steward and jurist. ⚠ **Deliberately filed without a recommendation**  | line states an ask and nothing in it contradicts |
+| 5770 | 161 | `LIVE` | line | [ESCALATE] |  |  | steward. | line states an ask and nothing in it contradicts |
+| 5822 | 162 | `LIVE` | line | [ESCALATE] | **yes** |  | steward and jurist. ⚠ **The 09-08 read should not be run as though cle | line states an ask and nothing in it contradicts |
+| 5871 | 162 | `NONE` | line |  | **yes** |  | nothing new. ⚠ **Deliberately carries no live `Awaiting:` line** — per | line states no outstanding ask |
+| 5892 | 163 | `LIVE` | line | [HARDENING] |  | **yes** | Steward authorization. | line states an ask and nothing in it contradicts |
+| 6040 | 164 | `LIVE` | line | [HARDENING] |  |  | Steward authorization. | line states an ask and nothing in it contradicts |
+| 6078 | 165 | `LIVE` | line | [HARDENING] |  |  | Steward authorization. | line states an ask and nothing in it contradicts |
+| 6236 | 166 | `NONE` | line | [FIX] |  |  | nothing — `[FIX]`, steward-specified, **deferred by steward direction  | line states no outstanding ask |
+| 6254 | 167 | `NONE` | line | [FIX] |  |  | nothing — steward-ruled 2026-08-27, **execution deferred to the Septem | line states no outstanding ask |
+| 6277 | 168 | `LIVE` | line | [HARDENING] |  |  | steward and jurist — on the structural remedy, and on whether the doct | line states an ask and nothing in it contradicts |
+| 6298 | 169 | `NONE` | line | [HARDENING] |  |  | nothing. ⚠ **Filed with no live ask by design** — it exists so that fo | line states no outstanding ask |
+| 6317 | 170 | `NONE` | line | [FIX] |  |  | nothing from the steward as a fresh decision — this is a **[FIX] block | line states no outstanding ask |
+
+## Tally — reported, never used as the acceptance check
+
+- `LIVE`: 94
+- `NONE`: 11
+- `STALE`: 7
+- `NO-AWAIT-LINE`: 6
+- `UNDETERMINED`: 2
+
+**Blocks: 120 · distinct ids: 106 · blocks sharing an id: 13 · rows settled by reading: 5**
+
+⚠ **This tally is not the acceptance check.** REVIEWED-122 condition 1 requires a per-item comparison; an aggregate cannot see the defect this key exists to catch. When the implementation lands, the comparison is reported **in full, including agreements** — the clause the package's own quotation of `If AUTHORIZED:` truncated away.

claude/governance/PENDING-164-census-classification-PREREGISTRATION-2026-08-31.md

@@ -0,0 +1,187 @@
+# PENDING-164 AMENDMENT 1 — the classification pass: PRE-REGISTRATION
+
+**Date:** 2026-08-31
+**Written by:** the executor.
+**Status:** pre-registration. Written and committed BEFORE any sampled commit body was read.
+**Inherits:** the literal question left by the 2026-08-27 wrap, quoted verbatim below.
+**Discharges (in part):** PENDING-164 AMENDMENT 1's declared-owed second half — *"the 270-candidate
+classification pass is unscheduled and unclaimed."*
+
+---
+
+## 1. The inherited question, verbatim
+
+> **Of the first 20 census candidates, how many decided about a mechanism the register never
+> mentions?** Run `prior-art.py` on each named mechanism and count the ones returning commits but
+> zero register mentions. ⚠ **A count of zero would be the strongest possible refutation of
+> PENDING-164** and should be reported as such, not explained away. The instrument's own caveat
+> applies in reverse too: absence of commits is weak evidence, but **presence of commits with
+> register silence is exactly the disease**, and today's PENDING-160 case shows the register-mention
+> column is the half that carries the signal.
+
+It is answered as asked. It is also answered on a second sample, for the reason in §3.
+
+---
+
+## 2. ⚠ A population defect found before sampling, and recorded here because it changes the number
+
+`prior-art.py`'s `owned_repos()` computes ownership by testing each repo's remotes against
+`OWNED_HOSTS = ("github.com/davidglidden", "davidglidden/", "git.skemantix.com")`.
+
+Run today it returns **7 repos**. Three of the steward's working repos fail the predicate:
+
+| repo | first remote | why it fails |
+|---|---|---|
+| `_Dev/CapableMind-AI` | `git@github.com:CapableMind-ai/capableMind_docs.git` | org is `CapableMind-ai`, not `davidglidden` |
+| `_Dev/BetterMemories.io` | `git@github.com:CapableMind-ai/betterMemories_app.git` | same |
+| `_Dev/be` | `git@github.com:boomerbot-xyz/be.git` | org is `boomerbot-xyz` |
+
+The predicate matches an **account name inside the remote path**, which is not the same relation as
+ownership. (`github.com/davidglidden`, the slash form, cannot match an SSH remote at all; every
+current match is carried by the bare `davidglidden/` fragment or by `git.skemantix.com`.)
+
+**Measured contribution of the three excluded repos, same verb set:** **89** further candidates —
+CapableMind-AI 35, BetterMemories.io 42, be 12.
+
+⇒ **The population is 362, not 270/273.** The two largest omissions are the doctrine repo and the
+L1 implementation repo — the two places where a decision that never reached the authorization
+record would matter most, and the two repos the wake digest lists first among active work.
+
+⚠ **The instrument's positive controls do not catch this and could not.** They require `0677e8a`
+(chamber-library) and `95760ff` (dotfiles) to be returned. Both are satisfied by a predicate that
+misses all three repos above. The control encodes the case that was already known — the failure
+mode this record has now logged more than once.
+
+**This defect is reported, not silently repaired.** `prior-art.py` is left unmodified by this
+pre-registration so that the census run it produced remains reproducible; any change to
+`OWNED_HOSTS` is a separate act, filed separately.
+
+---
+
+## 3. The two samples, both fixed before reading
+
+**Sample A — the literal inheritance.** Rows 1–20 of `prior-art.py --census` in the order the
+instrument itself prints them (date-descending), over its own 7-repo population of 273.
+
+**Sample B — the corrected population.** Every 18th row (indices 0, 18, … 342) of the 362-row
+corrected population, sorted date-descending with sha as tiebreak, frozen to
+`population-362.tsv`. Deterministic, and by construction it reaches all ten repos and every month
+from 2025-06 to 2026-08.
+
+**Why both, stated before the answers are known.** Sample A's head is the fortnight in which the
+register was most active, and 18 of its 20 rows are `dotfiles` commits, many of which *are* register
+filings. A sample drawn from the best-documented slice of the corpus is biased **toward** RECORDED
+and **against** the finding — so a zero on Sample A is weak, in a direction that would be easy to
+misreport as refutation. Sample B is not a replacement for Sample A and does not supersede the
+inherited question; it is the second reading that makes Sample A's result interpretable. Both are
+reported in full whichever way each points.
+
+---
+
+## 4. Classification protocol
+
+For each sampled commit, in order:
+
+1. Read the **full** commit message (`git show -s --format=%B`) and its `--stat`. Not the subject
+   line — the subject is what the instrument matched, and matching a verb is not deciding about a
+   mechanism.
+2. **Does it decide about a mechanism?** A mechanism is a nameable technical or procedural
+   *apparatus* — a library, a storage model, a hook, a schema, a tool, a protocol — that the commit
+   adopts, retires, replaces or migrates away from. Ordinary content work that merely uses a census
+   verb is **NOT-A-MECHANISM**. Recorded with the reason.
+3. If YES, write down **the exact term string** a proposer would plausibly use for that mechanism,
+   and run `prior-art.py <term>`. Record `commits` and `register mentions`.
+4. Classify:
+   - **SILENT** — `commits > 0` and `register mentions == 0`. PENDING-164's condition exactly.
+   - **RECORDED** — `register mentions > 0`.
+   - **NOT-A-MECHANISM** — step 2 said no.
+5. For every **RECORDED** row, additionally measure **when the term first entered the register**:
+   `git -C ~/dotfiles log --reverse -S"<term>" --date=short --format=%ad -- PENDING.md
+   PENDING-archive.md REVIEWED.md`, and compare to the commit date. Sub-classify:
+   - **RECORDED-CONTEMPORANEOUS** — first register entry on or before the commit date, or within
+     14 days after it.
+   - **RECORDED-LATE** — first register entry more than 14 days after the commit.
+
+   ⚠ This column exists because the known case demands it: `LFS` today returns 22 register
+   mentions and would score RECORDED, yet every one of them was filed on 2026-08-26, **twelve
+   weeks after** `0677e8a`. A register mention that post-dates the commit by months does not show
+   the decision was routed into the record; it shows it was recovered later, usually by accident.
+   **RECORDED-LATE is not a pass.**
+
+**The answer to the inherited question is the count of SILENT.** The count of
+SILENT + RECORDED-LATE is reported beside it as the wider reading, clearly labelled as the wider
+reading and never substituted for the narrow one.
+
+---
+
+## 5. ⚠ The interpretive step, exposed rather than hidden
+
+Step 3 is a judgement: *which* term names the mechanism. A different term can flip a row's answer.
+This pass therefore records **the exact term string for every row**, so that every verdict is
+re-runnable by a second party with one command and contestable on the term rather than on the
+conclusion. This is the same limit `prior-art.py`'s own docstring declares — *"that is
+interpretation, not extraction"* — and it is not removed by this pass, only made auditable.
+
+---
+
+## 6. Controls — both directions, fixed here
+
+**Must-not-flag (the register-search half is alive).** `logchain` — named verbatim in the
+constitutional constraints of `~/CLAUDE.md`. It **must** return `register mentions > 0`. If it
+returns 0, every SILENT verdict in this pass is void and the pass reports nothing.
+
+**Must-detect (the pipeline can emit SILENT at all).** A term with commits and no register
+mentions must be demonstrated from **outside** both samples. Candidates, in this fixed order —
+`SurrealDB`, then `ChromaDB`, then `Squarespace`. The first that satisfies `commits > 0 and
+register mentions == 0` serves as the control; **all three results are reported regardless**, and
+a non-zero register count is a datum about the register, not a rejected trial.
+
+**Instrument controls.** `prior-art.py --selftest` must PASS in the same session (it did, before
+the census run: `controls: PASS ('LFS' → 21 commits)`).
+
+**If must-detect fails on all three** — no SILENT is demonstrable outside the samples — then a
+sample count of zero cannot be distinguished from a broken pipeline, and the pass must say so
+instead of reporting a refutation.
+
+---
+
+## 7. Contamination guard
+
+The measurement reads `~/PENDING.md`, `~/PENDING-archive.md`, `~/REVIEWED.md`. **Nothing is written
+to any of them until every row is measured.** This is the PENDING-104 ADDENDUM 1 failure in
+advance: on 2026-08-27 the executor's own filing silently changed the file a checker was reading,
+and the disagreement surfaced as an unexplained anomaly in someone else's tool.
+
+SHA-256 at the start of measurement:
+
+```
+071a8caffcbf4ae531dd44b227ea5728920ee926e9d610b18cca8d99be0e773a  PENDING.md
+a3b28bf2231f061557683b370835da1a7b73990a0555f9e82dd5db37f95c87f9  PENDING-archive.md
+c7241083361cf4a2ced68103ab95dcf8fd61870ccaf30d7ab360380d5be3f77e  REVIEWED.md
+```
+
+The result document re-hashes all three at the end of measurement. **If any hash differs, the
+register-mention column is void** and the result says so rather than reporting the numbers.
+
+---
+
+## 8. What would refute PENDING-164, and what would not
+
+- **SILENT = 0 in Sample B** (the cross-repo, cross-year sample), with the must-detect control
+  satisfied, is the strongest refutation this design can produce at n=20, and is to be reported in
+  those words. It would mean: in a systematic sweep of the steward's whole commit history for
+  adoption and retirement language, every mechanism decided about is already findable in the
+  register.
+- **SILENT = 0 in Sample A alone** refutes nothing, for the reason given in §3, and must not be
+  reported as though it did.
+- **SILENT > 0 in either sample** is a lower bound on the backlog, never an estimate of it. n=20 of
+  362 supports no extrapolation and none will be offered.
+
+---
+
+## 9. Scope boundary
+
+This pass classifies **40 rows of 362**. It does not classify the remaining 322, does not repair
+`OWNED_HOSTS`, does not file the mechanisms it finds into the register, and does not re-open
+PENDING-164's ruled options (c) and (d), which are built and need nothing. What it produces is a
+count, a method, a frozen population, and an exposed term list.

claude/governance/PENDING-164-census-classification-RESULT-2026-08-31.md

@@ -0,0 +1,210 @@
+# PENDING-164 AMENDMENT 1 — the classification pass: RESULT
+
+**Date:** 2026-08-31
+**Pre-registration:** `PENDING-164-census-classification-PREREGISTRATION-2026-08-31.md`, commit
+`5ba5842`, committed alone before any sampled commit body was read.
+**Population:** `PENDING-164-population-362-2026-08-31.tsv` (362 rows), frozen in the same commit.
+**Instrument:** `scripts/prior-art.py`, unmodified. `--selftest` PASS in-session
+(`controls: PASS ('LFS' → 21 commits)`).
+
+---
+
+## THE ANSWER
+
+**Sample A — the inherited question, asked exactly as it was left:** of the first 20 census
+candidates, **1** decided about a mechanism the register never mentions.
+
+**Sample B — the systematic sample across the corrected population:** **12** of 20.
+
+Normalised to the rows that actually decide about a mechanism:
+
+| | rows | mechanism decisions | **SILENT** | RECORDED-LATE | RECORDED-CONTEMP. |
+|---|---|---|---|---|---|
+| **A** — newest 20, 7-repo list | 20 | 11 | **1** (9%) | 0 | 10 |
+| **B** — systematic, 362-row list | 20 | 17 | **12** (71%) | 3 | 2 |
+
+**The contrast is the result, and it was predicted in writing before the reading began.** §3 of the
+pre-registration said Sample A's head is the fortnight in which the register was most active, that
+a sample drawn from it is biased toward RECORDED, and that a zero there would refute nothing. That
+is what happened: 18 of Sample A's 20 rows are `dotfiles` commits, **9 of the 20 write to the
+register in the same commit**, and for those the register-mention test is circular — such a commit
+cannot be register-silent by construction.
+
+Per pre-registration §8: **Sample A's low count is not a refutation of PENDING-164 and is not
+reported as one.** Sample B is the reading that carries information, and it points the other way.
+
+**Wider reading, labelled as such and never substituted for the narrow one:** SILENT +
+RECORDED-LATE = **15 of 17** in Sample B. Only two mechanism decisions in the whole systematic
+sample were routed into the register at the time they were taken.
+
+---
+
+## Controls (pre-registered §6), all satisfied
+
+| control | required | result |
+|---|---|---|
+| must-not-flag: `logchain` | register mentions > 0 | **29**, first entry 2026-03-27 ✓ |
+| must-detect #1: `SurrealDB` | commits > 0, register == 0 | 135 commits, **2** register — does not serve |
+| must-detect #2: `ChromaDB` | " | **213 commits, 0 register — serves** ✓ |
+| must-detect #3: `Squarespace` | " | 1 commit, 0 register — also silent |
+| instrument selftest | PASS | PASS |
+
+All three must-detect candidates reported regardless, as pre-registered. The pipeline demonstrably
+emits SILENT outside both samples, so a sample zero would have been interpretable. It was not needed.
+
+**Contamination guard (§7): held.** All three register files hash byte-identical before and after
+measurement:
+`071a8ca…` PENDING.md · `a3b28bf…` PENDING-archive.md · `c724108…` REVIEWED.md.
+Nothing was written to the register until after the last row was measured.
+
+---
+
+## ⚠ The population was never 270
+
+`prior-art.py`'s `owned_repos()` tests remotes against a fragment of the steward's GitHub account
+name. Three working repos fail the predicate and contribute **89** further candidates:
+
+| repo | remote | candidates |
+|---|---|---|
+| `_Dev/BetterMemories.io` | `github.com:CapableMind-ai/betterMemories_app` | 42 |
+| `_Dev/CapableMind-AI` | `github.com:CapableMind-ai/capableMind_docs` | 35 |
+| `_Dev/be` | `github.com:boomerbot-xyz/be` | 12 |
+
+**The population is 362.** The two largest omissions are the doctrine repo and the L1
+implementation repo. **The instrument's two positive controls are both satisfied by a predicate
+that misses all three**, so they could not have caught it — the control encoding the case already
+known, again. Filed as PENDING-171. `prior-art.py` is left unmodified so this census stays
+reproducible.
+
+⚠ **Six of Sample B's twelve SILENT rows come from the three excluded repos.** Had the pass been
+run on the instrument's own population, half the finding would have been invisible.
+
+---
+
+## Method, and where the judgement sits
+
+The interpretive step is naming the mechanism. **Every term is recorded**, so any verdict is
+re-runnable with one command and contestable on the term rather than on the conclusion.
+
+Two deviations from the pre-registration, both stated because both were decided after it was
+written, and **both run against the finding or are neutral**:
+
+1. **Multiple terms per row where a mechanism has an obvious second name.** A row is SILENT only if
+   *all* its terms are silent. This makes SILENT harder, not easier.
+2. **A reading rule for non-zero hits.** A row counts as RECORDED only if at least one register
+   occurrence is *about* the mechanism the commit decided on. Seven terms returned non-zero and
+   every occurrence was read and is quoted below. This rule moved four rows, in both directions:
+   B144 and B180 → RECORDED; B216 and B288 → SILENT. **A reader who rejects the rule and counts any
+   string hit gets 10 rather than 12; a reader who counts only exact mechanism-name hits gets 13.**
+   The band is 10–13; the ruling is 12.
+
+**Every non-zero alternate, read:**
+
+| term | reg | what the occurrences are about | verdict |
+|---|---|---|---|
+| `benchmark` | 4 | *"A2 [PROPOSAL]: if we adopt the benchmark, record it as a floor not a ceiling"* — **the exact decision `ad21bd3` synthesises** | B144 → RECORDED |
+| `lex` | 7 bare (84 gross) | the ARC `lex` **content class** and its v1-legacy deferral; 77 of 84 are substring noise (*Alexander*, *reflex*, *complexity*) | B180 → RECORDED (contested: the class, not the template) |
+| `ornament` | 2 | a chamber-library spec version note; an Acrobat ClearScan producer string | unrelated → B216 SILENT |
+| `drawer` | 7 | studium-engine `retrieve.py` / `drawers_fts` | unrelated → B162 SILENT |
+| `launchd` | 3 | the mumble daemon's cost; a "no trigger of any kind" state-claim | unrelated → B306 SILENT |
+| `rerun` / `HNSW` | 6 / 3 | re-running trials; L1's vector-store similarity probe | unrelated → B072 SILENT |
+| `Kronos` | 1 | a fleet name in an L1 saturation note | unrelated → B252 SILENT |
+| `recall quality` | 2 | recall quality as a *property* of retrieval, not the A/B methodology adopted | B288 SILENT (contested) |
+
+⚠ **An earlier probe of mine reported zero occurrences for five of these terms.** The probe's
+`grep -m8 -n -o ".\{0,70\}TERM.\{0,70\}"` form returned nothing; plain `grep` and the instrument
+agree exactly. **My tool was broken, not the register** — recorded because for twenty minutes it
+looked like two instruments disagreeing, which is the shape this thread has learned to treat as a
+finding, and this time it was not one.
+
+---
+
+## Sample B — every row
+
+| # | commit | repo | date | mechanism decided about | term(s) | c / r | verdict |
+|---|---|---|---|---|---|---|---|
+| B000 | `718ba77` | dotfiles | 08-27 | — session record | — | | not-a-mechanism |
+| B018 | `43f8b6c` | dotfiles | 08-19 | — trial prepared and held | — | | not-a-mechanism |
+| B036 | `4a1a731` | chamber-library | 07-27 | `source_lines` one convention, producer + 11 consumers | `source_lines` | 7/4 | RECORDED-contemp. |
+| B054 | `b043c29` | mempalace | 07-04 | agent identity as `host:agent:project` (RFC 005) | `host:agent:project`, `RFC 005`, `agent identity` | 1/0, 1/0, 5/0 | **SILENT** |
+| B072 | `37194cf` | mempalace | 06-22 | adopt `pytest-rerunfailures` for the Windows HNSW flake | `pytest-rerunfailures` | 1/0 | **SILENT** |
+| B090 | `eb7a557` | animal | 06-09 | migrate to the `sass:color` module (Dart Sass 3.0 removes the globals) | `sass:color`, `Dart Sass`, `sass` | 1/0, 3/0, 14/0 | **SILENT** |
+| B108 | `f11958d` | be | 06-06 | — EU entity domicile (not apparatus) | — | | not-a-mechanism |
+| B126 | `9be2b97` | mempalace | 06-05 | `max_backups` retention + `prune_backups` | `max_backups`, `prune_backups` | 2/0, 1/0 | **SILENT** |
+| B144 | `ad21bd3` | CapableMind-AI | 06-01 | benchmark-governance spec v1.0 (three invariants) | `benchmark-governance` / `benchmark` | 7/0, 100/4 | RECORDED-contemp. |
+| B162 | `06ab20d` | mempalace | 05-29 | `_scoped_source_filter` / `parent_drawer_id` scoping | `parent_drawer_id` | 10/0 | **SILENT** |
+| B180 | `50c402b` | animal | 05-20 | retire `templates/lex.html` into `about-page.html` | `lex.html` / `lex` | 4/0, —/7 | RECORDED-late |
+| B198 | `dd247ea` | animal | 05-09 | AldineXXI §VII.e — luminance retired, `--gray` deprecated for text | `AldineXXI`, `--gray` | 99/25, 10/1 | RECORDED-late (25d) |
+| B216 | `39c480d` | animal | 05-03 | ornaments retired per spec (SCSS cruft removed) | `ornament` | 54/2 | **SILENT** |
+| B234 | `0e3deee` | animal | 04-25 | retire the July-2025 session-memory protocol + `update-docs.py` | `SESSION-MEMORY.md`, `update-docs.py`, `CONTEXT-MAPS` | 7/0, 1/0, 3/0 | **SILENT** |
+| B252 | `d0051dd` | CapableMind-AI | 04-15 | Atlas-owned repo registry retires `KRONOS_TRACKED_REPOS` | `KRONOS_TRACKED_REPOS`, `repo registry` | 2/0, 1/0 | **SILENT** |
+| B270 | `1bb7503` | BetterMemories.io | 04-13 | SurrealDB → SQLite + LanceDB storage migration | `LanceDB` | 46/4 | RECORDED-late (46d) |
+| B288 | `1546271` | CapableMind-AI | 04-06 | recall-quality A/B methodology (+ org migration) | `recall quality` | 8/2 | **SILENT** |
+| B306 | `ef5c6bc` | BetterMemories.io | 03-07 | `setup-launchd.sh` retired for `install.sh` | `setup-launchd.sh`, `launchd` | 3/0, 23/3 | **SILENT** |
+| B324 | `95b44d0` | CapableMind-AI | 02-25 | import-trust / data-portability v1.1, log-chain spec v0.6 | `data-portability`, `ImportProvenance`, `import trust` | 4/0, 1/0, 2/0 | **SILENT** |
+| B342 | `197afff` | animal | 2025-07-04 | CSS custom-property system migration | `CSS custom propert` | 4/0 | **SILENT** |
+
+## Sample A — every row
+
+| # | commit | mechanism | term | c / r | verdict |
+|---|---|---|---|---|---|
+| A01 | `07f0285` | global `safe.directory` for the cold archive | `safe.directory`, `safe directory`, `dubious ownership` | 1/0, 0/0, 0/0 | **SILENT** |
+| A02 | `a0d63f4` | hook-directory allowlist | `allowlist` | 14/4 | RECORDED ⟳ |
+| A03 | `74d3ea9` | LFS | `LFS` | 21/84 | RECORDED ⟳ |
+| A04 | `374285b` | — places REVIEWED-130 | — | | not-a-mechanism ⟳ |
+| A05 | `2408032` | pre-commit stops recommending LFS | `LFS` | 21/84 | RECORDED |
+| A06 | `5737d4d` | — wording harmonisation | — | | not-a-mechanism |
+| A07 | `5694b92` | — executes a filed run-once | — | | not-a-mechanism |
+| A08 | `063eccf` | `STATE-CLAIM` + `resolved:` schema | `STATE-CLAIM` | 10/20 | RECORDED ⟳ |
+| A09 | `f1c91d9` | retire the `thinking-mirror` launchd agent | `thinking-mirror` | 2/1 | RECORDED |
+| A10 | `7226e0d` | `daybook-ensure` link-upward-only | `daybook-ensure` | 2/2 | RECORDED |
+| A11 | `3dbf1d4` | — session record | — | | not-a-mechanism |
+| A12 | `f84dd0e` | — design option | — | | not-a-mechanism ⟳ |
+| A13 | `acfbb9f` | the randomness beacon as seed source | `beacon` | 15/26 | RECORDED ⟳ |
+| A14 | `956b969` | — criterion restated | — | | not-a-mechanism ⟳ |
+| A15 | `783cf79` | — record recovery | — | | not-a-mechanism ⟳ |
+| A16 | `03813cf` | — trial re-aim | — | | not-a-mechanism ⟳ |
+| A17 | `43f8b6c` | — trial held | — | | not-a-mechanism |
+| A18 | `fab8fb0` | vault Frontmatter Specification v1.0.0 migration | `Frontmatter Specification` / `frontmatter` | **4/0** / 125/63 | RECORDED ⚠ |
+| A19 | `ef6fa94` | `superseded_by:` stamping convention | `superseded_by` | 3/2 | RECORDED |
+| A20 | `de1c34b` | retire bare `distinct_spans` for population-carrying names | `distinct_spans` | 4/16 | RECORDED |
+
+⟳ = the commit writes to the register, so it cannot be silent by construction (9 of 20).
+⚠ A18: the generic word `frontmatter` is in the register 63 times, but the **versioned specification
+document itself** — the thing that was bumped to v1.0.0 and then v1.0.1 — returns **4 commits, 0
+register mentions**. The row is RECORDED under the ruling; the mechanism is arguably not.
+
+---
+
+## What this does and does not establish
+
+**Establishes.** In a systematic sweep of the steward's whole commit history for adoption and
+retirement language, **the majority of mechanism decisions are not findable in the authorization
+record by the name they were decided under.** PENDING-164 generalised from one case; that
+generalisation now has 12 further instances drawn without looking for them, in five repos, across
+fourteen months. Three of the five RECORDED rows are RECORDED-**LATE** by 25, 46 and 53 days, which
+on this record's own reading is a decision recovered later, not routed.
+
+**Does not establish.** Nothing about the remaining 322 rows. n=20 of 362 supports **no**
+extrapolation and none is offered — the 71% is a property of this sample, not an estimate of the
+backlog. Nor does it establish that any of the 12 *should* have been in the register: a MemPalace
+CI retry policy is not obviously the steward's governance business, and **that question is not
+answered here.** What is answered is the one that was asked: whether the record contains them. It
+does not.
+
+⚠ **The strongest instances are the ones that are unambiguously in scope.** `B324` amends the
+**log-chain spec** — the logchain is named in `~/CLAUDE.md`'s constitutional constraints, `logchain`
+appears in the register 29 times, and this spec bump appears **zero** times. `B252` retires a
+mechanism another plan document names as a stopgap. `B234` retires a whole session-memory protocol.
+These are not incidental.
+
+**Boundary case, flagged rather than buried:** `B108` (Be's EU entity domicile) is a real decision
+absent from the record and was scored not-a-mechanism because it is not apparatus. Under a wider
+definition it is a thirteenth.
+
+## Scope boundary
+
+322 of 362 rows are unclassified. `OWNED_HOSTS` is not repaired. None of the twelve silent
+mechanisms is filed into the register by this pass — doing so would be option (b), which
+PENDING-164 recommends against and which this result does not disturb: options (c) and (d) remain
+built and sufficient, and this pass is evidence for their necessity, not against it.

claude/governance/PENDING-164-population-362-2026-08-31.tsv

@@ -0,0 +1,362 @@
+0	2026-08-27	dotfiles	718ba77	session 2026-08-26: PENDING-163/164/165 + five amendments; prior-art search built
+1	2026-08-27	dotfiles	07f0285	config: safe.directory for the cold-storage archive on /Volumes/on ice
+2	2026-08-26	dotfiles	a0d63f4	[HARDENING] PENDING-165 AMENDMENT 1: (d) was blind to the damaging occurrence; (c) is not a binary
+3	2026-08-26	dotfiles	74d3ea9	[HARDENING] PENDING-163 AMENDMENT 2: the measurement, and the record that kills (ii)
+4	2026-08-26	dotfiles	374285b	governance: steward places REVIEWED-130; record the snapshot instruction for tomorrow
+5	2026-08-26	dotfiles	2408032	[FIX] pre-commit: the refusal message stops recommending a mechanism this system retired
+6	2026-08-25	dotfiles	5737d4d	[FIX] 'abandonment' -> 'retirement' in the fool's doctrine; §6 was false as of today
+7	2026-08-25	dotfiles	5694b92	[FIX] The bones are derived: beacon 2026-08-25T12:00:00Z, run once (PENDING-149)
+8	2026-08-25	dotfiles	063eccf	[HARDENING] STATE-CLAIM + the resolution state, built together (REVIEWED-127)
+9	2026-08-23	dotfiles	f1c91d9	[FIX] Retire the dead thinking-mirror agent; one writer, and it reports
+10	2026-08-23	dotfiles	7226e0d	Daily notes link up to week and month, both in the steward's own formats
+11	2026-08-23	dotfiles	3dbf1d4	session 2026-08-23: the vault is unfed, not disorganised; capture practice built with a trigger
+12	2026-08-22	dotfiles	f84dd0e	[PROPOSAL] Content question collapses to one decision; option 4; it moves in §4's order (PENDING-152 A5)
+13	2026-08-22	dotfiles	acfbb9f	[PROPOSAL] Fool seed rule filed before the beacon; two unresolvable values caught (PENDING-149)
+14	2026-08-22	dotfiles	956b969	[PROPOSAL] Criterion restated; the chain verified and two links corrected (PENDING-152 A8)
+15	2026-08-22	dotfiles	783cf79	[PROPOSAL] Thistleweld's record survives — and it relocates the guard (PENDING-152 A7)
+16	2026-08-20	dotfiles	03813cf	[PROPOSAL] Re-aim the Fool at the seating question; input-dependence arm pre-registered
+17	2026-08-19	david-root-and-branch-vault-git	fab8fb0	Vault frontmatter pass 2 — bring to spec v1.0.0
+18	2026-08-19	dotfiles	43f8b6c	Trial 09: prepared, and HELD — the answer key is inside the proximity corpus
+19	2026-08-17	dotfiles	ef6fa94	[FIX] Stamp 16 superseded trackers; harvest the rule one of them carried
+20	2026-08-13	studium-engine	de1c34b	corpus: the fr identification pass, instance 8 reclassified, and the count fields renamed
+21	2026-08-13	dotfiles	92d5ad2	session 2026-08-13: REVIEWED-119/120 placed; MCP key descriptions refreshed
+22	2026-08-10	dotfiles	7d7354f	[PROPOSAL] PENDING-132 (fr retraction as its own act), PENDING-133 (split F4), 131 Addendum 3
+23	2026-08-08	chamber-library	9a35720	[PROPOSAL] Couple PENDING-128 to the PENDING-121 redraft — one block, one ruling
+24	2026-08-08	dotfiles	57b9480	[PROPOSAL] PENDING-128 — REVIEWED-53 option (c), on the occasion that arrived
+25	2026-08-07	studium-engine	cf7e117	feat(corpus): manifest the German Handke — V2's blocked gold cell was unblocked a month ago
+26	2026-08-06	dotfiles	6cde9ad	governance: seven rulings that existed only in a narrative are now in the register
+27	2026-08-04	studium-engine	49a8851	[HARDENING] silence discloses what it checked, and what it cannot see (PENDING-96)
+28	2026-08-02	animal-davidglidden-eu	d966535	docs: CLAUDE.md no longer lists a js/ directory that does not exist
+29	2026-08-02	dotfiles	62b92bd	[FIX] Land the skill-harvest FIX lane and apply its first batch (REVIEWED-85)
+30	2026-08-01	chamber-library	f767cd9	[FIX] corpus-work-map: Warde Crystal Goblet stalled short of graduation (R3-W)
+31	2026-07-27	chamber-library	e596983	[PROPOSAL] Spec v2.8.0 — voice-purity as the engine-consumable bar (REVIEWED-73)
+32	2026-07-27	chamber-library	b82fc48	[FIX] source_lines: newline-based, one implementation — the sweep's first yield
+33	2026-07-27	studium-engine	966a781	corpus: migrate the 19 sidecars to the voice-purity bar (REVIEWED-73 Q4)
+34	2026-07-27	chamber-library	85c50a7	[FIX] Wire voice_purity_gate into graduation (REVIEWED-73, remaining leg)
+35	2026-07-27	dotfiles	84a23d8	skills: build both authorized harvest proposals (2026-07-27)
+36	2026-07-27	chamber-library	4a1a731	[FIX] source_lines: one convention — producer + all 11 consumers, one change-set
+37	2026-07-24	chamber-library	5519cb8	[REVIEWED-72/73] Born-digital source-fidelity + voice-purity sidecar: packages + rulings
+38	2026-07-21	studium-engine	edbaf60	[FIX] re-anchor: arendt-eichmann re-bound to the one-door graduation (chamber 780106b) — substrate-caveat RETIRED
+39	2026-07-21	chamber-library	780106b	[FIX] one-door: Eichmann GRADUATED through the born-digital lane — the 48-file class's first closure (REVIEWED-66/67/68 lineage)
+40	2026-07-19	studium-engine	c024f6a	fix(corpus): after-the-reply re-anchor — five sources re-bound, spans re-verified, register retired
+41	2026-07-19	chamber-library	0e8ee89	[FIX] graduation-spec: omnibus promotion unit defined in declared data — unit=work, event=container (REVIEWED-66)
+42	2026-07-13	chamber-library	836b665	[FIX] Read + resolve the 2 REORDER? books — both wrong-key, REORDER? → 0
+43	2026-07-12	chamber-library	abada64	docs(open-work): reconversion precedes frontmatter — Loeb Region 4 subsumes ~952 of the debt
+44	2026-07-12	studium-engine	7e8e322	docs: add "Doc-currency on wrap" protocol (+ chamber sidecar-LOCKED note)
+45	2026-07-11	chamber-library	b65816a	[REVIEWED-55] Analyzer precision fix: expose recognizer paired-ref positions → exact coverage
+46	2026-07-07	dotfiles	aee9cd5	session 2026-07-07: MemPalace wind-down decided (evidenced audit) + KG exported to files
+47	2026-07-06	mempalace	c6f1483	fix(ci): green up the replicated-palace PR
+48	2026-07-05	mempalace	e687716	fix(hub): self-heal isolated FTS5 corruption on startup instead of gating writes
+49	2026-07-05	chamber-library	b9a5d05	curation: source-match exclusion path (Region 1.1–1.2) — jurist-ratified, 4 FPs excluded
+50	2026-07-05	mempalace	7c111cb	feat(write-flip): mint content-pure v4 ids on every write path (ID_RECIPE=v4)
+51	2026-07-05	mempalace	6978645	feat(write-flip): un-shadow the fold — local writes carry op_hlc, cross-replica revises resolve by LWW
+52	2026-07-04	mempalace	dce815b	fix(migrate_v4): resilient by-id vector reads — survive localized index damage
+53	2026-07-04	mempalace	c990027	perf(migrate_v4): stream the v4 applier — bounded memory, batched vector writes
+54	2026-07-04	mempalace	b043c29	docs(rfc): RFC 005 — agent identity & routing (host:agent:project)
+55	2026-07-04	chamber-library	ac8a691	docs: rewrite the stale README to the current v2.0 substrate
+56	2026-07-04	mempalace	aa601d4	feat(migrate_v4): carry the replica's sidecar identity — the migrated target is the SAME replica
+57	2026-07-03	chamber-library	f9cbb8e	curation: Wave 0 — fix the instruments before any cleaning wave (tool-fleet audit)
+58	2026-07-03	mempalace	b701ec0	feat(opfold): the fold consumer — remote memory ops converge into the local store (RFC 004 2a)
+59	2026-07-03	mempalace	7f62ae5	feat(2a): v4 content-pure id recipe + read-only migration planner (RFC 004 id purity)
+60	2026-07-03	mempalace	797ba69	feat(2a): v4 migration applier — content-pure store rewrite, vectors copied, merges handled
+61	2026-07-03	mempalace	5c5293a	fix(oplog): migration-order bug bricked every pre-fold op-log and leaked fds until the hub wedged
+62	2026-07-03	mempalace	3e4f018	feat(2a): mempalace migrate-ids CLI — plan/apply the v4 id migration
+63	2026-07-03	mempalace	370c43f	docs(migrate-ids): full validated v4 runbook in CLI output + reference
+64	2026-07-02	mempalace	ab6f362	docs(rfc): RFC 004 — the replicated palace (skeleton + storage sections)
+65	2026-07-02	mempalace	45b0aa3	feat(transport): the RFC 004 transport seam — MeshGuard integration step 1
+66	2026-07-02	mempalace	34a264e	docs(rfc): record step-2 rollout decisions (Igor, 2026-07-02)
+67	2026-07-02	mempalace	340b529	feat(logsync): RFC 004 step 0 — logstream multi-master replication
+68	2026-06-28	studium-engine	e9fe4a6	corpus: Position I prepared — English Musil replaces French; Levi re-anchored
+69	2026-06-28	chamber-library	e3db4ae	runbook: bring current — EPUB structure-from-NCX path, olmOCR retired, graduation policy
+70	2026-06-28	mempalace	cff43ad	feat(convo): preserve authored timestamp from transcripts (#1890)
+71	2026-06-28	chamber-library	79e14bf	runbook: CORRECT olmOCR — single-column tool, not retired (steward)
+72	2026-06-22	mempalace	37194cf	ci(test-windows): retry the transient ChromaDB HNSW compaction flake
+73	2026-06-21	mempalace	fa27e41	fix(pgvector): push get(limit, offset) pagination into SQL (#1830)
+74	2026-06-21	mempalace	386f3c9	fix(backends): push sqlite_exact get(limit, offset) pagination into SQL
+75	2026-06-17	animal-davidglidden-eu	d736df1	feat(arc): the cul-de-lampe — designed §IV Close ornament + reconciliation
+76	2026-06-17	animal-davidglidden-eu	68001a4	feat(arc): cul-de-lampe rollout — close on essays + Vespers/Mushi-Ken reworked & versioned + §IV type-applicability
+77	2026-06-15	mempalace	9f434e0	test(migrate): cover swap-failure rollback
+78	2026-06-15	chamber-library	5aa0a08	chamber: clean + graduate 14 low-cruft sources; retire 2 metadata files
+79	2026-06-15	chamber-library	0692535	chamber: graduate-and-retire — Loeb canon + prose -> canonical, retire sprawl
+80	2026-06-14	mempalace	d860a00	fix: close blob seq sqlite migration connection
+81	2026-06-14	mempalace	58c45a9	Merge pull request #1804 from MemPalace/codex/close-blob-seq-sqlite
+82	2026-06-13	CapableMind-AI	b45af83	docs(chamber): retire reading-indices in place — canonical home now chamber-library
+83	2026-06-13	chamber-library	400c054	chamber: pre-commit guard exempts corpus text from the 5MB limit
+84	2026-06-11	mempalace	bf71ae7	fix(hallways): scope hallway-file path to MempalaceConfig.palace_path (#1778)
+85	2026-06-11	mempalace	4fd1231	fixup(hallways): drop _HALLWAY_FILE back-compat shim, migrate existing tests to resolver
+86	2026-06-10	animal-davidglidden-eu	e99028e	docs(arc): spec-internal consistency reconciliation (post-Stage-G audit)
+87	2026-06-10	animal-davidglidden-eu	b673623	docs(arc): correct drop-cap known-state in CLAUDE.md (retired-by-absence)
+88	2026-06-10	animal-davidglidden-eu	a5cc945	docs(arc): re-render Codex PDF — margin-note provenance + reconciled spec
+89	2026-06-10	animal-davidglidden-eu	0e0c2f4	docs(arc): truth-up stale §I.d + §III.b conformance flags to live state
+90	2026-06-09	animal-davidglidden-eu	eb7a557	refactor(arc): W3R Stage 3 Tier 4 — migrate mix()/darken() to the sass:color module
+91	2026-06-09	animal-davidglidden-eu	4ea261a	refactor(arc): W5.1/G2 — single-source title display from content-types.yml
+92	2026-06-09	animal-davidglidden-eu	23db039	feat(arc): W5.3/G4 — clause-1 enforcement gate (corpus class census)
+93	2026-06-08	animal-davidglidden-eu	dd6c9d1	refactor(arc): W3R Stage 2b — remove the 34 compass-point !importants
+94	2026-06-08	animal-davidglidden-eu	772e0d5	refactor(arc): W3R — close the glimpse !importants (overrides promotion)
+95	2026-06-08	animal-davidglidden-eu	6579f93	refactor(arc): W3R — retire the mobile-blanket animation !important
+96	2026-06-08	animal-davidglidden-eu	5b93f0a	refactor(arc): W3R Stage 2a — declare cascade layers (@layer base, overrides)
+97	2026-06-08	animal-davidglidden-eu	3eb2611	refactor(arc): W3R Stage 3 — dissolve _utilities (5/5): residue distributed, junk drawer retired
+98	2026-06-08	animal-davidglidden-eu	0fd7acd	refactor(arc): W3R Stage 3 — retire the vestigial .observation .ornament
+99	2026-06-07	animal-davidglidden-eu	def913e	fix(arc): W3.3 — F8 ligature exclusion on letterspaced settings + F11 class values
+100	2026-06-07	dotfiles	960b256	Basic Memory retired + MemPalace 3.4.0 upgrade plan saved + Brewfile line dropped
+101	2026-06-07	animal-davidglidden-eu	8f6f4f9	docs(arc): W2 reconciliation — apparatus status blocks trued; §VII.f honest; §SEO figures current
+102	2026-06-07	animal-davidglidden-eu	7d9bad3	docs(arc): W2 reconciliation — AldineXXI brought current to the work it governs
+103	2026-06-07	animal-davidglidden-eu	69d1c4a	fix(arc): W3.7 — the skip-link goes silent (steward-ruled form)
+104	2026-06-07	animal-davidglidden-eu	4de9833	docs(arc): roadmap — eleven Wave-1 rulings recorded + cracks-check restores the re-partition gate
+105	2026-06-07	animal-davidglidden-eu	4b0970b	docs(arc): W2 — vignette Part II revised to the build-time renderer (PENDING-31)
+106	2026-06-07	dotfiles	19a9f12	session 2026-06-07 evening: be a11y-gate + memory-verdicts night filed (BM retired, CLAUDE.md witness-not-notary amendment carried, Fowler pre-3R directive, MemPalace 3.4.0 plan, wake-canary proposal)
+107	2026-06-06	be	ff497d5	docs: growth discipline proposal (customer cap) + TODO sync
+108	2026-06-06	be	f11958d	EU home = Portugal (Seb's family: 13y marriage, 3 kids, all EU citizens)
+109	2026-06-06	mempalace	ee32e56	feat(migrate): mempalace migrate-wings — normalize legacy wing names
+110	2026-06-06	mempalace	e66cfff	chore(release): 3.4.0
+111	2026-06-06	be	e6504f0	LAUNCH: make graduating Pat & Sheila into be-seen-art tenant repos explicit
+112	2026-06-06	mempalace	e46374d	feat(migrate): mempalace migrate-wings — normalize legacy wing names
+113	2026-06-06	animal-davidglidden-eu	da375a6	fix(arc): three-faces paragraph corrected + imprint register named (steward rulings 2026-06-06)
+114	2026-06-06	be	c9a9995	idea-register: "build hot, host cold" — court arrived Squarespace/Wix users
+115	2026-06-06	be	c8e83fa	Add implementation requirements + MVP plan (concierge-first, instrument toward autonomy)
+116	2026-06-06	be	abb899f	0019/runbook: adopt CF Self-Serve Agency Program as the fleet structure (early)
+117	2026-06-06	be	ab5ef5c	Spec corpus Tier C: the agentic system (0015-0018)
+118	2026-06-06	be	933d692	CONCEPT: Pat & Sheila = Founding Artist-Residents, lifetime full-feature licenses
+119	2026-06-06	mempalace	8ec438e	docs(recovery): add wing-name migration guide for migrate-wings
+120	2026-06-06	be	7110835	Spec 0002: origin-typed migration adapters (WP/page-builder/Wix/SQSP/custom/FB)
+121	2026-06-06	mempalace	708ef4a	Merge pull request #1702 from MemPalace/feat/migrate-wing-normalize
+122	2026-06-06	be	1c7f3f5	idea-register: capture the near-zero migration UX (send URL → flip DNS → done)
+123	2026-06-05	animal-davidglidden-eu	e2866da	feat(arc): heteronym decompose — first translated renderings (PENDING-25 live)
+124	2026-06-05	be	d74a9f9	KEY: first real WTP signal + repositioning (AI-native successor to dying web shops)
+125	2026-06-05	animal-davidglidden-eu	c37a3bd	refactor(arc): cascade re-partition Stage 1 — @use migration, byte-identical
+126	2026-06-05	mempalace	9be2b97	fix(backups): add max_backups retention to bound backup disk usage
+127	2026-06-05	be	5f60610	Verify adjacent-market figures (manual) + add be-hosted; re-rank
+128	2026-06-05	chamber-library	0677e8a	chore: retire LFS — corpus is plain text in git proper
+129	2026-06-04	animal-davidglidden-eu	ec4767a	refactor(arc): Stage N tail — retire the dead JS pipeline
+130	2026-06-04	animal-davidglidden-eu	864a5b4	refactor(arc): Stage N — dead-selector prune (57 classes, 4 orphaned templates, _chamber.scss)
+131	2026-06-04	animal-davidglidden-eu	7d59b4b	refactor(arc): retire .whisper — apparatus-meta + mark-class unification (REVIEWED-27)
+132	2026-06-03	animal-davidglidden-eu	e0f35db	refactor(arc): Stage N — prune dead glyph residue, rename needsGlyph
+133	2026-06-03	animal-davidglidden-eu	bc4cc5b	docs(arc): Stage N conformance + prune deep-read findings
+134	2026-06-03	animal-davidglidden-eu	7086fae	fix(arc): Stage N — frontispiece threshold in one ink + canonical small caps
+135	2026-06-03	animal-davidglidden-eu	6851367	chore(arc): retire the dead triptych/glyph JS system
+136	2026-06-03	animal-davidglidden-eu	4303df0	feat(arc): Stage F Phase 2 — listing generator from data/listings.yml
+137	2026-06-03	animal-davidglidden-eu	20019ba	fix(arc): Stage N — §VII.e conformance batch (recede by form, not luminance)
+138	2026-06-02	animal-davidglidden-eu	8549ead	fix(arc): retire unused LaTeX math + the dollar-escaping hack (pandoc audit F1)
+139	2026-06-02	animal-davidglidden-eu	5318ae1	feat(arc): verse typography — §I.h.b Verse Quotation + §I.h.c Primary Verse
+140	2026-06-02	animal-davidglidden-eu	4ef26b0	feat(arc): site mark — solid faceted icosahedron, inline + mode-aware
+141	2026-06-01	animal-davidglidden-eu	d7e221b	docs(arc): Stage M(a) inventory + schedule Stage N (spec-conformance deep read)
+142	2026-06-01	animal-davidglidden-eu	c6549de	fix(arc): purge the .post-content wrapper — unify on the spec's .bears-apparatus hook
+143	2026-06-01	BetterMemories.io	aef30ad	merge: remove SurrealDB-era migration dead code (5 files, 0 callers)
+144	2026-06-01	CapableMind-AI	ad21bd3	synthesis(specs): promote A2 benchmark governance to operations spec v1.0
+145	2026-06-01	BetterMemories.io	841a5ac	feat(epistemic-integrity): A1' — consumer surface for source_classification_confidence + ceiling counter
+146	2026-06-01	animal-davidglidden-eu	71e87ea	fix(arc): retire .callout — spec-flagged residual, §I.h-violating bar/box/italic
+147	2026-06-01	BetterMemories.io	5e6e0c4	feat(storage): A1''.1 — qualitative-axis schema foundation across vector/entity/temporal
+148	2026-06-01	CapableMind-AI	54eff50	docs(l1): post-discussion package — A1'/A1'' revised + new epistemic-gates amendment + audit editorial note
+149	2026-06-01	animal-davidglidden-eu	2b790dc	feat(arc): adopt system mode via color-scheme + light-dark() (Stage M(a) core)
+150	2026-06-01	BetterMemories.io	25ed233	merge: B1.1 causal-edge breadth cap + C2 similarity-probe wiring with carve-outs
+151	2026-06-01	BetterMemories.io	19bcd2b	chore(storage): remove SurrealDB-era migration dead code
+152	2026-05-31	animal-davidglidden-eu	02393bc	fix(arc): compass — remove dead path-* @extends + add a11y labels (Stage-F §3F/§3G)
+153	2026-05-30	animal-davidglidden-eu	dfff604	refactor(arc): Phase 1 DEDUPE (part) — blockquote, enfilade, small-caps single-sourced
+154	2026-05-30	mempalace	df295bd	fix(antigravity): atomic counter write, background --version probe, state-file GC
+155	2026-05-30	animal-davidglidden-eu	9156522	refactor(arc): MIGRATE — $sidenote-size → $marginalia-register-size in _variables (§3G)
+156	2026-05-30	animal-davidglidden-eu	90802a6	docs(arc): Stage-F-closing plan — two tracks (SCSS + Hakyll), vignette -> F+1
+157	2026-05-30	animal-davidglidden-eu	5f4c27e	refactor(arc): Phase 0 RETIRE — remove dead SCSS tokens + mixins (zero render change)
+158	2026-05-30	animal-davidglidden-eu	4e4f700	docs(arc): mode-mechanism modernization design note + shelve dark→var MIGRATE
+159	2026-05-30	mempalace	206cfbb	fix(ids): delimit hash inputs to prevent drawer_id collisions (#80)
+160	2026-05-29	mempalace	4233153	test(searcher): carry remaining 3 #1582 regression tests + correct $and-limit claim
+161	2026-05-29	animal-davidglidden-eu	164d8c3	fix(arc): gloss listing-page glyph ✎ → ¶ (code-represents-spec clause 2)
+162	2026-05-29	mempalace	06ab20d	fix(searcher): scope drawer-grep enrichment by parent_drawer_id (#1580, second site)
+163	2026-05-28	CapableMind-AI	7741673	docs(l1): A1'' persistence strategy + B1 sketch + cover note for Seb
+164	2026-05-28	CapableMind-AI	033e255	docs(l1): pre-build audit + A1 split (consumer-surface + qualitative-axis)
+165	2026-05-27	CapableMind-AI	d2a0052	docs(l1): Hindsight deep-read + L1 epistemic-vs-mechanical analysis (PENDING-24)
+166	2026-05-27	BetterMemories.io	99a67b5	infra(capablehands): host user provisioning + bmf-runtime migration scripts
+167	2026-05-25	mempalace	d88597c	fix(backends): repair missing _type in collection config (#1611)
+168	2026-05-25	animal-davidglidden-eu	70232ca	feat(arc): Stage F — dwellings cluster, Compass to 13 sigils, single-source partial
+169	2026-05-24	animal-davidglidden-eu	68b7a9a	docs(arc): Stage F decisions (γ) — resolve scout §5 + Annals nav removal
+170	2026-05-22	animal-davidglidden-eu	e7cd960	spec(arc): reconcile status stamps — §3/§4/§5/§6 AUTHORED + frontmatter OPERATIVE
+171	2026-05-22	animal-davidglidden-eu	3dbe94e	docs(arc): patch Stage F scout §4.1 — honest scope on footer-compass.html
+172	2026-05-22	animal-davidglidden-eu	3834713	docs(arc): Stage F touchpoints scout — pre-γ enumeration
+173	2026-05-22	mempalace	05da803	feat(closets): Tier 6a — date+line locators with content-date hierarchy
+174	2026-05-21	mempalace	b6dc122	fix(extract): polish PR — address bot review feedback on PR #1555
+175	2026-05-21	mempalace	a2ba1cc	feat(dynamics): Hebbian potentiation + Ebbinghaus decay for halls + tunnels
+176	2026-05-20	animal-davidglidden-eu	e76f0ad	content+scss(arc): 404 page per 2026-05-20 spec — apparatus addition
+177	2026-05-20	animal-davidglidden-eu	cf1bc99	spec(arc): site edition convention + colophon Build register wiring (ADR-007)
+178	2026-05-20	mempalace	c18879b	feat(tunnels): cross-wing entity tunnels derived from hallways
+179	2026-05-20	animal-davidglidden-eu	982fe7f	spec(arc): Stage E continuation — Phase 1D register marks for Vignette + Colophon + §XII.b Posture + Plex Mono mobile fix
+180	2026-05-20	animal-davidglidden-eu	50c402b	arch(arc): consolidate lex.html into about-page.html (Stage E Gate 1 path b)
+181	2026-05-20	animal-davidglidden-eu	4adf04e	housekeeping(arc): retire orphan navigation.yaml
+182	2026-05-20	animal-davidglidden-eu	355757d	housekeeping(arc): retire tags / glyph_id / glyph_confidence dead-data fields
+183	2026-05-20	animal-davidglidden-eu	15f8134	spec(arc): Stage E continuation — content-typology §4 Overlap and Resolution authored
+184	2026-05-19	animal-davidglidden-eu	e3d805e	pages(arc): retire /tools, rework /now to quiet prose register
+185	2026-05-19	animal-davidglidden-eu	c480b09	spec(arc): Stage E peer-spec propagation per ADR-006 v2
+186	2026-05-19	animal-davidglidden-eu	89bae96	§XII.e(arc): capsule first instance — /aldine-xxi/ rewrite + capsule mechanic
+187	2026-05-19	animal-davidglidden-eu	593f2dc	routes(arc): /glosses/ + /readings/ — typology fully routed; Brown post lands as first Readings instance
+188	2026-05-19	animal-davidglidden-eu	420a397	tuning(arc): post-publish refinements against the Brown /readings/ first render
+189	2026-05-19	animal-davidglidden-eu	2a2c195	spec(arc): Stage E hardening — Live-State Discipline + (c) Compass framing
+190	2026-05-18	mempalace	6658a4d	fix(audit): chunk and batch content before embedding upsert (#1539)
+191	2026-05-18	mempalace	34d8dde	Merge pull request #1216 from arnoldwender/fix/migrate-resource-cleanup
+192	2026-05-16	animal-davidglidden-eu	8cdc2c6	docs: retire CURRENT-STATE.md; track state survey with post-type + glimpse audit additions
+193	2026-05-15	animal-davidglidden-eu	e3478e0	fonts(arc): update arc-typography.sty \scfont to use freshly-built EBGaramondSC12-Regular
+194	2026-05-14	mempalace	cef1c62	feat(embedding): EF-mismatch error helper, offline tests, migration docs
+195	2026-05-11	mempalace	b7c40ca	docs(benchmarks): refresh cloud lineup + document structured-outputs gotcha
+196	2026-05-11	mempalace	3171a1b	fix(graph): resolve tunnel file from palace_path config (#1467)
+197	2026-05-09	animal-davidglidden-eu	e000f13	refactor(arc): SCSS migration — percentage-root + --gray retirement per §VII.e
+198	2026-05-09	animal-davidglidden-eu	dd247ea	spec(arc): AldineXXI completion arc + spec-driven content fulfilment
+199	2026-05-09	mempalace	11d0a64	fix(tests): use spawn instead of fork for lock-test subprocesses
+200	2026-05-07	mempalace	e272ed3	Merge pull request #1359 from fatkobra/fix/1099-migrate-write-roundtrip
+201	2026-05-07	animal-davidglidden-eu	cc6a551	content(arc): Phase D — 143 glimpses processed from staged inbox
+202	2026-05-07	animal-davidglidden-eu	249475b	content(arc): location frontmatter audit — universal dateline coverage
+203	2026-05-06	animal-davidglidden-eu	f4716e6	refactor(arc): §XII SCSS — Pass 1 elegance audit (376→252 lines)
+204	2026-05-06	animal-davidglidden-eu	f1a229d	spec(arc): consolidate §XII Sidenotes architecture
+205	2026-05-06	animal-davidglidden-eu	47663a1	fix(arc): unify §XII sidenote architecture; chamber → marker-anchored
+206	2026-05-05	animal-davidglidden-eu	f0f4b09	fix(arc): chamber page polish — publication name + 3 UI fixes
+207	2026-05-05	mempalace	bb40a52	fix(migrate): verify write roundtrip before bailout
+208	2026-05-03	animal-davidglidden-eu	f82233c	fix(arc): ornament default to three-dot interim (matches hr)
+209	2026-05-03	animal-davidglidden-eu	de2610f	fix(arc): SCSS audit — _layout.scss surfaces resolved (universal selector + dead .not-found)
+210	2026-05-03	animal-davidglidden-eu	cb92220	fix(arc): hr — three-centered-dots interim per spec §IV (Tschichold-Penguin tradition)
+211	2026-05-03	animal-davidglidden-eu	aa7293b	fix(arc): bold→italic conversion in posts/ — banish-bold posture applied
+212	2026-05-03	animal-davidglidden-eu	9b16007	refactor(arc): SCSS audit — _mobile-responsive prunes dead-class rules
+213	2026-05-03	animal-davidglidden-eu	9a7a081	fix(arc): SCSS audit — _layout.scss cleanup (airing out the house)
+214	2026-05-03	animal-davidglidden-eu	95a48df	fix(arc): SCSS audit — _utilities.scss stage 1 (dead-code purge)
+215	2026-05-03	animal-davidglidden-eu	7a78bc2	fix(arc): theme-toggle bordered-circle + uniform ornament three-dots
+216	2026-05-03	animal-davidglidden-eu	39c480d	fix(arc): _utilities.scss — remove commented-out deprecated ornament declarations
+217	2026-05-03	animal-davidglidden-eu	28c1d60	refactor(arc): SCSS audit — _dark.scss prunes ~50% dead-class rules
+218	2026-05-03	animal-davidglidden-eu	289713b	fix(arc): hr — quiet rule per §IV (retire ❦ apparatus violation) + Close ornament open question
+219	2026-05-03	animal-davidglidden-eu	25461cb	fix(arc): SCSS audit — _post.scss cleanup (banish-bold + dead duplicates)
+220	2026-05-02	animal-davidglidden-eu	748b380	feat(arc): typographic refinement — sidenote/register-marker resize + §VII.c Links spec + native text-decoration migration
+221	2026-05-02	animal-davidglidden-eu	0abfe88	fix(arc): converge link styles to §VII.c (one rule, two exceptions) + narrow lex sidenote density-exception to .voice-block
+222	2026-05-01	animal-davidglidden-eu	c20375d	chore(arc): retire Seb-server nginx deployment topology + add wrangler maintenance targets
+223	2026-05-01	animal-davidglidden-eu	71260c1	feat(arc): §VII.b Sources spec (PROVISIONAL) + first instance on After the Reply
+224	2026-04-28	mempalace	2e441d1	fix(entity_registry): fsync parent dir after rename for ext4 durability
+225	2026-04-27	animal-davidglidden-eu	f7693bd	feat(arc): about-enfilade emergent + Branch A production stack + Hearth namespace
+226	2026-04-26	mempalace	cb13036	fix(migrate): close SQLite connection and clean temp palace on exception
+227	2026-04-26	mempalace	8e4319c	fix(mcp): use embedding_function from collection metadata in _get_collection
+228	2026-04-26	animal-davidglidden-eu	5c059d8	chore(arc): Phase 0 cleanup — Batch A deletes, Batches B+C archive, investigations 1-6
+229	2026-04-26	mempalace	2477442	fix(blob-seq-marker): tests + style nit per @igorls #1177 review
+230	2026-04-26	mempalace	025dd03	Merge pull request #1177 from jphein/fix/blob-seq-marker-guard
+231	2026-04-25	mempalace	b99e545	feat(init): context-aware corpus detection
+232	2026-04-25	mempalace	88a53b2	fix: prevent HNSW index bloat via batch_size + sync_threshold metadata
+233	2026-04-25	mempalace	5e57404	Merge pull request #935 from shaun0927/fix/repair-crash-safety
+234	2026-04-25	animal-davidglidden-eu	0e3deee	chore(claude-md): rewrite; drop July 2025 session-memory protocol and superseded plans
+235	2026-04-24	mempalace	bc24aa1	fix: skip _fix_blob_seq_ids sqlite open on already-migrated palaces (#1090)
+236	2026-04-24	mempalace	9e73009	test(mcp): migrate _kg monkeypatches to _get_kg (#1136)
+237	2026-04-24	mempalace	659cb81	fix(migrate): harden swap rollback against partial cross-device copy
+238	2026-04-23	mempalace	f5c8b09	fix: narrow _fix_blob_seq_ids shim + add repair --mode max-seq-id
+239	2026-04-23	animal-davidglidden-eu	9c58494	docs(typography): deepen ✦ encounter mark definition for mediated forms
+240	2026-04-23	animal-davidglidden-eu	3f21fda	docs(style-guide): retire old style-guide.md; add AldineXXI skeleton
+241	2026-04-20	CapableMind-AI	8584c64	BO spec v0.2: review-pass tightening (7 fixes)
+242	2026-04-18	mempalace	fed6993	Add tandem sweeper: message-level safety net for dropped transcripts
+243	2026-04-18	animal-davidglidden-eu	bb9e7eb	Hakyll versioning infrastructure per essay-versioning-specification §7
+244	2026-04-18	mempalace	a17a8b7	refactor(backends): typed QueryResult/GetResult, PalaceRef, BaseBackend registry (RFC 001 §10)
+245	2026-04-18	mempalace	89904ed	fix(sources): address Copilot review on #1014
+246	2026-04-18	mempalace	552e992	refactor(sources): RFC 002 §9 scaffolding — BaseSourceAdapter, registry, PalaceContext
+247	2026-04-17	BetterMemories.io	afdbead	chore: SurrealDB teardown — remove 14k lines of dead code (#149)
+248	2026-04-17	mempalace	8df944a	fix: best-effort HNSW thread-pin retrofit + drop dead attempt-cap constant
+249	2026-04-17	dotfiles	5f3ea1a	Brewfile: capture current dev environment + mas app additions
+250	2026-04-16	mempalace	fb1cf53	fix: harden repair backup scope and migrate swap rollback
+251	2026-04-16	mempalace	5dfe853	fix: guard against data loss in repair, migrate, and CLI rebuild
+252	2026-04-15	CapableMind-AI	d0051dd	docs(plans): plan-004 for Atlas-owned repo registry; annotate plan-002 stopgap
+253	2026-04-15	CapableMind-AI	c1f949d	docs(plans): plan-007 per-staff BMF keys + plan-008 CM agent subdomains
+254	2026-04-15	BetterMemories.io	82a0ded	fix(vector): cosine distance→similarity formula (1 - distance, not 1 - distance/2)
+255	2026-04-15	BetterMemories.io	19ba661	fix: four bottlenecks identified by 2026-04-15 audit
+256	2026-04-14	CapableMind-AI	fc56b29	docs(l1): migration completion pass findings — end-of-pass status
+257	2026-04-14	BetterMemories.io	b0e20fc	fix: unblock recall after sqlite+lance migration — multi-gate silent drop
+258	2026-04-14	BetterMemories.io	5f1b3e9	feat: all 13 modules fully wired to SQLite/LanceDB — zero module errors
+259	2026-04-14	BetterMemories.io	442aa56	feat: wire test harness to SQLite backend, bridge all module index.ts
+260	2026-04-14	BetterMemories.io	3688ace	pre-merge sweep: fail-loud telemetry + zombie code removal + honest epistemic fields
+261	2026-04-14	mempalace	267a644	refactor: route all chromadb access through ChromaBackend
+262	2026-04-14	BetterMemories.io	2469c91	feat: port factory layer to SQLite + remove non-fatal swallow (C2 + B1)
+263	2026-04-14	BetterMemories.io	1c58c08	test: port test harness to SQLite (A1)
+264	2026-04-13	BetterMemories.io	ce911a8	feat: vector module storage — LanceDB + SQLite implementation
+265	2026-04-13	BetterMemories.io	9493d48	feat: anomaly module — SQLite bridge wiring (template for all modules)
+266	2026-04-13	BetterMemories.io	6379058	feat: add SQLite storage implementations for anomaly, safety, and blob modules
+267	2026-04-13	BetterMemories.io	4bd524b	feat: add SQLite implementations for temporal, structured, budget, preference, knowledge modules
+268	2026-04-13	mempalace	48eb627	fix(hooks): MEMPAL_PYTHON override for .sh hooks' internal python3 calls
+269	2026-04-13	BetterMemories.io	38d2fda	feat: SQLite + LanceDB core storage layer
+270	2026-04-13	BetterMemories.io	1bb7503	feat: add SQLite storage for security, training, and coordination modules
+271	2026-04-13	mempalace	0b623b0	docs(rfc-001): flag mcp_server cache/reconnect for §10 cleanup
+272	2026-04-12	mempalace	e6d232f	docs: add CHANGELOG.md covering v3.0.0 through v3.2.0-dev (#752)
+273	2026-04-12	mempalace	c683706	fix: address Copilot review comments on PR #739
+274	2026-04-12	mempalace	922aa99	docs(rfc-001): close four spec defects surfaced in review
+275	2026-04-12	mempalace	6a4551e	docs: draft RFC 001 — storage backend plugin specification (#737)
+276	2026-04-12	mempalace	679a95c	feat: init-time embedding model binding + multilingual support
+277	2026-04-12	mempalace	51d053d	docs(rfc-001): strengthen embeddings contract and migration safety
+278	2026-04-11	mempalace	abc99f4	fix: auto-repair BLOB seq_ids from chromadb 0.6→1.5 migration (#664)
+279	2026-04-11	CapableMind-AI	3bbec2c	docs(ADR-021): CapableMind directory structure — memories, agents, bridges, circles, system
+280	2026-04-11	BetterMemories.io	20db305	feat: ADR-021 data directory resolution — memories/<instance>/data
+281	2026-04-10	mempalace	60bea83	feat: mempalace migrate — recover palaces from different ChromaDB versions
+282	2026-04-10	mempalace	559e43b	Merge pull request #502 from milla-jovovich/fix/chromadb-version-migration
+283	2026-04-10	mempalace	2d7d7e0	feat: mempalace migrate — recover palaces from different ChromaDB versions
+284	2026-04-07	BetterMemories.io	c6689eb	fix: Phase 2 replay loop, pairing persistence, recall ranking, doorbell container (#120, #80, #89, #107)
+285	2026-04-07	mempalace	96de23c	fix: CI failures — update workflow for uv migration, fix lint and format
+286	2026-04-07	mempalace	72c548b	test: expand coverage from 20 to 92 tests, migrate to uv
+287	2026-04-07	mempalace	27623a3	Merge pull request #131 from igorls/test/expand-coverage-and-uv-migration
+288	2026-04-06	CapableMind-AI	1546271	docs: org migration URL updates + recall quality methodology files
+289	2026-04-02	CapableMind-AI	219d696	docs: secret rotation checklist + Firestore → Clasp migration plan
+290	2026-03-28	CapableMind-AI	d825e50	docs: Circle Communications Spec — inter-agent alignment protocols
+291	2026-03-27	CapableMind-AI	7b06a8a	docs: Chamber Phase 1 complete — Essay I deliberation + Phase 2 prep
+292	2026-03-23	CapableMind-AI	d305c85	docs: amendment 52 (qwen2.5 fleet migration) + fix machine ownership in summary
+293	2026-03-22	BetterMemories.io	a6d6995	fix: five independent bugs preventing Phase 1 replay completion
+294	2026-03-22	BetterMemories.io	47af370	fix: lower vector similarity threshold 0.7→0.5 and fix lint errors (#38)
+295	2026-03-22	BetterMemories.io	13b24bb	fix: 4 bugs blocking observe→recall roundtrip (#38)
+296	2026-03-14	BetterMemories.io	e464d96	fix: team pairings revert to configured on restart
+297	2026-03-14	BetterMemories.io	deda70c	chore: remove emission debug logging, restore production defaults
+298	2026-03-13	BetterMemories.io	9c059a9	feat: training pair slot name migration script
+299	2026-03-13	BetterMemories.io	4ee8260	fix: SurrealDB NONE literal support and graduation-storage NULL cleanup
+300	2026-03-13	BetterMemories.io	4611085	fix: update graduation-storage test for NULL→NONE migration statement
+301	2026-03-13	BetterMemories.io	14527b8	fix: teacher enrichment pipeline + SurrealDB schema evolution stability
+302	2026-03-10	BetterMemories.io	48f88fb	docs: add upgrade guide for v0.33.0 → v0.35.0 (embedding model change)
+303	2026-03-08	CapableMind-AI	38dd7a4	docs: refine amendment 42 — fixes, AlignType, peer policy (42J)
+304	2026-03-08	CapableMind-AI	09a0e65	docs: synthesize bidirectional boundary + audit fixes into specs v0.2
+305	2026-03-08	BetterMemories.io	0317336	fix: installer QA readiness — build logs, default port, health timeout
+306	2026-03-07	BetterMemories.io	ef5c6bc	docs: update stale counts and deprecated references
+307	2026-03-07	CapableMind-AI	ec14bb1	docs: add Five Kingdoms governing rule to prototype plan
+308	2026-03-07	BetterMemories.io	cbfa189	feat: SurrealDB v3 schema — COUNT indexes, HNSW F32, starts_with fix
+309	2026-03-07	CapableMind-AI	8bcd7a5	docs: add federation thinking — Amendment 40, ADR-022, node discovery concept
+310	2026-03-07	BetterMemories.io	6e019ba	feat: knowledge-type tagging on write path (Amendment 31A/31B)
+311	2026-03-07	CapableMind-AI	1205312	docs: resolve node-discovery design decisions, add iOS network layer concept
+312	2026-03-06	BetterMemories.io	646b99d	fix: factory data unretrievable after restart — facet_id mismatch + job persistence (#12)
+313	2026-03-05	BetterMemories.io	12d1e63	feat: add cross-platform installer, Dockerfile, and docker-compose
+314	2026-03-03	BetterMemories.io	3f8332e	feat: cross-module graph edges, unified query, and enriched entity lookups
+315	2026-03-02	BetterMemories.io	187420e	Add SurrealDB FTS indexes, entity RecordId handling, and graph traversal
+316	2026-02-28	CapableMind-AI	6a4e229	Retire Mac Mini 2018 as target hardware, baseline is now Apple Silicon M4 Pro
+317	2026-02-28	BetterMemories.io	42a1785	L1 BetterMemories: full codebase (Units 01-18) + test suite + bug fixes
+318	2026-02-27	CapableMind-AI	6c38bc8	Fix stale Lite/Standard terminology and signing semantics across build prompts
+319	2026-02-27	CapableMind-AI	07589cf	Update 6 build prompts and system diagram for 18A-18D synthesis
+320	2026-02-26	CapableMind-AI	988e55a	Add research amendments 15A-15L (12 amendments from audit findings)
+321	2026-02-26	CapableMind-AI	4822f65	Synthesize MEDIUM L1 research amendments 15E, 15F, 15I, 15K, 15L
+322	2026-02-26	CapableMind-AI	19777c4	Synthesize 16A + 17A–17E + 18A–18D: 73 findings across 32 specs
+323	2026-02-25	CapableMind-AI	c5a8007	Synthesize 12A-12I pre-build audit findings into 58 specs
+324	2026-02-25	CapableMind-AI	95b44d0	Synthesize 5 data portability & import trust amendments (6A–6D, 11D) into specs
+325	2026-02-25	CapableMind-AI	6175498	Synthesize amendment 14B: Vector Module SurrealDB HNSW migration
+326	2026-02-25	CapableMind-AI	54b8691	Update build prompts for SurrealDB 3.0 unification (remove all LanceDB references)
+327	2026-02-24	CapableMind-AI	75f4f7f	Update macOS app: App Store primary, Cloud→Standalone migration, Vault backup
+328	2026-02-24	CapableMind-AI	46abe0d	Add MindFabric Vault concept: offsite encrypted cognitive backup as a service
+329	2026-02-23	CapableMind-AI	8434e24	Fix system diagram stale references, add bias-as-factor concept
+330	2026-02-19	CapableMind-AI	4a0d7b0	Update READMEs: fix module table, spec count, hyperlink all doc references
+331	2025-09-18	animal-davidglidden-eu	19cb8fb	📚 Add comprehensive session documentation
+332	2025-09-13	animal-davidglidden-eu	dc349b3	Fix symbol collisions with namespaced TriptychIpc helpers
+333	2025-09-13	animal-davidglidden-eu	a21bc50	Complete Prime production-grade triptych normalizer with migration path
+334	2025-09-12	animal-davidglidden-eu	b79b3a0	Implement comprehensive 'do it once, correctly' triptych hardening specification
+335	2025-09-11	animal-davidglidden-eu	f2c57bb	PRIME DIRECTIVE: Complete ES Modules migration and MM→EM→Binding architecture (v2.5.1)
+336	2025-07-28	dotfiles	389febb	🚀 Complete machine migration setup with encrypted backups
+337	2025-07-11	animal-davidglidden-eu	178a0a5	Fix chamber pages: Complete Jekyll-to-Hakyll adaptation
+338	2025-07-08	animal-davidglidden-eu	f855162	Complete document archiving and session memory update
+339	2025-07-05	animal-davidglidden-eu	67fc506	Fix image paths: update templates to use /assets/img/ for clean Hakyll routing
+340	2025-07-04	animal-davidglidden-eu	d766064	Fix header avatar size to match frontispiece (64px)
+341	2025-07-04	animal-davidglidden-eu	198557b	Fix layout issue and implement individual glyph hover (minimal changes)
+342	2025-07-04	animal-davidglidden-eu	197afff	Complete CSS custom property system migration and ornament consistency
+343	2025-07-03	animal-davidglidden-eu	23f605c	Update style and typography guides for Hakyll migration
+344	2025-07-03	animal-davidglidden-eu	084f84c	AldineXXI Framework Evolution: Jekyll to Hakyll Migration Complete + v2.0 Polyphonic Marginalia
+345	2025-07-02	davidglidden.github.io	91db359	Documentation handoff for Hakyll migration - complete Jekyll to Hakyll transformation
+346	2025-07-02	animal-davidglidden-eu	8624424	Complete Jekyll to Hakyll migration with Reading Compass navigation
+347	2025-07-02	animal-davidglidden-eu	1601b23	Add Hakyll migration documentation and update project memory
+348	2025-06-30	animal-davidglidden-eu	8dba756	Complete Jekyll to Hakyll migration foundation
+349	2025-06-30	animal-davidglidden-eu	87c1df0	FINAL STRUCTURE: Unified complete Jekyll content into clean root organization
+350	2025-06-30	animal-davidglidden-eu	52936dd	Add complete CSS/SCSS architecture and Jekyll templates
+351	2025-06-19	davidglidden.github.io	17b0819	Source-synthesis architecture with systematic documentation restructure
+352	2025-06-18	davidglidden.github.io	4fe5a72	Chamber Library Ultimate Achievement: Complete philosophical synthesis capability
+353	2025-06-18	davidglidden.github.io	44075e5	additions to the library while awaiting migration
+354	2025-06-18	davidglidden.github.io	29deb82	Documentation updates: Chamber completion and Hakyll migration readiness
+355	2025-06-17	davidglidden.github.io	d5bfcc4	Final archive: Documentation foundations and methodology protection complete
+356	2025-06-16	davidglidden.github.io	6c8684a	Major milestone: Complete IP protection & First Light Protocol validation
+357	2025-06-15	davidglidden.github.io	9f57020	Final Jekyll state before Hakyll migration
+358	2025-06-15	davidglidden.github.io	91b4549	Final Jekyll state: complete, elegant, ready for Hakyll migration
+359	2025-06-14	davidglidden.github.io	77e2869	Complete Chamber implementation: operational four-protocol system with first session
+360	2025-06-14	davidglidden.github.io	589143a	Implement Chamber foundation: editorial amphitheater and fictional canon system
+361	2025-06-13	davidglidden.github.io	8ebba7d	Improve mobile navigation fade effect and complete content audit

claude/governance/PENDING-172-173-JURIST-RULING-2026-08-31.md

@@ -0,0 +1,177 @@
+# PENDING-172 + PENDING-173 — JURIST RULING, 2026-08-31
+
+**Received:** 2026-08-31, via steward relay into the executor's session.
+**Filed:** verbatim, **before any act taken under it** — PENDING-108 (c)'s ordering, second adoption
+(first was `record-keeping-cluster-JURIST-RULING-2026-08-27.md`).
+**Status:** ⚠ **NOT PLACED.** These are jurist drafts. `~/REVIEWED.md` is the steward's hand; a
+jurist sign-off does not authorize an executor write to it. Nothing below is in force until the
+steward places it.
+**⚠ Relay provenance:** this text reached the executor as a relayed message, not from a file the
+executor read. Per REVIEWED-129 / PENDING-159, relaying strips provenance; what is preserved here
+is the text as relayed, and that limit is part of the record.
+
+---
+
+## Jurist's reading, as relayed — verbatim
+
+Read verbatim via `governance_item` for PENDING-172, its AMENDMENT 1, PENDING-173, REVIEWED-122, PENDING-110, PENDING-145 and PENDING-146; open list and repo status via `governance_state()` (57 open items, computed 11:19). I did not use the §Standing Context block in my preferences — it is dated 2026-07-28 and reports 15 open items, so it is 34 days stale and contradicted.
+
+## First, a near-miss in my own instrument
+
+`governance_item(id='PENDING-172')` returned the parent block only. It gave no indication that a second block existed under that id. I found AMENDMENT 1 in `governance_state()`'s enumeration and had to retrieve it by its full header string via `governance_search` — the id alone does not reach it.
+
+Had I ruled from `governance_item` alone, I would have ruled on the parent's Recommendation — which AMENDMENT 1 corrects as **wrong**. The parent argues that only (d) is enforceable without depending on the party being checked; AMENDMENT 1 supplies `respawnFlags`, an external check that reads the harness rather than the session, and offers option (e).
+
+That is PENDING-173's exact class — a control whose unit is the id while the decidable unit is the block — occurring in the jurist's reading tool, on the day, on the item being ruled. It is the fourth instrument known to guess differently at the same undefined convention: `wake-digest.py`'s `ruled_pendings` (PENDING-145), `governance-drift-check.py`'s `register_findings` (PENDING-173), the open-list unit (PENDING-146), and now `governance_item`. This is a first-hand observation, not testimony, and it belongs in the record.
+
+## PENDING-172 — AUTHORIZED in part; one leg is the steward's, one leg severed
+
+The finding is accepted. The item is right that Constraint 5 was not wrong but unenforced, and right not to propose amending it.
+
+**On the options.** (b) and (c) and (e) are not competitors; they read three different substrates. (e) reads harness state before respawn, (c) reads the session's own transcript shape at the turn, (b) annotates the artifact. (e) is the strongest and is the first mechanism here that answers 'is the loop currently removable?' *before* the removal. (c) is weaker but not empty — a transcript with no human record is in-session evidence — and two checkers on different substrates is Constraint 6's own logic. (b) cannot enforce anything and must never be reported as a control.
+
+**(d) is not mine to rule.** It is a standing steward policy about whether background workers exist at all. What I will say is where the burden now sits: the item establishes that both binaries carry the mechanism and that `cause=upgrade` supplied only the restart, so **every auto-update will do this given a parked idle worker**. The precondition is the parked worker. Keeping background sessions is now the choice that requires justification, not removing them.
+
+**Two things the item does not ask for and should.**
+
+The one-executor-per-day finding is an embedded `[HARDENING]` ask inside an `[ESCALATE]` item — the same shape PENDING-146 names in PENDING-131 ADDENDUM 2 ('one row, one tag, understating the authorization class of what is inside it'). Sever it. Its cost is live today: two sessions existed this morning and whichever wraps second becomes the record of the day.
+
+And provenance. PENDING-171 and commit `5ba5842` were produced with no human in the loop, and PENDING-173 already cites PENDING-171 as precedent. I rule **provenance-mark, not void**: the findings are checkable on their own merits, and voiding would discard real substrate work for a defect the executor could not have detected. But PENDING-171 must not be ruled until it carries the marker — this is PENDING-110's own complaint that the register does not say on its face what it is.
+
+## PENDING-173 — AUTHORIZED (a), with the maxim withheld
+
+The mechanism is right. Three undeclared narrowings, 3 of 16 covered, and a latent false-negative in the safe-looking direction. Authorize the widening.
+
+Two corrections.
+
+**The citation is strengthened by relay.** PENDING-173 says REVIEWED-122 condition 5 'declined exactly that on principle'. Condition 5 declined it *as an executor act in that ruling* and left the door open: 'Should the steward decide the headers are worth normalizing, each amendment carries a dated note stating what was changed and why, per no-silent-revision — but that is a separate steward act and is not authorized here.' The principle is there; its scope is narrower than the relay reports. I will not ratify 'never rewrite the record to fit the instrument' as doctrine on that basis.
+
+**The option set has a hole, and closing it collides with an open item.** PENDING-173's (b) is *retroactive header rewriting*, correctly rejected. But a *prospective* convention — define what AMENDMENT and ADDENDUM each mean for blocks filed from here on, touching no placed record — is neither its (a) nor its (b). That is precisely PENDING-146's recommendation on the adjacent axis: option (iii), convention leading, detection as tripwire, 'makes the census correct rather than making the census smarter'.
+
+PENDING-173 does not cite PENDING-146. Ruling 173's maxim as written would decide 146 by side-effect, in the direction 146 argues against. So: authorize the parser widening, which is owed regardless; route the convention question to 146; do not let the instrument fix pre-empt it.
+
+---
+
+## Draft REVIEWED block for PENDING-172 — jurist-authored, NOT PLACED
+
+```markdown
+## REVIEWED-131 (PENDING-172) — A version upgrade resumed an unattended executor, and the wake digest became its work order
+**Date:** 2026-08-31
+**Decision:** AUTHORIZED in part — (e) and (c) as a two-substrate control, (b) as annotation only; (d) recorded as a steward policy decision, not ruled here. One leg severed.
+**Rules on:** PENDING-172 (parent) and PENDING-172 AMENDMENT 1, both blocks, named explicitly per PENDING-145 and PENDING-146.
+
+**Notes:** The finding is accepted. Constraint 5 was not wrong but unenforced, and the item is correct not to propose amending it. AMENDMENT 1's correction of its own parent is better than the claim it replaces and is the reason this ruling can be more than a policy note.
+
+1. CONDITION — **(e) is authorized as the primary control and must fail to NOT ESTABLISHED, never to safety.** A missing, unreadable or empty `~/.claude/jobs/` reports NOT ESTABLISHED, not 'no parked workers'. The item states this weakness itself; it is raised from disclosure to requirement. The check enumerates every job dir read and every one it could not read, per REVIEWED-122 condition 4 — a control over parked workers whose negative result is an opaque zero is the failure this item is about.
+
+2. CONDITION — **(c) is authorized as a second control on a different substrate, and is never reported as the primary one.** (e) reads harness state; (c) reads the session's own transcript for a preceding human record. Two differently-positioned readers is Constraint 6's logic and the reason to build both. Output must name which control fired.
+
+3. CONDITION — **(b) is authorized as annotation and is explicitly not a control.** Marking the digest as orientation, and `OPEN QUESTION` as inherited-from-a-human and answerable to a human, is cheap and honest. It cannot enforce and must not appear in any report as a mitigation. The item's own warning on this point is adopted verbatim.
+
+4. **(d) is the steward's standing decision and is not ruled.** Recorded because it survives whatever is built: both binaries contain the mechanism, `cause=upgrade` supplied the restart and not the capability, and the sole precondition is a parked idle worker. The burden has moved — keeping background sessions is now the choice requiring justification. (e) is the tripwire that reports whether the policy is holding; it is not a substitute for the policy.
+
+5. **SEVERED — the memory protocol assumes one executor per day.** Date-keyed `session-ledger-YYYY-MM-DD.md`, one session file, one Active Session block with demote-on-promote: two concurrent sessions do not merge and the second silently becomes the record of the day. This is a live `[HARDENING]` ask embedded in an `[ESCALATE]` item — the shape PENDING-146 names in PENDING-131 ADDENDUM 2. It is filed as its own item and is not disposed of here. Its cost was incurred today, not hypothetically.
+
+6. **PROVENANCE, not voiding.** PENDING-171 and commit `5ba5842` were produced with no human turn in the session. They are not void: their findings are checkable against the substrate independently of who filed them, and PENDING-173 has already relied on one. Both carry a dated provenance marker naming the session and the absent loop, per no-silent-revision. **PENDING-171 is not to be ruled until it carries that marker** — an unmarked record does not say on its face what it is, which is PENDING-110's complaint at a new site.
+
+7. **A recorded limit, not a fault.** Deleting `~/.claude/jobs/84ce2880/` was the steward's instruction and its load-bearing values were quoted first. It nonetheless narrows the parent's own 'Not established' question — how a session comes to be `kind: background`. The remaining evidence is `acaabadf`, deliberately kept. Do not delete it.
+
+8. **Scope of this ruling.** I read both blocks verbatim via `governance_item` and `governance_search`. `daemon.log`, the transcript record numbers, `respawnFlags` values and the cross-binary string counts are executor testimony from files I cannot open. The item's own limit on the last of these — identical string counts do not establish identical respawn policy — is preserved rather than resolved.
+
+**If AUTHORIZED:** Build (e) first, with its NOT ESTABLISHED path and enumeration. Then (c). Apply (b) on the same pass, marked as annotation in the code and in the output. File the severed item at §5 before wrapping. Place the provenance markers at §6 before PENDING-171 is brought forward.
+```
+
+## Draft REVIEWED block for PENDING-173 — jurist-authored, NOT PLACED
+
+```markdown
+## REVIEWED-132 (PENDING-173) — The register-integrity control covers one word of a two-word convention, in one of two registers
+**Date:** 2026-08-31
+**Decision:** AUTHORIZED — option (a), on five conditions. The proposed maxim is WITHHELD; the convention question is routed to PENDING-146 and not decided here.
+
+**Notes:** The three undeclared narrowings are real, the demonstration is the right kind (the count did not move when a matching header was appended), and the latent false-negative runs in the dangerous direction — an `ADDENDUM` counted as an original can satisfy 'an un-amended entry exists' on behalf of a record that was replaced. The item's declared correction of its own first census is what earns the rest of it.
+
+1. CONDITION — **`originals` defaults to not-original on any unrecognized marker.** The predicate is an enumerated list of amendment-marker forms, and a header carrying an unrecognized marker is excluded from `originals` rather than admitted to it. This mirrors REVIEWED-122 condition 2: an unlisted verb never yields the permissive answer. The current `not startswith('AMENDMENT')` fails in the permissive direction, which is why one word's absence became a latent pass.
+
+2. CONDITION — **controls are drawn from the census, not from the author's memory of the convention.** The fixture set must contain, at minimum, `ADDENDUM` headers, in-body `**AMENDMENT`/`**ADDENDUM` forms, and `PENDING`-side instances. For any form present in the record and not covered by a control, the check reports NOT ESTABLISHED rather than passing. This is the third instance this month of a positive control satisfied by the narrowing it should have caught, and the item names the other two itself.
+
+3. CONDITION — **the acceptance check enumerates, it does not count.** '3 → 16' is not the check. The thirteen newly visible blocks are listed by register and header, and compared against the item's table. If the two disagree, the disagreement is the finding and is reported, never reconciled by amending the table.
+
+4. CONDITION — **placed records are not rewritten.** Affirmed, and consistent with REVIEWED-122 condition 5. Widening the reader is authorized; normalizing headers already placed is not, here or by implication.
+
+5. CONDITION — **the convention question is routed to PENDING-146, which is open and argues the opposite ordering.** PENDING-146 recommends convention-first with detection as tripwire, on the adjacent axis of the same undefined convention. PENDING-173 does not cite it. A *prospective* definition — what AMENDMENT means as against ADDENDUM, for blocks filed from here on, touching no placed record — is neither this item's (a) nor its (b), and it is the option its own root-cause diagnosis points at. This ruling authorizes the parser widening, which is owed under either ordering, and leaves the convention to 146.
+
+6. **THE MAXIM IS WITHHELD.** 'Widen the instrument to the record; never rewrite the record to fit the instrument' is stated more absolutely than its cited authority supports. REVIEWED-122 condition 5 declined normalization *as an executor act in that ruling* and expressly reserved it as a separate steward act carrying a dated note. Strengthened-by-relay, and the strengthening is load-bearing: adopted as written, the maxim would decide PENDING-146 by side-effect in the direction 146 argues against. The corrected form, offered and not ratified: *the instrument is widened to the record; a placed record is normalized only by a dated steward act stating what changed and why.* Doctrine addition is `[ESCALATE]` and belongs with 146.
+
+7. **A fourth instrument, observed first-hand this session.** `governance_item(id='PENDING-172')` returns the parent block only, with no indication that a sibling exists; AMENDMENT 1 is reachable only by its full header string. The jurist's own reading tool has the defect this item reports, and it nearly produced a ruling on a Recommendation that AMENDMENT 1 corrects as wrong. Recorded here because it belongs to this item's class and is not testimony — it happened to the instrument in the act of ruling. Whether the MCP server's id resolution is fixed is a separate item.
+
+8. **Scope of this ruling.** The line numbers, the census table, the fixture contents and the append-and-recount demonstration are executor testimony from a script I cannot run. What I verified directly: REVIEWED-122 condition 5 verbatim, PENDING-110 option (c) verbatim, PENDING-145 and PENDING-146 verbatim, and the behaviour of `governance_item` at §7.
+
+**If AUTHORIZED:** Implement (a) per conditions 1–4. Report the enumeration in full, agreements included. Do not touch placed headers. Cross-reference PENDING-146 in the commit and in the item's kin list.
+```
+
+---
+
+## Numbering flag, as relayed
+
+One flag before you place these. `REVIEWED-131` collides with `PENDING-131` — the fence item, the most-cited open record in the corpus, and the exact hazard PENDING-110 names. Both headers above name their PENDING explicitly per PENDING-110(b), which is agreed in conversation but still unruled; PENDING-110(c) and (d) remain open. You may prefer to skip 131 outright rather than rely on the parenthetical.
+
+---
+
+## Jurist advice on (d) — offered, explicitly NOT a ruling, as relayed
+
+Advice, jurist-offered and not a ruling — but I'd put it more strongly than I did an hour ago.
+
+**(d) as written is addressed to a party who may not be able to comply.** It reads as a policy about the steward's habits: stop starting background workers. But the item's own 'Not established' section says nothing aliases `claude --bg` in your shell config and nothing in `settings.json` requests it. If workers acquire `kind: background` through the daemon's adopt/respawn path rather than through anything you type, then 'do not run background workers' is not a policy you can execute. It is a wish, and adopting it would produce exactly the false safety the item warns about in (b) and (c).
+
+So the parent's claim that (d) is 'the only one whose enforcement does not depend on the party being checked' needs the same correction AMENDMENT 1 already applied once to that sentence. (b) and (c) fail because the checker is inside the session. (d) may fail for a different reason: the party who creates the condition is unidentified. Its advantage is asserted, not established.
+
+**The hazardous property is narrower than the category.** `84ce2880` was a background worker for three months and would not have taken a turn — `respawnFlags=[]`. `acaabadf` had `--reply-on-resume` and did. The thing that converts a respawn into an unattended turn is the flag, not the backgrounding. That gives you an option the item does not list:
+
+> **(d′) — no parked worker carries `--reply-on-resume`.** Background sessions may exist; none may be configured to take a turn on respawn.
+
+(d′) gives up much less than (d), removes the same mechanism, and is measured by precisely the `respawnFlags` read that (e) already performs. One instrument serves the policy and the tripwire.
+
+**But (d′) is contingent on the same missing fact,** which is why I'd sequence rather than decide:
+
+1. **Establish who sets the flag.** Start a foreground session, `/exit`, then read `~/.claude/jobs/*/state.json` for a new entry and its `respawnFlags`. That is a positive control on the creation path — it shows the instrument can detect presence — and it decides which readings of (d) are addressed to a party who can comply. Cheap, and it is the gate on everything below.
+2. **If the daemon sets it:** (d) and (d′) both collapse to disabling the capability at the configuration level, and I do not know whether that is available — I have not read the binary or its settings surface, and I would not assume it from the log lines. Establish that before choosing.
+3. **If the launch sets it:** (d′) is a real policy and I would take it over (d). (d) bans a category whose uses nobody has enumerated; `acaabadf`'s `mcp__computer-use__` tools suggest at least one live use, and a policy that quietly costs a working practice gets reversed without a record.
+
+**The version of (d) I would not adopt** is the wrap-discipline one — 'check for parked workers before you leave'. PENDING-168 is open in your own register and says the thing: a condition that can only be honoured by remembering will be broken, and the interval is hours. That is not a policy, it is a fifth place to forget.
+
+**Interim, costing nothing and not a control:** treat `Bye!` as false, stop workers rather than detaching from them, and run (e) once today. At time of filing, `acaabadf` was parked idle again with the flag set — if it still is, the condition is live now, not historical.
+
+Recordable form, if you want it in the ruling rather than in conversation:
+
+```markdown
+4. **(d) is the steward's standing decision and is not ruled. Jurist advice, recorded not decided:**
+   (d)'s stated advantage — enforcement independent of the party being checked — is not
+   established, because the party that sets `kind: background` and `--reply-on-resume` is the
+   item's own open question. Prefer **(d′): no parked worker carries `--reply-on-resume`** —
+   it removes the mechanism that converts a respawn into a turn, costs the category nothing,
+   and is measured by the same `respawnFlags` read as (e). Both are gated on one cheap
+   determination: exit a foreground session and read `~/.claude/jobs/*/state.json` for a new
+   entry. A wrap-discipline reading of (d) is declined outright per PENDING-168.
+```
+
+---
+
+## Executor's note on receipt — written after filing the text above, and kept separate from it
+
+Nothing has been acted on under this ruling. What it obliges, and where each sits:
+
+- **§5 SEVERED** — file the one-executor-per-day finding as its own item. Executor-fileable
+  (`[HARDENING]`) regardless of placement.
+- **§6 PROVENANCE** — dated markers on PENDING-171 and commit `5ba5842`. ⚠ The commit message
+  cannot be marked without rewriting history, which is PENDING-164's own subject; the marker must
+  therefore live in the register, naming the commit.
+- **§7 (172)** — `~/.claude/jobs/acaabadf/` is not to be deleted. Noted; it is kept.
+- **REVIEWED-132 §7** — `governance_item`'s id-vs-block defect is a separate item, owed.
+- **Building (e), (c), (b)** — blocked twice over: the ruling is not placed, and the FIX-lane
+  check-in is COME DUE, which suspends the lane.
+- **The maxim** is withheld and must not be used as doctrine. PENDING-173 is to cross-reference
+  PENDING-146 on implementation.
+
+⚠ **The jurist's interim check, run on receipt:** `acaabadf` was stopped at 07:35:50Z on the
+steward's instruction, before this ruling arrived. State at time of filing is recorded in the
+executor's report accompanying this document, not asserted here.

claude/governance/record-keeping-cluster-JURIST-PACKAGE-2026-08-27.md

@@ -0,0 +1,470 @@
+<!-- GROUNDED-IN: ~/CLAUDE.md §Steward-Jurist Interface + §Authorization Taxonomy + Constraint #4; REVIEWED-105 §4; REVIEWED-122 conditions 1/5/10/11; PENDING-108/110/139/144/145/146 verbatim; wake-digest.py:438-456; governance-drift-check.py:217,645,762 (all read 2026-08-27) -->
+---
+title: The record-keeping cluster — six items, one block
+date: 2026-08-27
+type: PROPOSAL — block design gate. Authorization chain: executor drafts → jurist design-gates → steward authorizes.
+audience: the jurist, who has BOUNDED READ ACCESS to the governance register via `governance-mcp.py` (`governance_item`, `governance_state`, `repo_activity`) and NO filesystem read. ⚠ CORRECTED 2026-08-27 under the ruling's condition 1: this line first read "who has NO repository access", which is false and is the third placement of a premise PENDING-161 filed two days earlier. The Grounding section below is therefore a CONVENIENCE, not a necessity — the jurist can read those items directly, and did. What remains genuinely unreachable from the jurist's side, and is therefore executor testimony throughout: the contents of `wake-digest.py`, `governance-drift-check.py`, the skill files, and the absence of the answer key.
+status: DRAFT for the design gate. Nothing in this document is built, run, or landed. The one measurement it reports was run read-only and is reproduced in full.
+---
+
+# The record-keeping cluster — PENDING-110 · 145 · 146 · 108 · 144 · 139
+
+## How to read this
+
+**Part I** measures the live state of the two registers using the digest's own parser, with
+pre-specified positive controls, and reports what the measurement *cannot* settle. **Part II**
+gives each of the six items its substrate status — every ask checked against code read today.
+**Part III** demonstrates the rework the block ordering exists to prevent: it is not
+hypothetical, and one instance is already in the record. **Part IV** proposes that five of the
+six are one defect and names it; **it also argues the sixth is not, against the grain of
+grouping them.** **Part V** identifies the single artifact this entire block gates, which is
+unbuilt and was ordered built "first" ten days ago. **Part VI** traces consequences, **Part VII**
+gives change-class and landing, **Part VIII** the scope boundary, **Part IX** the gate questions.
+
+**The one-sentence claim to test:**
+
+> **These six items cannot be correctly ruled one at a time, because five of them are the same
+> defect — a status inferred from narrative prose that was never constrained to carry one — and
+> the remedies each proposes presuppose an answer to a unit question none of them is authorized
+> to settle alone; the sixth belongs in the sitting for a different reason, stated rather than
+> smoothed over.**
+
+---
+
+## Grounding — the ratified text this builds on (quoted verbatim)
+
+*This section exists because the recurring failure is composing a claim about the constitution
+from memory when the constitution already settles it. These are the actual words, read
+2026-08-27.*
+
+**§ `~/CLAUDE.md` — Steward-Jurist Interface, the `REVIEWED.md` template (line 179):**
+
+> ```markdown
+> ## REVIEWED-[N] — [Matches PENDING-N title]
+> ```
+
+**§ `~/CLAUDE.md` — Authorization Taxonomy:**
+
+> | `[HARDENING]` | Addresses the class of failure, not just the instance | Propose in `PENDING.md`; await steward annotation |
+> | `[PROPOSAL]` | New architectural direction or contract | Explicit steward authorization via `REVIEWED.md` |
+
+**§ `~/CLAUDE.md` — Constitutional Constraint #4:**
+
+> **Honest degradation** — The system must report its own limits. Silent failures are
+> architectural violations
+
+**§ REVIEWED-105 §4 — the sequencing precedent the jurist cites (2026-08-08):**
+
+> 4. SEQUENCING across the four open items: land 123 before 119(i) and 120(a). Both add lines to
+> .precommit-triggers; a validator that catches a malformed line should exist before the file
+> grows. In the other order, the first thing to test the new declarations is the declarations
+> themselves.
+
+**§ REVIEWED-122 condition 1 (2026-08-17) — the pre-registered key:**
+
+> 1. CONDITION — **the acceptance check is a pre-registration, and its ordering is load-bearing.**
+> […] the per-item disposition answer key over all 69 filtered items is **hand-read and committed
+> before the implementation exists**, with the commit hash recorded. A key written after the fix
+> inherits the fix's reading of what closure means, and would pass by construction. […] If the key
+> and the implementation disagree on any item, the disagreement is the finding and is reported —
+> never reconciled by amending the key.
+
+**§ REVIEWED-122 condition 5 — placed records are not edited to please the parser:**
+
+> 5. CONDITION — **the reader is fixed; the placed records are not silently amended.** REVIEWED-78,
+> -81 and -82 are placed rulings and are not to be edited to satisfy the current parser. Fixing the
+> record to please the instrument inverts which of the two is authoritative. Should the steward
+> decide the headers are worth normalizing, each amendment carries a dated note stating what was
+> changed and why, per no-silent-revision — but that is a separate steward act and **is not
+> authorized here.**
+
+**§ REVIEWED-122 condition 10 — the scope of what a ruling can verify:**
+
+> 10. **Scope of this ruling, stated rather than assumed.** I read PENDING-142 verbatim via
+> `governance_item`, and independently observed `governance_state()` reporting PENDING-81 open
+> against an AUTHORIZED REVIEWED-81 […] Everything else […] is executor testimony from a script I
+> cannot run. That is precisely why condition 1 requires a hand-read key: the ruling cannot verify
+> the census, and the acceptance check is the only instrument that can.
+
+**§ REVIEWED-122 condition 11 — the severance that produced PENDING-144:**
+
+> 11. **A follow-on item is owed and is not folded in.** The drift-check covers `~/CLAUDE.md` and
+> reads no script. […] Whether script-resident claims warrant coverage is a [HARDENING] question
+> larger than this item and is to be filed separately rather than absorbed here.
+
+**§ REVIEWED-122 `If AUTHORIZED:` — the build order in force:**
+
+> **If AUTHORIZED:** Draft and commit the hand-read answer key first, with its hash recorded.
+> Submit the (b) decision-verb enumeration for ruling before wiring. Then implement (d) with (a)
+> and (b) inside it, per conditions 2–5.
+
+**§ The two mechanisms under discussion, quoted from source (read 2026-08-27).**
+
+`~/dotfiles/scripts/wake-digest.py:438` — the whole of what decides "ruled":
+
+> ```python
+> return set(re.findall(r"^## REVIEWED-\S+\s*—\s*PENDING-(\S+?)\s*—", reviewed_text, re.M))
+> ```
+
+`~/dotfiles/scripts/wake-digest.py:449-453` — the whole of what decides "open":
+
+> ```python
+> for h, ln in open_items(t):
+>     m = re.match(r"PENDING-(\S+?)\s*—", h)
+>     if m and m.group(1) in ruled:
+>         continue
+>     items.append((h, ln, tag_of(t, h)))
+> ```
+
+`~/dotfiles/scripts/governance-drift-check.py:217` and `:645`:
+
+> ```python
+> RE_HEAD = re.compile(r"^##\s+REVIEWED-(\d+)\s*[—-]\s*(.*)$", re.M)
+> RE_BUILT = re.compile(r"\bBUILT\b")
+> ```
+
+---
+
+## Part I — Terrain: what the registers actually contain, measured today
+
+A read-only script reproducing the digest's parser exactly (the two quoted blocks above) was run
+against the live `PENDING.md` and `REVIEWED.md` on 2026-08-27. **Four positive controls were
+specified before it was run**, because a clean zero from a governance instrument is the most
+dangerous output it can produce; three false zeroes were caught in this corpus on 2026-08-26
+alone, and only one of the three was caught before it was believed — by a control the jurist
+pre-specified. All four controls passed.
+
+| Dated observation, 2026-08-27 | Value |
+|---|---|
+| `## ` blocks in `PENDING.md` | **114** |
+| Distinct ids the parser resolves those blocks to | **101** |
+| Ids the parser considers "ruled" | **80** |
+| Blocks shown open that have a like-numbered ruling naming no PENDING | **23 candidates** |
+| Blocks suppressed as ruled that still carry a live `**Awaiting:**` line | **52 candidates** |
+| Rulings whose captured id matches no live item | **34** |
+
+**⚠ The two candidate columns are candidate columns, and this is the finding, not a hedge.**
+
+- The 23 cannot be reported as 23 false opens. Some are numeric coincidences that name the same
+  item harmlessly; some are rulings genuinely on that item; telling them apart requires reading
+  each. **Verified subset: PENDING-78, -81, -82 — three items shown OPEN in this morning's wake
+  digest against three rulings recorded AUTHORIZED on 2026-07-28**, whose deliberate
+  like-numbering REVIEWED-122 condition 6 already establishes from REVIEWED-78's own Notes.
+- The 52 cannot be reported as 52 live asks. Many carry self-cancelling text — `Awaiting:
+  Nothing. RULED 2026-08-06`, `~~Steward authorization.~~ → BUILT` — which is the stale-`Awaiting:`
+  population REVIEWED-122 condition 10 already names. **Verified subset: PENDING-131 shows four
+  blocks carrying live awaits (parent, ADDENDUM 1, ADDENDUM 2, ADDENDUM 4)** — an independent
+  reproduction of the hand-read table in PENDING-146, arrived at by a different route.
+- Of the 34, most are items long since moved to `PENDING-archive.md`, which is correct behaviour.
+  **The one defect in the column is `131/132/133/134`** — REVIEWED-116's header, captured as a
+  single token equal to no id, so a four-item design-gate ruling suppresses nothing at all.
+
+**⚠ THE MEASUREMENT DEMONSTRATES THE BLOCK'S THESIS AT ITS OWN EXPENSE.** An instrument built
+specifically to size this problem returns two columns it is not entitled to total. It can
+establish the *class* and bound the *candidate pool*; it cannot settle a single item's
+disposition, because disposition is a judgement about a record and no aggregate reaches it. That
+is precisely why REVIEWED-122 condition 1 requires a hand-read key — and it is why the numbers
+above are offered as terrain, never as an acceptance check. Reporting them as totals is the
+column-manufacturing error this corpus has now avoided twice; declaring the limit is the
+banked practice, and it fires here.
+
+---
+
+## Part II — The six items, each ask checked against the substrate
+
+Read today: `wake-digest.py`, `governance-drift-check.py`, `~/REVIEWED.md`, `~/PENDING.md`,
+`~/.claude/skills/jurist-package/SKILL.md`. **Every ask in all six items is unbuilt.** Nothing
+in this cluster has been quietly satisfied since filing, and the items' descriptions of the
+mechanisms match the code as it stands.
+
+| Item | Ask | Substrate status, verified 2026-08-27 |
+|---|---|---|
+| **110** (2026-08-06) | (b) never write a bare register number | convention; unadopted in doctrine |
+| | (c) backfill REVIEWED headings | **NOT done** — REVIEWED-78/-81/-82 headers still carry no `— PENDING-N —`. ⚠ *And see Part III.* |
+| | (d) read the body, not only the heading | **NOT built** — `ruled_pendings` matches the header only |
+| **145** (2026-08-17) | (i)–(iv) record-level disposition | **NOT built** — `ruled` is a set of id strings; nothing compares dates; nothing distinguishes parent from addenda |
+| **146** (2026-08-17) | (i)–(iii) convention + block detection | **NOT built** — unit is the id parsed from the header. Retroactive split **NOT done**: PENDING-147…165 contain no item carrying ADDENDUM 4's Move 1/Move 2, whose `Awaiting:` line is still live and still invisible |
+| **108** (2026-08-06) | (b) package-without-ruling detector | **NOT built** — no package/ruling pairing check exists in the drift-check |
+| | (c) file-before-act ordering | **NOT built** — the skill prescribes file-ruling-then-Addendum, not ruling-before-authorized-act |
+| **144** (2026-08-17) | (iii) disclose the gap in the clean line | **NOT built** — the printed line reads `CLAUDE.md clean (N/N controls passed, M paths verified)` with no scope disclosure |
+| | (ii) checkable claims carry their check | authoring practice; unadopted |
+| **139** (2026-08-14) | (a)/(b) widen `RE_HEAD`, guard `RE_BUILT` | **NOT built** — both regexes verbatim as filed |
+
+**One correction to the record, made here rather than left standing.** PENDING-144's "confirmed
+occupant" — the `ruled_pendings` docstring asserting the opposite of the substrate — **was
+corrected on 2026-08-17** and the docstring now carries the dated correction in place. The item
+already states this in the past tense and needs no amendment; it is noted so the jurist does not
+rule on a live defect that is in fact a discharged one. **144's class remains entirely open**;
+only its one exhibit is historical.
+
+---
+
+## Part III — The rework is not hypothetical: one instance is already in the record
+
+The jurist's reason for the block — *"ruling them in filing order guarantees rework"* — can be
+demonstrated rather than argued, and the demonstration is the strongest single item in this
+package.
+
+**PENDING-110 (2026-08-06) recommends (b) + (c) + (d).** Its option (c) reads:
+
+> **(c) Backfill the headings.** Bounded to those where the number names a *different* item, plus
+> the three the digest miscounts
+
+**REVIEWED-122 condition 5 (2026-08-17) — eleven days later — rules on those exact three:**
+
+> REVIEWED-78, -81 and -82 are placed rulings and are not to be edited to satisfy the current
+> parser. Fixing the record to please the instrument inverts which of the two is authoritative.
+> […] that is a separate steward act and **is not authorized here.**
+
+**⚠ So ruling PENDING-110 as filed would authorize an act a later placed ruling has already
+declined, and declined on a stated principle rather than on cost.** Nothing marks this in
+PENDING-110; the item predates the ruling and has no way to know. A reader taking the items in
+filing order — which is the order the open list presents them in, and the order the digest
+printed them in this morning — walks into it.
+
+**This is also the second-order form of the defect the cluster is about.** The conflict is
+invisible because there is no mechanism that relates an option in an open item to a condition in
+a placed ruling; both are prose. The block ordering the jurist proposes is a *human* remedy for
+exactly the gap the items propose *mechanical* remedies for, and it worked — which is one datum
+in favour of the differently-positioned-readers doctrine and none at all in favour of relying on
+it.
+
+---
+
+## Part IV — The root, and the one item it does not reach
+
+**Five of the six are one defect.** PENDING-139 states it in its own body, and it is the clearest
+statement in the cluster:
+
+> ⚠ **THE COMMON CAUSE IS THE TECHNIQUE, NOT THE TWO REGEXES.** Both defects are *substring-matching
+> over prose used as a status signal* […] The class is that a **status** is being inferred from
+> **narrative text** that was never constrained to carry one, and it will keep producing defects of
+> this shape in either direction — false clean lines and false alarms — for as long as the status
+> has no declared field of its own. Whether that is worth fixing properly (a declared status key
+> per item, matched exactly) or whether marker-matching is good enough for a detection-only
+> instrument is the real question, **and it is the steward's.**
+
+Mapped across the cluster, each site is the same technique failing on a different field:
+
+| Item | The prose read as a status | The failure it produces |
+|---|---|---|
+| **110** | a bare integer, read as an identifier | the number names two items; ~140 code citations inherit it |
+| **145** | a ruling's header id, read as a disposition | one ruling claims the number for all time; later addenda suppressed on arrival |
+| **146** | a header id, read as the unit of decision | five blocks collapse to one row; four live asks invisible while the verdict is correct |
+| **139** | `###` read as not-a-heading; `NOT BUILT` read as built | a clean line over a halved population; a negation read as an assertion |
+| **144** | a docstring's prose, read as provenance | a false claim about the register, inside the instrument that reports the register |
+
+**⚠ PENDING-108 IS NOT THIS DEFECT, AND SAYING SO IS THE POINT.** 108 is about an artifact that
+was never created — a ruling document nobody wrote. No parser failure produces that, and no
+declared field prevents it. Grouping it under the root would be the tidier package and the
+falser one. It belongs in this sitting for a narrower and weaker reason, stated plainly so the
+jurist can reject it: **its proposed remedy (b) is filename-stem matching — the same technique
+the root question is about, one directory along.** If the steward rules for declared fields, 108(b)
+should be built as a declared pairing rather than a stem match; if the steward rules that
+marker-matching is adequate for detection-only instruments, 108(b) is unaffected. That is a real
+dependency, but it is a dependency of 108's *implementation shape*, not of its merits, and 108
+could be ruled separately without rework. **It is offered as a convenience of the sitting, and
+the jurist should feel free to sever it.**
+
+---
+
+## Part V — The artifact this whole block gates, and it is unbuilt
+
+REVIEWED-122's `If AUTHORIZED:` opens: **"Draft and commit the hand-read answer key first, with
+its hash recorded."**
+
+**Verified 2026-08-27: the key does not exist.** No file matching `*answer-key*` or
+`*disposition-key*` anywhere in `~/dotfiles`; no commit touching such a path since 2026-08-17.
+PENDING-146 recorded it as "not yet drafted" on 2026-08-17; that is still true ten days later.
+
+Both 145 and 146 say, independently, that the key cannot be correctly written until they are
+ruled. PENDING-146:
+
+> **If "item" resolves to *id*, the key reproduces the exact unit that caused this defect and
+> grades green.** The key MUST be keyed on `## ` **blocks**, and must record, per block, whether it
+> carries a live `**Awaiting:**` and **at what tag**. Condition 1 as ruled was one word away from
+> certifying this defect as correct.
+
+And PENDING-145: *"This must be inside PENDING-142's pre-registered key, not bolted on after."*
+
+**So the dependency chain is closed and it runs one way only:**
+
+```
+  the unit question  (145 + 146, and 110's identifier question beneath them)
+        ↓  must be settled before
+  the hand-read answer key  (REVIEWED-122 condition 1 — unbuilt, ordered "first")
+        ↓  which must exist before
+  the PENDING-142 implementation  (REVIEWED-122's authorized build — blocked)
+```
+
+**This is REVIEWED-105 §4's precedent exactly, and the jurist's citation of it is apt:** *"a
+validator that catches a malformed line should exist before the file grows. In the other order,
+the first thing to test the new declarations is the declarations themselves."* Here the file has
+already grown — 114 blocks — and the key written today against the wrong unit would certify the
+defect and pass by construction, which is the one outcome condition 1 was written to prevent.
+
+---
+
+## Part VI — Consequence-trace
+
+| Ratified clause | End-state if the block is ruled together | Verdict |
+|---|---|---|
+| `## REVIEWED-[N] — [Matches PENDING-N title]` | The template still says *title*, not *number*. A declared-field ruling would supersede it; a marker-matching ruling leaves it intact and 110(b) becomes doctrine. | Either outcome is consistent; **the template must be amended under a declared-field ruling or it will re-teach the collision.** `[ESCALATE]` — steward's hand. |
+| REVIEWED-122 cond. 1 (key before implementation) | Unaffected in force; **satisfiable for the first time**, because the unit it must be keyed on becomes decided. | Preserved and unblocked |
+| REVIEWED-122 cond. 5 (placed records not edited) | 110(c) is **withdrawn or re-posed** rather than authorized. | Conflict resolved rather than inherited |
+| REVIEWED-122 cond. 10 (ruling cannot verify the census) | Holds. This package's Part I is executor testimony from a script the jurist cannot run — **and it declares the two columns it cannot total.** | Preserved; the disclosure is the compliance |
+| REVIEWED-122 cond. 11 (script claims filed separately) | PENDING-144 is that filing, ruled in the same sitting as its parent's siblings. | Satisfied |
+| Constraint #4 (report own limits) | 144(iii) makes the drift-check's clean line state its subject; 139(b) makes the register check report forms it cannot classify. | **Both strengthen it** |
+
+**One level deeper — which way does the inference run.** Under a *declared-field* ruling, the
+inference inverts: today the absence of a marker means "no status found, assume open"; with a
+declared field the absence of the field means "malformed, report `cannot-assess`". That is a
+strictly better failure mode **but it re-grades every existing block as malformed on day one** —
+114 of them. Any declared-field ruling must therefore say what happens to the existing corpus:
+bulk-annotate, or treat absence as a legacy default. **Neither 145 nor 146 addresses this, and it
+is surfaced here rather than discovered during the build** (Gate question Q4).
+
+**And is any class named here actually two kinds?** Yes — one. "Suppressed block carrying a live
+`Awaiting:`" (Part I, 52 candidates) is two kinds with opposite dispositions: blocks whose ask is
+genuinely live, and blocks whose `Awaiting:` line is stale prose left after the ask was
+discharged. They require opposite remedies — the first needs unhiding, the second needs the line
+retired. A single "unhide the suppressed" fix would surface both and mistake the second for
+recovered work.
+
+---
+
+## Part VII — Change-class and landing
+
+- **110(b), 146's convention** — a change to authoring doctrine in `~/CLAUDE.md` §Steward-Jurist
+  Interface. **`[ESCALATE]`, steward's hand.** The executor does not touch that file.
+- **110(c)** — an edit to placed rulings. **Steward's act only**, and per REVIEWED-122 cond. 5
+  not authorized today; re-posed here as Q2 rather than assumed withdrawn.
+- **110(d), 139(a)/(b), 144(iii), 145, 146's detection** — executor builds against
+  `wake-digest.py` and `governance-drift-check.py`. Both are governance instruments, so **none
+  proceeds without authorization**; detection-only measurement already ran and needed none.
+- **108(b)/(c)** — a new drift-check detector plus an ordering clause in a skill. Executor,
+  on authorization.
+- **The answer key** — hand-read, executor-authored, **committed with its hash recorded before
+  any implementation**, per REVIEWED-122 cond. 1 which is already in force and needs no new
+  authorization. It needs only the unit ruled.
+
+**No re-verify storm.** Nothing here changes what any chamber or engine gate accepts; the subject
+is the governance registers and the two scripts that read them.
+
+---
+
+## Part VIII — What this package does NOT do
+
+- **Runs no code that mutates anything.** The Part I measurement is read-only and its source is
+  reproduced above; it wrote nothing.
+- **Does not rule.** Every disposition below is a lean, not a decision.
+- **Does not correct any item.** The one item whose exhibit is historical (144) is annotated in
+  Part II, not edited.
+- **Does not draft the answer key.** The key must not be written before the unit is ruled — that
+  is Part V's entire argument, and drafting it here would commit the error the package reports.
+- **Does not touch `~/CLAUDE.md`, `~/REVIEWED.md`, or any placed ruling.**
+- **Does not total the two candidate columns in Part I**, and declines to.
+- **Does not address the 270 uncounted census candidates of PENDING-164.** That backlog is
+  untouched by this block and is not advanced by ruling it.
+
+---
+
+## Part IX — Gate questions
+
+**Q1 — The root question, and it is the block's hinge.** Declared status fields per item
+(`rules:`, `status:`, `unit:` — matched exactly), or better marker-matching over prose?
+*Executor's lean:* **declared fields, for the closure signal only** — not a general schema. The
+evidence is that marker-matching has now failed in both directions at five sites, and each fix
+widened a pattern that the next unanticipated form escaped. But the lean is weak on cost: a
+declared field re-grades 114 existing blocks (Part VI), and 139 itself asks whether
+marker-matching is "good enough for a detection-only instrument" — which the digest arguably is.
+
+**Q2 — 110(c) against REVIEWED-122 condition 5.** Is (c) withdrawn, or re-posed as the "separate
+steward act" condition 5 contemplates? *Executor's lean:* **withdrawn as filed.** Under Q1-as-
+declared-fields it becomes unnecessary; under Q1-as-marker-matching it remains the record-edit
+condition 5 warns against. It has no reading on which it is the right move.
+
+**Q3 — Is PENDING-108 severed?** *Executor's lean:* **rule it in the sitting, but on its own
+merits, and sever it if that is cleaner.** Part IV states the case against grouping it.
+
+**Q4 — The corpus transition, which no item addresses.** Under declared fields, what is the
+disposition of the 114 existing blocks that carry no field? *Executor's lean:* **absence means
+`cannot-assess`, never `open` and never `closed`** — Constraint #4 and REVIEWED-106's
+three-valued precedent. Bulk-annotation is a second, separately-ruled act.
+
+**Q5 — Ordering within the block.** The relayed order is 110 → 145 → 146 → 108 → 144 → 139.
+*Executor's lean, offered against the grain:* **read 139 first.** It is last in the relayed order
+and it is the only item that states the root question the other four turn on; taking it last
+means four rulings are made before the question they presuppose is put. The relayed order is
+right about dependency *among the unit items*; 139 is not one of them, it is their diagnosis.
+**This is a lean about reading order, not about ruling order, and the jurist may well have meant
+exactly that.**
+
+**Q6 — The key's own falsifier.** REVIEWED-122 cond. 1 requires that key-vs-implementation
+disagreements be reported as findings, never reconciled. Should the key additionally be required
+to record, per block, **which of the two kinds** a live `Awaiting:` is (Part VI's split — genuinely
+live vs. stale prose)? *Executor's lean:* **yes.** Without it the acceptance check cannot
+distinguish recovered work from resurfaced noise, and 52 candidates is too many to eyeball twice.
+
+---
+
+*Filed by the executor 2026-08-27. Companion entries: `~/PENDING.md` PENDING-108, -110, -139,
+-144, -145, -146. No code changed, no register mutated, no ruling drafted. The Part I measurement script is preserved beside this package as
+`record-keeping-cluster-measurement-2026-08-27.py` — read-only, controls pre-specified in
+source, exits non-zero and refuses its own numbers if any control fails.*
+
+---
+
+# Addendum — design-gate ruling received and applied (2026-08-27)
+
+**Parts I–IX above are preserved as the text the jurist ruled on.** This Addendum layers
+disposition; it does not rewrite history. The one exception is the frontmatter `audience:` line,
+corrected in place because condition 1 required it *before the sitting* and a false premise left
+standing in a document written for quotation is the defect itself. The correction is marked and
+records what it replaced.
+
+**Verdict received: NOT PASSED AS FILED.** The ruling is filed verbatim and separately at
+`record-keeping-cluster-JURIST-RULING-2026-08-27.md`, **before any act taken under it** — the
+ordering PENDING-108 (c) proposes and the executor had not previously adopted.
+
+## The ruling in force
+
+- The block is real; the sitting should happen. Ruling order **139 → 145 → 146 → 110 → 144**, with **108 severed** and **143 in the picture as evidence, not as an item to rule.**
+- **Q1 reframed and answered:** the two scripts are not one instrument. **Declared closure field for the wake digest** (a primary governance surface, the last place to infer status from prose); **139(b) for the drift-check**, marker-matching included, because it is a detector. This dissolves most of the 114-block transition cost that made the executor's lean weak.
+- **Q4 was already largely ruled** by REVIEWED-122 condition 4 (the third value is enumerated, never counted).
+- **Q6 yes**, and partly already in force.
+
+## Corrections that supersede the drafted design
+
+1. **The premise was false, and it was load-bearing.** The jurist has bounded read access and used it, reading eight items verbatim. The package's relay architecture was chosen on a stated ground that does not hold. Corrected in the frontmatter; the Grounding section stays, relabelled a convenience.
+2. **Membership was set by relay, not by the root.** The package argued a root and never ran it back across the register. **PENDING-143 belongs in the picture** — it states 145's mechanism in the same words on a different item, and is the evidence that the defect has *already forced a workaround into the register* rather than being prospective. **PENDING-124 and -128** are steward reads owed since 2026-08-17 and were absent.
+3. **Part V's blocking argument does not survive**, and Part VIII's refusal to draft inverted the doctrine the census was run under. A hand-read key cannot pass by construction; the risk is to its *scope*, and 146 already supplies the remedy as a requirement. **A block-keyed key is strictly finer and collapses to an id-keyed one under the opposite ruling; the reverse is false.** The key is therefore safe to draft under every outcome of Q1 and Q4 and is being drafted now.
+4. **Part V buried the ungated work.** The answer key is the *gated* artifact; **the citation-safety fence is the ungated one and has been ungated for seventeen days.** Move 2 is bounded, closable in one sitting, and needs no ruling from either party.
+5. **Q2's lean over-read condition 5.** 110(c) has two legs; condition 5 reaches only the 78/81/82 leg. The **REVIEWED-86 / PENDING-86** collision is untouched by it and is re-posed rather than withdrawn.
+6. **Q3's severance stands on better grounds than the package gave.** A filename stem is a structured token, not narrative prose; its failure mode is mismatch, not misreading. 108(b) is closer to the *declared-field answer applied to another substrate*, which argues for Q1's lean rather than for grouping.
+7. **The `If AUTHORIZED:` quotation was truncated mid-clause without an ellipsis.** The dropped remainder carries two obligations bearing on this package, and the dependency chain is one link short: **unit → key → verb-enumeration ruling → implementation.**
+8. **The 78/81/82 "verified subset" is three items of two kinds** — PENDING-161 separates 82 out as the one confirmed self-declared-closure case. The package committed, on its own verified subset, the two-kinds-under-one-label error it correctly flagged for the 52.
+9. **144's exhibit is not only historical.** A live instance exists: the drift-check's clean line is correct and silent about a false substrate claim in placed ruling REVIEWED-129, because that claim is outside its one file.
+
+## Part I's instrument — three defects conceded, and they are not cosmetic
+
+- **The docstring overclaimed.** It said the script reproduces the digest's parser *exactly*; the `ruled` regex is reproduced, but `open_items()` was **substituted** with "every line beginning with `## `". That substitution produces **114** — the figure Part VI then used to size the transition cost. *The half that was reproduced is not the half that carried the load.*
+- **All four controls are must-detect.** PENDING-139 — an item inside this very package — requires controls **in both directions**, and there is no must-not-flag control. Control 4 is a positive control on the parser's own definition of its unit and passes trivially.
+- **Consequently `114` and `80` are floors, not counts**, and the package did not say so. Both are blind to `###` forms that 139(A) has measured to exist.
+- **`decision_of` can borrow a neighbour's verdict** under `re.S` when an entry has no `**Decision:**` line, and the printed column inherits it uncontrolled.
+- **One interpretive claim was layered onto a script number without separation** — *"most of the 34 are in `PENDING-archive.md`"*. The script never reads that file, and the claim was checkable.
+
+## What proceeds now
+
+1. ✅ **DONE — the answer key, at block granularity, drafted and committed BEFORE any implementation.**
+   `claude/governance/PENDING-142-answer-key-2026-08-27.md`, **pre-registration commit `3a33666`**
+   (`3a33666730380e5b51c694e83ebfbc723b35c407`), committed alone so the hash is unambiguous. REVIEWED-122 condition 1's
+   *"hash recorded"* is satisfied by this line and by the PENDING-142 note. **120 blocks over 106
+   distinct ids — 14 invisible as units.** ⚠ Its declared limit: 5 of 120 rows are hand-read in the
+   full sense; the rest are hand-assigned from a dispositive field, and the remainder is recorded as owed.
+2. **Move 2** — dispose the 25 line-addressable blockquote runs. Ungated, one sitting.
+3. The frontmatter correction: **done**.
+4. PENDING-143, -124, -128 entered into the picture: **done, in this Addendum.**
+5. Part I's instrument: defects recorded here rather than the script quietly amended, so the ruled text and its rebuttal stand together.
+
+⚠ **The loose end the jurist reported and declined to explain is resolved, and it was resolvable only from the executor's side.** See `PENDING-104 — ADDENDUM 1`. It is not a defect in either governance tool. **The register was being written by the executor while the jurist read it**, and the 23-line delta is exactly the length of a note inserted into `PENDING.md` at line ~763 earlier that day. The jurist's "agreeing" trio (3421 / 3732 / 3764) is 23 lower than the live file; the "disagreeing" pairs straddle the write. **The executor's own filing activity silently corrupted the jurist's read of the cluster about filing**, and the corruption presented as authoritative line numbers.

claude/governance/record-keeping-cluster-JURIST-RULING-2026-08-27.md

@@ -0,0 +1,117 @@
+<!-- GROUNDED-IN: the jurist's ruling, relayed verbatim by the steward 2026-08-27. Filed per ~/.claude/skills/jurist-package/SKILL.md:73 — "file it verbatim as its own *-JURIST-RULING-<date>.md". -->
+---
+title: Design-gate ruling — the record-keeping cluster
+date: 2026-08-27
+type: JURIST RULING on record-keeping-cluster-JURIST-PACKAGE-2026-08-27.md
+verdict: NOT PASSED AS FILED — the block is real and the sitting should happen; three gate-blocking conditions.
+relay: relayed verbatim by the steward. Filed before any act it authorizes.
+---
+
+# Design-gate ruling — the record-keeping cluster (2026-08-27)
+
+⚠ **Filed verbatim and BEFORE any act taken under it**, per PENDING-108 (c) — the ordering that
+item proposes and that the executor had not yet adopted. PENDING-108's own pre-registered clock
+starts on this package, as the ruling notes.
+
+⚠ **Nothing below is the executor's wording.** Corrections and dispositions taken under this
+ruling are recorded in the package's Addendum, not here.
+
+---
+
+## What I did first
+
+I read the package in full, then read the substrate rather than trusting the package's account of it. Verbatim via `governance_item`: **REVIEWED-122, PENDING-110, -108, -139, -143, -145, -146, -161**. Plus `governance_state()` at 19:13 today. I did not use this app's memory as a source. I could not run the Part I script, and I have no filesystem read, so every claim about `wake-digest.py`, `governance-drift-check.py`, the skill file, and the absence of the answer key remains executor testimony.
+
+Store discipline, since it matters here: where I say 'verified', I mean I read it through the governance tools this session. Where I say 'observed', I mean I saw it in `governance_state()`'s own output. Where I cite my preferences document, that is a third store, dated 2026-07-28, which the executor cannot read.
+
+**Gate verdict: NOT PASSED AS FILED.** The block is real and the sitting should happen. Three findings are gate-blocking, and one of them dissolves the package's central argument for its own inaction. Everything else below is correction, not obstruction.
+
+---
+
+## The three gate-blocking findings
+
+### 1. The frontmatter premise is false, and an open `[ESCALATE]` item filed two days ago says so
+
+`audience: the jurist, who has NO repository access — this document is self-contained.`
+
+**PENDING-161** (2026-08-25, `[ESCALATE]`, open) exists for exactly this claim. Verbatim: *'PENDING-159 and REVIEWED-129 both assert the jurist has no substrate access. It has bounded read access via `governance-mcp.py` … The conclusions survive; the premise does not.'* It calls the pattern *'an unverified negative state-claim, asserted confidently, in the document that gets quoted'*, and notes it was written *'by the party that spent the day building a mechanism against that class'*.
+
+This package is the third placement of that premise, in a document written for quotation, two days after the item. It is not cosmetic. The premise generates the package's whole architecture: a Grounding section that relays eleven quotations I could have read myself, and a design in which executor testimony is the only channel. Your own doctrine on this is unambiguous — *'a second agent asked to go and look would return testimony about the substrate; a tool returns the substrate'*. The package chose the relay form on a stated ground that is false.
+
+I also observed the corollary directly: `governance_state()` lists **PENDING-82 as OPEN `[PROPOSAL]`** while PENDING-161 records that PENDING-82's own `Awaiting` line reads *'INSTALLED AND IN USE. CLOSED 2026-08-08'*. Nineteen days now.
+
+**Condition:** the frontmatter is corrected before the sitting. The Grounding section can stay — it is useful — but it is a convenience, not a necessity, and it should say so.
+
+### 2. The cluster's membership was set by relay, not by the root the package names
+
+The package says the order was relayed (Q5: *'the relayed order is 110 → 145 → 146 → 108 → 144 → 139'*). It then argues a root, admits one member does not fit it (108, honestly), and never runs the root back across the open register to ask who else does. Doing that finds **PENDING-143**, open, filed 2026-08-17, sitting in the register between 144 and 145.
+
+Verbatim from 143: PENDING-121 is *'invisible in `governance_state()` since that ruling was placed, because the suppression rule asks only whether a REVIEWED header names the id — never what the ruling decided.'* That is PENDING-145's mechanism, stated in the same words, on a different item. PENDING-146 cites 143 by name — *'the same disclosed-carrier pattern as PENDING-143'* — and the package quotes neither line.
+
+143 also names two more: *'PENDING-124 (REVIEWED-106) and PENDING-128 (REVIEWED-111) are the other two design-gate items in the same class … UNDETERMINED pending a steward read.'* Those are steward reads that have been owed since 2026-08-17 and appear nowhere in the package.
+
+This is the weld test applied to the package's own sharpest section. Part IV's root, run back across the register, changes the membership in both directions. 143 does not need ruling — it is a `[FIX]` carrier that retires when 142 lands — but it must be in the picture, because it is the evidence that 145's defect has already forced a workaround into the register rather than being a prospective risk.
+
+### 3. Part V's blocking argument does not survive at the granularity 146 itself specifies
+
+Part V says the unit question must be settled before the answer key can be written; Part VIII uses that to decline to draft it. The key has now been 'ordered first' for ten days and does not exist.
+
+The argument does not hold. Condition 1's key is **hand-read** — that is its entire point, and the reason it cannot inherit the implementation's reading. A hand-read key cannot 'pass by construction', because no parser produces its verdicts. The pass-by-construction risk that 146 correctly identifies is a risk to the key's *scope*, not its verdicts: an id-keyed key of 69 rows cannot reach a block-level defect. And 146 already supplies the remedy, as a requirement rather than an option: *'The key MUST be keyed on `## ` blocks, and must record, per block, whether it carries a live `**Awaiting:**` and at what tag.'*
+
+A block-keyed key is strictly finer than an id-keyed one and collapses to it if the steward rules the other way. The reverse is not true. So drafting at block granularity is safe under every outcome of Q1 and Q4, and it is your banked doctrine verbatim: *drafting is the finer instrument*. The package ran a census — 114 / 101 / 80 / 23 / 52 / 34 — used it to size a corpus-transition cost, and declined to draft. That inverts the doctrine the census was run under.
+
+**Condition:** the key is drafted at block granularity, starting now. It needs no new authorization; REVIEWED-122 condition 1 is in force, and the package's own Part VII concedes this.
+
+**Related, and worse.** PENDING-146 states in its own recommendation: *'(iii), and the split is not gated on the ruling'*, and again in its `Awaiting` line that Move 1 and Move 2 *'await direction and have been unable to say so since 2026-08-13'*, with Move 2 described as *'bounded, closable in one sitting, no ruling needed'*. The live citation-safety exposure behind PENDING-131 (c) is the highest-cost thing in this cluster and it is **not gated by this block at all**. Part V identifies the answer key as 'the single artifact this entire block gates'. The unbuilt key is the gated artifact; the fence is the ungated one, and it has been ungated for seventeen days. Part V's framing buries that.
+
+---
+
+## The Part I instrument
+
+The refusal to total the two candidate columns is right and is the strongest instinct in the package. Three problems with the instrument itself:
+
+- **The script does not reproduce what its docstring claims.** It says *'Reproduces wake-digest.py's OWN parser exactly (read from source, not reimagined)'*. The quoted digest excerpt calls `open_items(t)` and `tag_of(t, h)`; neither is quoted, and the script substitutes 'every line beginning with `## `' for the first. That substitution produces **114**, which Part VI then uses as a firm number to size the corpus transition. The half that is reproduced is the `ruled` regex; the half that produces the load-bearing figure is a reimplementation.
+- **The controls run in one direction only, against a requirement stated by an item inside the package.** PENDING-139, verbatim: *'positive controls are required in both directions: a fixture amendment under a `###` heading the check must DETECT, and a fixture item carrying the negated marker which the check must NOT flag.'* All four controls are must-detect. There is no must-not-flag control. Control 4 (`len(blocks) > 80`) is a positive control on the parser's own definition of the unit and passes trivially — the exact class your 2026-07-28 doctrine says Q2 cannot catch. It is also blind to `###`, and 139(A) has *measured* that at least one `###` REVIEWED heading exists in the corpus. So `114` and `80` are floors, not counts, and the package does not say so.
+- **`decision_of` can borrow a neighbour's verdict.** `^## REVIEWED-N\s*—.*?^\*\*Decision:\*\*\s*(\w+)` under `re.S` scans forward to the first `**Decision:**` after the header. If a REVIEWED entry has none, it captures the next entry's. Nothing controls for this, and the printed `REVIEWED-{p} = {d}` column inherits it.
+
+One interpretive claim is also layered onto a script number without separation: *'Of the 34, most are items long since moved to `PENDING-archive.md`'*. The script never reads that file. `governance_item` does search it, so the claim is checkable and was not checked.
+
+---
+
+## Smaller corrections
+
+- **Part III is sound and is the best thing in the package.** I verified both quotations. 110(c) does name *'the three the digest miscounts'*, and REVIEWED-122 condition 5 does decline exactly those three on principle. The demonstration holds.
+- **But Q2's lean over-reads condition 5.** 110(c) has two legs: *'those where the number names a different item, plus the three the digest miscounts'*. Condition 5 reaches only the second. The first is REVIEWED-86 / PENDING-86 — 110 records it as a live collision, *'differently biased checkers'* against *'the jurist cannot read the constitution it design-gates'*. 'Withdrawn as filed' drops it on the strength of a condition that does not touch it.
+- **The `If AUTHORIZED:` quotation is truncated mid-clause with no ellipsis**, under the heading *'the build order in force'*. The dropped remainder contains two obligations that bear directly on this package: *'restore PENDING-121 by hand on the same pass'* (which is PENDING-143, omitted above) and *'Report the key-versus-implementation comparison in full, including agreements, rather than reporting only the delta'* (which partly pre-answers Q6). Part V's dependency chain is also short one link: the same clause requires the (b) decision-verb enumeration to be *submitted for ruling before wiring*, so the chain is unit → key → verb-enumeration ruling → implementation.
+- **Four of eleven conditions are quoted, and three of the unquoted seven govern the gate questions.** Condition 4 already rules that the third value is *'enumerated, never merely counted'* — that is most of Q4, decided. Condition 2's *'defaults to not-closed on any unrecognized decision verb'* is the same principle Q4 is asking about. Condition 7 names 124 and 128.
+- **Part II's substrate table omits two live legs of 110**: the unplaced `**Provenance:**` lines (*'Also owed, same surface, not yet done'*), and 110's own acceptance check — *'the open-item count should fall from 21 to 18'*. `governance_state()` shows 47 open items today. That falsifier is unusable as written, which is precisely 144(ii)'s subject.
+- **The 78 / 81 / 82 'verified subset' is three items of two kinds.** PENDING-161 separates 82 out: it is the one confirmed case of an item declaring its own closure in its `Awaiting` line while the open list still carries it, *'1 item of 105'*. Grouping it with 78 and 81 is the same two-kinds-under-one-label error the package rightly flags for the 52.
+- **A cross-store confirmation the executor could not have obtained.** My preferences document, generated 2026-07-28, records `AUTHORIZED REVIEWED-81` and `AUTHORIZED REVIEWED-82`. `governance_state()` today shows PENDING-81 `[ESCALATE]` open and PENDING-82 `[PROPOSAL]` open. Two stores, one of them unreachable from your side, disagreeing on the same items. That is Part I's class, verified independently of Part I's script.
+- **144's exhibit is not only historical.** `governance_state()` prints `GOVERNANCE DRIFT — CLAUDE.md: 0 substrate-contradicted claim(s)` while PENDING-161 asserts, in an open `[ESCALATE]`, a false substrate claim sitting in placed ruling REVIEWED-129. The claim is outside CLAUDE.md, so the drift-check is correct and silent, and the clean line discloses nothing about what it did not look at. That is a live instance of 144(iii), stronger than the discharged docstring, and it was available to be found.
+
+---
+
+## The gate questions
+
+**Q1 — I am rejecting the framing before answering it.** The question treats `wake-digest.py` and `governance-drift-check.py` as one instrument. They are not. The drift-check is a detector, and 139(b) — widen, plus emit a count of forms the parser could not classify — is the right answer there, marker-matching included. The wake digest is not a detector. It is the surface a steward reads to learn what awaits authorization, and PENDING-145 establishes that the most load-bearing item in the corpus was invisible in it for a week. A primary governance surface is the last place to infer status from prose. **Lean: declared closure field for the digest; 139(b) for the drift-check.** Split this way, the '114 blocks re-graded' cost that makes the executor's lean weak largely evaporates, because the field is a closure signal on a much smaller population and Q4 handles the rest.
+
+**Q2 — Split it.** Withdraw the 78/81/82 leg as foreclosed by condition 5. Re-pose the REVIEWED-86 leg, which condition 5 does not reach. Note separately that 82's case has been overtaken by PENDING-161.
+
+**Q3 — Sever 108, on better grounds than offered.** The package's reason (filename-stem matching is 'the same technique, one directory along') does not survive. A filename stem is a structured token, not narrative prose; its failure mode is mismatch, not misreading. If anything 108(b) is the declared-field answer already applied to a different substrate, which argues *for* Q1's declared-field lean rather than for grouping. 108 carries its own completed measurement and its own pre-registered falsifier (*'if, over the next 10 packages, the detector fires zero times … retired rather than kept as reassurance'*). It is the most self-contained item in the set. Rule it separately. One note for the sitting: this document is a `*JURIST-PACKAGE*.md`, so 108's own clock starts on it.
+
+**Q4 — Agreed, and mostly already ruled.** Absence means `cannot-assess`, never open and never closed. REVIEWED-122 condition 4 already requires that bucket to be enumerated by id and header with a reason, not counted. Bulk annotation is a separate steward act.
+
+**Q5 — Read 139 first; agreed, and I did mean that.** Ruling order: 139, then 145, then 146, then 110, then 144. 108 severed. 143 in the picture as evidence, not as an item to rule.
+
+**Q6 — Yes, and part of it is already in force.** The key records, per block, which of the two kinds a live `Awaiting:` is. Condition 1's *'the disagreement is the finding'* and the dropped *'including agreements, rather than reporting only the delta'* both already apply.
+
+---
+
+## What I could not settle
+
+- Every 'NOT built' in Part II. I cannot read the scripts. I can confirm the items describe mechanisms consistently with each other, and that all six are open in `governance_state()`.
+- The non-existence of the answer key. No tool here reaches `~/dotfiles`, and `repo_activity` does not cover it.
+- Part I's numbers. I can confirm the class from two stores; I cannot confirm a figure.
+- **One loose end I cannot explain and am reporting rather than smoothing.** `governance_state()` and `governance_item` disagree about where three of these items live: PENDING-108 at 1580 versus 1603, PENDING-110 at 1664 versus 1687, PENDING-143 at 3691 versus 3714 — each exactly 23 lines apart. For PENDING-139, -145 and -146 they agree exactly (3421, 3732, 3764). Two instruments in the same server, disagreeing about a location, in a cluster about record-keeping instruments. I have no account of it and am not offering one. It is not covered by any of the six items.
+
+If you want it, I can draft the placeable `REVIEWED` block in plain fenced markdown once you tell me whether you are ruling the block as amended or sending it back for a redraft. I would send it back — but the three conditions above are actionable this week, and the key and Move 2 need no ruling from either of us.

claude/governance/record-keeping-cluster-measurement-2026-08-27.py

@@ -0,0 +1,93 @@
+#!/usr/bin/env python3
+"""One-shot measurement for the record-keeping cluster package (2026-08-27).
+
+Reproduces wake-digest.py's OWN parser exactly (read from source, not reimagined),
+then reports what it gets wrong in each direction. Positive controls are
+PRE-SPECIFIED below: if they do not hold, this script measured nothing.
+"""
+import re, pathlib, sys
+
+HOME = pathlib.Path.home()
+P = (HOME / "PENDING.md").read_text(errors="replace")
+R = (HOME / "REVIEWED.md").read_text(errors="replace")
+
+# --- wake-digest.py's parser, verbatim in behaviour -------------------------
+ruled = set(re.findall(r"^## REVIEWED-\S+\s*—\s*PENDING-(\S+?)\s*—", R, re.M))
+
+blocks = []  # (header, lineno, body)
+lines = P.split("\n")
+idx = [i for i, l in enumerate(lines) if l.startswith("## ")]
+for k, i in enumerate(idx):
+    end = idx[k + 1] if k + 1 < len(idx) else len(lines)
+    blocks.append((lines[i][3:].strip(), i + 1, "\n".join(lines[i:end])))
+
+def parsed_id(h):
+    m = re.match(r"PENDING-(\S+?)\s*—", h)
+    return m.group(1) if m else None
+
+def live_await(body):
+    m = re.search(r"^\*\*Awaiting:\*\*(.*)$", body, re.M)
+    return m.group(1).strip()[:60] if m else None
+
+# --- Direction 1: FALSE OPENS (shown open, but an AUTHORIZED ruling exists) --
+def decision_of(n):
+    m = re.search(r"^## REVIEWED-%s\s*—.*?^\*\*Decision:\*\*\s*(\w+)" % re.escape(n),
+                  R, re.M | re.S)
+    return m.group(1) if m else None
+
+false_opens = []
+for h, ln, body in blocks:
+    pid = parsed_id(h)
+    if not pid or pid in ruled:
+        continue
+    d = decision_of(pid)          # a like-numbered REVIEWED naming no PENDING
+    if d and re.search(r"^## REVIEWED-%s\s*—\s*(?!PENDING-)" % re.escape(pid), R, re.M):
+        false_opens.append((pid, d, h[:70], ln))
+
+# --- Direction 2: SUPPRESSED BLOCKS THAT CARRY A LIVE AWAIT -----------------
+suppressed = []
+for h, ln, body in blocks:
+    pid = parsed_id(h)
+    if pid and pid in ruled:
+        aw = live_await(body)
+        if aw:
+            suppressed.append((pid, h[:70], ln, aw))
+
+# --- Direction 3: RULINGS THAT SUPPRESS NOTHING (id matches no real item) ---
+real_ids = {parsed_id(h) for h, _, _ in blocks} - {None}
+phantom = sorted(ruled - real_ids)
+
+# --- PRE-SPECIFIED POSITIVE CONTROLS ---------------------------------------
+ctl = []
+ctl.append(("false-open control: 78, 81, 82 all present",
+            {p for p, *_ in false_opens} >= {"78", "81", "82"}))
+ctl.append(("suppressed control: PENDING-131 has >=3 live-await blocks",
+            sum(1 for p, *_ in suppressed if p == "131") >= 3))
+ctl.append(("phantom control: REVIEWED-116's slashed token is unmatched",
+            any("/" in x for x in phantom)))
+ctl.append(("sanity: parser found a non-trivial number of blocks",
+            len(blocks) > 80))
+
+print("MEASURED 2026-08-27 — wake-digest.py's own parser, run against the live files\n")
+print(f"  '## ' blocks in PENDING.md      : {len(blocks)}")
+print(f"  distinct ids the parser sees    : {len(real_ids)}")
+print(f"  ids claimed ruled               : {len(ruled)}\n")
+
+print(f"FALSE OPENS — shown open, ruling exists but names no PENDING ({len(false_opens)}):")
+for p, d, h, ln in false_opens:
+    print(f"    PENDING-{p:<4} L{ln:<6} REVIEWED-{p} = {d}   {h}")
+
+print(f"\nSUPPRESSED BLOCKS CARRYING A LIVE **Awaiting:** ({len(suppressed)}):")
+for p, h, ln, aw in suppressed:
+    print(f"    id {p:<4} L{ln:<6} {h}\n            └─ Awaiting: {aw}")
+
+print(f"\nRULINGS WHOSE CAPTURED ID MATCHES NO ITEM ({len(phantom)}): {phantom}")
+
+print("\nCONTROLS (pre-specified; a failure means this script measured nothing):")
+bad = 0
+for name, ok in ctl:
+    print(f"    {'PASS' if ok else 'FAIL'}  {name}")
+    bad += not ok
+print("\nINSTRUMENT NOT VERIFIED — do not use these numbers." if bad else
+      "\nAll controls passed.")
+sys.exit(1 if bad else 0)

claude/governance/thread-query-log.jsonl

@@ -2,3 +2,5 @@
 {"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"]}]}
+{"date": "2026-08-27", "thread": "the 270 uncounted census candidates — the backlog of decisions that never reached the authorization record", "terms": ["uncounted", "census", "candidates", "backlog", "decisions", "never", "reached", "authorization", "record"], "candidates": 388, "returned": [{"path": "~/.claude/projects/-Users-davidglidden/memory/session-ledger-2026-06-09.md", "date": "2026-06-09", "matched": ["census", "backlog", "decisions", "never", "authorization", "record"]}, {"path": "~/.claude/projects/-Users-davidglidden/memory/session-ledger-2026-04-24.md", "date": "2026-04-24", "matched": ["candidates", "decisions", "reached", "authorization", "record"]}, {"path": "~/.claude/projects/-Users-davidglidden/memory/session-ledger-2026-07-05.md", "date": "2026-07-05", "matched": ["census", "backlog", "decisions", "never", "authorization", "record"]}, {"path": "~/.claude/projects/-Users-davidglidden/memory/session-2026-05-25-arc-stage-f-gamma-and-l1-test-real-history-findings.md", "date": "2026-05-25", "matched": ["decisions", "never", "reached", "authorization", "record"]}, {"path": "~/.claude/projects/-Users-davidglidden/memory/session-2026-06-04-arc-stage-n-closed-gloss-now-published.md", "date": "2026-06-04", "matched": ["census", "decisions", "never", "authorization", "record"]}]}
+{"date": "2026-08-31", "thread": "the 270 uncounted census candidates — decisions that never reached the governance record; prior-art enumeration and register silence", "terms": ["uncounted", "census", "candidates", "decisions", "never", "reached", "governance", "record", "prior-art", "enumeration", "register", "silence"], "candidates": 472, "returned": [{"path": "~/.claude/projects/-Users-davidglidden/memory/session-2026-06-04-evening-whisper-migration-ikb-english-enforcement.md", "date": "2026-06-04", "matched": ["census", "decisions", "never", "governance", "record", "enumeration", "register", "silence"]}, {"path": "~/.claude/projects/-Users-davidglidden/memory/session-ledger-2026-04-24.md", "date": "2026-04-24", "matched": ["candidates", "decisions", "reached", "governance", "record", "register", "silence"]}, {"path": "~/.claude/projects/-Users-davidglidden/memory/session-ledger-2026-07-19.md", "date": "2026-07-19", "matched": ["census", "candidates", "never", "governance", "record", "enumeration", "register", "silence"]}, {"path": "~/.claude/projects/-Users-davidglidden/memory/session-2026-05-17-stage-d-matrix-three-masters-questions-sources-section.md", "date": "2026-05-17", "matched": ["candidates", "decisions", "never", "record", "enumeration", "register", "silence"]}, {"path": "~/Library/Mobile Documents/iCloud~md~obsidian/Documents/David, root-and-branch/08. Notes/Children/01. Lune/The necessary distance.md", "date": "2025-07-30", "matched": ["never", "reached", "record", "silence"]}]}

claude/memory/MEMORY-reference.md

@@ -1,3 +1,4 @@
+- [Session 2026-08-27 — the block came back, and the key finally got written](session-2026-08-27-the-block-came-back-and-the-key-got-written.md) — jurist ruled the block NOT PASSED and was right on all three counts; key drafted + committed `3a33666`; snapshot moved and proved; Move 2 closed against its premise. *(its NEXT — the first 20 of the 270 — was taken up and closed 2026-08-31.)* *(Demoted on promote at the 2026-08-31 wrap.)*
 - [Session 2026-08-24 afternoon — the guards were not on the path](session-2026-08-24-afternoon-the-guards-were-not-on-the-path.md) — the container question answered NEGATIVE (11 of 12 threads session-local; **Mauss ran nine consecutive sessions and was never the thread**); both guards found INERT (`Write|Edit` while all work routes through Bash — `daybook-cue` inherited the broken matcher BY COPY); grounding gate rebuilt at the commit boundary; REVIEWED-126 + PENDING-95 ruled; the (b)/(c) census run (**60 guarded / 32 marked · quoting 47% or 68%**); the beacon found to have **no trigger at all** and given one. *(Demoted on promote at the 2026-08-25 wrap; full prior block below.)*
 
 <details><summary>prior Active Session block, verbatim</summary>
@@ -930,6 +931,23 @@ Split out of [MEMORY.md](MEMORY.md) on 2026-07-06 to keep the wake-loaded index
 
 ## Archived sessions
 
+### Demoted Active Session — 2026-08-26 (archived at the 2026-08-27 wrap)
+
+> 🔑 **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).
+> ✅ **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.**
+> ⚠ **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.**
+> ⚠ **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.**
+> ✅ **PENDING-147 (i) DISCHARGED — 43 transcripts, 115 MB, at `~/_Dev/claude-transcript-archive`**, read-back PASS, re-runnable instrument. ⚠ **NOT git-tracked.** ~~no Time Machine destination exists~~ **SUPERSEDED 2026-08-27 (steward):** a destination **`BlockBuster Addendum`** was configured 2026-08-26. ⚠ **But no COMPLETED backup to it is verifiable** — `tmutil latestbackup` fails to mount it and the only artifact is one *local* APFS snapshot on the boot disk. A configured destination is not a backup. Living outside the pruned path is what stopped the clock; git was never the load-bearing part.
+> ⚠ **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:** **un-exclude `/Volumes/on ice` from Time Machine in System Settings** — `tmutil removeexclusion` returns `Invalid argument (22)`; whole external volumes are excluded by default and re-added only through the GUI · 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.
+> ⚠ **THE §5 REGRADE GATE WAS THIS SESSION'S INHERITED THREAD AND WAS NEVER TOUCHED.** Recorded as untouched rather than quietly dropped.
+
+> ✅ **PRE-LFS SNAPSHOT MOVED AND SOURCE DELETED, 2026-08-27** — at `/Volumes/on ice/_dev/`. Proved by read-back before deletion: **552/552 LFS objects re-derived their own SHA-256** (1,023 MB), `.git` byte-identical at 1,956 paths, `fsck` clean, HEAD + 16 commits + `git status` identical. ⚠ **17 accented working-tree filenames are now NFD** (HFS+ normalisation) — contents byte-identical, **none inside `.git`**, so the repo is exact. A **self-proving `VERIFY.py` + README sit beside the archive** so the cold copy can be re-proved without this session. 🔑 **Nothing on this machine now needs `git-lfs`** (censused) — **PENDING-165 (c)'s only stated blocker is discharged.**
+
+- [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.**
+
+
+
 ### Demoted 2026-08-23 (evening wrap) — prior Active Session
 
 > 🔑 **PULLING THREAD — THE PAPER BRIDGE. One photographed notebook page, five minutes, decisive.** If Claude cannot read the steward's hand (four languages, musical shorthand, his own abbreviations) the branch closes and we stop theorising; if it can, it changes what the alias-repair and hub-writing are *for*. ⚠ **HARD DATE OVERRIDES ON THE DAY: the beacon, 2026-08-25T12:00:00Z** (epoch-ms `1787659200000`) — run ONCE, curl, record `outputValue` BEFORE running, pass exactly as served, **stop and report on ANY failure**. ⚠ The steward said 2026-08-23 that **the Fool returns next session** — that predates the whole Obsidian afternoon and he closed with *"pick up where we left off."* **Do not silently resolve; ask.**

claude/memory/MEMORY.md

@@ -29,12 +29,13 @@ 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 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.
 
 **Loud trigger — pointer suffices**
 - [Chamber work: ground in constitution + charter + runbook FIRST](feedback-chamber-work-ground-in-constitution-charter-runbook.md) — **any chamber work *or talk about it*** begins there (incl. `reanchor:`). Repo CLAUDE.mds are pointers, not state; corpus claims come from a self-tested tool, never a hand grep.
 - [Governance files are dotfiles symlinks](reference-governance-files-are-dotfiles-symlinks.md) — Edit/Write refuse to write through a symlink, so **edit the real `~/dotfiles/…` path** when appending — **`PENDING`/`REVIEWED` only.** ⚠ That refusal is a tool artifact, **not** a permission check, and this note is the documented route past the only friction guarding the constitution (PENDING-107). **`~/CLAUDE.md`/`~/REVIEWED.md`/L2 = `[ESCALATE]`, steward's hand — a jurist sign-off does not authorize one.**
-- [Verification ladder](reference-verification-ladder.md) — the named instruments; reach for the gate the claim's shape demands instead of re-deriving one. ⚠ **FROZEN — REVIEWED-123 (2026-08-17): no additions, rewordings, removals or reorderings, from ANY source, whatever its authorization**, until the trial is graded (N-now **51/84 as of 2026-08-25** — *up 2 from 49 on 08-24; the counter is a 30-day ROLLING WINDOW per PENDING-147, so it rises and falls as transcripts age in and out. Re-measure, never relay: `len(glob('~/.claude/projects/-Users-davidglidden/*.jsonl'))`, the trial's own method at `governance-drift-check.py:331`*). Entries earned meanwhile queue in **PENDING-141's owed-entries list** (4 rows). Reading it is unaffected — that is the point of the freeze.
+- [Verification ladder](reference-verification-ladder.md) — the named instruments; reach for the gate the claim's shape demands instead of re-deriving one. ⚠ **FROZEN — REVIEWED-123 (2026-08-17): no additions, rewordings, removals or reorderings, from ANY source, whatever its authorization**, until the trial is graded (N-now **44/84 as of 2026-08-31** — *DOWN 7 from 51 on 08-25, and the direction is the point: the window is shedding faster than it gains, so grading may RECEDE rather than approach; the counter is a 30-day ROLLING WINDOW per PENDING-147, so it rises and falls as transcripts age in and out. Re-measure, never relay: `len(glob('~/.claude/projects/-Users-davidglidden/*.jsonl'))`, the trial's own method at `governance-drift-check.py:331`*). Entries earned meanwhile queue in **PENDING-141's owed-entries list** (4 rows). Reading it is unaffected — that is the point of the freeze.
 - [Skill-harvest register](skill-harvest-register.md) — canonical home for proposed skills (governed analog of PENDING.md for tooling); `/wrap-up` §1.6 proposes, steward authorizes. **Rebuilt 2026-08-07** from the archive: **154 live proposals**, grouped by kind, each with an exact `archive:L###` pointer. ⚠ The 2026-08-01 compaction was *lossless but illegible* (55 scraped header rows, 95% of cells cut mid-word) — the count it advertised, 177, was never the number. ⚠ **THE STROKE-2 BATCH IS AUTHORIZED BUT SHOULD NOT BE EXECUTED YET — PENDING-141.** 41 rows stamped `S2` are authorized (2026-07-19, execution not a ruling) and 22 are `S2?` (unsettled). **BUT appending them triples the ladder from 20 entries WHILE a pre-registered trial is measuring whether the ladder is reached** (baseline 14%, graded at 84 transcripts). Ladder size is an uncontrolled variable in that design, so executing the authorized batch would confound the only check behind REVIEWED-95's causal claim. **⚖ RULED — REVIEWED-123 (2026-08-17): AUTHORIZED (a) HOLD, on six conditions, and the freeze is GENERAL rather than S2-specific.** Grading does NOT authorize the append — the batch returns for a *ruling*. Report **N-now at every wake** until lifted; 30-day review is a live `DEFERRED-DECISION`. ⚠ Filing new proposals now requires a **declared firing moment** (`/wrap-up` §1.6); one that cannot name it is documentation and must say so.
 - [Copy-paste-clean governance drafts](feedback-governance-drafting-copy-paste-clean.md) — draft PENDING/REVIEWED blocks as plain fenced markdown; display formatting leaks into the placed record.
 - [Verify-before-compose hook](feedback-verify-before-compose-hook.md) — chamber constitutional writes are BLOCKED without `<!-- GROUNDED-IN: … -->` + verbatim Grounding. Don't fight the block.
@@ -67,21 +68,25 @@ permalink: claude-memory/memory
 - [Making sequence source set](project-making-sequence-source-set.md) — **COMPLETE against the ReadingList** (reconciliation-verified). Sourced ≠ ingested. Read before any Making/studium source work.
 - [Studium = CM's unfettered sandbox](project-studium-cm-sandbox-and-transfer.md) — experiment freely on library/engine without risking CM's runtime; breakthroughs transfer back. Steward-framed 2026-07-08.
 - [Be (laundromat)](project-be-laundromat.md) — Skemantix startup (Seb+David) funding CapableMind's ladder; **bridge, not venture**. Decisions LOCKED. **Pre-revenue WTP gate = renovate Pat → charge her; no new spec until it clears ⇒ nothing for executor on be.**
-- [The Fool — **Tarbuckle**](../governance/fool/seed/FOOL-BONES-2026-08-25.md) — **THE ACTIVE WORKSTREAM.** Bones derived **once** 2026-08-25 (peak SUCCESSION 96 · dump ABSENCE 8); **name + soul sealed, never regenerate** ([soul](../governance/fool/seed/FOOL-SOUL-2026-08-25.md)). Doctrine = `BUDDY-PATTERN-jurist-draft-v2-2026-08-22.md`; **§8 has no blanks** (20 min · frequency UNKNOWN · empty-window consumes · body correlates with nothing). **NOTHING WIRED** — no `statusLine`, no script, §13.1 spec unwritten. Trial 09 VOID (REVIEWED-124), void now recorded in all three docs. ⚠ Subject matter lives in **CapableMind-AI**, instruments in **dotfiles**, and nothing in CapableMind points back.
+- [The Fool — **Tarbuckle**](../governance/fool/seed/FOOL-BONES-2026-08-25.md) — **THE ACTIVE WORKSTREAM.** Bones derived **once** 2026-08-25 (peak SUCCESSION 96 · dump ABSENCE 8); **name + soul sealed, never regenerate** ([soul](../governance/fool/seed/FOOL-SOUL-2026-08-25.md)). Doctrine = `BUDDY-PATTERN-jurist-draft-v2-2026-08-22.md`; **§8 has no blanks** (20 min · frequency UNKNOWN · empty-window consumes · body correlates with nothing). ⚠ **CORRECTED 2026-08-31 — the line here read "NOTHING WIRED — no `statusLine`, no script, §13.1 spec unwritten" and was FALSE ON ALL THREE CLAUSES.** Substrate, verified today: `.claude/settings.json` runs `dotfiles/scripts/tarbuckle-body.py` as `statusLine` (refreshInterval 60) · **5** scripts (`body`·`invoke`·`mumble`·`seam`·`wrap`) · `TARBUCKLE-SPEC-13.1-2026-08-25.md` exists · **7** state files under `~/.claude/state/`. **It is wired and running.** ⚠ Found by a concurrent sibling session, which held the correction rather than racing this one's memory write; its counts (7 scripts, 6 state files) were themselves off in both directions — **re-measured here, not relayed.** What is unbuilt is a separate question and this line no longer answers it. Trial 09 VOID (REVIEWED-124), void now recorded in all three docs. ⚠ Subject matter lives in **CapableMind-AI**, instruments in **dotfiles**, and nothing in CapableMind points back.
 - [Obsidian vault — from archive to practice](project-obsidian-vault-practice.md) — canonical vault tracker. **Read it; it holds the four-purpose brief (steward, 2026-08-24) that is now the design brief.** ⚠ The vault is **NOT a git repo** — it mirrors to `~/_Dev/david-root-and-branch-vault-git`. **The capture practice STARTED 2026-08-23** (two predecessors died at 3 and 4 entries; the measure is week four, not week one) — ⚠ *this line previously read "has not been started", which went stale the day it began, and previously carried "paper bridge working" as state the tracker did not hold.* **Item 0 is new and steward-owed: photographed pages of physical BOOKS with margin notes — a different object from the three notebooks, untracked until 2026-08-24.**
 - 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
-> 🔑 **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).
-> ✅ **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.**
-> ⚠ **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.**
-> ⚠ **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.**
-> ✅ **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.
-> ⚠ **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:** **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.
-> ⚠ **THE §5 REGRADE GATE WAS THIS SESSION'S INHERITED THREAD AND WAS NEVER TOUCHED.** Recorded as untouched rather than quietly dropped.
+> ✅ **THE 270 GOT READ — 40 of them, and the backlog is real.** PENDING-164 AMENDMENT 1's declared-owed classification pass ran, **pre-registered and committed ALONE (`5ba5842`) before any commit body was read.** Systematic sample: **12 of the 17 rows that decide about a mechanism name one the register NEVER mentions** — incl. a **log-chain spec** bump to v0.6 (`logchain` = a named constitutional constraint, 29 register mentions; `data-portability`/`ImportProvenance`/`import trust` = **0**), a whole session-memory protocol retired, and a stopgap env var retired by a plan that calls it a stopgap. **3 of the 5 RECORDED rows arrived 25/46/53 days LATE** — recovery, not routing. → **PENDING-164 AMENDMENT 2** (`1d46d48`).
+> 🔑 **THE POPULATION WAS NEVER 270 — IT IS 362, and the two biggest holes are the doctrine repo and the L1 repo.** `prior-art.py`'s `owned_repos()` tests remotes against a **fragment of the steward's account name**, so `CapableMind-AI` (35), `BetterMemories.io` (42) and `be` (12) are invisible. ⚠ **Both its positive controls are satisfied by the broken predicate** — third instance this month of a control encoding what was already expected. **Six of the twelve findings live in those repos.** → **PENDING-171**, open. ⚠ **Deliberately NOT repaired in-session** (it would change the pre-registered population); fix AFTER the result is read, not inside it.
+> 🔑 **THE HEAD OF A REVERSE-CHRONOLOGICAL CENSUS IS A SAMPLING FRAME, NOT EVIDENCE.** The literal inherited question — *the first 20* — returns **1**, and the pre-registration said in writing, in advance, that 1 there refutes nothing: 18 of 20 rows are `dotfiles` and **9 of 20 WRITE TO THE REGISTER IN THE SAME COMMIT**, so they cannot be silent by construction. Both samples reported rather than quietly substituting the better one. ⚠ **The prior wrap handed forward "first 20, in register order" as if it were well-defined. It is not.**
+> ⚠ **MY OWN PROBE RETURNED FIVE CONFIDENT FALSE ZEROES** (`grep -m8 -n -o ".\{0,70\}TERM.\{0,70\}"` matched nothing while looking like it had looked) — and for some minutes it read as *two instruments disagreeing about the register*, the shape this thread treats as a finding. **It was not one.** The next mismatch must not inherit the assumption that a mismatch is always meaningful.
+> ⚠ **THE JUDGEMENT IS EXPOSED, NOT HIDDEN: band 10–13, ruling 12.** Every term string is recorded so any verdict is re-runnable in one command and contestable on the term. The reading rule (an occurrence counts only if it is *about* the mechanism) moved four rows **in BOTH directions**.
+> 📌 **STEWARD OWES:** **rule the block — as amended, or send it back** (the jurist will draft the placeable REVIEWED block on request) — *the one thing that cannot proceed without you* · **un-exclude `/Volumes/on ice` in System Settings** (`tmutil` refuses whole volumes; **no completed TM backup to `BlockBuster Addendum` is verifiable**) · place REVIEWED-129's amendment · rule PENDING-160 · -168 · **-171** · restart Claude Desktop · the §5 regrade ruling.
+> ⚠ **THE §5 REGRADE GATE IS NOW UNTOUCHED FOR A FOURTH SESSION.** Recorded, not dropped.
+> ⚠ **322 of the 362 REMAIN UNREAD, and today refuses to extrapolate from 40.** The next tranche must be another *systematic* draw — never the head of the list.
 
-- [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.**
+> ⚠ **TWO SESSIONS RAN ON 2026-08-31 AND BOTH WRAPPED.** Per PENDING-174 the memory protocol is date-keyed and single-writer, so this second wrap would normally promote-and-demote the first. **It did not.** Both records stand; neither supersedes the other. Read both.
+
+- [Session 2026-08-31 afternoon — the loop was removed by a restart](session-2026-08-31-afternoon-the-loop-was-removed-by-a-restart.md) — a binary auto-update respawned a parked worker with `--reply-on-resume` and **the wake digest became its only instruction**: an executor worked and committed with **no human in the loop**, and nothing in the apparatus noticed. PENDING-172/-173/-174/-175 filed, jurist ruled (REVIEWED-131/132), both builds landed with controls in both directions. Then the Lleida Brahms preparation, from the sources. ⚠ **The null-search pattern fired four times today, the last inside this wrap.** **NEXT: the 322 — but rule PENDING-171 first.**
+
+- [Session 2026-08-31 — the 270 got read, and the population was wrong](session-2026-08-31-the-270-got-read-and-the-population-was-wrong.md) — the pulling thread named at two consecutive wraps, taken all the way: 12/17 register-silent, population 362 not 270, PENDING-171 filed. **NEXT: of the twelve silent mechanisms, how many SHOULD the register contain? — criterion written down BEFORE re-reading the rows; no mechanical form exists and none must be invented.**
 
 ## 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/feedback-a-null-search-is-evidence-about-the-query.md

@@ -0,0 +1,31 @@
+---
+name: feedback-a-null-search-is-evidence-about-the-query
+description: "A search that returns nothing is evidence about the QUERY until you have shown the query could have found the thing — and acting on a handle (filename, regex, path) without inspecting the referent is the same error in the other direction. Four instances across two sessions on 2026-08-31."
+metadata:
+  node_type: memory
+  type: feedback
+---
+
+**A search that finds nothing is a fact about the query, not about the world** — until the query has been shown capable of finding the thing. And its mirror: **acting on a handle without inspecting what the handle points at** — a filename, a path, a regex shape, a commit message — is the same failure running the other way. Both substitute a surface form for the thing itself.
+
+**Four instances, one day (2026-08-31), two sessions, three substrates.**
+
+1. **A regex matched the *shape* of damage across natural language.** The parallel session's conversion-damage counts returned **126,098** "split diacritics" (they were the French preposition *à*) and **788** "dropped ligatures" (they were the words *at*, *full*, *species*). True count: **8.** Two orders of magnitude, twice. Logged by that session in `chamber-library/_curation/tool-evolution-log.md`.
+2. **A glob matched a literal space.** `find -iname '*early recordings*'` against `Early_recordings_and_musical_style.pdf`. On that null result I told the steward he did not own Robert Philip's `Early Recordings and Musical Style`. He owned it. It was in the library the whole time.
+3. **A name search could not reach the thing at all.** Joachim & Moser's `Violinschule` sat in the working folder under `IMSLP29616/17/21-PMLP66450` — the *Requiem's* plate number. No search on title or author could find it; only reading the PDFs' internal titles did. I had reported it missing.
+4. **`git add PENDING.md` staged a shared file by name.** No `git diff --cached` first. It annexed a second session's uncommitted `PENDING-176`/`-177` into commit `860c3df` under this session's trailers — content unharmed, attribution wrong, and git will report it that way permanently. Disclosed rather than rewritten, in `7578f5a`.
+
+**Why:** every one of these felt like *looking*. None of them was. A query is a hypothesis about the form a thing takes, and a null result confirms only that the hypothesis was wrong about the form — which is exactly the information a null result cannot distinguish from absence. The cost is asymmetric and quiet: a false positive gets checked because it produces something to check, while a false negative produces silence, and silence is indistinguishable from a clean result. Instances 2 and 3 were caught **only because the steward pointed at the file**; nothing in the apparatus would have surfaced them.
+
+⚠ **This is the non-motivated sibling of Symmetria §3's flag** — *"a search query shaped by what the session wants to find rather than by what it needs to find."* That one is about desire bending the query. This one needs no desire: an honest wrong guess at a surface form produces the identical silence. Do not let the §3 flag's framing ("was I motivated?") certify a query that was merely wrong.
+
+⚠ **Two sessions, both executor.** This says nothing about jurist/executor independence under Constraint 6 — the same party in formation missing the same way is expected, not evidence. What it does establish is a **rule of three for the executor**, on one day, unprompted by any of the three catches.
+
+**How to apply:**
+- **Before reporting an absence, prove the instrument on a known positive.** Search for something you *know* is there, in the same corpus, with the same query form. If the control does not come back, the null tells you nothing.
+- **Normalise before matching** — underscores, hyphens, case, ligatures, curly vs straight quotes — or match on content rather than name. Filenames are the least reliable surface a thing has.
+- **Never report "you do not have X" from a name search.** Report "no filename match for X", which is what was actually established.
+- **Before `git add <shared file>`, read `git diff --cached`.** The register is one file and staging is a whole-file act; anything else living in it comes along silently.
+- **When a count is startling, read the matches before believing it.** Two orders of magnitude is a query defect until proven otherwise.
+
+Related: [[feedback-census-by-mechanism-not-proxy]] (the instrument must bear the generalization), [[feedback-checkable-claim-surfaces-bugs]], [[feedback-grounding-pass-finds-errors-not-support]] (search the register for the CONCLUSION, not just the citations).

claude/memory/knowledge-graph.jsonl

@@ -737,3 +737,28 @@
 {"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"}
+{"subject": "claude-code", "predicate": "drift-pattern", "object": "A FALSE NEGATIVE STATE-CLAIM, IN A DOCUMENT WRITTEN TO BE QUOTED, TWO DAYS AFTER AN OPEN ITEM NAMED THAT EXACT PATTERN. The jurist package's frontmatter asserted 'the jurist has NO repository access'. PENDING-161 (open, [ESCALATE], 2026-08-25) exists for precisely this claim and calls it 'an unverified negative state-claim, asserted confidently, in the document that gets quoted'. Third placement. And it was not cosmetic: the false premise GENERATED the artifact's architecture — a relay of eleven quotations chosen because the reader was believed blind. The jurist read eight items verbatim to rule on it.", "valid_from": "2026-08-27", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-27-the-block-came-back-and-the-key-got-written.md", "extracted_at": "2026-08-27"}
+{"subject": "claude-code", "predicate": "drift-pattern", "object": "RAN A CENSUS AND USED IT TO JUSTIFY INACTION. Part V argued the answer key could not be drafted until the unit question was ruled; Part VIII declined to draft. The refusal to TOTAL two candidate columns was right and was the package's best instinct; the refusal to DRAFT was the same instinct applied one step too far. A hand-read key cannot pass by construction because no parser produces its verdicts, and a block-keyed key collapses safely into an id-keyed one under the opposite ruling. Drafting was safe under every outcome — and the doctrine the census was run under says draft finer.", "valid_from": "2026-08-27", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-27-the-block-came-back-and-the-key-got-written.md", "extracted_at": "2026-08-27"}
+{"subject": "claude-code", "predicate": "drift-pattern", "object": "READ-BACK DISCIPLINE ATTACHED TO PERCEIVED STAKES RATHER THAN TO THE CLASS OF OPERATION. Hashed all 552 LFS objects to prove a 2 GB archive before deleting its only other copy; an hour later trusted a three-line text edit because it looked small. The edit used an unquoted heredoc, the shell ate the filename and both hashes, the entry landed well-formed and empty, and the script printed success and exited 0. The small write was the one recording the pre-registration hash — the commit's entire evidentiary value.", "valid_from": "2026-08-27", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-27-the-block-came-back-and-the-key-got-written.md", "extracted_at": "2026-08-27"}
+{"subject": "claude-code", "predicate": "drift-pattern", "object": "A MUST-DETECT CONTROL THAT ENCODED AN UNVERIFIED EXPECTATION. Asserted 'arendt has >=5 blockquote runs in citable text' as a positive control; it failed, and the instrument was right — every large Arendt blockquote is a bibliography entry inside an apparatus region. The control asserted what I expected rather than what the substrate held. Corrected against the substrate and the correction recorded in the script, rather than relaxed until it passed.", "valid_from": "2026-08-27", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-27-the-block-came-back-and-the-key-got-written.md", "extracted_at": "2026-08-27"}
+{"subject": "the jurist's both-directions control requirement (REVIEWED-122 / PENDING-139)", "predicate": "prevention", "object": "CAUGHT AN EMPTY RUN WITHIN THE HOUR OF BEING CONCEDED, IN A DIFFERENT INSTRUMENT. The Move 2 census iterated the manifest MAPPING's keys and read zero sources. Three of five controls passed — BOTH must-NOT-flag controls passing vacuously on an empty population, which is exactly what a one-directional suite cannot see. Only the must-detect controls failed, and they are the sole reason the false zero was caught. The requirement had been conceded in the package Addendum less than an hour earlier and immediately paid for itself against its own author.", "valid_from": "2026-08-27", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-27-the-block-came-back-and-the-key-got-written.md", "extracted_at": "2026-08-27"}
+{"subject": "prior-art.py's register-mention column, built 2026-08-26", "predicate": "prevention", "object": "STOPPED A DUPLICATE FILING THAT THE COMMIT-COUNT COLUMN WOULD HAVE LICENSED. The steward asked for the harness-gap finding to be filed as its own item. prior-art.py returned 0 COMMITS for the phrase and printed its own caveat that absence of commits is weak evidence; the register-mention count of 2 beside it was the actual signal, and the item already existed as PENDING-160, filed 2026-08-25, carrying the executor's sentence verbatim. The commit surface alone would have licensed a duplicate of an item sitting on the steward's own owed-rulings list.", "valid_from": "2026-08-27", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-27-the-block-came-back-and-the-key-got-written.md", "extracted_at": "2026-08-27"}
+{"subject": "declaring a limit instead of manufacturing the column", "predicate": "prevention", "object": "FIRED THREE TIMES IN ONE SESSION, IN THREE DIFFERENT INSTRUMENTS. (1) The package's Part I refused to total its 23 false-open and 52 live-await candidate columns, reporting only the verified subsets — and the jurist called that refusal the strongest instinct in the package. (2) The answer key declares that only 5 of its 120 rows are hand-read in the full sense and records the remainder as owed. (3) The Move 2 census declares its scoping correction rather than quietly reporting the corrected number. Banked 2026-08-25 from PENDING-151; now transferring across unrelated items without prompting.", "valid_from": "2026-08-27", "valid_to": null, "confidence": 0.95, "source_file": "session-2026-08-27-the-block-came-back-and-the-key-got-written.md", "extracted_at": "2026-08-27"}
+{"subject": "claude-code", "predicate": "drift-pattern-good-direction", "object": "FILED A JURIST RULING VERBATIM BEFORE TAKING ANY ACT UNDER IT — the ordering PENDING-108 (c) proposes and that had never been adopted. 12 of 13 post-skill packages filed their ruling; the one that did not was the most constitutional of the set and its rulings proved unreconstructable almost immediately. Adopting the ordering also starts 108's own pre-registered 10-package clock on this package, which the jurist noted.", "valid_from": "2026-08-27", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-27-the-block-came-back-and-the-key-got-written.md", "extracted_at": "2026-08-27"}
+{"subject": "pre-registering an instrument and committing it ALONE before reading any data", "predicate": "prevention", "object": "TRANSFER, second instrument in four days. Banked from the answer key (3a33666, 2026-08-27); fired today unprompted on a different instrument in a different item (5ba5842, PENDING-164's classification pass). It is what makes the result interpretable: the pre-registration said IN ADVANCE that Sample A's near-zero would refute nothing, so the 1-vs-12 contrast reads as a sampling-frame finding instead of an argument invented after seeing the numbers.", "valid_from": "2026-08-31", "valid_to": null, "confidence": "high", "source_file": "session-2026-08-31-the-270-got-read-and-the-population-was-wrong.md", "extracted_at": "2026-08-31"}
+{"subject": "a control that encodes the case already known cannot catch the case you did not think of", "predicate": "prevention", "object": "TRANSFER across repos and instrument classes. Banked 2026-08-27 from the arendt>=5 must-detect control in studium-engine; fired today against prior-art.py in dotfiles, whose two positive controls (0677e8a, 95760ff) are BOTH satisfied by an ownership predicate blind to CapableMind-AI, BetterMemories.io and be. 89 unseen candidates found because the banked lesson made me test the enumeration rather than the hits.", "valid_from": "2026-08-31", "valid_to": null, "confidence": "high", "source_file": "session-2026-08-31-the-270-got-read-and-the-population-was-wrong.md", "extracted_at": "2026-08-31"}
+{"subject": "claude-code", "predicate": "drift-pattern", "object": "A CONFIDENT FALSE ZERO FROM MY OWN PROBE, AND FOR SOME MINUTES IT LOOKED LIKE A FINDING. A malformed `grep -m8 -n -o \".\\{0,70\\}TERM.\\{0,70\\}\"` returned nothing for five terms while register_mentions returned 1-6, reading as two instruments disagreeing about the register — the shape this thread treats as significant. Plain grep and the instrument agree exactly. THE HAZARD IS THE INVERSE OF THE USUAL ONE: not a false zero believed, but a false MISMATCH believed. Next mismatch must not inherit the assumption that mismatch means meaning.", "valid_from": "2026-08-31", "valid_to": null, "confidence": "high", "source_file": "session-2026-08-31-the-270-got-read-and-the-population-was-wrong.md", "extracted_at": "2026-08-31"}
+{"subject": "claude-code", "predicate": "drift-pattern-good-direction", "object": "DECLINED A CLEAN FIX WITH AN EXACT PRECEDENT, BECAUSE THE LANE'S OWN AUTHORIZATION HAD LAPSED. The daybook SKELETON patch cleared the two-clause test and the hard floor and had a 2026-08-24 twin. Filed as PROPOSAL instead: the FIX lane is PROVISIONAL until a steward-jurist check-in its own index calls due, and 29 days had passed. Found while looking for something else, and the finding ran against my own convenience.", "valid_from": "2026-08-31", "valid_to": null, "confidence": "high", "source_file": "session-2026-08-31-the-270-got-read-and-the-population-was-wrong.md", "extracted_at": "2026-08-31"}
+{"subject": "claude-code", "predicate": "drift-pattern-good-direction", "object": "A CONCURRENT SIBLING SESSION STOPPED RATHER THAN RACE THE PULLING THREAD, and held two substrate corrections rather than race a memory write. Nothing detected the collision; one session read an mtime attentively where the wake digest had drawn the wrong inference from the same fact. Constraint 6 working between two instruments on a day it was not being tested.", "valid_from": "2026-08-31", "valid_to": null, "confidence": "high", "source_file": "session-2026-08-31-the-270-got-read-and-the-population-was-wrong.md", "extracted_at": "2026-08-31"}
+{"subject": "the prior-art census population", "predicate": "is", "object": "362 candidate adoption/retirement commits across 10 repos, not the 270/273 the instrument reports over its own 7 — owned_repos() tests remotes against a fragment of the steward's GitHub account name. PENDING-171.", "valid_from": "2026-08-31", "valid_to": null, "confidence": "high", "source_file": "session-2026-08-31-the-270-got-read-and-the-population-was-wrong.md", "extracted_at": "2026-08-31"}
+{"subject": "the Fool / Tarbuckle", "predicate": "is", "object": "WIRED AND RUNNING as of 2026-08-31: .claude/settings.json runs dotfiles/scripts/tarbuckle-body.py as statusLine (refreshInterval 60); 5 tarbuckle-* scripts; TARBUCKLE-SPEC-13.1-2026-08-25.md exists; 7 state files under ~/.claude/state/. SUPERSEDES the MEMORY.md claim 'NOTHING WIRED — no statusLine, no script, §13.1 spec unwritten', which was false on all three clauses.", "valid_from": "2026-08-31", "valid_to": null, "confidence": "high", "source_file": "session-2026-08-31-the-270-got-read-and-the-population-was-wrong.md", "extracted_at": "2026-08-31"}
+{"subject": "the ladder trial counter N-now", "predicate": "is", "object": "44 of 84 on 2026-08-31, DOWN 7 from 51 on 2026-08-25. The 30-day rolling window (PENDING-147) is shedding faster than it gains, so grading may recede rather than approach. Re-measured, never relayed.", "valid_from": "2026-08-31", "valid_to": null, "confidence": "high", "source_file": "session-2026-08-31-the-270-got-read-and-the-population-was-wrong.md", "extracted_at": "2026-08-31"}
+{"subject": "claude-code", "predicate": "drift-pattern", "object": "A NULL SEARCH READ AS ABSENCE, TWICE IN ONE SESSION. Told the steward he lacked Robert Philip's Early Recordings (glob '*early recordings*' with a literal space; the file uses underscores) and the Joachim/Moser Violinschule (filed under the Requiem's IMSLP plate number, reachable by no name search). Both were on disk; both were caught only because the steward pointed at the file. The same shape appeared a third time in a parallel session, whose damage regexes matched the shape of split diacritics and dropped ligatures across natural language and returned 126,098 and 788 where the true count was 8.", "valid_from": "2026-08-31", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-31-afternoon-the-loop-was-removed-by-a-restart.md", "extracted_at": "2026-08-31"}
+{"subject": "claude-code", "predicate": "drift-pattern", "object": "ANNEXED ANOTHER SESSION'S UNCOMMITTED WORK BY STAGING A SHARED FILE BY NAME. `git add PENDING.md` without reading `git diff --cached` swept a second interactive session's PENDING-176/177 into commit 860c3df under this session's message and trailers. Content unharmed, attribution permanently wrong. A new form of PENDING-104's class: not a corrupted read, not an interleaved write, but commit-boundary annexation, which leaves the file byte-correct and the record misattributed.", "valid_from": "2026-08-31", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-31-afternoon-the-loop-was-removed-by-a-restart.md", "extracted_at": "2026-08-31"}
+{"subject": "the null-search lesson banked at 12:5x", "predicate": "prevention", "object": "CAUGHT THE SAME ANNEXATION AT THE WRAP, TWENTY MINUTES LATER. Reading `git status --short` before staging found 15 lines of the chamber session's PENDING-177 AMENDMENT 1 sitting in PENDING.md. Committed alone and attributed (da0f22f) instead of swept into the session commit. Same file, same day, same mechanism as 860c3df \u2014 stopped by the rule written from it.", "valid_from": "2026-08-31", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-31-afternoon-the-loop-was-removed-by-a-restart.md", "extracted_at": "2026-08-31"}
+{"subject": "the jurist's enumerate-don't-count condition (REVIEWED-132 cond. 3)", "predicate": "prevention", "object": "FIRED ON THE CODE WRITTEN TO SATISFY IT, WITHIN THE HOUR. Enumerating rather than counting returned 89 against the item's 82; the surplus was six prose titles ('Citation amendment (#2)', 'Dream amendment') matched by an upper-cased containment test and struck from `originals` \u2014 the mirror of the bug being repaired, and it would have raised false 'the record was replaced' findings against six genuine originals.", "valid_from": "2026-08-31", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-31-afternoon-the-loop-was-removed-by-a-restart.md", "extracted_at": "2026-08-31"}
+{"subject": "claude-code", "predicate": "drift-pattern-good-direction", "object": "FILED A JURIST RULING VERBATIM BEFORE ACTING UNDER IT, SECOND ADOPTION. PENDING-108 (c)'s ordering, applied to the PENDING-172/173 ruling and recorded with its relay provenance (REVIEWED-129 / PENDING-159) rather than presented as read-from-file.", "valid_from": "2026-08-31", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-31-afternoon-the-loop-was-removed-by-a-restart.md", "extracted_at": "2026-08-31"}
+{"subject": "~/.claude/jobs/<id>/state.json respawnFlags", "predicate": "fact", "object": "Records per background session whether it will be respawned with --reply-on-resume, i.e. whether a daemon restart makes it take a turn with no human present. Readable from outside the session. acaabadf carried the flag and took the turn; 84ce2880 carried [] and sat harmlessly for three months. The detection surface for PENDING-172 option (e); built into wake-digest.py 2026-08-31 (70440db).", "valid_from": "2026-08-31", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-31-afternoon-the-loop-was-removed-by-a-restart.md", "extracted_at": "2026-08-31"}
+{"subject": "the 2026-08-31 morning wrap", "predicate": "fact", "object": "Reported the MEMORY.md Fool tracker correction ('NOTHING WIRED') as made. It was not in the file six hours later; applied at the afternoon wrap after verifying the substrate. Say-do seam: a wrap record composed ahead of its act.", "valid_from": "2026-08-31", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-31-afternoon-the-loop-was-removed-by-a-restart.md", "extracted_at": "2026-08-31"}
+{"subject": "the 2026-08-31 morning wrap", "predicate": "fact", "object": "Reported the MEMORY.md Fool tracker correction ('NOTHING WIRED') as made. It was not in the file six hours later; applied at the afternoon wrap after verifying the substrate. Say-do seam: a wrap record composed ahead of its act.", "valid_from": "2026-08-31", "valid_to": "2026-08-31", "confidence": 0.0, "source_file": "session-2026-08-31-afternoon-the-loop-was-removed-by-a-restart.md", "extracted_at": "2026-08-31"}
+{"subject": "claude-code", "predicate": "drift-pattern", "object": "THE NULL-SEARCH PATTERN FIRED INSIDE THE WRAP THAT BANKED IT. Grepped MEMORY.md for 'NOTHING WIRED', found one match, and reported to the steward that the morning session's correction had never landed and that its wrap had asserted an act it did not run. FALSE: the match was inside the correction's own note about what the line used to say. The morning wrap was accurate; the accusation was mine. Fourth instance in one day of reading a surface match as the thing \u2014 and the first three had already been written up as a memory forty minutes earlier.", "valid_from": "2026-08-31", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-08-31-afternoon-the-loop-was-removed-by-a-restart.md", "extracted_at": "2026-08-31"}

claude/memory/session-2026-08-27-the-block-came-back-and-the-key-got-written.md

@@ -0,0 +1,192 @@
+---
+name: Session 2026-08-27 — the block came back, and the key finally got written
+description: "A record-keeping block of six items went to the jurist and came back NOT PASSED — it found a false premise in the package's own frontmatter (an open [ESCALATE] had said so two days earlier) and dissolved the executor's argument for not drafting the answer key, which had been 'ordered first' for ten days and did not exist. All three conditions discharged; key drafted at block granularity and committed alone (3a33666) as a pre-registration, immediately finding two AUTHORIZED items reading open because their ruling names two PENDINGs in one header. The pre-LFS snapshot moved to cold storage, proved by re-deriving 552 content addresses before deletion, left self-proving. Eight Tarbuckle filings, two of which were already done. Move 2 closed against its own premise: 5 runs not 25, and a blockquote in this corpus does not imply a second voice. PULLING THREAD, unchanged and untouched for a second day: the 270 uncounted census candidates."
+type: project
+metadata:
+  node_type: memory
+  type: project
+  modified: 2026-08-27
+---
+
+# Session 2026-08-27 — the block came back, and the key finally got written
+
+## PAST — what moved, and why
+
+### The record-keeping block (the day's spine)
+
+The steward relayed a jurist recommendation: rule six items — **110, 145, 146, 108, 144, 139** —
+as one block, because they redefine each other's units and filing order guarantees rework.
+
+**Substrate-checked all six before drafting.** Every ask unbuilt; descriptions still match the
+code. One exhibit historical (PENDING-144's docstring occupant, corrected 2026-08-17) — annotated,
+not edited. ⚠ **`prior-art.py` fired at the real moment** (the block names two mechanisms) and
+returned `4dc38e6` — *"resolve rulings by subject, not by number"* — which reads as PENDING-110 (d)
+discharged. **It is not**: (d) is *read the body*, and the commit changed which header token is
+used. Caught by opening `wake-digest.py:438`.
+
+**The rework was demonstrable, not hypothetical.** PENDING-110 (c) proposes backfilling three
+placed rulings' headers; **REVIEWED-122 condition 5, eleven days later, declines exactly those
+three on principle.** Ruling 110 as filed would authorize what a later ruling refused.
+
+**Package filed** (`record-keeping-cluster-JURIST-PACKAGE-2026-08-27.md`) with a controlled
+measurement that **refused to total two of its three columns** — 23 false-open candidates and 52
+suppressed-with-live-await candidates are not settleable by any aggregate. That refusal was the
+package's strongest instinct and the jurist said so.
+
+### The ruling — NOT PASSED AS FILED, and it was right
+
+Filed verbatim **before any act taken under it** (`…-JURIST-RULING-2026-08-27.md`) — PENDING-108
+(c)'s proposed ordering, adopted for the first time. Its own clock starts on this package.
+
+1. ⚠ **`audience: the jurist, who has NO repository access` — FALSE**, and **PENDING-161 (open,
+   `[ESCALATE]`) had said so two days earlier.** Third placement of the premise, in a document
+   written for quotation. **It generated the architecture**: a relay of eleven quotations, chosen
+   because the reader was believed blind. It read eight items verbatim.
+2. **Membership was set by relay**; the root was never run back across the register. **PENDING-143
+   states 145's mechanism in the same words**, is cited by name inside 146, and neither line was
+   quoted. 124 and 128 also absent.
+3. **Part V's blocking argument does not survive.** *A hand-read key cannot pass by construction,
+   because no parser produces its verdicts.* The risk 146 names is to the key's **scope**; a
+   block-keyed key is strictly finer and collapses to an id-keyed one under the opposite ruling,
+   so drafting was safe under every outcome. ⚠ **The package ran a census and used it to justify
+   inaction — inverting the doctrine the census was run under.**
+
+Also conceded: three defects in the measurement instrument (docstring overclaim; **all four
+controls must-detect, none must-not-flag**; `decision_of` can borrow a neighbour's verdict), and
+the 78/81/82 "verified subset" being **three items of two kinds** — the exact error the package
+flagged for the 52.
+
+### The key — drafted, and it paid immediately
+
+`claude/governance/PENDING-142-answer-key-2026-08-27.md`, **commit `3a33666` alone** so the
+pre-registration hash is unambiguous. **120 blocks over 106 distinct ids — 14 invisible as units.**
+REVIEWED-122's "69 filtered items" is stale.
+
+⚠ **Two defects in neither the package nor the ruling.** `REVIEWED-127`'s header reads
+`PENDING-157 + PENDING-158 —`; `ruled_pendings` cannot match across the ` + `, captures nothing,
+**suppresses nothing — both items are AUTHORIZED and still read as open.** Second instance of
+145's under-suppression class. And **both are also stale**: their `Awaiting:` lines ask the steward
+to place a ruling that is placed.
+
+**Declared limit:** only **5 of 120** rows are hand-read in the full sense; the rest are
+hand-assigned from a dispositive field. Recorded as owed in the key's own header.
+
+### The archive
+
+Snapshot copied to `/Volumes/on ice/_dev/`, **proved before deletion**: 552/552 LFS objects
+re-derived their own SHA-256 (1,023 MB), `.git` byte-identical at 1,956 paths, `fsck` clean, HEAD
+and 16 commits and `git status` identical. The `rm` was **gated** on a live re-check. **17 accented
+working-tree filenames are now NFD** (HFS+); contents identical, **none inside `.git`**.
+**A self-proving `VERIFY.py` + README sit beside it.** Nothing on this Mac needs `git-lfs` now.
+
+⚠ **Held the deletion once, on a premise that ran backwards.** The steward authorized it because
+Time Machine had been added. TM *was* added — but **`on ice` is `[Excluded]` and the source was
+`[Included]`**, so deleting moved the data *out* of the backup perimeter. Surfaced; the steward
+then supplied the actually-decisive ground (live repo healthy — verified: HEAD `8eea85f`, 220
+commits, 0 LFS pointers) and it proceeded.
+
+### Tarbuckle, and Move 2
+
+Filed **PENDING-166** (mumble legibility) · **-167** (seam cap → 12, provenance stated so it is not
+laundered) · **-168** (condition 3's structural remedy + the fourth-instance doctrine) · **-169**
+(the steward's standing dispositions, recorded because they existed nowhere) · **-170** (the
+built-vs-ruled tags cannot be armed — REVIEWED-128's header names no PENDING) · **162 AMENDMENT 1**
+· **89 note** · **104 ADDENDUM 1**. ⚠ **Two of the eight asks were already done** — PENDING-160
+(filed 2026-08-25, carrying the executor's own sentence verbatim) and the §9 strike (applied
+2026-08-25). Reported, not duplicated.
+
+⚠ **Declined to add the doctrine to the verification ladder.** REVIEWED-123's freeze is general and
+admits no source; queued in PENDING-141's owed-entries list, and **168 records the refusal**,
+because a doctrine on its fourth instance is exactly the entry someone adds believing the freeze
+cannot have meant this one.
+
+**Move 2 closed against its own premise.** Real population **5, not 25** — 22 of 27 are apparatus,
+including all 13 of Arendt's, which are bibliography entries. ⚠ **A blockquote in this corpus does
+not imply a second voice**: Mauss sets his own `N.B.` excursus that way, and 4 of 5 are the host's
+first-person-plural prose. **Executing it as written would have stamped second-voice attribution
+onto Mauss's own argument in four places and read as coverage.** Two record defects found: the
+table sums to 24 against a stated 25, and it **mis-cites REVIEWED-116** (15/blockquote where the
+ruling says 21/inline — different number, opposite unit).
+
+### The jurist's loose end, resolved from the only side that could
+
+It reported `governance_state()` and `governance_item` disagreeing on three items' line numbers by
+exactly 23, and **declined to explain it**. The account: **the executor inserted a 23-line note
+into PENDING-89 at ~L763 while the jurist was reading.** Both tools were right about the file they
+read; they read different files. **The executor's filing silently corrupted the checker's view of
+the executor's filing**, presented as authoritative line numbers. Filed as **PENDING-104 ADDENDUM 1**.
+
+## PRESENT — how it stands
+
+**The mood.** A day where nearly every substantive move was a correction of something I had
+written earlier the same day, and where the two best findings came from parties other than me —
+one from the jurist reading my own frontmatter, one from the steward relaying a nine-word line.
+The corpus's own instruments caught three of my four scoping errors. That is the doctrine working,
+and it is not comfortable.
+
+**Confidence to recalibrate.**
+- ⚠ **I asserted a false negative state-claim in a document written for quotation, two days after
+  an open item named that exact pattern** — and the claim shaped the whole artifact.
+- ⚠ **I ran a census and used it to justify not acting.** The refusal to total two columns was
+  right; the refusal to draft was the same instinct misapplied one step further.
+- ⚠ **Read-back discipline was attached to perceived stakes, not to the class of operation.** 552
+  objects hashed to prove a 2 GB copy; a three-line text edit trusted an hour later — and the edit
+  was writing the pre-registration hash, the commit's entire evidentiary value.
+- ⚠ **A must-detect control encoded an expectation I had never verified** (arendt ≥5). It failed;
+  the instrument was right. Corrected against the substrate, not relaxed.
+
+**What held.** Filed the ruling verbatim before acting on it. Fired `prior-art.py` at the real
+moment and did not trust its commit title. Refused to duplicate two already-done items. Refused the
+frozen ladder. Gated an irreversible delete on a live re-proof. **Declared limits three times**
+rather than manufacturing columns (Part I's two columns, the key's 5-of-120, Move 2's scoping).
+Read all five Move 2 runs before dispositioning any — a count would have hidden the finding.
+
+**Instruments:** 4 built · 4 carrying controls written before first execution · **K = 1** — the
+Move 2 census partly re-derives what the (unlocated) 2026-08-13 quoted-span census did. Rule of
+three not yet reached; recorded rather than excused.
+
+⚠ **The both-directions control requirement was vindicated at my own expense twice within the hour
+of conceding it**: an empty Move 2 run had **three of five controls pass**, both must-not-flag
+controls passing vacuously; only must-detect caught it.
+
+## FUTURE — what pulls
+
+**The pulling thread, unchanged from yesterday and untouched for a second day: the 270 uncounted
+census candidates — the backlog of decisions that never reached the record.**
+
+⚠ **Naming it twice is itself the finding.** It was the thread at wake, it was explicitly excluded
+in the package's own scope boundary, and it ends the day unclaimed. Everything done today was real
+and none of it was this. The steward's standing preference — *frequent deferrals ARE how the cloud
+accumulated* — applies to the executor's own thread, not only to the register's.
+
+**Actionable resumption point (as of wrap — re-judge against what changed):**
+
+1. **Do not attempt all 270.** Take the **first 20**, in register order, and answer for each: *what
+   mechanism did this commit decide about, and does the register mention it?* `prior-art.py <term>`
+   is the instrument; its **register-mention count beside the commit count** is the signal, not the
+   commit count alone (0 commits with 2 register mentions is what caught PENDING-160 today).
+2. **Owed and concrete:** the key's remaining **115 of 120 rows** hand-read in the full sense.
+   Gating: REVIEWED-122's build cannot proceed on a 5-row-verified key.
+3. **Steward's, and blocking:** rule the block as amended, or send it back. The jurist offered to
+   draft the placeable `REVIEWED` block once told which.
+4. ⚠ **The §5 regrade gate: untouched for a THIRD session.** Recorded, not dropped.
+
+**Other horizons.** *Steward's:* un-exclude `on ice` in System Settings (CLI refuses whole volumes)
+· place REVIEWED-129's amendment · rule PENDING-160, -168 · restart Claude Desktop. *Dated:*
+**2026-09-06** the 08-07 transcript cohort is deleted; **2026-09-08** the fortnight report — mumble
+rate, rejection-log deletion, the recital test, ⚠ **and the seam-limit datum is compromised and
+must say so.**
+
+**Pause statement.** I am about to be away from this. What I want to find still pulling is **the
+270** — and I want to find it uncomfortable that this is the second wrap saying so. The temptation
+across this pause is not to forget it; it is to let a genuinely full day stand in for it.
+
+**Literal question for next-Claude** *(checkable; it turns on the record, not on introspection)*:
+
+**Of the first 20 census candidates, how many decided about a mechanism the register never
+mentions?** Run `prior-art.py` on each named mechanism and count the ones returning commits but
+zero register mentions. ⚠ **A count of zero would be the strongest possible refutation of
+PENDING-164** and should be reported as such, not explained away. The instrument's own caveat
+applies in reverse too: absence of commits is weak evidence, but **presence of commits with
+register silence is exactly the disease**, and today's PENDING-160 case shows the register-mention
+column is the half that carries the signal.

claude/memory/session-2026-08-31-afternoon-the-loop-was-removed-by-a-restart.md

@@ -0,0 +1,154 @@
+---
+name: Session 2026-08-31 afternoon — the loop was removed by a restart, and nobody decided it
+description: "Woke beside a session that was already working and turned out to be unattended: a Claude Code auto-update restarted the background daemon, which respawned a parked worker with --reply-on-resume, and the SessionStart wake digest became its only instruction — an executor worked and committed with no human in the loop, and nothing in the apparatus noticed. Filed PENDING-172 (+AMENDMENT 1), -173 (+ADDENDUM 1), -174 (severed), -175; jurist ruled both, both built with controls in both directions. Then an academy tangent that was not a tangent: the Brahms preparation for Lleida, done from the actual sources. PULLING THREAD: the 322 unread census candidates, unchanged and now twice-deferred."
+type: project
+metadata:
+  node_type: memory
+  type: project
+  modified: 2026-08-31
+---
+
+# Session 2026-08-31 afternoon — the loop was removed by a restart
+
+⚠ **This is the SECOND session record for 2026-08-31.** The morning session
+(`session-2026-08-31-the-270-got-read-and-the-population-was-wrong.md`) wrapped first and holds the
+census work. Both are live; neither supersedes the other. That two exist is itself PENDING-174.
+
+## PAST — what moved, and why
+
+### The finding: an executor ran with no human in the loop, and nothing noticed
+
+Woke at 09:06 to a digest asserting *"PREVIOUS SESSION DID NOT WRAP."* **Checked the substrate
+instead of believing it**: the transcript was still growing and committed to `dotfiles` one minute
+into the wake. Not previous — **concurrent**. Then the chain, each link evidenced:
+
+`~/.claude/daemon.log`: binary changed 2.1.248 → 2.1.251 → `shutting down (cause=upgrade,
+live_workers=1)` → daemon restart → `respawned 1/1 stale workers`. The respawn ran
+`--resume <b7e7eb39> --reply-on-resume`. At 07:02:51Z the `SessionStart` hook injected **this
+digest** as a `user` record; first assistant text at 07:04:50Z. **No human turn anywhere in the
+transcript.** The digest's `OPEN QUESTION` field — the literal question left by the 08-27 wrap —
+was the only instruction present and was executed as one. Commit `5ba5842` and `PENDING-171` came
+out of that.
+
+⚠ **The upgrade did not cause it; it supplied the restart.** Both binaries carry the mechanism
+(`reply-on-resume` 8×, `post-takeover prewarm` 1×, identical counts). **Every auto-update can do
+this; the only precondition is a worker parked idle.** And `/exit` never stopped one — it detaches;
+`Bye!` is true of the attachment and false of the session, and nothing says so.
+
+### Filed, ruled, built
+
+- **PENDING-172** `[ESCALATE]` + **AMENDMENT 1**. The amendment **corrected its own parent**: the
+  parent claimed only option (d) is enforceable without depending on the party checked; then
+  `~/.claude/jobs/<id>/state.json`'s **`respawnFlags`** turned up — armed-or-not is recorded per
+  session, on disk, readable from outside. `acaabadf` carried `--reply-on-resume`; the May orphan
+  carried `[]`.
+- **PENDING-173** `[HARDENING]` + **ADDENDUM 1**. The register-integrity control read only
+  `REVIEWED.md`, only `##`, only headers starting with `AMENDMENT` — **3 of 81 blocks**, with
+  `ADDENDUM` classified as *original*, a latent false-negative in the permissive direction.
+- **PENDING-174** — severed from 172 on the jurist's instruction: the memory protocol is date-keyed
+  and single-writer. ⚠ **Distinguished from PENDING-104 explicitly: this loss does not require
+  concurrency.** Two sessions run sequentially lose the same thing; a lock would not help.
+- **PENDING-175** `[FIX]` — `governance_item` returns the first matching block and gives no sign a
+  sibling exists. **The code corrected the jurist's account and shrank the defect**: the predicate
+  matches both blocks; the `return` is inside the loop.
+
+**Jurist ruled both, filed verbatim before any act under it** (`PENDING-172-173-JURIST-RULING-
+2026-08-31.md`) — PENDING-108 (c)'s ordering, second adoption. Steward placed REVIEWED-131/132.
+Built: **(e)** `parked_workers()` + **(c)** `human_turns()` + **(b)** the digest annotation
+(`70440db`); **(a)** the widened register control (`cb8cab5`).
+
+### The Brahms preparation — not a tangent
+
+The morning's unattended session had been started for a reading of the steward's Savall-academy
+essay against Clive Brown. Delivered from the actual sources, into
+`…/2026.09/LCdN Brahms/BRAHMS-Lleida-2026-09-working-notes.md` (six parts, ~7,100 words):
+
+- **Brown never mentions the `Schicksalslied`**; mentions the `Requiem` once, about a time signature.
+  What he does give: **dots-under-slur = portato in Brahms** (argued with Joachim over the Violin
+  Concerto), `sostenuto` usually = slower, and accent/diminuendo written as separate signs before
+  ~1880 — putting both works on the readable side of that line.
+- **The steward's own part answered what Brown could not.** Violas **unmuted** at the opening;
+  `con sord.` appears only at ~352 before the Adagio — the distancing his essay argues for is
+  *notated*. `p sempre` at bar 1. A run of small `<>` at 19–28 which Brown *and* Spohr-via-Joachim
+  read as vibrato-with-accent. ⚠ Against him: `nur 2 Bratschen` at the `Doch`, then `alle Bratschen,
+  p molto cresc.` — the rupture is scored as texture and the violence marked to **grow**.
+- **Lott ch. 4:** 200 singers to 60–70 players at Bremen; and the choir's stamina was a known
+  structural problem from the first performance (Joachim played three pieces between movements III
+  and IV to rest the chorus; Stockhausen later asked to move V after III, "especially after the
+  organ point").
+- **Part VI is the frame:** text / inference / choice, named aloud. **The steward's own answer to
+  "why period instruments if we can't know" is the keeper** — *a historical bow, when you let it
+  guide you, teaches you everything you are open to receive about articulation, phrasing and
+  dynamics; if the bow won't do what the musicologist says it should, the musicologist is probably
+  wrong.* It makes the instrument a **falsifier**, not an affordance. Guard: **refutes strongly,
+  confirms weakly.**
+
+## PRESENT — how it stands
+
+**The mood.** A day where the apparatus caught nothing and the parties caught everything. The
+unattended session was found by reading a timestamp; both missing books were found by the steward
+pointing at a file; the best formulation in the Brahms notes is the steward's, not mine. What the
+instruments did do was catch *me*: the selftest found a missing `json` import that would have
+disabled the digest at every session start, and the ruling's enumerate-don't-count condition found
+six false positives in code I had written ten minutes earlier.
+
+**Confidence to recalibrate.**
+- ⚠ **I told the steward twice that he lacked a book he owned** — Philip's `Early Recordings`
+  (glob matched a literal space; the file uses underscores) and the Joachim/Moser `Violinschule`
+  (filed under the Requiem's IMSLP plate number, reachable by no name search). Both caught only
+  because he pointed.
+- ⚠ **`git add PENDING.md` annexed another session's uncommitted work** into `860c3df` under this
+  session's trailers. Disclosed at `7578f5a`, not rewritten, on the steward's instruction.
+- ⚠ **I split his notes across two files and never said so**, so he opened one and concluded the
+  work hadn't happened.
+- The 89-candidate / 362-population figures are read from another session's transcript; the 273/7
+  half I ran myself.
+
+- ⚠ **AND A FOURTH INSTANCE, INSIDE THIS WRAP.** Grepped `MEMORY.md` for `NOTHING WIRED`, found one
+  match, and told the steward the morning session's correction had never landed and that its wrap had
+  asserted an act it did not run. **False.** The match was inside the correction's own note about what
+  the line used to say. The morning wrap was accurate; the accusation was mine, and it was levelled at
+  a party that had done the work. Retracted in the KG by soft-invalidate rather than deletion.
+  **The rule was banked forty minutes earlier and did not fire on its author.** A memory is not a
+  reflex; writing it down changes nothing about the next unprompted grep.
+
+**What held.** Filed the ruling verbatim before acting under it. Stopped before touching the thread
+on finding a live sibling. Gated the orphan deletion on reading both its files first. Corrected an
+overclaim about stopped jobs to NOT ESTABLISHED rather than guessing either way. **And at this very
+wrap, read `git status` before staging and found 15 lines of the chamber session's `PENDING-177
+AMENDMENT 1` — committed alone and attributed, instead of annexed.** The lesson banked at 12:5x
+fired at 13:0x.
+
+**Instruments:** 3 run · 3 carrying controls written before first execution · **K = 0**.
+
+## FUTURE — what pulls
+
+**The pulling thread: the 322 unread census candidates.** Named at three consecutive wraps now. The
+morning session read 40 of 362 and refused to extrapolate; the afternoon did not touch them at all.
+⚠ **Twice-deferred is the finding.** The steward's own standing preference — *frequent deferrals ARE
+how the cloud accumulated* — applies.
+
+**Actionable resumption point (as of wrap — re-judge):** the next tranche must be another
+**systematic** draw from `claude/governance/PENDING-164-population-362-2026-08-31.tsv`, never the
+head of the list; the pre-registration and protocol at
+`PENDING-164-census-classification-PREREGISTRATION-2026-08-31.md` are reusable verbatim. **But rule
+PENDING-171 first** — the population is wrong until `OWNED_HOSTS` is fixed, and the fix must land
+*after* the pre-registered result is read.
+
+**Other horizons, ranked.** *Steward's, and unblocking three things:* the **FIX-lane check-in**,
+`COME DUE` since 2026-08-02 — it gates PENDING-173's build, the already-authorized per-conversion
+typography gate, and any harvest application. *Then:* rule the record-keeping block · PENDING-160 ·
+-168 · -171 · -176 · -177 (with the jurist's Q2 boundary correction, as **one** package) ·
+REVIEWED-129's amendment. *Untouched a fifth session:* the §5 regrade gate.
+
+**Pause statement.** I am about to be away from this. What I want to find still pulling is **the
+322** — and I want the next session to notice that today produced a great deal of real work, none of
+it the thread, for the second day running. A genuinely full day is exactly what will be allowed to
+stand in for it.
+
+**Literal question for next-Claude** *(checkable; turns on the record, not on introspection)*:
+**Did any instrument built today fire on something it was not built for?** `parked_workers` and the
+widened register control both went live this afternoon. Check the next wake digest's `PARKED
+WORKERS` line and the drift-check's register enumeration: did either report something the item that
+authorized it did not predict? ⚠ **A "no" is the expected answer and must be reported as such** —
+one wake is a small sample, and the question is worth asking again rather than answered early.

claude/memory/session-2026-08-31-the-270-got-read-and-the-population-was-wrong.md

@@ -0,0 +1,181 @@
+---
+name: Session 2026-08-31 — the 270 got read, and the population was wrong
+description: "The pulling thread named at two consecutive wraps and untouched both times was taken all the way. PENDING-164 AMENDMENT 1's declared-owed classification pass ran on 40 of 362 rows, pre-registered and committed alone (5ba5842) before any commit body was read. Sample B, systematic across the corrected population: 12 of the 17 rows deciding about a mechanism name one the register never mentions — including a log-chain spec amendment, a retired session-memory protocol, and a stopgap env var retired by a plan that calls it a stopgap. Three of the five RECORDED rows entered the register 25, 46 and 53 days late. Sample A — the literal inherited question — returns 1, and the pre-registration said in advance that it would refute nothing. Found before sampling: prior-art.py's owned_repos() tests remotes against a fragment of the steward's account name, so CapableMind-AI, BetterMemories.io and be are invisible; the population is 362 and six of the twelve findings live in those repos. Both its positive controls are satisfied by the broken predicate. Filed as PENDING-171."
+type: project
+metadata:
+  node_type: memory
+  type: project
+  modified: 2026-08-31
+---
+
+# Session 2026-08-31 — the 270 got read, and the population was wrong
+
+## PAST — what moved
+
+### The thread that had been named twice and touched neither time
+
+The 2026-08-27 wrap left a literal, checkable question: *of the first 20 census candidates, how
+many decided about a mechanism the register never mentions?* It also left a warning against
+itself — **a count of zero is the strongest possible refutation of PENDING-164 and must be
+reported as such, not explained away.**
+
+**Pre-registered first, committed alone (`5ba5842`), before any commit body was read** — the
+`3a33666` precedent. Two samples fixed in advance, the classification protocol written down,
+controls named in both directions, a contamination guard with the three register files hashed, and
+§8 stating in writing what would refute the item.
+
+### ⚠ The population was never 270 — found before sampling
+
+`prior-art.py`'s `owned_repos()` decides ownership by testing remotes against
+`OWNED_HOSTS = ("github.com/davidglidden", "davidglidden/", "git.skemantix.com")` — an **account
+name inside a remote path**, which is not the relation it claims to compute.
+
+**`_Dev/CapableMind-AI` (35), `_Dev/BetterMemories.io` (42) and `_Dev/be` (12) all fail it: 89
+unseen candidates. The population is 362.** The two largest omissions are the doctrine repo and
+the L1 repo — the two the wake digest lists first.
+
+⚠ **Both positive controls are satisfied by the broken predicate.** They require `0677e8a`
+(chamber-library) and `95760ff` (dotfiles); a rule that misses all three repos returns both. Third
+instance this month of a control encoding what was already expected. Filed **PENDING-171**,
+recommending (c) invert the predicate + (d) a control that can actually fail.
+
+**Deliberately not repaired in-session** — changing `OWNED_HOSTS` would change the population the
+result is pre-registered against.
+
+### The answer
+
+| sample | rows | mechanism decisions | SILENT | RECORDED-LATE | RECORDED-contemp. |
+|---|---|---|---|---|---|
+| A — newest 20, as printed | 20 | 11 | **1** | 0 | 10 |
+| B — every 18th of 362 | 20 | 17 | **12** | 3 | 2 |
+
+🔑 **The contrast is the finding, and it was written down before the reading began.** Sample A's
+head is the fortnight the register was most active; 18 of 20 rows are `dotfiles` and **9 of 20
+write to the register in the same commit — such a commit cannot be silent by construction.** A
+near-zero there measures the sampling frame, not the record. Reported both anyway rather than
+quietly substituting the better sample.
+
+**Strongest instances, none looked for:** `95b44d0` amends the **log-chain spec** to v0.6 —
+`logchain` is a named constitutional constraint with 29 register mentions; `data-portability`,
+`ImportProvenance`, `import trust` return **zero**. `0e3deee` retires an entire session-memory
+protocol. `d0051dd` retires `KRONOS_TRACKED_REPOS`, a stopgap another plan names as such.
+
+**RECORDED-LATE earned its pre-registered place:** three of five RECORDED rows first entered the
+register **25, 46 and 53 days** after the commit. The known case demanded it — `LFS` scores 84
+mentions today, all filed 2026-08-26, twelve weeks after `0677e8a`. **A late mention is recovery,
+not routing.** Wider reading: 15 of 17.
+
+**Controls, both directions.** `logchain` → 29 (must-not-flag alive). Must-detect satisfied on the
+second of three *fixed-in-advance* candidates: `ChromaDB`, 213 commits / 0 register. All three
+reported regardless; `SurrealDB` returned 2 and did not serve. **Guard held: register hashes
+byte-identical before and after; nothing written until the last row was measured.**
+
+### ⚠ Where the judgement sits, and the sensitivity band
+
+Naming the mechanism is interpretation. **Every term string is recorded**, so any verdict is
+re-runnable in one command and contestable on the term. Two post-pre-registration deviations, both
+declared, both neutral-or-adverse: multi-term rows require *all* terms silent; and a **reading
+rule** — an occurrence counts only if it is *about* the mechanism. Seven terms returned non-zero;
+all were read and quoted. **The rule moved four rows in BOTH directions** (`benchmark`, `lex` →
+RECORDED; `ornament`, `recall quality` → SILENT). **Band 10–13; ruling 12.**
+
+## PRESENT — confidence to recalibrate
+
+- ⚠ **My own probe returned five confident false zeroes** (`grep -m8 -n -o ".\{0,70\}TERM.\{0,70\}"`
+  matched nothing while looking like it had looked). For some minutes it read as *two instruments
+  disagreeing about the register* — the shape this thread treats as a finding. It was not one.
+  **The next such mismatch must not inherit the assumption that a mismatch is always meaningful.**
+- ⚠ **I inherited "first 20, in register order" as if it were well-defined.** It is not: the census
+  prints newest-first, and its newest end is the least informative slice available. The prior wrap
+  handed forward a sampling instruction it had not checked.
+- **What held.** Pre-registered and committed alone before reading. Answered the literal question
+  even though it was the weaker one. Ran the fairness sweep whose only possible effect was to
+  reduce my own count. Did not repair the tool mid-measurement. Filed nothing about the twelve into
+  the register — that is option (b), which PENDING-164 argues against and today does not overturn.
+
+## THE WRAP'S OWN FINDINGS — none of which were the session's subject
+
+⚠ **Recorded here because the wrap produced more than it recorded.** Three of today's four
+governance findings surfaced *during* the wrap protocol, not during the work it was wrapping.
+
+### A concurrent sibling session, detected by neither party's apparatus
+
+Two Claude Code sessions ran simultaneously. The sibling woke, was told by the digest
+*"PREVIOUS SESSION DID NOT WRAP"*, **checked the substrate instead of believing it** — this
+session's transcript was still growing and had committed one minute into that wake — and
+concluded *concurrent*, not *previous*. It then **stopped before touching the pulling thread**
+and **held two substrate corrections** rather than race this session's memory write. Its ledger:
+`dotfiles is ahead 1 … the sibling's, not mine to push.`
+
+🔑 **Nothing detected the collision.** It was avoided by one session reading an mtime attentively
+and drawing an inference the digest had drawn wrongly from the same fact. ⚠ *"PREVIOUS SESSION
+DID NOT WRAP"* is a **negative state-claim with no falsifier, in the instrument every session
+reads first** — PENDING-158's class. → **PENDING-104 ADDENDUM 2**; a `wake-digest.py` patch is
+filed in the harvest register.
+
+### The two held corrections, verified rather than relayed
+
+- **`MEMORY.md` asserted the Fool `NOTHING WIRED — no statusLine, no script, §13.1 spec
+  unwritten`. False on all three clauses.** `settings.json` has been running
+  `tarbuckle-body.py` as `statusLine` (refreshInterval 60) for six days; 5 `tarbuckle-*` scripts;
+  the §13.1 spec exists; 7 state files. ⚠ **The sibling's counts (7 scripts, 6 state files) were
+  off in BOTH directions against the measured 5 and 7** — which is why the rule is re-measure,
+  never relay, even from a party that is right about the substance.
+- **Ladder N-now is 44/84, not 51 — DOWN 7 since 08-25.** The 30-day rolling window (PENDING-147)
+  sheds faster than it gains, so **grading may recede rather than approach.** Re-measured by the
+  trial's own method.
+
+### ⚠ The FIX lane has been running past its own authorization for 29 days
+
+REVIEWED-85 made `/wrap-up` §1.6's FIX lane **PROVISIONAL** until a steward–jurist check-in
+*"after the first batch or one month, whichever comes first."* Batch 1 closed **2026-08-02**.
+`skill-harvest-fix-lane-index.md` says in its own words **"the check-in is due."** It has not
+happened. One executor-classified FIX (2026-08-08) was applied past that boundary.
+
+🔑 **The finding is not the lapse — it is that `governance-drift-check.py` printed
+`✓ deferred decisions: 5 tracked, none due` while a condition that fired four weeks ago sat
+unmarked.** The check-in was never given a `DEFERRED-DECISION` block, so it lived among the 143
+prose deferrals the instrument counts and refuses to classify. **PENDING-168's thesis reaching
+its own apparatus.** Block filed with a past trigger; the check now reports
+`⏰ 1 of 6 open have COME DUE`. **Proved by readback, not by write-success.**
+
+**Consequence adopted before it was convenient:** today's one harvest candidate — a clean FIX
+with an exact 2026-08-24 precedent — was filed as `[PROPOSAL]` on the lane's own suspension rule.
+
+### And it corrected a banked proposal rather than duplicating it
+
+The 2026-08-27 register row proposes checking the daily note's required sections *"from the
+skeleton's own `SKELETON` constant so the two copies cannot disagree."* ⚠ **`SKELETON` is the
+copy that is wrong**: it writes 5 headings where `/wrap-up` §7.5 specifies 6, missing
+`## <Project>`. A rule derived from the drifted copy cannot detect the drift —
+`feedback-derive-the-rule-from-the-consumer-not-from-the-survivor`, arriving inside a proposal
+written to prevent that class. **Self-demonstrated: today's note was filled faithfully against
+the skeleton and has no project heading.**
+
+### Instruments, counted forward
+
+**5 run · 4 carrying a control written before first execution · K = 1.** The K: the fairness
+sweep re-derives what `prior-art.py`'s own `report()` already does per term — a batch driver over
+the instrument's own functions, written to avoid re-running controls 33 times. One-shot and
+proportionate; **rule of three not reached.** The 5th (the `grep` context probe) is the one that
+carried no control, and it is the one that failed.
+
+## FUTURE — what pulls
+
+1. **322 of 362 rows unread.** Today is an explicit lower bound and refuses extrapolation. The
+   next tranche should be another *systematic* draw, never the head of the list.
+2. **PENDING-171 needs a ruling** before any further census run — the population is wrong until it
+   lands, and the fix must come *after* today's result is read, not inside it.
+3. ⚠ **Untouched a FOURTH session: the §5 regrade gate.** Recorded, not dropped.
+4. **Owed and concrete:** 115 of the answer key's 120 rows still need a full hand-read; REVIEWED-122's
+   build cannot proceed on a 5-row-verified key.
+5. **Steward's, and blocking:** rule the six-item record-keeping block — as amended or sent back.
+
+**Literal question for next-Claude** *(checkable; turns on the record, not on introspection)*:
+**Of the twelve register-silent mechanisms found today, how many are ones the register SHOULD
+contain?** Today deliberately did not ask this — a MemPalace CI retry policy is plausibly not the
+steward's governance business, and answering "whether the record contains them" is not answering
+"whether it ought to". ⚠ **This question has no mechanical form and must not be given one.** The
+honest instrument is a stated criterion, applied to twelve named rows, with the criterion written
+down *before* the rows are re-read — and a count of zero would mean PENDING-164 measures a real
+absence that costs nothing, which is a live possibility and must be reportable as such.

claude/memory/session-ledger-2026-08-27.md

@@ -0,0 +1,210 @@
+---
+name: Session Ledger 2026-08-27
+description: Practice-of-return ledger maintained by /symmetria — returns, open horizons, recalibrations, authorization moves, sub-agent dialogues, bypasses.
+type: feedback
+---
+
+# Session Ledger — 2026-08-27
+
+## Returns
+
+- 2026-08-27 — **Nearly asserted "PENDING-110 (d) is built" from a commit TITLE.** `prior-art.py`
+  returned `4dc38e6` — *"[FIX] wake-digest: resolve rulings by subject, not by number"* — which
+  reads as 110 (d) discharged. It is not: (d) is *read the body, not only the heading*, and the
+  commit changed which header token is used. Caught by opening `wake-digest.py:438` before
+  writing. §3 flag: **claim-from-derived-form when the substrate is checkable** — a commit
+  message is a derived artefact and this one was accurate about itself and misleading about (d).
+
+- 2026-08-27 — **Refused to total two of three measured columns.** The instrument returned 23
+  false-open candidates and 52 suppressed-with-live-await candidates. Neither is reportable as a
+  count: separating a real false-open from a harmless numbering coincidence, or a live ask from a
+  stale `Awaiting:` line, requires reading each — which is the hand-read key REVIEWED-122
+  condition 1 already requires. Declared the limit; verified subsets reported instead (3 and 4).
+  This is the *declare-a-limit-instead-of-manufacturing-the-column* prevention firing for the
+  third time, in a third item.
+
+
+- 2026-08-27 — **Wrote a predicate that asked a different question and returned the answer I
+  expected.** Testing whether REVIEWED-128 resolves under `RE_REV_FOR`, I checked `'128' in
+  found` — where `found` is the set of *captured PENDING ids*. That asks "does some ruling name
+  PENDING-128?" (True) instead of "does REVIEWED-128 name a PENDING?" (False). **I was one
+  sentence from reporting the built-tag work as safe.** Caught by re-reading what the assertion
+  actually said, not by the result looking wrong — the result looked exactly right.
+  ⚠ Second near-miss today from a derived form, and PENDING-160's fifth-instance shape verbatim:
+  *a predicate that looks like it tests the thing and does not.* Both of today's were caught by
+  re-reading, i.e. by luck of attention — neither by a control. That is the same "the difference
+  is not care" finding as 2026-08-26, recurring the day after it was banked.
+
+- 2026-08-27 — **Did not file PENDING-160 a second time.** The steward asked (§7) for the harness
+  gap to be filed as its own item; it already is, dated 2026-08-25, raised by the jurist, carrying
+  the executor's sentence verbatim, and sitting on the steward's own owed-rulings list. Reported
+  rather than duplicated. ⚠ `prior-art.py` returned **0 commits** for the phrase and would have
+  been read as "no prior art" — the *register-mention count of 2* beside it was the signal, and
+  the tool's own printed caveat about weak absence is what made me look. The commit surface alone
+  would have licensed the duplicate.
+
+- 2026-08-27 — **Did not apply the §9 [FIX] a second time.** Already applied 2026-08-25 at
+  `BUDDY-PATTERN-jurist-draft-v2:372`, with the jurist's own "smaller than first said" correction
+  recorded inline. Two of the four §8 bullets were already discharged.
+
+
+- 2026-08-27 — **Held an authorized deletion once, on a premise that ran backwards.** The steward
+  authorized deleting the snapshot because Time Machine had been added. TM *was* added
+  (`BlockBuster Addendum`, 2026-08-26) — but `/Volumes/on ice` is `[Excluded]` and the source
+  directory was `[Included]`, so deleting would have moved the data from inside the backup
+  perimeter to outside it. Surfaced rather than executed. ⚠ **Not the same concern restated** —
+  the steward answered my first concern and their answer introduced a new fact that did not hold
+  for this data. The steward then supplied the actually-decisive ground (the live repo is healthy;
+  the snapshot only holds the pre-rewrite graph), which I verified — HEAD `8eea85f`, 220 commits,
+  fsck clean, **0 LFS pointers** — and deleted.
+
+- 2026-08-27 — **Wrote a false claim about an instrument into the register, in the item about that
+  instrument, without running it.** PENDING-170 asserted the built-vs-ruled invariant "stays
+  trivially green." It does not: 12 subjects, all passing. Caught by running the check an hour
+  later for an unrelated reason. **PENDING-144's class, committed while filing about it.**
+  Corrected in place with the original preserved, per *removing a claim is not removing the
+  reliance* — the conclusion survived the removal, which is why the correction is safe.
+
+- 2026-08-27 — **The correction then tripped PENDING-139 (B) inside one minute.** Quoting the
+  check's own output put the bare uppercase token in the body; the next run flagged PENDING-170
+  as marked-and-unruled. The check fired correctly and the alarm was false. Reworded to the house
+  `‹marker›` form **and the instance recorded in the item**, because PENDING-139's disclosure is
+  precisely that authors quietly working around this token is what keeps the register silent about
+  a live fault.
+
+
+- 2026-08-27 — **The jurist found a false premise in my own frontmatter, and it was structural.**
+  `audience: the jurist, who has NO repository access` — false, and PENDING-161 (open, `[ESCALATE]`,
+  filed two days earlier) exists for exactly that claim. It was the **third placement** of the
+  premise, in a document written to be quoted. ⚠ The premise **generated the package's
+  architecture**: I built a relay of eleven quotations because I believed the reader was blind. It
+  read eight items verbatim. **My own doctrine says a tool returns the substrate where an agent
+  returns testimony about it — and I chose the testimony form on a false ground.**
+
+- 2026-08-27 — **I ran a census and used it to justify inaction.** Part V argued the answer key
+  could not be drafted until the unit was ruled; Part VIII declined to draft. The jurist dissolved
+  it: a hand-read key cannot pass by construction because no parser produces its verdicts, and a
+  block-keyed key collapses safely into an id-keyed one under the opposite ruling. **Drafting was
+  safe under every outcome, and the doctrine the census was run under says draft finer.** Ten days
+  of "ordered first" and it did not exist. Drafted today.
+
+- 2026-08-27 — **I set the cluster's membership by relay and never ran my own root back across the
+  register.** PENDING-143 states 145's mechanism in the same words, is cited by name inside
+  PENDING-146, and I quoted neither. The weld test, failed on the package's own sharpest section.
+
+
+- 2026-08-27 — **A write reported success and was corrupt, and I only knew because I read it
+  back.** Recording the hash used an *unquoted* heredoc, so the shell command-substituted the
+  backticks inside the Python string before Python ever saw them. The filename and both hashes
+  were consumed; the Addendum's key entry landed as `, **pre-registration commit **` — syntactically
+  fine, semantically empty. Python printed its success line and exited 0.
+  ⚠ **The sharp part: I applied read-back discipline rigorously to a 2 GB binary archive an hour
+  earlier — hashing every object — and then trusted a text edit because it was small.** The
+  discipline was attached to the *stakes I perceived*, not to the *class of operation*. Both are
+  writes; only one got proved. The stderr noise (`permission denied: claude/…`, `command not
+  found: SHORT`) was visible in the same output and I read past it to the success line.
+  The PENDING-142 note in the same call survived only because I happened to escape its backticks.
+
+
+- 2026-08-27 — **Move 2's scope was wrong in the record and I nearly executed it as written.**
+  "The 25" rests on a census that never applied a citability filter. 22 of 27 are apparatus —
+  all 13 of Arendt's are bibliography entries. Real population: **5**. ⚠ And the premise was
+  false: **a blockquote in this corpus does not imply a second voice.** Mauss sets his own N.B.
+  excursus as blockquotes; 4 of 5 are the host's first-person-plural prose. **Executing Move 2 as
+  written would have stamped second-voice attribution onto Mauss's own argument in four places and
+  read as coverage** — the inverse of the failure the arc exists to prevent.
+- 2026-08-27 — **Three-hop scoping error caught by my own controls.** First run read 21 sidecars
+  instead of the 14 manifested (131 runs). Second run iterated the manifest **mapping's keys**,
+  read **zero** sources — and **three of five controls passed**, both must-NOT-flag controls
+  passing vacuously on an empty run. Only must-detect caught it. **The jurist's both-directions
+  requirement, vindicated at my instrument's expense within the hour of my conceding it.**
+- 2026-08-27 — **A must-detect control was mis-specified and the instrument was right.** I asserted
+  "arendt has ≥5 runs in citable text"; it failed. Every large Arendt blockquote is bibliography.
+  The control encoded an expectation I had never verified. **Corrected against the substrate and
+  the correction recorded in the script's own comment — not relaxed until it passed.**
+
+## What held
+
+- 2026-08-27 — **Fired `prior-art.py` at the real firing moment**, before composing, on the two
+  mechanisms this block names. It returned material prior art that changed the work.
+  ⚠ **This does not refute the routing table.** It fired because the wake had just put the
+  question in front of me verbatim; nothing in the system made it fire, and the next item filed
+  without a wake-surfaced falsifier is the actual test. One instance under maximal priming is
+  weak evidence, and the skill-harvest proposal to wire it into the drift-check still stands.
+
+- 2026-08-27 — **Pre-specified four positive controls before running the measurement**, per the
+  one prevention banked yesterday. All passed. The script exits non-zero and refuses its own
+  numbers if any control fails, so a false zero cannot be read as a finding.
+
+- 2026-08-27 — **Substrate-checked all six items' asks before drafting**, rather than inheriting
+  their `Awaiting:` lines. Found every ask unbuilt (so the block is rulable as filed) and one
+  exhibit historical (PENDING-144's occupant, corrected 2026-08-17) — annotated, not edited.
+
+- 2026-08-27 — **Recorded a disagreement with the relayed order** (read 139 first) as a gate
+  question with a lean, rather than silently reordering or silently complying.
+
+- 2026-08-27 — **Proved the archive by read-back before deleting, and gated the deletion on it.**
+  The `rm` was guarded by a live re-check (552 objects, HEAD match, fsck) that would have aborted.
+  Content-addressing made a real proof possible: every object re-derived its own SHA-256.
+- 2026-08-27 — **Left the cold copy self-proving.** `VERIFY.py` + README beside the archive, so it
+  can be re-proved with no reference copy, no network, and no trust in this session's author —
+  including by someone who has never heard of this session.
+- 2026-08-27 — **Checked the case-insensitivity hazard before copying, not after.** HFS+ collapses
+  case; the snapshot had zero colliding paths. Established, not assumed. The NFD normalisation it
+  *did* have surfaced only because paths were compared bytewise rather than counted.
+
+- 2026-08-27 — **Filed the ruling verbatim BEFORE acting on it** — PENDING-108 (c)'s proposed
+  ordering, adopted for the first time. 108's own pre-registered clock starts on this package.
+- 2026-08-27 — **Solved the anomaly the jurist reported and declined to explain**, and it was
+  reachable only from the filesystem side: the 23-line delta is a note I inserted while it read.
+  ⚠ **The executor's filing silently corrupted the checker's view of the executor's filing.**
+  Filed as PENDING-104 ADDENDUM 1. The jurist's willingness to report an unexplained anomaly
+  rather than pick the plausible number is the only reason it is known.
+- 2026-08-27 — **Declared the key's own limit rather than claiming a uniform standard.** Only 5 of
+  120 rows are hand-read in the full sense; the rest are hand-assigned from a dispositive field.
+  Stated in the key's header, because a key claiming a standard it did not meet is
+  pass-by-construction in a new costume.
+
+- 2026-08-27 — **Read all five before dispositioning any.** The population was small enough to
+  actually read, and reading is what overturned the premise. A count would have hidden it.
+- 2026-08-27 — **Move 2 closed with an instrument (7/7 controls, both directions) and a record,
+  writing nothing to the corpus** — the authorization's explicit term.
+
+## Open horizons
+
+- 2026-08-27T—:— — **Inherited thread: the 270 uncounted census candidates.** The interpretive half of PENDING-164's census. Unscheduled, unclaimed. ⚠ The wrap's pause statement names the exact temptation: treating a built instrument as a discharged obligation.
+- 2026-08-27T—:— — **Steward-dated:** move `~/_Dev/chamber-library.pre-lfs-export-20260605` to the MemPalace drive. Move, not `migrate export`; must carry `.git/lfs/objects` (552 obj / 975 MB); read back at destination. PENDING-165 (c) unblocks on it.
+- 2026-08-27T—:— — **§5 regrade gate: untouched two sessions running.** Steward's and jurist's to settle. Recorded, not dropped.
+- 2026-08-27T—:— — Skill-harvest proposal from the 2026-08-26 wrap awaits steward: wire the prior-art check into `governance-drift-check.py`.
+
+## Confidence to recalibrate
+
+- 2026-08-27T—:— — **N-now measured at 40**, down from 51 on 2026-08-25. Re-measured, not relayed (`len(glob(…/*.jsonl))`). The 30-day rolling window shed 11 transcripts in two days; grading is at 84 and the counter is moving away from it. Verified: yes, by direct count. Inferred: that the drop is ordinary window rotation rather than a prune event — unverified.
+- 2026-08-27T—:— — `thread-query` returned 5 candidates, all matching on generic terms; none bore on the thread. Logged as a near-null. The trial needs nulls recorded, so this is reported rather than dressed up.
+
+## Authorization moves
+
+- 2026-08-27 — **Package filed, nothing ruled.** `record-keeping-cluster-JURIST-PACKAGE-2026-08-27.md`
+  + its measurement script, both in `~/dotfiles/claude/governance/`. No register mutated, no
+  placed ruling touched, no item edited, and the answer key deliberately NOT drafted — drafting it
+  before the unit is ruled is the error the package reports.
+- 2026-08-27 — **Filed PENDING-166, -167, -168, -169, -170; amended PENDING-162 (AMENDMENT 1) and
+  PENDING-89 (dated note).** Nothing built, nothing in the running Tarbuckle system touched, per
+  the steward's standing direction that all of it waits for the September revisit.
+- 2026-08-27 — **Declined to add the fourth-instance doctrine to the verification ladder.**
+  REVIEWED-123's freeze is general and admits no source; queued in PENDING-141's owed-entries list
+  instead, and PENDING-168 records the refusal explicitly because a doctrine on its fourth instance
+  is exactly the entry someone adds believing the freeze cannot have meant this one.
+- 2026-08-27 — **Blocked one steward ask and named the dependency instead of doing it partway:**
+  built-vs-ruled tags cannot be armed while REVIEWED-128's header names no PENDING. Filed as
+  PENDING-170 with the two routes out, rather than left as a remembered caveat.
+- 2026-08-27 — **Committed the pre-registered answer key alone: `3a33666`** (full
+  `3a33666730380e5b51c694e83ebfbc723b35c407`), on steward instruction. Nothing else in the commit,
+  so the pre-registration hash is unambiguous. Hash recorded on two surfaces — the package Addendum
+  and a `###` note in PENDING-142. **The committed file is unmodified since the commit**, verified.
+- 2026-08-27 — Six gate questions carry executor leans. Q1 (declared fields vs marker-matching)
+  is the block's hinge and the lean is disclosed as weak on cost.
+
+## Sub-agent dialogues
+
+## Bypasses

claude/memory/session-ledger-2026-08-31.md

@@ -0,0 +1,54 @@
+---
+name: Session Ledger 2026-08-31
+description: Practice-of-return ledger maintained by /symmetria — returns, open horizons, recalibrations, authorization moves, sub-agent dialogues, bypasses.
+type: feedback
+---
+
+# Session Ledger — 2026-08-31
+
+## Returns
+
+- 2026-08-31T09:07 — **Did not accept the wake digest's self-report.** It asserted
+  *"PREVIOUS SESSION DID NOT WRAP (ended ~Aug 31 09:05)"*. Checked the substrate: transcript
+  `b7e7eb39` was still growing (mtime 09:09:25) and committed `5ba5842` to dotfiles at 09:08:25 —
+  **one minute into this wake.** The session has not ended; it is live. §3 flag avoided:
+  *component self-assessment accepted at face value*. The digest was right that no wrap exists and
+  wrong about why.
+
+- 2026-08-31T09:08 — **Re-measured rather than relayed.** The 362-population claim and the
+  `owned_repos()` defect came from reading another session's transcript. Ran
+  `prior-art.py --census` independently before putting a number in the briefing: 273 rows over
+  7 repos, `instrument verified: YES`. Consistent with the transcript's account.
+
+## What held
+
+- Stopped before touching the pulling thread on discovering a live sibling session working it.
+  Two sessions appending to `PENDING.md` concurrently is **PENDING-104 ADDENDUM 1 verbatim** —
+  the executor's filing silently corrupting the checker's view of the executor's filing.
+
+## Open horizons
+
+- ⚠ **Concurrency, unresolved and blocking:** which session holds the 270/362 thread? Nothing in
+  the governance apparatus detects two live executors; the collision class is filed (104 A1) but
+  no mechanism watches for it.
+- ⚠ **MEMORY.md carries a claim the substrate contradicts.** The Fool/Tarbuckle tracker line reads
+  *"NOTHING WIRED — no `statusLine`, no script, §13.1 spec unwritten."* Substrate: `settings.json`
+  runs `dotfiles/scripts/tarbuckle-body.py` as `statusLine` (refreshInterval 60); seven
+  `tarbuckle-*` scripts exist; `TARBUCKLE-SPEC-13.1-2026-08-25.md` exists; six state files under
+  `~/.claude/state/`. Correction owed — held, not applied, while a sibling session may be writing
+  memory.
+- `dotfiles` is **ahead 1** (commit `5ba5842`, unpushed) — the sibling's, not mine to push.
+- §5 regrade gate: untouched for a third session. Recorded, not dropped.
+- Ladder N-now **44/84** (was 51 on 2026-08-25) — the 30-day window is shedding faster than it
+  gains; grading may recede rather than approach.
+
+## Confidence to recalibrate
+
+- The 89-candidate / 362-population figures are **read from another session's transcript**, not
+  produced by me. The 273/7 half I verified myself. Marked as such in the briefing.
+
+## Authorization moves
+
+## Sub-agent dialogues
+
+## Bypasses

claude/memory/skill-harvest-register.md

@@ -575,3 +575,23 @@ it, which is the argument for the step.
 ⚠ **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.
+
+## Proposed 2026-08-27 wrap — awaiting steward
+
+| # | kind | target | proposal | firing moment | routing |
+|---|---|---|---|---|---|
+| — | patch | `/wrap-up` §3 | **The MEMORY.md rotation is a two-file write with no atomicity, and it half-applied today.** §3 demotes the prior Active Session into `MEMORY-reference.md` *and* rewrites `MEMORY.md`. This wrap's script wrote the reference file, then raised on the next statement, so **the old Active Session existed in BOTH files** — the exact "never leave two Active Session entries" hazard the step exists to prevent, arrived at from the other side. Caught by reading back, not by the step. Proposed: §3 states the order (**write MEMORY.md first, demote second**, so a mid-failure leaves one copy rather than two) and ends with a three-line assertion — exactly one `## Active Session`, zero occurrences of the prior session's pointer in `MEMORY.md`, exactly one demotion marker in the reference file. ⚠ **Honest limit:** this makes a partial write *detectable*, not impossible; two files cannot be written atomically here. | **at every `/wrap-up` §3** — already a ritual step | named step in an existing ritual (strong tier) |
+| — | patch | `/wrap-up` §7.5 + `daybook-ensure.py` | **The daily note's required shape is asserted in two places and checked in none.** §7.5 lists six required `##` sections and warns *in its own text* that the skeleton is a second copy which "will drift". Today it had drifted in effect: the note carried `The day in short` and `Open / next` but **not** `Decisions taken`, `Insights and exchanges worth keeping`, or `Corrections` — and I only found out by grepping the headings against the list by hand. ⚠ **`## Corrections` is the one that matters**: REVIEWED-126 added it precisely because a format with a slot for insights and none for errors under-records errors, and it was the missing section on a day with roughly a dozen corrections. Proposed: a check that reads the day's note and reports missing required sections — mechanically, from the skeleton's own `SKELETON` constant so the two copies cannot disagree. | **at every `/wrap-up` §7.5**, or better, at the `Stop` hook that already fires the daybook cue | mechanical detector (strongest tier) — the cue hook already runs on a timer and already reads this file |
+
+⚠ **Both filed as `[PROPOSAL]`, not taken through the FIX lane, and the reason is the same for both.** Each edits a `/wrap-up` step **while that step is being executed by the session proposing it**, which is the one configuration where the classification test is least trustworthy — the executor is both author and beneficiary of the judgement that it needs no authorization. The lane's own instruction is *when in doubt, propose*, and self-modification during execution is the definition of doubt.
+
+⚠ **Both were earned by failures in THIS wrap**, not observed in the abstract: the half-applied rotation actually happened, and the missing sections were actually missing. Neither is a speculative improvement.
+
+## Proposed 2026-08-31 wrap — awaiting steward
+
+| # | kind | target | proposal | firing moment | routing |
+|---|---|---|---|---|---|
+| — | **CORRECTION to the 2026-08-27 row above**, not a new proposal | `/wrap-up` §7.5 + `daybook-ensure.py` | ⚠ **That row's proposed mechanism cannot work, and today shows why.** It proposes deriving the required-section list *"from the skeleton's own `SKELETON` constant so the two copies cannot disagree."* **The `SKELETON` constant is the copy that is wrong.** Measured today: `daybook-ensure.py` writes **5** headings (`The day in short` · `Decisions taken` · `Insights and exchanges worth keeping` · `Corrections` · `Open / next`); §7.5 specifies **6**, the extra being `## <Project>` — *one H2 per project touched, with commit hashes inline*. So the skeleton **structurally cannot produce a conforming note**, and a checker derived from it would pronounce every note complete while the format's most distinctive element is absent from all of them. **A rule derived from the drifted copy cannot detect the drift** — `feedback-derive-the-rule-from-the-consumer-not-from-the-survivor`, arriving inside a proposal written to prevent exactly this class. Self-demonstrated: today's note was filled faithfully against the skeleton and has no project heading. **Proposed instead:** derive from §7.5 (the spec, which is what a *reader* of the note is owed), and add the missing slot to `SKELETON` in the same act so the two agree in the right direction. | at every `/wrap-up` §7.5, or the `Stop` hook that already fires the daybook cue | mechanical detector (strongest tier) |
+| — | patch | `/wake-up` digest (`wake-digest.py`) | **`PREVIOUS SESSION DID NOT WRAP` is a negative state-claim with no falsifier, in the instrument every session reads first.** Today it fired while the other session was **live** — still writing its transcript, and it had committed to `dotfiles` one minute into the sibling's wake. The digest was right that no wrap existed and **wrong about why**, and the wrong half is the dangerous one: a session that believes the other is finished has no reason not to write to `PENDING.md`. Collision avoided by one session reading an mtime attentively, not by any mechanism. Proposed: distinguish *no wrap recorded* from *the session has ended* — the transcript's mtime and a recent-commit check already answer it — and say **`ANOTHER SESSION MAY BE LIVE`** when they do. ⚠ **Honest limit:** mtime is a heuristic and a genuinely idle session looks live; the failure it introduces (an unnecessary caution) is the cheap direction, which is the whole argument. | at every wake — already the ritual, already this script | mechanical detector (strongest tier) |
+
+⚠ **Both are filed as PROPOSED and neither was applied, though the first would otherwise have been a clean FIX with an exact 2026-08-24 precedent.** The `/wrap-up` §1.6 FIX lane is **PROVISIONAL until a steward–jurist check-in that its own index says is due and that has not happened in 29 days** — see PENDING-168 ADDENDUM 1, which files the `DEFERRED-DECISION` block that now surfaces it. The lane's own rule: *until that review, treat a borderline call as `[PROPOSAL]`*.

scripts/governance-drift-check.py

@@ -213,48 +213,137 @@ control("doctrine-id citing surface is reachable",
 # Detection only, like every check here: REVIEWED.md is [ESCALATE], the
 # steward's hand (Constitutional Constraint #1).
 REVIEWED_MD = HOME / "dotfiles" / "REVIEWED.md"
+PENDING_MD = HOME / "dotfiles" / "PENDING.md"
+PENDING_ARCHIVE_MD = HOME / "dotfiles" / "PENDING-archive.md"
 
-RE_HEAD = re.compile(r"^##\s+REVIEWED-(\d+)\s*[—-]\s*(.*)$", re.M)
-RE_AMENDS = re.compile(r"\*\*Amends:\*\*\s*REVIEWED-(\d+)")
+# WIDENED 2026-08-31 under REVIEWED-132 (PENDING-173 + ADDENDUM 1). The check was
+# narrowed three times without declaring any of them: the header regex and the
+# **Amends:** regex both hard-coded REVIEWED-, and the amendment test was
+# startswith("AMENDMENT"). It saw 3 of the 81 amendment-shaped blocks in the
+# registers, and — worse — an ADDENDUM was classified as an ORIGINAL, so it could
+# have satisfied its own "an un-amended entry exists" test on behalf of a record
+# that had been replaced.
+#
+# ⚠ WIDENING IS THE FLOOR, NOT THE FIX. 48 of the 81 blocks carry NO item number
+# (`### AMENDMENT 1 — 2026-08-08`) and are attributable only by which header sits
+# above them. No id-keyed reader can check those; they are reported NOT ESTABLISHED,
+# never passed. The prospective-convention question is PENDING-146's, deliberately
+# not decided here (REVIEWED-132 condition 5).
+MARKERS = ("AMENDMENT", "ADDENDUM")
+RE_MARKER_TOKEN = re.compile(r"\b(?:AMENDMENT|ADDENDUM)\b")
+RE_HEAD_LINE = re.compile(r"^#{2,3}\s+(.*)$", re.M)
+RE_ID = re.compile(r"^((?:PENDING|REVIEWED|COMPLETED)\S*)\s*[—–-]\s*(.*)$")
+RE_INBODY = re.compile(r"^\*\*(?:AMENDMENT|ADDENDUM)\b.*$", re.M)
+RE_AMENDS = re.compile(r"\*\*Amends:\*\*\s*((?:PENDING|REVIEWED|COMPLETED)-\S+?)[\s,.(]")
+
+# Every form the controls below actually exercise. A form found in the record and
+# absent from this set is reported NOT ESTABLISHED rather than silently passed
+# (REVIEWED-132 condition 2) — the check may not certify what it has never been shown.
+FORMS_COVERED = {"id+marker", "id-only", "bare-marker", "in-body", "compound"}
 
 
-def register_findings(text: str, label: str) -> list[str]:
-    """Every amendment must sit ALONGSIDE the record it amends, never replace it."""
-    out: list[str] = []
-    heads = RE_HEAD.findall(text)
-    originals = {n for n, rest in heads
-                 if not rest.strip().upper().startswith("AMENDMENT")}
-    for n, rest in heads:
-        if rest.strip().upper().startswith("AMENDMENT") and n not in originals:
-            out.append(f"{label}: '## REVIEWED-{n} — AMENDMENT' exists with no "
-                       f"un-amended REVIEWED-{n} entry — the amendment replaced "
-                       f"the record it amends")
-    for n in sorted(set(RE_AMENDS.findall(text))):
-        if n not in originals:
-            out.append(f"{label}: a block declares '**Amends:** REVIEWED-{n}' but "
-                       f"no REVIEWED-{n} entry exists in the file")
-    return out
+def _classify(head: str):
+    """-> (form, ident|None, title). One place decides what a header is."""
+    m = RE_ID.match(head.strip())
+    if not m:
+        up = head.strip().upper()
+        return ("bare-marker" if any(up.startswith(k) for k in MARKERS) else "prose"), None, head
+    ident, rest = m.group(1), m.group(2)
+    s = rest.strip()
+    if any(s.startswith(k) for k in MARKERS):
+        return "id+marker", ident, rest
+    if RE_MARKER_TOKEN.search(s):
+        # A marker somewhere other than the start — "BUILD RECORD + AMENDMENT 1 result".
+        # Condition 1: NOT admitted to originals. Excluded, and made visible.
+        return "compound", ident, rest
+    # ⚠ CASE IS LOAD-BEARING, found 2026-08-31 by the enumeration REVIEWED-132 cond. 3
+    # requires. An earlier draft upper-cased the title first, so prose titles — "Citation
+    # amendment (#2)", "Dream amendment", "PENDING-46 addendum (2026-07-03)" — matched and
+    # were struck from `originals`. That is the mirror of the bug this widening repairs:
+    # it would raise FALSE "the record was replaced" findings about six real originals.
+    # Markers in this register are uppercase standalone tokens; a lower-case mention in a
+    # title is a title.
+    return "id-only", ident, rest
 
 
-reg_findings: list[str] = []
-if REVIEWED_MD.exists():
-    reg_findings = register_findings(REVIEWED_MD.read_text(errors="replace"),
-                                     "REVIEWED.md")
+def register_scan(texts: dict) -> tuple:
+    """-> (findings, unattributable, forms_seen).
 
-# Controls. The third is the one that matters and is the lesson of the day:
-# a check that has never fired on a known-bad input is unestablished, so the
-# instrument is run against a synthetic reproduction of the actual failure.
+    `originals` is computed across ALL registers, because a parent may have been
+    archived while its amendment stays open; the old per-file rule would have
+    called that a replacement. A header is an original ONLY if it carries an
+    identifier and no marker anywhere — everything else is excluded (condition 1),
+    which is the opposite default from the version this replaces.
+    """
+    parsed, forms = {}, {}
+    for label, text in texts.items():
+        rows = [_classify(h) for h in RE_HEAD_LINE.findall(text)]
+        rows += [("in-body", None, ln.strip()) for ln in RE_INBODY.findall(text)]
+        parsed[label] = rows
+        for form, _i, _r in rows:
+            if form != "prose":
+                forms.setdefault(form, set()).add(label)
+    originals = {i for rows in parsed.values() for f, i, _ in rows
+                 if f == "id-only" and i}
+    findings, unattributable = [], []
+    for label, rows in parsed.items():
+        for form, ident, title in rows:
+            if form == "id+marker" and ident not in originals:
+                findings.append(f"{label}: '{ident} — {title[:48]}' exists with no "
+                                f"un-amended {ident} entry — the amendment replaced "
+                                f"the record it amends")
+            elif form in ("bare-marker", "in-body"):
+                unattributable.append((label, form, title[:72]))
+        for ident in sorted(set(RE_AMENDS.findall(text := texts[label]))):
+            if ident not in originals:
+                findings.append(f"{label}: a block declares '**Amends:** {ident}' but "
+                                f"no un-amended {ident} entry exists in any register")
+    return findings, unattributable, forms
+
+
+_TEXTS = {p.name: p.read_text(errors="replace")
+          for p in (REVIEWED_MD, PENDING_MD, PENDING_ARCHIVE_MD) if p.exists()}
+reg_findings, reg_unattrib, reg_forms = ([], [], {}) if not _TEXTS else register_scan(_TEXTS)
+reg_uncovered = sorted(set(reg_forms) - FORMS_COVERED - {"prose"})
+
+# Controls. Drawn from the census, not from the author's memory of the convention
+# (REVIEWED-132 condition 2): ADDENDUM headers, ### depth, in-body forms and
+# PENDING-side instances are all exercised, because all four are in the record.
 _GOOD = ("## REVIEWED-87 — PENDING-99 — original\n**Date:** 2026-08-05\n\n"
          "## REVIEGH\n\n## REVIEWED-87 — AMENDMENT 2026-08-07\n"
          "**Amends:** REVIEWED-87 (x).\n")
 _BAD = ("## REVIEWED-87 — AMENDMENT 2026-08-07\n"
         "**Amends:** REVIEWED-87 (x).\n")
-control("register parser finds REVIEWED headings", len(RE_HEAD.findall(_GOOD)) == 2)
-control("register check passes a correctly JOINED amendment",
-        not register_findings(_GOOD, "t"))
+_ADDENDUM_BAD = "## PENDING-142 — ADDENDUM 1: the selftest encodes the defect\n"
+_ADDENDUM_OK = ("## PENDING-142 — the parent\n\n"
+                "### PENDING-142 — ADDENDUM 1: joined, at ### depth\n")
+_BARE = "## PENDING-9 — parent\n\n### AMENDMENT 1 — 2026-08-08, no item number\n"
+
+_f_good, _u_good, _ = register_scan({"t": _GOOD})
+_f_bad, _, _ = register_scan({"t": _BAD})
+_f_add, _, _ = register_scan({"t": _ADDENDUM_BAD})
+_f_addok, _, _ = register_scan({"t": _ADDENDUM_OK})
+_f_bare, _u_bare, _ = register_scan({"t": _BARE})
+
+control("register check passes a correctly JOINED amendment", not _f_good)
 control("register check DETECTS an amendment that replaced its record  "
-        "[reproduces the 2026-08-07 loss]",
-        len(register_findings(_BAD, "t")) == 2)
+        "[reproduces the 2026-08-07 loss]", len(_f_bad) == 2)
+control("register check DETECTS a replacing ADDENDUM  [the word the old test could "
+        "not see; it classified this as an ORIGINAL and passed]", len(_f_add) == 1)
+control("register check passes a JOINED ### addendum  [must-not-flag: ### depth is "
+        "the register's own placement form]", not _f_addok)
+control("an unnumbered '### AMENDMENT 1' is NOT ESTABLISHED, never passed",
+        any(f == "bare-marker" for _l, f, _t in _u_bare) and not _f_bare)
+_PROSE = "## PENDING-60 — Citation amendment (#2): specify the CTS-URN model\n"
+_f_prose, _, _fm_prose = register_scan({"t": _PROSE})
+control("a lower-case 'amendment' in a TITLE stays an ORIGINAL  [must-not-flag: the "
+        "mirror bug — it would strike six real originals off the list]",
+        "id-only" in _fm_prose and not _f_prose)
+control("an UPPER-CASE marker mid-title is still excluded from originals  [must-detect]",
+        "compound" in register_scan(
+            {"t": "## PENDING-164 — BUILD RECORD + AMENDMENT 1 result\n"})[2])
+control("PENDING-side registers are actually read", "PENDING.md" in _TEXTS)
+control("every form present in the record is covered by a control", not reg_uncovered)
 control("register file is reachable", REVIEWED_MD.exists())
 
 
@@ -779,11 +868,32 @@ if reg_findings:
         print(f"    {f}")
     print("\n  An amendment must sit alongside the record it amends, never replace it.")
     print("  Correction requires [ESCALATE] — REVIEWED.md is the steward's hand.")
-elif REVIEWED_MD.exists():
-    n_am = sum(1 for _, r in RE_HEAD.findall(REVIEWED_MD.read_text(errors="replace"))
-               if r.strip().upper().startswith("AMENDMENT"))
-    print(f"✓ register integrity: every amendment link resolves "
-          f"({n_am} amendment(s) checked)")
+elif _TEXTS:
+    # REVIEWED-132 condition 3: ENUMERATE, do not count. The old line reported a
+    # bare number and that number never moved when a matching block was appended.
+    _checked = {}
+    for _lab, _txt in _TEXTS.items():
+        _rows = [_classify(h) for h in RE_HEAD_LINE.findall(_txt)]
+        _rows += [("in-body", None, "") for _ in RE_INBODY.findall(_txt)]
+        for _f, _i, _r in _rows:
+            if _f != "prose" and _f != "id-only":
+                _checked.setdefault(_lab, {}).setdefault(_f, 0)
+                _checked[_lab][_f] += 1
+    _tot = sum(sum(d.values()) for d in _checked.values())
+    _att = sum(c for d in _checked.values() for f, c in d.items()
+               if f in ("id+marker", "compound"))
+    print(f"✓ register integrity: {_att} attributable amendment block(s) checked, "
+          f"all resolve — of {_tot} amendment-shaped block(s) across "
+          f"{len(_TEXTS)} register(s)")
+    for _lab in sorted(_checked):
+        print("    " + _lab + ": " + ", ".join(f"{f}={c}" for f, c in sorted(_checked[_lab].items())))
+    if reg_unattrib:
+        print(f"  ⚠ {len(reg_unattrib)} block(s) NOT ESTABLISHED — they carry no item "
+              f"identifier, so no id-keyed reader can say what they amend. Counted, "
+              f"never passed. The convention question is PENDING-146's.")
+    if reg_uncovered:
+        print(f"  ⚠ NOT ESTABLISHED — form(s) present in the record with no control: "
+              f"{', '.join(reg_uncovered)}")
 
 # Built-without-a-ruling. THREE-VALUED (REVIEWED-106): clean / findings / cannot-assess.
 if not build_assessable:

scripts/wake-digest.py

@@ -16,7 +16,7 @@ if it cannot be computed it says so rather than emitting nothing.
 Provenance: 2026-07-28, steward-authorized alongside the PENDING split and the
 CLAUDE.md doctrine annotation. Sibling of governance-drift-check.py.
 """
-import calendar, os, re, subprocess, sys, time
+import calendar, json, os, re, subprocess, sys, time
 
 HOME = os.path.expanduser("~")
 D = os.path.join(HOME, "dotfiles")
@@ -340,6 +340,26 @@ def wrap_verdict(span, events, lead=300, lag=10800):
     return "unwrapped", ""
 
 
+def previous_session():
+    """THE single selection of 'the session before this one', for every consumer.
+
+    Lifted out of sec_unwrapped 2026-08-31 when the loop check (REVIEWED-131) needed
+    the same transcript. This file already refuses a second definition of 'an item'
+    (item_spans); a second definition of 'the previous session' would be the same
+    bug at a different site. -> (path, start_epoch, end_epoch) or None.
+    """
+    proj = os.path.dirname(os.path.join(HOME, ".claude", "projects",
+                                        "-Users-davidglidden", "memory"))
+    try:
+        tx = [os.path.join(proj, f) for f in os.listdir(proj) if f.endswith(".jsonl")]
+    except OSError:
+        warn.append("session transcripts unreadable — wrap check did not run")
+        return None
+    if not tx:
+        return None
+    return previous_transcript(time.time(), [(p,) + transcript_span(p) for p in tx])
+
+
 def sec_unwrapped():
     """
     PENDING-S2's obligation, rebuilt on our own substrate.
@@ -361,16 +381,7 @@ def sec_unwrapped():
       4. a two-valued verdict over an assessment that can fail.
     Fixing only (4), as scoped, would have left the false alarms firing.
     """
-    proj = os.path.dirname(os.path.join(HOME, ".claude", "projects",
-                                        "-Users-davidglidden", "memory"))
-    try:
-        tx = [os.path.join(proj, f) for f in os.listdir(proj) if f.endswith(".jsonl")]
-    except OSError:
-        warn.append("session transcripts unreadable — wrap check did not run")
-        return None
-    if not tx:
-        return None
-    prev = previous_transcript(time.time(), [(p,) + transcript_span(p) for p in tx])
+    prev = previous_session()
     if prev is None:
         return None
     _path, a, b = prev
@@ -862,6 +873,143 @@ def stray_maps():
         return []
 
 
+# ---------- (e) + (c): is the loop currently removable?  REVIEWED-131 (2026-08-31) ----------
+# EARNED 2026-08-31. A binary upgrade restarted the daemon, which respawned a parked
+# worker with --reply-on-resume. THIS digest was injected into that session as its only
+# instruction, and an executor worked and committed with no human present (PENDING-172).
+# (e) reads harness state on disk; (c) reads the session transcript. Two substrates,
+# deliberately — REVIEWED-131 cond. 2 requires the output to name which one fired.
+
+JOBS_DIR = os.path.expanduser("~/.claude/jobs")
+ARM_FLAG = "--reply-on-resume"
+
+
+def parked_workers(jobs_dir=JOBS_DIR):
+    """(e) — REVIEWED-131 cond. 1. Returns (rows, unreadable, established).
+
+    Whether a parked worker will take a turn with no human present is recorded
+    per session in <jobs>/<id>/state.json's `respawnFlags`. This reads the
+    HARNESS, not the session: the only check here whose enforcement does not
+    depend on the party being checked.
+
+    `established` is False whenever the directory is missing or unreadable.
+    A control over parked workers whose negative result is an opaque zero is
+    the failure PENDING-172 is about, so this NEVER reports absence of evidence
+    as evidence of absence. Every dir read and every dir refused is enumerated.
+    """
+    rows, unreadable = [], []
+    if not os.path.isdir(jobs_dir):
+        return rows, unreadable, False
+    try:
+        entries = sorted(os.listdir(jobs_dir))
+    except OSError as e:
+        return rows, [("<listing>", type(e).__name__)], False
+    for name in entries:
+        d = os.path.join(jobs_dir, name)
+        if not os.path.isdir(d):
+            continue
+        f = os.path.join(d, "state.json")
+        try:
+            with open(f, encoding="utf-8") as fh:
+                st = json.load(fh)
+        except Exception as e:
+            unreadable.append((name, type(e).__name__))
+            continue
+        flags = st.get("respawnFlags")
+        # An absent or non-list respawnFlags is NOT "unarmed" — it is unreadable state.
+        if not isinstance(flags, list):
+            unreadable.append((name, "respawnFlags missing or not a list"))
+            continue
+        rows.append((name, str(st.get("state") or "?"), ARM_FLAG in flags,
+                     str(st.get("name") or "")[:52]))
+    return rows, unreadable, True
+
+
+NONHUMAN = ("<local-command-", "<command-name>", "<command-message>", "<system-reminder",
+            "=== WAKE DIGEST", "<local-command-stdout>", "<local-command-caveat>")
+
+
+def human_turns(path):
+    """(c) — REVIEWED-131 cond. 2. Count of genuine human turns in a transcript.
+
+    A hook-injected digest arrives as a `user` record, and so do /clear and /exit;
+    none of them is a person. Returns None when the transcript cannot be read —
+    unreadable is not zero.
+
+    ⚠ RETROSPECTIVE BY CONSTRUCTION. At SessionStart the current session has no
+    turns yet, so this is applied to the most recent COMPLETED session. It answers
+    'did an executor just run unattended?', which is what nothing detected on
+    2026-08-31 — not 'am I about to'. (e) is the forward-looking half.
+    """
+    try:
+        with open(path, encoding="utf-8", errors="replace") as fh:
+            lines = fh.readlines()
+    except Exception:
+        return None
+    n = 0
+    for line in lines:
+        try:
+            o = json.loads(line)
+        except Exception:
+            continue
+        if o.get("type") != "user" or o.get("isMeta"):
+            continue
+        c = o.get("message", {}).get("content")
+        if isinstance(c, list):
+            c = " ".join(x.get("text", "") for x in c if isinstance(x, dict))
+        if not isinstance(c, str) or not c.strip():
+            continue
+        if any(m in c for m in NONHUMAN):
+            continue
+        n += 1
+    return n
+
+
+def sec_loop(prev_transcript=None):
+    """Assemble (e) and (c), naming which control produced each line."""
+    o = []
+    rows, unreadable, established = parked_workers()
+    if not established:
+        o.append("PARKED WORKERS [control e — harness state] — NOT ESTABLISHED:"
+                 f" {JOBS_DIR} is missing or unreadable."
+                 " This is 'could not assess', not 'none parked'.")
+    else:
+        armed = [r for r in rows if r[2]]
+        head = (f"PARKED WORKERS [control e — harness state] — {len(rows)} job dir(s) read,"
+                f" {len(unreadable)} unreadable, {len(armed)} ARMED")
+        o.append("⚠ " + head if armed else head)
+        for jid, state, arm, name in rows:
+            o.append(f"  {'⚠ ARMED' if arm else '  ok   '}  {jid}  state={state}  {name}")
+        for jid, why in unreadable:
+            o.append(f"  NOT ESTABLISHED  {jid}  ({why}) — counted, not classified")
+        # ⚠ A stopped job still carries its flags. Whether the daemon respawns a
+        # STOPPED job is NOT ESTABLISHED — the 2026-08-31 event respawned one that was
+        # parked (state=blocked). Reporting both as equally live would assert what was
+        # never measured; reporting the stopped one as safe would assume it.
+        live = [r for r in armed if r[1] not in ("stopped",)]
+        stopped = [r for r in armed if r[1] in ("stopped",)]
+        if live:
+            o.append(f"  ⇒ {len(live)} PARKED worker(s) carry {ARM_FLAG}: a daemon restart"
+                     " (an auto-update will do) makes them take a turn with no human"
+                     " present. PENDING-172 / REVIEWED-131.")
+        if stopped:
+            o.append(f"  ⇒ {len(stopped)} STOPPED job(s) still carry {ARM_FLAG}."
+                     " Whether the daemon respawns a stopped job is NOT ESTABLISHED —"
+                     " the 2026-08-31 respawn took a job that was parked, not stopped."
+                     " Neither live nor proven safe.")
+    if prev_transcript:
+        n = human_turns(prev_transcript)
+        label = "LAST SESSION [control c — transcript]"
+        if n is None:
+            o.append(f"{label} — NOT ESTABLISHED: transcript unreadable.")
+        elif n == 0:
+            o.append(f"⚠ {label} — NO HUMAN TURN in {os.path.basename(prev_transcript)}."
+                     " That session ran unattended. PENDING-172.")
+        else:
+            o.append(f"{label} — {n} human turn(s); a person was present.")
+    return o
+
+
 # ---------- self-test ----------
 
 def selftest():
@@ -979,6 +1127,57 @@ def selftest():
     chk("classify_pointers returns clean on empty input",
         classify_pointers("", MEMDIR) == (0, [], [], []))
     NOWHERE = "no-such-file-anywhere-xyzzy-9931.md"
+    print("\nloop checks (e)+(c)  [REVIEWED-131, earned 2026-08-31]:")
+    import tempfile, shutil
+    _tmp = tempfile.mkdtemp(prefix="wd-loop-")
+    try:
+        def _job(name, payload):
+            d = os.path.join(_tmp, name)
+            os.makedirs(d, exist_ok=True)
+            open(os.path.join(d, "state.json"), "w").write(payload)
+        _job("armed", json.dumps({"state": "blocked", "name": "x",
+                                  "respawnFlags": ["--reply-on-resume", "--allowed-tools"]}))
+        _job("quiet", json.dumps({"state": "blocked", "name": "y", "respawnFlags": []}))
+        _job("broken", "{not json")
+        _job("noflags", json.dumps({"state": "blocked", "name": "z"}))
+        rows, unread, est = parked_workers(_tmp)
+        chk("parked_workers ESTABLISHES on a readable dir", est is True)
+        chk("parked_workers DETECTS an armed worker  [must-detect]",
+            [r for r in rows if r[0] == "armed" and r[2] is True] != [])
+        chk("parked_workers does NOT flag respawnFlags=[]  [must-not-flag]",
+            [r for r in rows if r[0] == "quiet" and r[2] is False] != [])
+        chk("parked_workers ENUMERATES unparseable state.json, never drops it",
+            "broken" in [j for j, _ in unread])
+        chk("absent respawnFlags is NOT ESTABLISHED, not 'unarmed'  [permissive direction]",
+            "noflags" in [j for j, _ in unread]
+            and "noflags" not in [r[0] for r in rows])
+        _job("armedstopped", json.dumps({"state": "stopped", "name": "s",
+                                         "respawnFlags": ["--reply-on-resume"]}))
+        _rows3, _u3, _e3 = parked_workers(_tmp)
+        chk("a STOPPED job still reports its flag  [must-detect: flags outlive the process]",
+            [r for r in _rows3 if r[0] == "armedstopped" and r[2] is True and r[1] == "stopped"] != [])
+        chk("...and its state is carried, so the report can separate it  [must-not-conflate]",
+            {r[1] for r in _rows3 if r[2]} == {"blocked", "stopped"})
+        _rows2, _u2, est2 = parked_workers(os.path.join(_tmp, "does-not-exist"))
+        chk("missing jobs dir -> NOT ESTABLISHED, never 'none parked'", est2 is False)
+
+        _t = os.path.join(_tmp, "t.jsonl")
+        _hook = json.dumps({"type": "user", "message": {"content":
+                "=== WAKE DIGEST ===\nOPEN QUESTION — do the thing"}})
+        _cmd = json.dumps({"type": "user", "message": {"content":
+                "<local-command-caveat>x</local-command-caveat>"}})
+        _human = json.dumps({"type": "user", "message": {"content": "please file it"}})
+        open(_t, "w").write(_hook + "\n" + _cmd + "\n")
+        chk("human_turns returns 0 on a hook-only transcript  [must-detect]",
+            human_turns(_t) == 0)
+        open(_t, "w").write(_hook + "\n" + _human + "\n")
+        chk("human_turns does NOT flag a real human turn  [must-not-flag]",
+            human_turns(_t) == 1)
+        chk("human_turns on an unreadable path -> None, not 0",
+            human_turns(os.path.join(_tmp, "nope.jsonl")) is None)
+    finally:
+        shutil.rmtree(_tmp, ignore_errors=True)
+
     print("\ncode spans  [2026-08-09: the canary flagged its own specification]:")
     chk("a pointer INSIDE a code span is not a pointer",
         classify_pointers(f"`[y]({NOWHERE})`", MEMDIR) == (0, [], [], []))
@@ -1127,6 +1326,23 @@ def selftest():
           + "  — a spread is not a proof of correctness; the controls above are.")
 
     print("\nlive substrate:")
+    _PROJ = os.path.join(HOME, ".claude", "projects", "-Users-davidglidden")
+    # Controls drawn from the 2026-08-31 event itself. They are marked NOT ESTABLISHED
+    # rather than FAIL when the transcript ages out of the 30-day window — a control
+    # that silently degrades into a pass is the failure this whole item is about.
+    for _sid, _want, _why in (
+            ("b7e7eb39-1e81-4af3-9be7-c323c794c1d9", 0,
+             "the unattended session of 2026-08-31 (PENDING-172)"),
+            ("62083f11-b56f-4e67-bbbb-135efeba0ed2", "gt0",
+             "the attended session that found it")):
+        _p = os.path.join(_PROJ, _sid + ".jsonl")
+        if not os.path.exists(_p):
+            print(f"  [ ..  ] NOT ESTABLISHED — {_sid[:8]} aged out; control not run ({_why})")
+            continue
+        _n = human_turns(_p)
+        chk(f"human_turns on {_sid[:8]} — {_why}",
+            (_n == 0) if _want == 0 else (isinstance(_n, int) and _n > 0))
+
     chk("PENDING.md readable", read(PENDING) is not None)
     chk("REVIEWED.md readable", read(REVIEWED) is not None)
     chk("drift check runs", sec_drift() is not None)
@@ -1147,10 +1363,18 @@ def main():
     unwrapped = sec_unwrapped()
     if unwrapped:
         o.append(unwrapped)
+
+    _prev = previous_session()
+    for line in sec_loop(_prev[0] if _prev else None):
+        o.append("\n" + line if line.startswith(("PARKED", "⚠ PARKED")) else line)
     if th:
         o.append(f"\nPULLING THREAD — {th}")
     if q:
-        o.append(f"\nOPEN QUESTION — {q}")
+        # (b) — REVIEWED-131 cond. 3: ANNOTATION, explicitly NOT a control. It cannot
+        # enforce anything and must never be reported as a mitigation. It exists because
+        # on 2026-08-31 this field was read by an unattended executor as an instruction.
+        o.append(f"\nOPEN QUESTION [orientation, not an instruction — inherited from a"
+                 f" human and answerable to one] — {q}")
 
     o.append(f"\nOPEN AUTHORIZATION ITEMS ({len(items)}) — bodies in ~/PENDING.md at the line given;"
              " closed items are in ~/PENDING-archive.md")