[PROPOSAL] PENDING-124 gate passed; five conditions discharged, and the gate found a tenth instance

Q1 is applied, not extended: Constraint 4 has two clauses and my contrary reading
engaged only the second. Limits, not failures — and "I could not look" is a limit. I
had overstated my own uncertainty on the question I withdrew a recommendation over.

The condition that cost most: my quote-verification pass reported verified on a
reconstruction of REVIEWED-104 — contractions, re-punctuation, two blocks spliced, and
the closing sentence dropped. A two-valued verifier inside a package arguing verifiers
must be three-valued. Rebuilt at ~/dotfiles/scripts/verify-quotes.py. The first rebuild
had three tiers and cried wolf on every correctly-copied quote, since a record stored
with hard wraps is byte-different from the same text quoted as one line; splitting
re-wrapped from normalized is the same two-strengths lesson the fleet learned. Both
directions proven: corrected package exit 0, original reconstruction not-found exit 1.

The dropped sentence answered my own Q2. It was in the record the package quoted.

Both citation errors in that package had one cause, which the script cannot diagnose: I
quoted the ADVISORY message and attributed it to the PLACED record. Different
documents; placement adds and cuts, so quoting the advisory loses exactly what
placement contributed.

My "five instances, same shape" was wrong — two are the shape, three belong to the
attested-absence family whose parent is already ratified (REVIEWED-47, 2026-07-05). I
searched for a doctrinal parent among R0 and Constraint 4 and missed the ratified
sibling closest in content. The ladder entry now joins that lineage.

Filed as a watch-item, with an operative memory note: third package running where the
grounding pass was incomplete and every substantive omission cut against my own
argument. It optimises for finding my errors, not my support.

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

PENDING.md

@@ -2099,6 +2099,26 @@ Three cases, all discriminated: a rule ran → existing output already says so,
 
 ---
 
+### AMENDMENT 2 — 2026-08-08, DESIGN GATE PASSED WITH CONDITIONS; five conditions discharged
+
+**Q1 — APPLIED, and firmly.** Constraint 4 has **two clauses**, and my contrary reading engaged only the second. *"The system must report its own limits"* does not speak of failures at all — it speaks of **limits**, and *"I could not look"* is one. **No constitutional change; no `[ESCALATE]`.** ⚠ Recorded because I withdrew a recommendation on this question: the replacement is firm, and I had **overstated my own uncertainty**.
+
+**Q2 — binds at BOTH, and the aggregation half was ALREADY RULED — in the sentence I dropped.** REVIEWED-104 §1 closes: *"A green fleet that includes an unassessed binding case is the same overstatement one layer along."* It was in the record the package quoted. **The two-strengths distinction is required, not optional.**
+
+**Q3 — free, and the line I said I could not find EXISTS and is ratified:** the hash-locality principle's *"the distinct NAMES prevent the collision."* **Names are individuated by REFERENT, not by concept.** Four referents, four names — correct; one-concept-four-homes only if **one referent** carries four names.
+
+**Q4 — ratify, not provisional — but NOT on the count.** ⚠ Four of the nine instances are dated 2026-08-08 and **downstream of the advisory that proposed the doctrine** — the register responding to its own proposal, which CLAUDE.md's ratified caution governs precisely (jurist and executor *"do not differ from each other in formation"*). Once Q1 is *applied*, authority comes from Constraint 4, not from the count. **Chamber tool-fleet census: owed, not blocking.**
+
+**⚠ CONDITION 2 relocated the proposal.** My *"five instances, same shape"* was **wrong**: **two** are the shape, **three** belong to the **attested-absence family**, whose parent — REVIEWED-47, **2026-07-05**, *"attested absence lives in its own honest top-level key"* — is **already ratified**. I searched for a parent among R0 (correctly withdrawn) and Constraint 4 and **missed the ratified sibling closest in content**. Corrected on the record per condition 3.
+
+**⚠ CONDITION 1 — a tenth instance, produced BY THE GATE and the only one independent of the advisory.** My quote-verification pass reported `verified` on a **reconstruction** of REVIEWED-104 — contractions, re-punctuation, two blocks spliced, and the closing sentence dropped. **A two-valued verifier, inside a package arguing that verifiers must be three-valued.** Rebuilt as `~/dotfiles/scripts/verify-quotes.py` with **four tiers** — `exact` / `re-wrapped` / `normalized` / `not-found`, plus author-declared `own-text`. ⚠ The first rebuild had **three** and cried wolf on every correctly-copied quote, because a record stored with hard wraps is byte-different from the same text quoted as one line; splitting `re-wrapped` from `normalized` is the **same two-strengths lesson**. **Both directions proven:** corrected package → exit 0; the original reconstruction → **not-found, exit 1**.
+
+**Discharged:** (1) verifier rebuilt + controlled · (2) ladder entry names the attested-absence family and cites 2026-07-05 · (3) evidence statement corrected · (4) III.1 now carries the environment-vs-defect split in the normative text · (5) landed as **one ladder entry**, nothing in `~/CLAUDE.md`.
+
+⚠ **Standing observation, filed as a watch-item:** third package running where the grounding pass was incomplete and **every substantive omission cut AGAINST my own argument** — a stable dated pattern, not an impression. The pass optimises for finding its own errors and not its own support. Operative note: `feedback-grounding-pass-finds-errors-not-support.md`.
+
+---
+
 ## PENDING-125 — A live false attestation in the governed record: Mauss's `reading_index_status` has read VERIFIED-BOUND for 53 days
 
 **Date:** 2026-08-08