governance: PENDING-88 amended — (d) is already authorized and its method cannot work

Measured against the register before acting, and the item survives in direction but not
in numbers or remedy.

Option (d) has been authorized since 2026-07-19 — Stroke 4 of the register's own
authoritative head block — and simply never executed; Stroke 2, the ~25-30 entry
verification-ladder batch-append, is authorized and unexecuted in the same slot.

But Stroke 4's method ("ruled items collapse to verdict lines") cannot achieve the goal:
of 190 table rows, 13 are ruled and 177 are open. Collapsing every ruled row removes ~7%
of the file. The register is not large with settled history; it is large with open
proposals, so the prescribed remedy leaves it over the cap and the loop still broken.

The item's counts are unreliable and so were mine until I stated an inclusion rule; with
one stated, 123 PROPOSED / 8 BUILT / 4 AUTHORIZED over table rows. The item's own
falsifier is not triggered — 166,589 bytes, 177 open, oldest 2026-05-24 — so the
diagnosis stands and only the arithmetic needs restating.

Newly found: one section spans 411 lines and 58% of the file while carrying 33 distinct
dates from 2026-05-24 to 2026-07-19. Five weeks of wrap-appends landed in an existing
section rather than new dated ones, so the register misreports its own chronology and
§1.6's append step is silently mis-filing.

Proposed method, on the MEMORY.md precedent that already worked (213KB -> 17KB): a live
index of open proposals plus a detail archive, ~19 KB, lossless in the working tree,
compacting by form rather than by dropping items. Proposed and not applied: Stroke 4
authorized compaction, not this method, and restructuring the surface that decides what
reaches the steward is PROPOSAL-class by the item's own test.

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

PENDING.md

@@ -659,3 +659,20 @@ Executed as §VII eyeball-after-gate: pages rendered with `pdftoppm` and read, n
 **Executor's declared interest — and a correction to how it was first stated (amended 2026-07-29, steward-challenged).** This item would loosen a constraint on the executor, proposed by the executor, immediately after the steward invited it. The interest is real and is stated so it cannot be read without seeing it. **But the first draft of this paragraph over-claimed, and the over-claim was itself the failure it warned about.** It implied the proposal should be discounted *because the steward would welcome it* — which makes welcomeness the evidence, and would disqualify every correct thing the executor ever produces. The steward's challenge: *"Does 'pleases you' and 'successfully achieve what's necessary' mean two different things? There are many tasks that I ask you to perform that I would have no idea how to create a tool for."* Both halves land. (i) The two coincide whenever the true answer is also the welcome one; contamination is the case where they **diverge** and the output bends toward comfort. (ii) For an instrument the steward could not have specified, deference has **nothing to defer to** — there is no interlocutor-position to drift toward, so the pressure has no target and what remains is only whether the tool is right. (iii) Performing scrupulousness is *itself* pleasing — cheap, safe-looking, and it buys the executor the appearance of rigor at the cost of a working tool. `~/CLAUDE.md`: *"Deference that lets the human waste time is not respect — it is a failure of the partnership."*
 **The discipline that actually applies is answerability, not purity** — the chamber's own thesis, turned on the executor: *"you don't make the reader trustworthy by purifying it. You make it answerable by binding it to the marks"* (the Chamber touchstone, §2). So the operative mitigation is **not** the disclosure; it is that every load-bearing claim here is one command from refutation: `151 PROPOSED / 26 BUILT / 13 AUTHORIZED` and `166 KB` from `skill-harvest-register.md`, oldest open batch `2026-06-05`, the §1.6 blanket rule and the `[FIX]` taxonomy row quotable verbatim. **What would falsify the item:** if the register reads under the cap, or if the PROPOSED backlog is small or recent, the diagnosis fails and option (a) stands. Remaining structural mitigations, unchanged: the recommendation *adds* a hard floor rather than only removing a gate; the FIX lane carries a mandatory **report**, preserving awareness by disclosure rather than permission; and this is filed as `[PROPOSAL]`, not implemented — which its own proposed test also requires, since changing what the executor may do is exactly the PROPOSAL-class case.
 **Awaiting:** Steward authorization.
+
+### PENDING-88 — AMENDMENT (2026-08-01): option (d) is already authorized, and its authorized METHOD cannot work
+Measured against the register itself before acting. Four corrections; the item's direction survives all of them, its numbers and its remedy do not.
+
+**1. (d) does not need a ruling — it has one, from 2026-07-19.** The register's own head block is authoritative: *"**Stroke 4 — register compaction: AUTHORIZED; same slot as Stroke 2**"*. The compaction has been authorized for six weeks and simply never executed. **Stroke 2** — the verification-ladder batch-append, *"ALL earned ladder entries queued in this register (~25–30)"* — is authorized and unexecuted in the same slot. Two authorized housekeeping acts, both waiting on a slot rather than on the steward.
+
+**2. The authorized method is inapplicable to the actual condition.** Stroke 4 prescribes *"ruled items collapse to verdict lines; detail stays in git history."* Measured over the file: of **190** table rows, **13** are ruled (8 BUILT · 4 AUTHORIZED · 1 DEFERRED) and **177 are open**. Collapsing every ruled row would remove ~7% of the register. **It is not large with settled history; it is large with open proposals.** The prescribed remedy leaves it over the cap and the loop still broken.
+
+**3. The counts in this item are unreliable — and so were mine until I stated a rule.** The item claims *151 PROPOSED against 26 BUILT + 13 AUTHORIZED*. Counting **markdown table rows with ≥5 pipes, excluding header and separator rows** — stated so it can be checked — gives **123 PROPOSED · 54 unmarked · 8 BUILT · 4 AUTHORIZED · 1 DEFERRED**. The BUILT/AUTHORIZED gap is because most ruled history lives in the *"Built / authorized (lineage)"* bullet list and in prose blocks, which no table-row counter sees. Fourth instrument-defines-its-own-count disagreement today. **The item's own falsifier is NOT triggered:** the file is **166,589 bytes** (over cap; the item's "166 KB" is exact), 177 open is not small, and the oldest open item is **2026-05-24**, not recent. **The diagnosis stands; the arithmetic should be restated with a rule.**
+
+**4. A structural defect the item does not name, and it is most of the file.** One section — `## New proposals (2026-06-13 post-clear — …)` — spans **411 lines / 96,848 bytes = 58% of the register** and contains **33 distinct dates running 2026-05-24 → 2026-07-19**. Five weeks of wrap-appends landed in an existing section instead of new dated ones, so **the register misreports its own chronology**: "oldest open batch 2026-06-05" undersells it by twelve days, and §1.6's append step is silently mis-filing.
+
+**A method that does work, with a house precedent that already succeeded:** the **MEMORY.md two-file split** (2026-07-06 — 213 KB → 17 KB, 91.8%; live index + reference layer). Applied here: a **live index of open proposals** (one line each: skill · kind · one-line · date · status), full rationale/origin prose relocated to `skill-harvest-archive.md`. Sizing: 177 entries × ~110 bytes ≈ **19 KB** — cap-clearing, and **lossless in the working tree**, so nothing depends on git recovery. It compacts by **form**, not by dropping items — required here, because dropping open proposals would cross this item's own proposed hard floor (*"anything that would reduce what gets surfaced to the steward"*). Git-backing verified regardless: the memory directory sits inside `~/dotfiles` and the register is tracked.
+
+**Why proposed and not applied.** Stroke 4's authorization covers compaction; it does not cover *this* method, and the change is not cosmetic — it restructures the surface that decides what reaches the steward. By this item's own test, that is PROPOSAL-class.
+
+**It sharpens the recommendation rather than replacing it.** 177 proposals opened since 2026-05-24 against **one** full review (2026-07-19) is the actual cost driver. Compaction is hygiene on the symptom; the **FIX lane in (b)/(c) is the load-bearing half** — without it the register re-bloats, exactly as MEMORY.md re-bloated after the 2026-06-08 compress-in-place pass *"attacked the level not the class."* **Recommendation unchanged in substance, corrected in method: (c), plus (d) executed by split rather than by collapse.**

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

@@ -5,7 +5,7 @@ metadata:
   node_type: memory
   type: feedback
   originSessionId: be51f191-8658-4b4c-ad1e-1f14c934f624
-  modified: 2026-08-01T08:23:47.093Z
+  modified: 2026-08-01T08:35:56.040Z
 ---
 
 # Session Ledger — 2026-08-01
@@ -26,7 +26,8 @@ metadata:
 ## Authorization moves (cont.)
 
 - **PENDING-85 CLOSED** (`[FIX]`, executor authority) with a full disposition; digest count 19 → 18.
-- **PENDING-84 DIAGNOSIS filed** — not a remedy; `[HARDENING]` stays with the steward.
+- **PENDING-84 DIAGNOSIS filed** — not a remedy; `[HARDENING]` stays with the steward. **→ SUPERSEDED same day: TRIAGED + CLOSED** on steward direction (`136b882`). The item's question (triage of priority) is answered so the item closes; the §V violation is **dispositioned, not repaired**, and both the item and `CLAUDE.md` say so. Remedy built as the **§VII quarantine artifact** rather than frontmatter — the constitution's own ruling, and the lane it called "designed, not built" turned out to have a real case waiting.
+- **Confirmation of the morning's digest bug:** closing PENDING-84 left the visible count at 18. It never counted — suppressed all along by the number-match against REVIEWED-84 (which rules on PENDING-87). Closing an item the instrument cannot see produces no visible change.
 - **REVIEWED-83 Amendment 1 DRAFTED** for steward placement. Steward confirmed "amendment" mid-turn. I left the one genuinely judgmental clause undecided (whether V-DPDF now needs re-demonstration against the OCR-then-re-typeset family) — that is the jurist's, not mine to fold into a placement block.
 - **Classifier repaired + promoted on explicit steward authorization** — bounded scope, `08ae83e`, both remotes verified. Commit + push taken as the documented routine per the repo's own CLAUDE.md, **not** re-asked — the corrective from 2026-07-29's over-caution drift, applied.