diff --git a/PENDING.md b/PENDING.md
index 5b26b7b..dbacd9d 100644
--- a/PENDING.md
+++ b/PENDING.md
@@ -3413,3 +3413,54 @@ The third is the sharpest: **both halves are in the same document**, so this is
 **Awaiting:** Steward authorization. ⚠ **Independently of the mechanism: PENDING-131 ADDENDA 2 and 4 await steward action now** and have been unable to say so since they were filed.
 
 ---
+## PENDING-146 — CLASS E: the open list's unit is the ID; the decidable unit is the BLOCK — so four live asks under PENDING-131, including the fence unblocker, are invisible while the verdict is correct
+**Date:** 2026-08-17
+**Tag:** [HARDENING]
+**Summary:** Filed at steward direction as its own item. `PENDING-142` is entirely about the *closure* signal — whether a REVIEWED header names an id. This is upstream of that: it is about **what counts as an item at all**, and none of (a)/(b)/(c)/(d) reaches it.
+
+**The defect.** Five `## ` blocks share the id `131`. Every header parses under `PENDING-(\S+?)\s*—` to `131`, so the open list's unit is the **id** while the unit a steward can actually decide is the **block**.
+
+⚠ **The consequence is worse than a wrong verdict, because the verdict is right.** PENDING-131 *is* open. Option (d) would report it OPEN, correctly, and still conceal that it carries multiple separate asks, filed three days apart, at different authorization classes. **A correct answer that hides the decision is not something a three-valued report can fix.**
+
+**Measured against the substrate this session, and it corrects two prior reports — the executor's and the jurist's:**
+
+| block | date | tag | live `**Awaiting:**` |
+|---|---|---|---|
+| PENDING-131 (parent) | 08-10 | `[HARDENING]` | **yes** — Steward authorization |
+| ADDENDUM 1 | 08-10 | `[HARDENING]` | **yes** — Steward authorization |
+| ADDENDUM 2 | 08-10 | `[HARDENING]` | **yes** — on (b), (c)-as-PROPOSAL, and §6 |
+| ADDENDUM 3 | 08-10 | (none) | no — correctly invisible |
+| ADDENDUM 4 | 08-13 | `[HARDENING]` | **yes** — Move 1 and Move 2 |
+
+⚠ **Four blocks carry a live await, not two.** The executor reported "ADDENDA 2 and 4" to the steward; the jurist, ruling on that testimony, **explicitly disclosed it had not verified ADDENDUM 1** and took the executor's naming as given. ADDENDUM 1 has one. **The disclosure is what made the gap findable** — the jurist named exactly the check it had not run, and the check overturned the count. That is the differently-positioned-readers doctrine paying out in the direction it is supposed to.
+
+⚠ **Second gap closed, also disclosed by the jurist and unverifiable from its side:** `governance_state()` shows **zero rows** mentioning `131` — not a collapsed row, not a row displaying one of five. Nothing.
+
+⚠ **And the tag understates the class.** ADDENDUM 2 §5 re-tags (c) as `[PROPOSAL]`, which under the taxonomy requires **explicit steward authorization** rather than the annotation a `[HARDENING]` row implies. One row, one tag, understating the authorization class of what is inside it.
+
+**THE LIVE COST, and it is not bookkeeping.** ADDENDUM 4 contains the unblocker for a citation-safety exposure that has been open since 2026-08-10 behind (c) — which is cross-repo, since `studium/meta@1` is locked by the Chamber Library constitution and no studium ruling reaches it. **Move 1** puts the fence on the citation *at emission*, engine-side under D-1: no schema change, no cross-repo consent, no per-region curation, covering **all 532 spans** the day it lands including sources added later. **Move 2** disposes of the 25 line-addressable blockquote runs today, needing nothing beyond a disposition. **The thing that dissolves the cross-repo blocker is the thing the instrument cannot show.** Meanwhile the exposure is live and named: a grounded claim about Alexander may be supported by Shakespeare's or Buber's words, at Pattern 26's bold invariant slot — the position that looks most authoritative.
+
+⚠ **THIS SAVES REVIEWED-122 CONDITION 1 FROM PASSING WHILE BLIND, and the key is not yet drafted.** Condition 1 requires a hand-read per-item answer key over the 69 filtered items. **If "item" resolves to *id*, the key reproduces the exact unit that caused this defect and grades green.** The key MUST be keyed on `## ` **blocks**, and must record, per block, whether it carries a live `**Awaiting:**` and **at what tag**. Condition 1 as ruled was one word away from certifying this defect as correct. *(The jurist's relay wrote "REVIEWED-142 condition 1"; the ruling is REVIEWED-122 — third instance today of the independent-sequence confusion PENDING-110 names.)*
+
+**A RECURRENCE, NOT A NOVELTY.** On 2026-07-28 a parser defined an item as `^## PENDING-<digits>` and hid twenty items, ten of them open, with every check inheriting the blind spot. That fix corrected the **header pattern** and left the **unit** untouched. Same instrument, one convention along. It is also the weld-test shape verbatim — *a census cannot see the thing because the unit it counts is larger than the unit the thing lives in* — now at its third site, and the two Fool-trial instances in REVIEWED-122 cond. 9 make this a wide family rather than a run of coincidences.
+
+**THE REMEDY IS A CONVENTION ALREADY IN THE RECORD, NOT A PARSER CHANGE.** `PENDING-132` states it as its own reason for existing — verified verbatim in `PENDING.md`: *"PENDING-131 Addendum 2 supplies the \*finding\*; it must not supply the \*decision\*. A later reader asking why the fr cell shrank should find a dated act with a stated basis, not an inference they have to reconstruct from an addendum about something else."*
+
+**Proposed convention:**
+> An addendum may carry findings, reversals, corrections and standing posture. An addendum may **NOT** carry a live `**Awaiting:**`. Where an addendum's reasoning produces a new decidable ask, that ask is filed as its own `## PENDING-<id>` item cross-referencing the parent — as PENDING-132 and PENDING-133 already were, and for the reason PENDING-132 states in its own body.
+>
+> **Retroactive application, minimum:** ADDENDUM 4's Move 1 and Move 2 split into their own item(s). ADDENDUM 2's residual (b)/(c) await either split likewise or retired — §6 within it was subsequently built and steward-authorized per ADDENDUM 3 §4, so that await is **partially discharged and says so nowhere.** ADDENDUM 1's and the parent's awaits reviewed on the same pass.
+
+**Options:**
+- **(i) Convention first, parser second.** Adopt the convention, split retroactively, then add block-level detection as a *tripwire* rather than as the primary remedy. **Makes the census correct rather than making the census smarter.**
+- **(ii) Parser first.** Report per-block awaits without changing authoring practice. Cheaper today; leaves the record structurally ambiguous and needs the smarter parser forever.
+- **(iii) Both, convention leading** — (i) with (ii)'s detection wired at the same time so a future addendum carrying an `Awaiting:` is caught rather than trusted to discipline.
+
+**Recommendation: (iii), and the split is not gated on the ruling.** The convention is the remedy; detection is how we learn it is being followed. ⚠ **But the four live asks should be surfaced now regardless of which option wins** — they are carried in this item's own body above so they are visible in the open list today, the same disclosed-carrier pattern as PENDING-143.
+
+**Suggested order for the fence work itself, if the steward wants one** (jurist-offered, recorded not decided): **Move 2 first** — bounded, closable in one sitting, no ruling needed. **Then Move 1** as a build direction, with the control requirement ADDENDUM 4 states about itself: controls drawn from **each structural class present**, reporting `NOT ESTABLISHED` rather than zero for any class it has no control for. That requirement is earned — **four of the five defects in that census escaped controls drawn entirely from Mauss.**
+
+**Files affected:** authoring convention (`/wrap-up` §1.6 or `~/CLAUDE.md` §Steward-Jurist Interface — the latter is `[ESCALATE]`, steward's hand); `~/dotfiles/scripts/wake-digest.py` for detection.
+**Awaiting:** Steward. ⚠ **Independently of any ruling: Move 1 and Move 2 await direction and have been unable to say so since 2026-08-13; the parent, ADDENDUM 1 and ADDENDUM 2 have been unable to say so since 2026-08-10.**
+
+---