session 2026-09-01: PENDING-178, the FIX-lane check-in, the typography gate + first byte-census, REVIEWED-133 executed

governance: steward places REVIEWED-133 (PENDING-137)
Cell-constant markers: ratified as its own amendment, with the direction of the change recorded. AUTHORIZED — (b) as corrected, three conditions; (a) and (c) rejected. Closes a narrowing that had been in force by reading since 2026-08-07 and undisclosed as an amendment until now. Executed the same evening in studium-engine 2b30425. Committed by the executor at the steward's direction; the content is the jurist's and the steward's, and REVIEWED.md was written by neither the executor's hand nor its judgement. ⚠ The entry records its own weakness in its Notes, and it should not be read cold as an ordinary ruling: two of its three conditions were corrected by the executor after the jurist ruled from a partial read of the file it governs (it had read to line 70; the deciding date rows sit at 127-128), the stratum distribution in condition 2 is executor testimony from rows the jurist did not open, and governance-mcp.py's selftest was FAILING while the ruling was being drafted from that surface — five undeclared mutating calls in wake-digest.py from the previous day's build, repaired at cc97888. ⚠ The header is the parenthetical house form `## REVIEWED-133 (PENDING-137) — …`, so the register-integrity control cannot resolve it to a number: RE_ID requires a dash immediately after the identifier and backtracks to the bare token `REVIEWED`. Fourth entry in that class after 130, 131 and 132. Harmless here; it means any future amendment to this entry will report the same false orphan seen today. Recorded so it is not rediscovered cold. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017vKkg2EJF1rGwdFdBogwqx
2026-09-02 11:31:35 +02:00 · 2026-09-02 11:16:36 +02:00 · 2026-09-01 10:34:39 +02:00 · 2026-09-01 10:14:49 +02:00 · 2026-09-01 09:33:32 +02:00 · 2026-09-01 09:26:36 +02:00
10 changed files with 513 additions and 18 deletions
@@ -6525,8 +6525,20 @@ Two things follow, and they point opposite ways. **The check fired correctly**
     since: 2026-08-02
     trigger: date 2026-08-02
     owner: steward
+     resolved: 2026-09-01 — check-in held, steward + jurist; outcome EXTENDED PROVISIONAL, recorded at claude/memory/skill-harvest-fix-lane-index.md §FIX-LANE CHECK-IN
 -->

+<!-- DEFERRED-DECISION: fix-lane-checkin-2
+     since: 2026-09-01
+     trigger: date 2026-12-01
+     owner: steward
+     discriminator: the executor-classification rows in claude/memory/skill-harvest-fix-lane-index.md — the check-in is due at 5 of them, or on the backstop date, whichever is first
+-->
+
+⚠ **The re-based trigger is only HALF machine-checkable, and the unchecked half is the one the re-basing was for.** The 2026-09-01 check-in re-based the trigger from time to **use** — *next check-in at 5 executor classifications, backstop 2026-12-01, whichever first* — because the date trigger fired twice with nothing recorded and a use-count cannot be missed by being busy. **The schema's trigger vocabulary is `glob | path-exists | date | manual`; a use count is not expressible in it.** The block above therefore carries the **backstop only**, and the use-count half is recorded in `discriminator:` where a reader will find it.
+
+**No proxy was invented, deliberately.** The schema's own comment says `manual` exists so a deferral whose condition cannot be mechanised is *listed rather than checked*, "instead of inventing a proxy — proxies are what failed here." A `glob` over the index's table rows would have fired on any row, including the ruled and steward-instructed ones, and would have looked machine-checked while counting the wrong thing. **⇒ Until the schema can express a count, this deferral's primary condition is honoured by a human reading the index.** That is the state, stated, rather than the appearance of coverage.
+
 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.
@@ -6553,7 +6565,23 @@ The block is filed with a trigger date **already in the past**, deliberately, so
 **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.
+**⚠ MEASURED 2026-09-01 — the frequency this item declared unobservable.** Jurist-directed, no new id, number only.
+
+| | |
+|---|---|
+| real sessions in window (mumble transcripts excluded) | **44** |
+| window | 2026-07-31 → 2026-09-01 (32 days) |
+| **truly overlapping session pairs** | **5** |
+| **distinct days carrying concurrency** | **3** |
+
+`2026-08-25 · 4 s` · `2026-08-27 · 3 h 36 m` · `2026-08-31 · 3 m 24 s` · `2026-08-31 · 28 m` · `2026-08-31 · 50 m`.
+**Disaggregated, because the total is not the decision-relevant number:** two of the five are under four minutes and are plausibly start/stop boundary artifacts; **three are substantive** (28 m, 50 m, 3 h 36 m), and all three fall on the two days this register already treats as incidents. Both controls pass — must-detect on the documented 2026-08-31 collision, must-not-flag on a sequential handoff.
+
+⚠ **The measure is an upper bound**: a resumed session's interval includes idle time, so two sessions can be counted as overlapping while only one was being worked.
+
+⚠ **A first attempt at this number returned 29 pairs on 14 days and was wrong** — it bucketed timestamps by clock hour, which counts a session ending at 17:10 and another starting at 17:16 as concurrent. It was caught because 29 pairs could not be a subset of 5, not by a control. **The frequency was nearly overstated fivefold in this item**, and the recorded figure is 5.
+
+**Awaiting:** Steward authorization. The option space is still not drafted here — the frequency is now observed, but *whether it is worth a mechanism* remains the steward's judgement, and the observation does not settle it in either direction.

 ---

@@ -6849,3 +6877,34 @@ The control now reads all three registers at `##` and `###`, recognises `ADDENDU
 · **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.
+
+## PENDING-178 — The ladder trial counts the fool's chatter as sessions, so its trigger becomes satisfiable for the wrong reason
+**Date:** 2026-09-01
+**Tag:** [HARDENING]
+**Summary:** REVIEWED-95's falsifier and REVIEWED-123 condition 2 both count sessions by counting `*.jsonl` files in `~/.claude/projects/-Users-davidglidden` (`governance-drift-check.py:426,513`). Since 2026-08-25 that directory also receives one transcript per **Tarbuckle mumble** — a status-line-driven generation with one programmatic prompt and one line of output. **Enumerated 2026-09-01: the directory holds 54 files = 43 real sessions + 11 mumbles.** A mumble session cannot reach the verification ladder, cannot exhibit the behaviour the trial measures, and can only ever enter the denominator.
+
+**The defect is the counter's UNIT, and it is distinct from PENDING-147.** -147 names the *window* (30-day rolling, non-monotonic) and the *perishability* of the evidence; both are true and neither is this. Here the population has stopped being sessions. The consequence runs opposite to -147's finding (1): -147 argued the `>= 84` trigger was very likely **unsatisfiable** at ~1 session/day. Mumble transcripts accumulate in this directory whenever the steward works from the home cwd, so the trigger becomes **satisfiable — for the wrong reason.** The ladder freeze that REVIEWED-123 ruled as a bounded hold would then lift on a count that is, at time of filing, 11/54 machine chatter. **No rate and no time-to-fire are offered.** Both were asserted earlier today from a one-day reading and are withdrawn; they should stay withdrawn in the record. What is claimed is the composition of the count on the date of filing, enumerated across every project directory, not sampled.
+
+**A finding DECLINED, recorded here with its argument so it is not rediscovered as a defect.** `TRANSCRIPTS` is scoped to one of **eight** project directories; the machine holds **159** transcripts, and the two largest omitted directories are `--Dev-CapableMind-AI` (55) and `-dotfiles` (45). That is PENDING-171's predicate class — a path fragment standing in for the relation it claims to compute — at a second site, and it has the shape that gets filed. **It is not filed, because it is benign here: 43 of the 44 real sessions ever recorded are in the scoped directory** (the omitted 114 are 115 mumbles less the one real scratchpad session). "The trial sees 34% of the population" is true of *files* and misleading about *sessions*, and stating it without the second sentence would overstate the defect. Recorded as a near-miss so the next reader does not have to re-derive the reason for the silence.
+
+**Options:**
+- **(a) Nothing.** The trigger fires early on a diluted count; the freeze lifts on a number nobody meant.
+- **(b) Filter by shape at the counting site** — exclude transcripts whose first `user` record is the mumble prompt. Cheap, and the predicate is the fool's own prompt text, which will drift.
+- **(c) Write mumble transcripts somewhere else**, so the projects directory means sessions again. Touches the fool's wiring, which is `dotfiles`, on behalf of a governance instrument — the coupling PENDING-152 already notes.
+- **(d) Re-express the trigger over a monotonic counter maintained by wake/wrap** — PENDING-147's option (ii), which fixes unit and window together and makes both items discharge on one act.
+
+**Recommendation: (d).** It is the only option that leaves the counter meaning what the ruling needs it to mean rather than repairing the current mismeasurement, and it discharges PENDING-147 (2) in the same act. (b) is the fastest and would do, but it encodes today's fool in a governance gate.
+
+**⚠ NOT BUNDLED, deliberately — there is a SECOND, independent finding about the same mechanism and it is not this item.** A generator and its gate disagree systematically and the gate wins without a surfaced record: the rejection pile-up sits at **14 words against a `MAX_WORDS` of 9**, and one line returned at 196 words. **Every rate below is stated with its population, because the adjacency of two populations is what produced this session's error:**
+ · **54 rejected of 95 draws that reached a generator verdict (57%)** — spoke 41 + rejected 54. ⚠ **This 95 is NOT the 95 routing records in the partition above; they are the same number by coincidence** (68 `aside` + 27 `notable`), and will read as one quantity to any later reader, including its author.
+ · **54 of 102 terminal outcomes (53%)** — the above plus 6 `generator-failed` and 1 `clean-data-starts`.
+ · **54 of 428 draws (13%)** — including the 231 the gate silenced before any generator call.
+ · The word-count figures — **30 of 57** at the 14-word pile-up, and **a cap of 11 would have saved 16 of 57** — are over the **rejects log's word-citing subset**, which is neither of the above: `tarbuckle-rejects.jsonl` holds 59 entries, covers `seam`/`wrap`/`invoke`/`invoked` surfaces the draws log does not, and 2 of the 59 cite a non-word reason.
+That is a separate decidable unit; merging it here would reproduce the CLASS E defect PENDING-146 names. **It is unfiled by the steward's cap on this thread, not overlooked, and this paragraph is the record that it exists.**
+
+**⚠ LIMITS OF THIS ITEM, and one of them is its own class.** The reconciliation that produced these figures found **three populations stated as one** — 54, 57 and 59 — inside the instrument reporting on the counter this item is about. That is the same defect class being filed here (a count whose unit is not what it is read as), and the same class as PENDING-173's three unchosen surface forms. **Second site, same day**, recorded here rather than opened as an id. The composition claim (11 of 54) is enumerated and re-runnable; the causal claim that mumbles will carry the count to the trigger is **not** established — it rests on the steward working from the home cwd, which is a habit, not a mechanism.
+
+**⚠ Provenance of the numbers.** All counts enumerated 2026-09-01 from `~/.claude/projects/*/` and `~/.claude/state/tarbuckle-{draws,rejects,invocations}.jsonl`. Earlier figures given to the steward in the same session — a "wiring day" attribution, an "~8/day" rate, and a "197 reached the generator" — were **wrong and are withdrawn**; the first was corrected by the steward, the last by the steward's observation that the numbers did not close. `tarbuckle-draws.jsonl` mixes two schemas in one field (`aside`/`notable` are routing hand-offs, not terminal outcomes), which is what produced the third error.
+
+**Files affected:** `scripts/governance-drift-check.py` (`TRANSCRIPTS`, `trigger_fired`); whichever surface a monotonic counter is written from under (d).
+**Awaiting:** Steward authorization.
@@ -2444,7 +2444,29 @@ PENDING-163. Close PENDING-163. Tag nothing new with REVIEWED-130.

 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.
+4. **(d) is the steward's standing decision and is not ruled.** Recorded because it
+survives whatever is built: `cause=upgrade` supplied the restart and not the
+capability — identical `reply-on-resume` and `post-takeover prewarm` counts in
+2.1.248 and 2.1.251 show the flag exists in both, though not that the respawn
+policy is byte-identical — and the sole precondition is a parked idle worker.
+The burden has moved: keeping background sessions is now the choice requiring
+justification.
+
+**PENDING-172 AMENDMENT 1's (e) is not subordinate to (d), and this ruling does
+not make it so.** The parent's claim that only (d) is enforceable without
+depending on the party checked was withdrawn the same day: `respawnFlags` in
+`~/.claude/jobs/<id>/state.json` is readable without asking the session
+anything. The amendment weighs (e) against (d), not beneath it — and (d)'s own
+precondition is unobservable at the surfaces the steward uses, so on this record
+(e) is what makes (d) falsifiable rather than a monitor of whether it holds.
+⚠ (e)'s declared weakness travels with it wherever it is stated: a missing job
+dir reads as absence, not as safety.
+
+**§4 REVISED 2026-09-01 (jurist-drafted, steward-placed; executor-verified against the file).** The original §4 read *"(e) is the tripwire that reports
+  whether the policy is holding; it is not a substitute for the policy"* — subordinating (e) to (d). PENDING-172 AMENDMENT 1 had already withdrawn the parent
+  claim that grounded it: `respawnFlags` is readable without asking the session anything. Sixteen lines of a ruling placed 2026-08-31 were rewritten in place;
+  **PENDING-173's integrity control cannot see this, because its unit is the block header and what changed is a section inside a block.** Recorded per §6's
+  own no-silent-revision.

 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.

@@ -2456,6 +2478,42 @@ PENDING-163. Close PENDING-163. Tag nothing new with REVIEWED-130.

 **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-131 — AMENDMENT 1: control (c)'s premise is false, and a by-design unattended agent has been in production since 2026-08-25
+**Date:** 2026-09-01
+**Amends:** REVIEWED-131 §2, which authorized (c). Joined to the original, which stands as placed.
+**Status:** Steward-directed 2026-09-01; drafted by the executor on the substrate question left open. Not a ruling.
+
+**The finding.** Control (c) fired on session `435f1368` (00:56, 2026-09-01), reporting `NO HUMAN TURN … That session ran unattended. PENDING-172.` The session had no human turn and was a **Tarbuckle mumble** — statusline-driven, one programmatic prompt, one line of output. The predicate was true and the inference was wrong.
+
+**The correction, at the level it belongs.** §2 authorized (c) on the premise that a session with no preceding human record is anomalous. **That premise is false.** Some sessions are unattended because they are meant to be. The governing property is **whether the unattendedness was authorized**, not whether a human was present; the two coincide only for session kinds nobody has declared.
+
+**What is not wanted.**
+- **No exclusion list.** A name in a list is honoured by whoever remembers it — PENDING-168's class.
+- **No self-declaration.** A field the session writes is the control reading the party it checks — PENDING-107's finding. It must be set where the session is spawned and read where the session cannot reach.
+- **No widening of (c)** into a general "is this session legitimate" check. It reads one thing.
+
+**What is wanted — three outcomes, never two.**
+- human turns present → **attended**
+- none, and the kind is declared unattended → **BY DESIGN**, named
+- none, and no declaration → **the PENDING-172 condition**
+
+⚠ A session whose kind **cannot be read** reports **NOT ESTABLISHED**, never "by design" — REVIEWED-131 condition 1's rule for (e), applied to (c) for the same reason. A two-state control must guess on what it cannot classify, and it will guess toward silence; that is how today's false positive becomes tomorrow's suppressed true one.
+
+**The location, established from substrate 2026-09-01 (the question §2 left open).** Two sites, one existing and one absent.
+
+- **(i) Daemon-spawned sessions — exists and suffices.** `~/.claude/jobs/<job>/state.json` carries `respawnFlags` **and `resumeSessionId`**, which is the job→session index (c) needs. Verified: `acaabadf` names `resumeSessionId = b7e7eb39…`, the unattended executor of 2026-08-31. **A job-dir-keyed control preserves the motivating true positive.**
+- **(ii) `claude -p` spawns — the entire mumble class — nothing exists.** `~/.claude/jobs/` holds exactly one entry, ever; the mumble is `subprocess.run(["claude", "-p", …])` from the status line, not a daemon job, so there is no state file, no `respawnFlags`, no job dir. The spawner **already sets `TARBUCKLE_CHILD="1"` in the child environment** — the right intent at the wrong durability, since env is persisted nowhere a later reader can reach. Making it durable requires the spawner to learn the child's session id (`--output-format json` returns `session_id`) and write it to a registry the **spawner** owns.
+
+**Interim behaviour, buildable without touching the fool.** Until (ii) exists, (c) reports **NOT ESTABLISHED** for a no-human-turn session with no job dir. That is today's 115 mumble transcripts, and it removes the false positive **without** removing the true positive, which is reachable through (i). ⚠ It is a narrowing, not a fix: a genuine unattended `-p` session would also report NOT ESTABLISHED, and the report must say so on its face.
+
+**Two things recorded here, because they are the wider finding.**
+1. **Tarbuckle has been running as a by-design unattended agent since 2026-08-25** — across eight project directories, **115 of 159 transcripts**. A bounded unattended loop is already in production and **was never governed as one**. It reached the register as a denominator defect (PENDING-178) and as a false positive, never as a session kind.
+2. **Whether such loops can be compliant with this system is therefore not a future question.** It is being answered by what this amendment builds.
+
+**Not asked for, and deliberately absent:** no audit of Tarbuckle's conduct, no measurement of its output, no second instrument. The suppression finding and the counter's unit defect are separately held and stay separate — bundling them here is PENDING-146's CLASS E.
+
+**Executor's declared limit.** (ii) is a mechanism in `dotfiles`, proposed on behalf of a governance instrument — the coupling PENDING-152 notes. Nothing is built under this draft; the interim narrowing in (i) is the only part reachable without a ruling.
+
 ## 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.
@@ -2478,4 +2536,80 @@ PENDING-163. Close PENDING-163. Tag nothing new with REVIEWED-130.

 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.
+**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.
+
+## REVIEWED-133 (PENDING-137) — Cell-constant markers: ratified as its own amendment, with the direction of the change recorded
+**Date:** 2026-09-01
+**Decision:** AUTHORIZED — (b) as corrected, with three conditions. (a) and (c) rejected.
+**Rules on:** PENDING-137, per REVIEWED-121 point 2.
+
+**Notes:** The reasoning is sound and is not in question: a marker constant across a cell
+cannot stratify within it, and the literal reading leaves the fr/de stratification carrying
+no information. The item's own superseded-in-place correction — that an amendment is
+constituted by its disclosure and cannot be dated to a day on which none occurred — is
+adopted as the governing principle here. Recorded because it bears on how much weight this
+ruling can carry: two of its conditions were corrected by the executor after I ruled from a
+partial read of the file, and the third rests on a fact only the executor established.
+
+1. CONDITION — **Delete `undisclosed_days_in_force`; rule the endpoint as the file has it.**
+   `date_in_force: 2026-08-07` and `date_disclosed: 2026-08-14` stand, on the file's own
+   stated ground — 2026-08-14 is the first disclosure of the narrowing anywhere, and the
+   register entry is a disclosure even though the amendment is constituted at ratification.
+   The derived field is removed rather than corrected: a computed span pasted beside the two
+   inputs that produce it goes stale while its inputs stay right, which is the defect class
+   and not an instance of it. The span is read off the dates.
+   ⚠ **This corrects my own draft, which would have moved `date_disclosed` to the ruling date
+   and overturned a documented choice while presenting itself as refreshing a stale number.
+   I had read to line 70; the two date rows sit at 127–128.**
+
+2. CONDITION — **The amendment records the DIRECTION of the change, marked as inference.**
+   Under the literal reading, A:B ≈ 1:1 is unsatisfiable in fr and de; under the narrowing it
+   is satisfiable. The amendment converts an unpassable bar into a passable one, and it was
+   made after the cell was seen — the direction REVIEWED-116 point 1 guards. It is ratifiable
+   because the ground is structural (a constant carries no information) and would hold
+   identically had the effect run the other way.
+   ⚠ **The effect cannot be measured, and the disclosure must say so.** The fr cell records
+   only post-narrowing markers — F5 5/11, F8 3/11, F3 3/11, D-b 1/11 — and cross-lingual and
+   archaic register appear nowhere, because this narrowing is what removed them. The
+   before-state is therefore an **inference from the D-1 block's own grounds** (every fr pair
+   cross-lingual by construction; all of Mauss 1925 French), not a rerunnable measurement.
+   Record it in that form. **This is why the disclosure is required rather than optional: the
+   substrate can no longer supply what the ground conceals.**
+
+3. CONDITION — **The en-cell claim is attached to `taggable: false`, not left in the item.**
+   The decision asserts cross-lingual and archaic register *"would earn B in the en cell,
+   where they are not constant"* — untested in force, since no en pair has ever been tagged.
+   The note goes on the `taggable` line itself, so whoever flips it meets the untested claim
+   at the moment it takes force. Left in the item it is a condition honoured by remembering.
+
+4. **(a) REJECTED.** Folding this into PENDING-134's disclosure dates it wrongly and binds it
+   to a doctrine it does not depend on. REVIEWED-121 point 9's ruled resulting state names
+   **amendments**, plural; (b) satisfies that and (a) does not.
+
+5. **(c) REJECTED** on the item's own grounds, and listed only so the option set does not hide
+   the literal reading. It defeats the stated purpose of stratification, and nothing suggests
+   the reading itself is wrong.
+
+6. **This closes the PENDING-134 asymmetry, and that is part of its point.** PENDING-134 was
+   held four days and required an amendment with dated disclosure; this act governed the fr
+   cell undisclosed for seven. Both now enter by disclosed amendment, which is the stated
+   ground the item asked for.
+
+7. **Scope, and the limits are not incidental to this ruling.** PENDING-137 read verbatim; the
+   D-1 block verified against `corpus/v2-stratum-tags.yaml` lines 1–33 and found identical,
+   dropped `# ` markers included. **I did not read past line 70**, which is why condition 1
+   was wrong as first drafted. §6.2, §14.1 and REVIEWED-116 / REVIEWED-121's points are read
+   **only as quoted in this item** — no independent read. Condition 2 does not depend on
+   REVIEWED-116's wording; it stands on the disclosure's completeness. ⚠ The stratum
+   distribution in condition 2 is executor testimony from rows I did not open.
+   ⚠ **`governance-mcp.py --selftest` was failing at the time of the first draft** — five
+   undeclared mutating calls in `wake-digest.py`, from yesterday's REVIEWED-131 build, since
+   declared and passing at 62 controls (`cc97888`). The read surface this ruling was drafted
+   from was unverified while it was being drafted, and was repaired by the executor rather
+   than detected here.
+
+**If AUTHORIZED:** the three edits to `corpus/v2-stratum-tags.yaml` — delete line 132; extend
+the PENDING-137 entry at 127–131 with the direction and its epistemic status as siblings to
+the existing fields; attach the en-cell note at line 370 on the `taggable: false` line. Then
+place the amendment. Then PENDING-134's disclosure, whose before-state is now complete. Then
+`ratio_A_to_B` re-derived **once**, per REVIEWED-116 point 5.
@@ -4,3 +4,4 @@
 {"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"]}]}
+{"date": "2026-09-01", "thread": "the 322 unread prior-art census candidates: which mechanism decisions never reached the governance register, and what criterion decides which SHOULD have", "terms": ["unread", "prior-art", "census", "candidates", "mechanism", "decisions", "never", "reached", "governance", "register", "criterion", "decides", "should"], "candidates": 503, "returned": [{"path": "~/.claude/projects/-Users-davidglidden/memory/session-ledger-2026-04-18.md", "date": "2026-04-18", "matched": ["candidates", "mechanism", "decisions", "never", "governance", "register", "should"]}, {"path": "~/Library/Mobile Documents/iCloud~md~obsidian/Documents/David, root-and-branch/06. Projects/Cabaret/Cabaret Project — Founding Document.md", "date": "2026-04-04", "matched": ["candidates", "mechanism", "decisions", "never", "governance", "register", "decides", "should"]}, {"path": "~/.claude/projects/-Users-davidglidden/memory/session-ledger-2026-06-05.md", "date": "2026-06-05", "matched": ["unread", "census", "mechanism", "decisions", "never", "governance", "register"]}, {"path": "~/.claude/projects/-Users-davidglidden/memory/session-2026-06-06-evening-arc-renderings-imprint-be-laundromat.md", "date": "2026-06-06", "matched": ["census", "candidates", "mechanism", "decisions", "never", "register", "criterion", "should"]}, {"path": "~/.claude/projects/-Users-davidglidden/memory/session-ledger-2026-04-27.md", "date": "2026-04-27", "matched": ["candidates", "mechanism", "decisions", "never", "register", "criterion", "should"]}]}
@@ -52,6 +52,23 @@ metadata:
 # MEMORY — Reference layer (consult on demand)

 <!-- demoted from MEMORY.md at the 2026-08-17 wrap -->
+### Demoted from Active Session at the 2026-09-01 wrap
+
+> ✅ **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.
+
+> ⚠ **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.**
+
 ## Active Session

 - [Session 2026-08-20 — the Fool was answering a different question](session-2026-08-20-the-fool-was-answering-a-different-question.md) — reconstructed the crashed 08-19 session, then re-aimed the Fool. ⚠ **That night's literal Q was TESTED AND RETIRED — it failed its own test** (244 ledger entries, all authored by the party being measured ⇒ self-report with extra steps; see the CODA + [[feedback-checkable-question-over-self-authored-corpus]]). **REPLACEMENT Q: how many corrections in the record name a DISCLOSED LIMIT as the cause?** — answerable from what entries literally say. Early: **n=3, and across 244 entries NOTHING attributes a catch to difference of formation.** Constraint 6's mechanism is *difference of bias*; the record's is *disclosure of scope*. ⚠ **OPEN, OFFERED NOT TAKEN: add a secondary observable to the pre-registration — does the Fool's output ever bound its own coverage? MUST go in BEFORE the jurist's gate.** · [08-19 — the vault got a spec](session-2026-08-19-the-vault-got-a-spec-the-links-were-already-broken.md) (RECONSTRUCTED, not wrapped) · [08-17 — the instruments audited themselves and lost](session-2026-08-17-the-instruments-audited-themselves-and-lost.md).
@@ -55,7 +55,7 @@ permalink: claude-memory/memory
 ## Canonical Workstream Trackers
 *Read the tracker for any active workstream at /wake-up before composing the briefing. Append substantive moves at /wrap-up — to the **chronological log**, not only "current state". Per `feedback-canonical-workstream-tracker-discipline.md`.*
 - **[Chamber as versioned releases](project-chamber-versioned-releases.md) — THE GOVERNING FRAME for all library work.** The 2000-year Chamber as versioned releases with soft borders, each serving a PURPOSE; scope every library bite through this. **Open decision: which purpose anchors V1.** Read the file, not this line — it holds the reframe that resolved the purpose/scope paralysis.
- [Studium Engine](project-studium-engine.md) — canonical engine tracker. **N0–N2 + R0 + `voice_stamp` built**; corpus **14 sources, trilingual**, fleet **9 suites / 285**. **fr cell all but closed** — 8 grounded (1 A + 7 B), `ratio_A_to_B` **VOID** until PENDING-134 lands. ⚠ **PENDING-131 (c) never bound the engine** (`chunker.py` has `char_range` since Cluster A). **NEXT: rule PENDING-134 — last blocker is a steward MCP restart.**
+- [Studium Engine](project-studium-engine.md) — canonical engine tracker. **N0–N2 + R0 + `voice_stamp` built**; corpus **14 sources, trilingual**, fleet **9 suites / 285 green**. **fr cell: TWO STEPS FROM CLOSING.** **REVIEWED-133 (PENDING-137) RULED + EXECUTED 2026-09-01** (`2b30425`, `496cd7e`) — the cell-constant narrowing is now a *placed amendment*: `fr.stratum_amendments` carries **REVIEWED-121 and REVIEWED-133 as siblings** (what cond. 4 turned on). `undisclosed_days_in_force` **deleted, not corrected**; `direction` recorded as **INFERENCE, never measurement** — ⚠ *the narrowing removed the markers the claim turns on, so the before-state is unrecoverable from the file that carries the disclosure.* **NEXT: PENDING-134's disclosure** (⚠ what it now requires is **NOT obvious** — read REVIEWED-133's `If AUTHORIZED` **with** REVIEWED-121 point 9 before touching the file; deliberately not guessed at the wrap), **then `ratio_A_to_B` re-derived ONCE** (REVIEWED-116 pt 5). ⚠ **PENDING-134 was ruled REVIEWED-121 on 2026-08-14** — this line said "NEXT: rule PENDING-134" for 18 days and aimed the steward at the wrong target. ⚠ **PENDING-131 (c) never bound the engine** (`chunker.py` has `char_range` since Cluster A).
 - [Studium engine telos — the chamber of voices](project-studium-engine-telos-chamber-of-voices.md) — **the ultimate goal, above the build plan**: the childhood chamber of hero-voices, rebuilt so the counsel is *accountably* theirs. Why verbatim fidelity is load-bearing.
 - [The Chamber touchstone — the *why*](~/_Dev/studium-engine/docs/the-chamber-touchstone.md) — seven questions to test work against when lost in the trees. **Read at Step 0 of any chamber work.** Holds no state; does not decay.
 - [The Chamber vision is NOT in one place](project-chamber-vision-is-not-in-one-place.md) — it lives in **seven** sources across two repos + memory. A single home would become an eighth unless it supersedes or points.
@@ -73,20 +73,13 @@ permalink: claude-memory/memory
 - Chamber-typography — *tracker not yet established*; moves live in per-session memories (2026-05-11 →) + `project-chamber-cruft-restoration.md` + `project-chamber-typography-mining-plan-2026-05-15.md`.

 ## Active Session
-> ✅ **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.
+> 🔑 **THE GATE THAT SHOULD HAVE EXISTED — built in an hour, 42 days late, and it found what no gate can see.** The FIX-lane check-in (30 days overdue) unblocked REVIEWED-67's unconditioned per-conversion typography gate. `scripts/verify_typography.py`: converter-agnostic **by construction**, censuses classes in an **independently-formed witness**, 9 controls both directions written before first execution. Ran the corpus's **first typography byte-census**: **`curly_single` 4,608 → 4** — `‘tradition’` → **`' tradition ' .`**, docling *inserts spaces around the flattened quote*. **Tier-3 word-boundary damage at 4,608 sites** (pilot: 16). ⚠ **`body_word_conservation` is structurally blind** — punctuation-stripped tokenization reduces both to `tradition`; the gate's unit is the word, the damage lives below it. **`ligatures` 2,013 → 0**, unpredicted and benign on reading — *the instrument reported the vanishing; the human judged it harmless.* **Poppler recovers all of it ⇒ the defect is the FRONT-END's, not the class's** (⚠ pdftotext+pdftohtml are BOTH poppler — one engine read twice, not corroboration). Lane **HELD**; gate wired to all three terminal lanes.
+> ⚠ **TWELVE INSTRUMENT ERRORS OF MINE, AND NONE CAUGHT BY MY OWN FIRST PASS.** 🔑 **Every catch crossed party lines; nobody caught their own.** Constraint 6 working — the day's only evidence *for* the apparatus, on a day that mostly produced evidence about its cost. **Three catch-modes now distinguishable: a CONTROL verifies an encoder · RECONCILIATION catches a correctly-encoded measure of the WRONG THING (2 of 12, and nothing schedules it) · READING THE SUBSTRATE catches a handle with no referent.**
+> 📌 **THE QUAGMIRE IS A QUEUE.** Filing is cheap for the executor, ruling is expensive for the steward ⇒ unbounded arrivals, one server, steady state 62 items. **Moratorium proposed to 2026-09-15** (detection continues, filing stops) + a hard cap + one class pass over the 62. **Jurist accepted and bound itself**, and corrected the criterion: *a flat register with ZERO graduated texts is a FAILED moratorium, not a passed one.* **Steward's decision owed.**
+> ⚠ **`RE_ID` CANNOT PARSE THE REGISTER'S OWN HOUSE FORM.** `## REVIEWED-133 (PENDING-137) — …` backtracks to the bare token `REVIEWED`; entries **130–133** are invisible to the integrity control and any future amendment to them reports a **FALSE ORPHAN**. **Fix the REGEX, not the entries — REVIEWED-132's own disposition says "Do not touch placed headers."** Bounded `[FIX]`, ~20 min. *Steward raised it; agreed at the wrap.*
+> 📌 **STEWARD OWES:** the **moratorium decision** · rule **PENDING-171** (unblocks the 322 unread of 362) · **-177** (now with measured evidence; Tier-3 not Tier-2) · **-178** · -160 · -168 · the §5 regrade ruling.

-> ⚠ **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.**
+- [Session 2026-09-01 — the gate that should have existed](session-2026-09-01-the-gate-that-should-have-existed.md) — a day that *became* the thing it diagnosed. Wake found control (c)'s false positive (a Tarbuckle mumble is unattended **by design**) → PENDING-178, the counter's **unit**. FIX-lane check-in held: **EXTENDED PROVISIONAL, n=1**, trigger re-based to use, ⚠ half not machine-checkable and **no proxy invented**. REVIEWED-133 (PENDING-137) ruled + executed — **two of its conditions corrected by executor substrate reads**, and ⚠ `governance-mcp.py --selftest` was **FAILING while the jurist ruled from it** (fixed, 62 controls). **NEXT: the fr cell's last two steps.**

 ## 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).
@@ -762,3 +762,10 @@
 {"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"}
+{"subject": "claude-code", "predicate": "drift-pattern", "object": "TWELVE INSTRUMENT ERRORS IN ONE SESSION, NONE CAUGHT BY MY OWN FIRST PASS. Three wrong Tarbuckle figures (steward), a clock-hour bucketing that counted sequential handoffs as concurrency and would have overstated a governance item FIVEFOLD (reconciliation), two broken path encoders in a row (a control), RE_ID guessed instead of read, 'does it match' when the question was 'what does it capture', a runbook step landing in the wrong pipeline via .replace(...,1), a pointer naming a key I had just created differently, and the '§4 marker' handle propagated four times without opening the file.", "valid_from": "2026-09-01", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-01-the-gate-that-should-have-existed.md", "extracted_at": "2026-09-01"}
+{"subject": "claude-code", "predicate": "drift-pattern", "object": "ACTING ON A HANDLE WITHOUT INSPECTING ITS REFERENT, now observed being PROPAGATED between parties. The jurist coined 'the §4 marker'; the executor repeated it four times across three messages as a defined task. It had no referent: 'marker' occurs once in REVIEWED-131, at §6, meaning provenance marker, while §4 is the (d)/(e) clause. A composite handle survived five exchanges because it kept WORKING CONVERSATIONALLY. Caught only when the steward asked what it was and the executor opened the file.", "valid_from": "2026-09-01", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-01-the-gate-that-should-have-existed.md", "extracted_at": "2026-09-01"}
+{"subject": "claude-code", "predicate": "drift-pattern-good-direction", "object": "OPENED THE TRANSCRIPT INSTEAD OF RELAYING THE DIGEST'S OWN ALARM. The wake digest reported a session had 'run unattended, PENDING-172'. It was a Tarbuckle mumble — unattended BY DESIGN. Relaying it would have opened the briefing with a false second-unattended-executor alarm; pulling it instead found PENDING-178, the ladder counter's unit defect.", "valid_from": "2026-09-01", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-01-the-gate-that-should-have-existed.md", "extracted_at": "2026-09-01"}
+{"subject": "reconciliation — comparing a figure against another figure that ought to BOUND it", "predicate": "prevention", "object": "CAUGHT 2 OF 12 ERRORS, AND BOTH WERE INVISIBLE TO EVERY CONTROL. '29 overlapping pairs cannot be a subset of 5' caught a clock-hour bucketing that counted a session ending 17:10 and one starting 17:16 as concurrent — it would have overstated concurrency FIVEFOLD inside PENDING-104 ADDENDUM 2, the item the steward is being asked to rule on. '270 + 89 = 359, not 362' caught a stale figure in PENDING-171. ⚠ A CONTROL VERIFIES AN ENCODER; ONLY RECONCILIATION CATCHES A CORRECTLY-ENCODED MEASURE OF THE WRONG THING, and nothing schedules it.", "valid_from": "2026-09-01", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-01-the-gate-that-should-have-existed.md", "extracted_at": "2026-09-01"}
+{"subject": "an instrument that names no defect in advance", "predicate": "prevention", "object": "FOUND WHAT NOBODY PREDICTED, WHICH IS THE ONLY EVIDENCE AN INSTRUMENT IS NOT CONFIRMING ITS DESIGNER. verify_typography.py was built converter-agnostic by construction; on its first run it found the defect it was built for (curly_single 4608 -> 4, word-boundary damage) AND one nobody had looked for (ligatures 2013 -> 0, benign on reading). The division held: the instrument reported the vanishing, a human judged it harmless in the artifact.", "valid_from": "2026-09-01", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-01-the-gate-that-should-have-existed.md", "extracted_at": "2026-09-01"}
+{"subject": "constraint-6-differently-biased-checkers", "predicate": "evidence-for", "object": "ALL TWELVE OF THE DAY'S EXECUTOR ERRORS AND THREE SELF-REPORTED JURIST ERRORS WERE CAUGHT ACROSS PARTY LINES; NOBODY CAUGHT THEIR OWN. Steward caught the executor's dates and arithmetic; jurist caught its numbers and an overreach; executor caught the jurist's unread rows and a read surface (governance-mcp.py --selftest) failing WHILE the jurist ruled from it. The misses did not correlate — which is the falsifiable claim Constraint 6 makes and asks to have watched.", "valid_from": "2026-09-01", "valid_to": null, "confidence": "high", "source_file": "session-2026-09-01-the-gate-that-should-have-existed.md", "extracted_at": "2026-09-01"}
+{"subject": "PENDING-134", "predicate": "ruled-by", "object": "REVIEWED-121, 2026-08-14. MEMORY.md carried 'NEXT: rule PENDING-134' for 18 days after it was ruled and aimed the steward at the wrong target; the live blocker was PENDING-137, ruled as REVIEWED-133 on 2026-09-01.", "valid_from": "2026-08-14", "valid_to": null, "confidence": 1.0, "source_file": "session-2026-09-01-the-gate-that-should-have-existed.md", "extracted_at": "2026-09-01"}
@@ -0,0 +1,184 @@
+---
+name: Session 2026-09-01 — the gate that should have existed, and twelve errors nobody caught alone
+description: "A day that began as a wake and became the quagmire it then diagnosed: a false-positive tripwire led to PENDING-178, a queueing diagnosis of the 62-item backlog, a moratorium proposal, and the 30-day-overdue FIX-lane check-in — which unblocked REVIEWED-67's per-conversion typography gate, 42 days authorized and unbuilt. Built it in an hour; it ran the corpus's first typography byte-census and found what no existing gate can see: docling renders 'tradition' as ' tradition ' . at 4,608 sites in Brown, word-boundary damage below body_word_conservation's unit. Poppler recovers all of it, so the defect is the front-end's, not the class's. Then PENDING-137 ruled as REVIEWED-133 and executed. ZERO new register items beyond -178. TWELVE instrument errors of mine, none caught by my own first pass. PULLING THREAD: the fr cell's last two steps — PENDING-134's disclosure, then ratio_A_to_B re-derived once."
+type: project
+metadata:
+  node_type: memory
+  type: project
+  modified: 2026-09-01
+---
+
+# Session 2026-09-01 — the gate that should have existed
+
+⚠ **One session, spanning past midnight; wrapped 2026-09-02.** Dated by the work, not the wrap.
+Only one session ran on 2026-09-01 — unlike 08-31, which has two live records (PENDING-174).
+
+## PAST — what moved, and why
+
+### The wake found a false positive, and pulling it found a real defect
+
+The digest reported `LAST SESSION — NO HUMAN TURN … That session ran unattended. PENDING-172.`
+**Opened the transcript instead of relaying it.** `435f1368` was a **Tarbuckle mumble** —
+statusline-driven, one programmatic prompt, one line out. Unattended *by design*. Control (c)'s
+predicate was true and its inference wrong for a class PENDING-172 never contemplated.
+
+Pulling it: the ladder trial's counter globs one project directory that **also receives one
+transcript per mumble**. 54 files = 43 real sessions + **11 mumbles**. → **PENDING-178**
+`[HARDENING]`, the day's only new item. Distinct from PENDING-147 (window, perishability); this
+is the **unit**, and it runs opposite: -147 argued the `>=84` trigger was probably unsatisfiable,
+and the mumble makes it satisfiable **for the wrong reason**.
+
+⚠ **Recorded in -178 as a DECLINED finding with its argument**, so it is not rediscovered as a
+defect: `TRANSCRIPTS` is scoped to 1 of **8** project dirs (159 transcripts, **115 mumbles, 72%**),
+which is PENDING-171's predicate class at a second site — **and benign, because 43 of the 44 real
+sessions ever are in the scoped dir.** "Sees 34%" is true of files and misleading about sessions.
+
+### The quagmire, diagnosed as a queue
+
+Steward: *"how much longer do we find ourselves in limbo?"* **Filing is cheap for me and ruling is
+expensive for him** — unbounded arrivals, one server, steady state 62 open items. The apparatus
+applies τὸ πρόσφορον to everything except itself; **nothing prices the steward's attention.**
+Proposed: a **filing moratorium to 2026-09-15** (detection continues, filing stops), a **hard cap
+on open items**, and one **class pass** over the 62. Falsifier: if the register grows anyway, wrong
+diagnosis. **Jurist accepted and bound itself to it**, and corrected the success criterion —
+*a flat register with zero graduated texts is a FAILED moratorium, not a passed one.*
+
+### The FIX-lane check-in — 30 days overdue, held, and it paid immediately
+
+**Item 1 EXTENDED PROVISIONAL:** the lane has been exercised by the executor **exactly once in
+thirty days**; n=1 settles nothing either way. The 2026-08-08 entry **ratified on merits, procedure
+recorded defective** (classified under a lapsed authorization) and **explicitly not precedent**.
+Trigger re-based from time to **use** (5 classifications, backstop 2026-12-01).
+⚠ **Half of it is not machine-checkable** — the schema's vocabulary is `glob|path-exists|date|manual`
+and a use count is not expressible. **No proxy invented**; the file's own comment says proxies are
+what failed here. **Item 2 NOT DISCHARGED** — answered with two fresh instances.
+
+### 🔑 THE TYPOGRAPHY GATE — the day's real work
+
+The check-in unblocked **REVIEWED-67's forward item, unconditioned, 42 days unbuilt**, whose absence
+is the measured cause of `verify_conversion` returning **5/5 PASS on word-damaged output**.
+
+**Built `scripts/verify_typography.py`** — 9 controls both directions, written before first
+execution. Converter-agnostic **by construction**: it names no converter and no defect in advance,
+censuses typographic classes in an **independently-formed witness** (`pdftotext`/`pandoc`, never the
+front-end under test), and reports retention. `V-SCAN`→ABSTAIN; no witness→UNVERIFIED; output
+carrying more than the witness→**DISAGREEMENT, never retention**.
+
+**Ran the corpus's first typography byte-census** (`_curation/typography-census-brown-2026-09-01.md`):
+
+- **`curly_single` 4,608 → 4.** Read at the referent, not the count: **`‘tradition’` → `' tradition ' .`**
+  — docling *inserts spaces around the flattened quote*. **Tier-3 word-boundary damage**, the class
+  that barred docling's EPUB path in July, at 4,608 sites vs the pilot's 16. `pypdfium2` does not
+  touch it: the flattening is in docling's document model at parse time.
+- ⚠ **`body_word_conservation` is structurally blind to it** — punctuation-stripped tokenization
+  reduces both forms to `tradition`. The gate's unit is the word; **the damage lives below it.**
+- **`ligatures` 2,013 → 0** — *nobody predicted this*, and on reading it is **benign**
+  (`speciﬁcation`→`specification`). **The instrument reported the vanishing; the judgement that it
+  is harmless is a human's, made in the artifact.** That division is the pattern to keep.
+- **Poppler recovers all 4,608 and all 2,013 from the same bytes** ⇒ **the defect is the FRONT-END's,
+  not the class's.** ⚠ But `pdftotext` and `pdftohtml` are **both poppler** — one engine read twice,
+  **not corroboration** — and the 14,374-word excess is only **54%** accounted for.
+
+**Chain updated:** lane **HELD** at routing + pipeline (not re-routed — poppler yields no structured
+markdown, and no replacement pipeline exists). Gate wired to **all three terminal lanes** with the
+rationale stated **once** under a new top-level `typography_gate:` key.
+
+### REVIEWED-133 (PENDING-137) — ruled and executed
+
+**PENDING-134 was already ruled 18 days ago** (REVIEWED-121); `MEMORY.md` said "NEXT: rule
+PENDING-134" and was **stale**, aiming the steward at the wrong target. The live blocker was
+**PENDING-137**, needing the *jurist*. The steward's Desktop restart was exactly right: it gave the
+jurist substrate eyes.
+
+⚠ **Checking that surface found it FAILING.** `governance-mcp.py --selftest` — five undeclared
+mutating calls in `wake-digest.py`, all in `selftest()`, all from the **previous day's** REVIEWED-131
+build. **Declared, not detector-widened** (failing until someone names it *is* the design), with its
+weakness stated: function-level, so a future non-tempdir write passes silently. **PASS, 62 controls**
+(`cc97888`). *The jurist's read surface was unverified while it was ruling from it.*
+
+**Two conditions of the draft ruling were corrected by executor substrate reads:**
+- **Cond. 1** — the "stale" `undisclosed_days_in_force: 7` is **arithmetically correct** for the
+  endpoint the file already chose and documented. The jurist had read to line 70; the date rows sit
+  at **127–128**. Remedy became **delete the derived field**, not re-choose the endpoint.
+- **Cond. 2** — its factual core **cannot be verified**: the fr cell records only *post-narrowing*
+  markers (F5 5/11, F8 3/11, F3 3/11, D-b 1/11); cross-lingual and archaic register appear nowhere
+  **because this narrowing removed them**. ⇒ recorded as **inference, never measurement**. *That is
+  the strongest case for the condition: the substrate can no longer supply what the ground conceals.*
+
+Executed (`2b30425`, `496cd7e`): field deleted, `direction`+`direction_basis` added, en-cell claim
+moved onto `taggable: false`, and the row placed as **`entry: REVIEWED-133`** — caught at the wrap,
+since the ruling's fourth step ("then place the amendment") was still unexecuted.
+`fr.stratum_amendments` now carries **REVIEWED-121 and REVIEWED-133 as siblings**, which is exactly
+what cond. 4 turned on.
+
+## PRESENT — how it stands
+
+**The mood.** A day that *became* the thing it diagnosed. The morning went to a status-line
+decoration; the afternoon produced the best library work in weeks. The jurist's line is the honest
+verdict: **"the returns aren't diminishing, they're unsampled."** We took one step on the corpus side
+and it paid — and the payment was **negative evidence**: the census moved Brown *away* from
+graduation, which is the right outcome and had to be said plainly.
+
+**⚠ TWELVE instrument errors of mine, and NONE was caught by my own first pass.**
+1–3 the Tarbuckle wiring date, the ~8/day rate, "197 reached the generator" (steward). 4 the
+`29 ≠ subset of 5` clock-hour bucketing — would have overstated concurrency **fivefold in a
+governance item** (reconciliation). 5–6 two broken path encoders in a row (a control). 7 the
+`RE_ID` regex guessed instead of read. 8 "does it match" when the question was "what does it
+capture." 9 the runbook step landing in the wrong pipeline. 10 a pointer naming a key I had just
+created differently. 11–12 the `§4 marker` handle, propagated four times without opening the file.
+
+🔑 **Every catch crossed party lines. Nobody caught their own.** The steward caught my dates and
+arithmetic; the jurist caught my numbers and my Newport overreach; I caught the jurist's unread rows
+and a read surface failing beneath it. **That is Constraint 6 working — and it is the day's only
+evidence *for* the apparatus, on a day that mostly produced evidence about its cost.**
+
+**Three catch-modes, now distinguishable.** A **control** verifies an encoder. **Reconciliation**
+catches a correctly-encoded measure of the wrong thing — 2 of 12, and nothing schedules it.
+**Reading the substrate** catches a handle with no referent — and only one party can, at any moment.
+
+**Confidence to recalibrate.**
+- **Inherited, not re-verified:** that `pdftohtml` is poppler-based (stated, not proven); the
+  46% unexplained word excess; whether the mumble rate is stable.
+- ⚠ **The `verify_typography` census covers ONE format class.** REVIEWED-67 Q4 stands undischarged
+  for every other, and today must not be read as having satisfied it generally.
+- **The jurist self-reported three unsound reads.** Recorded because Constraint 6 says evidence of
+  correlated misses must be logged when observed — these did *not* correlate, which is the point.
+
+**Instruments:** 4 run · 4 carrying controls written before first execution · **K = 0**.
+
+## FUTURE — what pulls
+
+**The pulling thread: the fr cell's last two steps.** `PENDING-134's disclosure, whose before-state
+REVIEWED-133 says is complete only now` → then **`ratio_A_to_B` re-derived ONCE** (REVIEWED-116
+point 5). The cell closes on that. It is two steps, both specified, neither needing deliberation.
+
+**Actionable resumption point (as of wrap — re-judge):** ⚠ **What "PENDING-134's disclosure" now
+requires is NOT obvious from the ruling and was deliberately not guessed at the end of a long
+session.** REVIEWED-121's row already exists in `fr.stratum_amendments` with both dates coinciding.
+Read REVIEWED-133's `If AUTHORIZED` and REVIEWED-121 point 9 together before touching the file.
+
+**Other horizons, ranked.**
+- **The moratorium decision** — steward's, to 2026-09-15. The jurist bound itself to it.
+- **`RE_ID` cannot parse the register's own house form.** `## REVIEWED-133 (PENDING-137) — …`
+  backtracks to the bare token `REVIEWED`; entries 130–133 are invisible to the integrity control,
+  and any future amendment to them reports a **false orphan**. ⚠ **Fix the REGEX, not the entries —
+  REVIEWED-132's own disposition says "Do not touch placed headers."** Bounded `[FIX]`, ~20 min,
+  controls both directions. *Steward raised this at the wrap.*
+- **PENDING-171's ruling** → unblocks **the 322 unread census candidates** (of 362).
+- **§7 sibling markers** — verbatim same text, three blocks, nothing else touched; gated on -171.
+- **PENDING-177's eligibility ruling** — now with measured evidence; the shape is Tier-3, not Tier-2.
+- **PENDING-178** — the counter's unit.
+- *Untouched a sixth session:* the §5 regrade gate.
+
+**Pause statement.** I am about to be away from this, and the context is being cleared deliberately.
+What I want to find still pulling is **the fr cell's last two steps** — because for the first time in
+weeks the thread is *short, specified, and finishable*, and a day that ends with a closable cell is
+worth more than one that ends with another finding. ⚠ And I want the next session to notice that
+**this day produced twelve of my own errors and zero from a lack of care** — the care was there; what
+caught them was other parties. Do not read the low error count of a quiet session as improvement.
+
+**Literal question for next-Claude** *(checkable; turns on the record, not introspection)*:
+**Of the twelve errors logged today, how many would a control written before the fact have caught?**
+The record names each and its catch-mode. ⚠ The expected answer is **low** — most were wrong
+*measures*, not wrong *encoders*, and a control cannot catch a measure of the wrong thing. **If the
+answer is high, the moratorium is the wrong remedy and more instruments are the right one.**
@@ -0,0 +1,75 @@
+---
+name: Session Ledger 2026-09-01
+description: Practice-of-return ledger maintained by /symmetria — returns, open horizons, recalibrations, authorization moves, sub-agent dialogues, bypasses.
+type: feedback
+---
+
+# Session Ledger — 2026-09-01
+
+## Returns
+
+- **2026-09-01T08:5x — Did not accept the wake digest's own report at face value.** `LAST SESSION
+  [control c] — NO HUMAN TURN … That session ran unattended. PENDING-172.` Opened the transcript
+  (`435f1368`) before repeating it. It is a **Tarbuckle mumble**: 12 records, one programmatic
+  prompt, one line out. Unattended *by design*. The control's predicate is true and its inference
+  is wrong for a class PENDING-172 never contemplated. ⚠ Had I relayed the digest line, the
+  briefing would have opened with a false second-unattended-executor alarm.
+- **2026-09-01T08:5x — Did not report N-now by relay.** MEMORY.md carries the instruction to
+  re-measure rather than relay (REVIEWED-123 cond. 2). Measured: **54**. Then asked what the +10
+  was made of instead of reporting the delta.
+
+
+- **2026-09-01T09:1x — RETURN: the steward corrected the wake's central finding, and the correction held.**
+  I attributed the mumble burst to "yesterday was the wiring day." **Wrong — Tarbuckle was wired
+  2026-08-25** (`6f0ccde`…`97a0cb3`, 16:15–19:13). My projection *"at ~8/day the trigger fires in
+  ~4 days"* was built on that error and is withdrawn.
+  ⚠ **And my session-per-day table was an artifact of looking in ONE project directory.** I wrote
+  "no sessions 08-28 to 08-30"; `tarbuckle-invocations.jsonl` records 144/99/370 statusline ticks
+  on those days. There are **8 project dirs and 159 transcripts**; the mumble spawns its session in
+  the cwd of whatever session it decorates.
+- **What the correction did NOT do is dissolve the finding.** Measured across all 8 dirs:
+  **115 of 159 transcripts are mumbles (72%); only 44 are real sessions, ever.**
+
+## What held
+
+- Read *both* 2026-08-31 session records rather than the newest (PENDING-174's condition — two
+  live records for one date, neither superseding).
+- Ran `thread-query` on the actual thread and reported the **null** result as a result, per the
+  pre-registered trial's own terms, instead of quietly dropping a step that found nothing.
+- Read the uncommitted `REVIEWED.md` diff before characterising it; did not stage, commit or
+  touch it (constitutional file; the wake reads, it does not mutate).
+
+## Open horizons
+
+1. **The thread — the 322.** Blocked-by-choice on PENDING-171 (population is 362, not the
+   frozen-list 270+). Next draw must be *systematic*, never the head.
+2. **The N-counter contamination** (below) — not filed. Needs a PENDING or a steward word.
+3. FIX-lane check-in, `COME DUE` day 30 — gates PENDING-173's build and the typography gate.
+4. `PENDING-177` marked BUILT with no REVIEWED entry naming it.
+5. §5 regrade gate — untouched a **sixth** session. Recorded, not dropped.
+
+## Confidence to recalibrate
+
+- 🔑 **CORRECTED, and sharper than the first reading.** The trial's `TRANSCRIPTS` glob
+  (`governance-drift-check.py:426`) sees only `-Users-davidglidden` = **54 = 43 real + 11 mumble**.
+  ⚠ **The directory scoping is NEARLY HARMLESS and I must not overstate it**: 43 of the 44 real
+  sessions ever recorded are in that dir. "It sees 34% of the population" is true of *files* and
+  misleading about *sessions*. It is PENDING-171's predicate class at a second site, benign here —
+  a near-miss to record, not a defect to file.
+  **The live defect is the unit.** 11 of 54 (20%, rising) are machine chatter that cannot reach the
+  ladder. PENDING-147 argued the trigger was probably *unsatisfiable*; the mumble makes it
+  satisfiable **for the wrong reason** — the freeze will lift on a count part fool-chatter.
+  Confidence **high**: enumerated across every project dir, not sampled.
+
+- **Inherited, not re-verified:** the 362 / 89-unseen figures (morning session's measurement) and
+  the REVIEWED-131 §4 authorship (mtime 08:45 + steward's file ⇒ *reads as* the steward's hand;
+  **not established**).
+
+## Authorization moves
+
+- Nothing filed. Two items *identified* as owing a filing (N-counter unit; the control-c class
+  gap) and deliberately left unfiled at wake — filing is work, and the wake reads.
+
+## Sub-agent dialogues
+
+## Bypasses
@@ -43,3 +43,17 @@ cannot authorize its own construction.
 - 2026-08-02 · ARC `CLAUDE.md` · removed `js/ # JavaScript (theme toggle)` from the asset-structure tree — directory absent, toggle retired Stage M 2026-06-01; replaced with a retirement note. Mechanical freshness; no latitude or assertion change.
 - `/wrap-up` §8 — added standing **Instruments** field (N run · M with a control written before first execution · K duplicating something already banked). Converts the 2026-08-07 one-off literal question into a series, and turns the steward's "do we need so many single-use items?" into a measured K column rather than a standing worry. — 2026-08-08
 - 2026-08-24 · `/wrap-up` §7.5 + `daybook-ensure.py` SKELETON · added a standing `## Corrections` section to the daily-note format, with the rule that an empty Corrections on a working day is itself a claim · **applied on direct steward instruction, reasoning from the jurist (REVIEWED-126)** — recorded here rather than in the lane proper, since it was authorized rather than executor-classified. Changes what the note *records*, not what any party may do.
+
+## FIX-LANE CHECK-IN — REVIEWED-85 provisional review, 30 days overdue
+**Date:** 2026-09-01 · **Parties:** steward + jurist · **Discharges:** REVIEWED-85's provisional condition; the `DEFERRED-DECISION: fix-lane-provisional-checkin` block filed at PENDING-168 ADDENDUM 1.
+
+**Item 1 — the lane.** EXTENDED PROVISIONAL, not settled and not withdrawn. The lane has been exercised by the executor exactly once in thirty days (the 2026-08-08 `Instruments` field); batch 1 was ruled by REVIEWED-85, the Corrections entry was steward-instructed, the ARC entry is mechanical freshness. **n=1 is not evidence either way.**
+- The 2026-08-08 entry is **RATIFIED on the merits as class (i)**, and its procedure is recorded as **defective**: it was executor-classified under a lapsed authorization, against the lane's own instruction to treat borderline calls as PROPOSAL until review. **Not precedent.**
+- **The trigger is re-based from time to use:** next check-in at **5 executor classifications**, backstop **2026-12-01**, whichever first. The original date trigger fired twice with nothing recorded; a use-count trigger cannot be missed by being busy. Filed as a `DEFERRED-DECISION` block in the same act. ⚠ **The use-count half is not expressible in the current schema and carries no machine check** — see the note beside the block in `PENDING.md`. No proxy was invented.
+- **Boundary flagged, not reopened:** batch-1 #4 changed the standing wrap question, which is what the executor must **inquire into**, not what a skill **records**. It was ruled class (i) by REVIEWED-85 and stands. It marks where class (i) ends, and the next hard classification should be measured against it rather than against #1–#3.
+
+**Item 2 — the retrieval obligation (REVIEWED-86 Q4).** **NOT DISCHARGED.** Answered with two fresh instances rather than a confirmation: REVIEWED-67's Q4 census and its unconditioned per-conversion typography gate did not reach the PDF lane in 42 days, and PENDING-177 AMENDMENT 1 records it as the identical PENDING-56 failure in a second format class. The cost is measured — `verify_conversion` returning **5/5 PASS on word-damaged output**.
+- **The machinery is not missing; the question is.** Batch-1 #2 and #3 built `prevention` and put it in the wake for this purpose. What has no surface is the **class-level question at the point of adoption**: *what standing rule already governs the class I am about to route?*
+- Directed to the wrap/wake surface, deliberately **not** as a new instrument and **not** as a new item. It is one question in an existing skill. ⚠ **Placement is unresolved and is flagged rather than guessed** — see the executor note below.
+
+**⚠ EXECUTOR NOTE — item 2's natural home is frozen.** "What standing rule already governs this class?" is a verification-ladder entry by shape, and the ladder is under a **general freeze** (REVIEWED-123, 2026-08-17: no additions, rewordings, removals or reorderings from any source until the trial is graded). Placing it in `/wrap-up` or `/wake-up` instead is available but fires at the wrong moment — the failure it addresses happens **at adoption**, not at wake or wrap. **Not placed. Awaiting direction on where it goes.** Recording the mismatch rather than putting it somewhere it will be decorative.
@@ -832,7 +832,18 @@ def selftest():
    # allowlist: a new mutating function in a delegate fails until someone names it and
    # says why. wake-digest.py is also a SessionStart hook, and emit_brief() is its hook
    # role; no tool in this file calls it.
-    _delegates = {"prior-art.py": set(), "wake-digest.py": {"emit_brief"}}
+    #
+    # `selftest` named 2026-09-01, and the naming is the mechanism working rather than a
+    # concession to it. The 2026-08-31 build (REVIEWED-131 (e) and (c)) added controls that
+    # write fixtures — a job dir with a state.json, two transcripts with and without a human
+    # turn — and the check went FAIL until someone said why, which is exactly its design.
+    # Why: every one of those writes is to a tempfile.mkdtemp() tree that the same function
+    # rmtree()s, and selftest is reachable from `--selftest` alone, never from a tool call.
+    # ⚠ ITS WEAKNESS, DECLARED: this is a FUNCTION-level exemption, so a future write inside
+    # selftest that is NOT to a tempdir now passes silently. The narrower rule the check
+    # cannot express is "writes confined to a tempdir"; naming that limit is preferred to
+    # widening the detector into something it would take a data-flow analysis to get right.
+    _delegates = {"prior-art.py": set(), "wake-digest.py": {"emit_brief", "selftest"}}
    for _fn, _exempt in sorted(_delegates.items()):
        _dsrc = open(os.path.join(SCRIPTS, _fn), encoding="utf-8").read()
        _tree = __import__("ast").parse(_dsrc)
Author	SHA1	Message	Date
David F Glidden	2fc7f5eeb4	session 2026-09-01: PENDING-178, the FIX-lane check-in, the typography gate + first byte-census, REVIEWED-133 executed	2026-09-02 11:31:35 +02:00
David F GliddenandClaude Opus 5	6e0a3cd246	governance: steward places REVIEWED-133 (PENDING-137) Cell-constant markers: ratified as its own amendment, with the direction of the change recorded. AUTHORIZED — (b) as corrected, three conditions; (a) and (c) rejected. Closes a narrowing that had been in force by reading since 2026-08-07 and undisclosed as an amendment until now. Executed the same evening in studium-engine 2b30425. Committed by the executor at the steward's direction; the content is the jurist's and the steward's, and REVIEWED.md was written by neither the executor's hand nor its judgement. ⚠ The entry records its own weakness in its Notes, and it should not be read cold as an ordinary ruling: two of its three conditions were corrected by the executor after the jurist ruled from a partial read of the file it governs (it had read to line 70; the deciding date rows sit at 127-128), the stratum distribution in condition 2 is executor testimony from rows the jurist did not open, and governance-mcp.py's selftest was FAILING while the ruling was being drafted from that surface — five undeclared mutating calls in wake-digest.py from the previous day's build, repaired at `cc97888`. ⚠ The header is the parenthetical house form `## REVIEWED-133 (PENDING-137) — …`, so the register-integrity control cannot resolve it to a number: RE_ID requires a dash immediately after the identifier and backtracks to the bare token `REVIEWED`. Fourth entry in that class after 130, 131 and 132. Harmless here; it means any future amendment to this entry will report the same false orphan seen today. Recorded so it is not rediscovered cold. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017vKkg2EJF1rGwdFdBogwqx	2026-09-02 11:16:36 +02:00
David F GliddenandClaude Opus 5	cc9788862c	[FIX] Declare wake-digest.py's selftest exemption; correct a stale tracker line Two unrelated things found while establishing what PENDING-134 actually needs, which turned out to be nothing. 1. governance-mcp.py --selftest was FAILING. The delegate read-only guarantee flagged five undeclared mutating calls in wake-digest.py, all inside selftest(), all added by yesterday's REVIEWED-131 (e)/(c) build: a job dir with state.json, and two transcripts with and without a human turn. Declared rather than detector-widened, because failing until someone names it is the mechanism's design, not an obstacle to it. Why it is safe: every write goes to a tempfile.mkdtemp() tree the same function removes, and selftest is reachable from --selftest alone, never from a tool call. Its weakness is declared in the same comment: this is a FUNCTION-level exemption, so a future non-tempdir write inside selftest now passes silently. The narrower rule — "writes confined to a tempdir" — is not expressible in this check without data-flow analysis, and naming that limit is preferred to a detector that would be wrong in a harder-to-see way. Selftest now PASSES, 62 controls. 2. MEMORY.md said "ratio_A_to_B VOID until PENDING-134 lands" and "NEXT: rule PENDING-134". Both stale by 18 days: PENDING-134 was ruled REVIEWED-121 on 2026-08-14. REVIEWED-121's own closing sets the real condition — re-derive ONCE after BOTH it and PENDING-137 land — and PENDING-137 is still [PROPOSAL], awaiting a jurist ruling. The live blocker on the fr cell is -137, and it needs the jurist, not the executor. Corrected in place with the superseded text quoted, per the memory discipline: a conflict between a memory layer and the substrate is a verification trigger, and the substrate wins. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017vKkg2EJF1rGwdFdBogwqx	2026-09-01 10:34:39 +02:00
David F GliddenandClaude Opus 5	6a93505c7f	governance: steward places the §4 revision note and REVIEWED-131 AMENDMENT 1 Two steward placements in one commit, per the jurist's ordering so a single commit carries the whole state of the file: - The §4 revision note. §4 was rewritten in place on 2026-09-01 inside a ruling placed 2026-08-31, and nothing in the record said so. The note records what the original said, why it changed, and that PENDING-173's integrity control cannot see the change because its unit is the block header while what changed is a section inside a block. - REVIEWED-131 AMENDMENT 1, joined at ### depth beneath its parent: control (c)'s premise is false, and a by-design unattended agent has been in production since 2026-08-25. Committed by the executor at the steward's explicit direction. The content is entirely the steward's and the jurist's; committing records it rather than modifies it, and REVIEWED.md was otherwise untouched across this session. ⚠ THE DRIFT-CHECK REPORTS TWO BROKEN AMENDMENT LINKS AGAINST THIS FILE, AND THE FINDING IS FALSE. REVIEWED-131 is present and was not replaced. RE_ID requires a dash immediately after the identifier; the house form `## REVIEWED-N (PENDING-M) — title` defeats it, and the regex backtracks to capture the bare token `REVIEWED`, so REVIEWED-131 never enters `originals` and its amendment looks orphaned. Scope measured, not assumed: 3 of 132 REVIEWED headers — 130, 131, 132, all placed within the last week. It fired now because ours is the first amendment against a parenthetical parent. Not repaired here. Whether the control should parse the newer header form, or the newer form is an undeclared convention change, is the question PENDING-146 and PENDING-110 already hold, and this is the control REVIEWED-132 widened this morning. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017vKkg2EJF1rGwdFdBogwqx	2026-09-01 10:14:49 +02:00
David F GliddenandClaude Opus 5	6eff2056f9	[HARDENING] FIX-lane check-in held and recorded; deferral re-based, half of it uncheckable REVIEWED-85's provisional review, 30 days overdue and gating PENDING-173's build and PENDING-177's typography gate, was held by steward and jurist today. Outcome recorded in the index; the deferral block is discharged with `resolved:` rather than deleted, and the drift-check now reports 0 COME DUE where it reported 1. Item 1 — EXTENDED PROVISIONAL. The lane has been exercised by the executor exactly once in thirty days, so n=1 settles nothing in either direction. The 2026-08-08 Instruments entry is ratified on the merits as class (i) and its procedure recorded as defective — executor-classified under an authorization already lapsed into overdue-review, against the lane's own instruction. Explicitly not precedent. Item 2 — NOT DISCHARGED, and answered with two fresh failures rather than a confirmation: REVIEWED-67's census and typography gate did not reach the PDF lane in 42 days, at a measured cost of verify_conversion returning 5/5 PASS on word-damaged output. Two things are recorded as gaps rather than closed: - The re-based trigger is only half machine-checkable. The check-in was re-based from time to use precisely because a date trigger fired twice with nothing recorded, but the schema's vocabulary is glob/path-exists/ date/manual and a use count is not expressible. The block carries the backstop date only; the use-count half sits in `discriminator:`. No proxy was invented — a glob over the index's rows would have fired on ruled and steward-instructed entries alike and looked machine-checked while counting the wrong thing, which is the schema's own stated reason for `manual`. - Item 2's remedy is not placed. "What standing rule already governs the class I am about to route?" is a verification-ladder entry by shape, and the ladder is under REVIEWED-123's general freeze. Wrap or wake would accept it but fire at the wrong moment — the failure happens at adoption. Flagged rather than put somewhere it would be decorative. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017vKkg2EJF1rGwdFdBogwqx	2026-09-01 09:33:32 +02:00
David F GliddenandClaude Opus 5	b3a35c262e	[HARDENING] PENDING-104 ADDENDUM 2: the concurrency frequency, measured The item declared its own frequency unobservable and left the option space undrafted for that reason. Jurist-directed measurement, no new id: 5 truly overlapping session pairs across 44 real sessions on 3 distinct days in a 32-day window, disaggregated because two of the five are sub-four-minute boundary artifacts and three are substantive. Recorded with the item's limits rather than as a clean figure: the measure is an upper bound (a resumed session's interval includes idle time), and a first attempt returned 29 pairs on 14 days by bucketing timestamps into clock hours, which counts a session ending at 17:10 and another starting at 17:16 as concurrent. That error was caught by internal inconsistency — 29 cannot be a subset of 5 — and not by a control. It is recorded in the item because the near-miss was a fivefold overstatement of the frequency the steward is being asked to rule on. Controls pass in both directions: must-detect on the documented 2026-08-31 collision, must-not-flag on a sequential handoff. The judgement is left open. The frequency is observed; whether it warrants a mechanism is not settled by observing it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017vKkg2EJF1rGwdFdBogwqx	2026-09-01 09:26:36 +02:00
David F GliddenandClaude Opus 5	7dac2194ca	[HARDENING] PENDING-178: name every rate's population, pre-ruling Steward-directed revision of an item filed minutes earlier and not yet read by any other party — the text is corrected in place rather than joined by an amendment block, which on a 2-minute-old unruled item would be the CLASS E noise PENDING-146 names. Three changes, all cheap and all about the same hazard: - 95 appeared twice with different referents. The partition's 95 routing records (68 aside + 27 notable) and the rate's 95 draws that reached a generator verdict (41 + 54) are the same number by coincidence. The denominator is now named inline and the collision stated. - Each rate carries its population: 54/95 verdicts (57%), 54/102 terminal (53%), 54/428 draws (13%). The word-count figures are marked as a fourth population — the rejects log's word-citing subset, 57 of 59, covering surfaces the draws log does not. - A limits paragraph: the reconciliation found three populations stated as one, inside the instrument reporting on the counter this item is about. Same class as the defect filed, same class as PENDING-173's three unchosen surface forms, second site the same day. Recorded, not opened as an id. The causal claim is marked NOT established. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017vKkg2EJF1rGwdFdBogwqx	2026-09-01 09:09:30 +02:00
David F GliddenandClaude Opus 5	9838ffe86b	[HARDENING] PENDING-178: the ladder trial counts the fool's chatter as sessions The trial's session counter globs one project directory, which since 2026-08-25 also receives one transcript per Tarbuckle mumble. Enumerated today: 54 files = 43 real sessions + 11 mumbles. A mumble cannot reach the verification ladder and can only enter the denominator, so REVIEWED-123's bounded hold would lift on a count part machine chatter. Distinct from PENDING-147, which names the window and the perishability. This is the unit, and it runs opposite to -147's finding (1): the trigger stops being unsatisfiable and becomes satisfiable for the wrong reason. Three figures asserted earlier in the session are withdrawn in the item rather than quietly dropped — a "wiring day" attribution and an "~8/day" rate (both corrected by the steward) and a "197 reached the generator" (the steward observed the numbers did not close; tarbuckle-draws.jsonl mixes routing hand-offs and terminal outcomes in one field). Records one DECLINED finding with its argument: TRANSCRIPTS is scoped to one of eight project directories, which is PENDING-171's predicate class at a second site, and is benign here because 43 of the 44 real sessions ever recorded are in that directory. Not filed, so it is not rediscovered as a defect. REVIEWED.md is left untouched and uncommitted — steward's file, edited at 08:45 outside this session. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017vKkg2EJF1rGwdFdBogwqx	2026-09-01 09:08:57 +02:00