diff --git a/PENDING.md b/PENDING.md
index b81ac3a..77a15ad 100644
--- a/PENDING.md
+++ b/PENDING.md
@@ -6867,7 +6867,14 @@ The control now reads all three registers at `##` and `###`, recognises `ADDENDU
 
 **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.** Of Tarbuckle's 102 terminal generator results, **54 were rejected against 41 spoken (57%)**, the rejection pile-up sits at **14 words against a `MAX_WORDS` of 9**, and one line returned at 196 words. A generator and its gate disagree systematically and the gate wins without a surfaced record. 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 sentence is the record that it exists.**
+**⚠ 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.