[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

claude/governance/three-valued-checks-JURIST-PACKAGE-2026-08-08.md

@@ -47,34 +47,26 @@ This is the whole basis. Everything below argues that a two-valued check **canno
 limit *"I did not look"*, and therefore violates Constraint 4 by construction whenever its subject
 can be absent.
 
-### I.2 — `~/REVIEWED.md` REVIEWED-104 §1 (steward ruling, reachable as `reviewed`)
+### I.2 — `~/REVIEWED.md` REVIEWED-104 (steward ruling, reachable as `reviewed`)
 
-> A live-corpus assertion makes one suite depend on `chamber-library` being present and reachable.
-> Every other suite builds under `tmp` and is portable; this one won't be. The item doesn't say
-> what happens on a fresh clone with no chamber beside it, and both obvious answers are wrong:
-> **Red on absent** — a suite that goes red for reasons unrelated to the code under test. That
-> trains people to discount fleet red, which is the worst possible outcome for this particular
-> thread. **Skip on absent** — the silent net, in the very assertion added to correct an
-> overstatement.
-> So: **three states — `bound` / `drifted` / `cannot-assess`** — and `cannot-assess` must be
-> distinguishable in the fleet summary, never folded into green.
+⚠ **REPLACED 2026-08-08 at the design gate. What stood here was a NORMALIZED RECONSTRUCTION of
+this ruling, not its placed text**, and my own quote-verification pass counted it among the
+verified. Differences the jurist enumerated and I confirmed against the record: `will not be` →
+`won't be`; `does not say` → `doesn't say`; `wrong.` → `wrong:`; `CONDITION:` → `So:`; the Notes
+paragraph and §1 spliced into one block though the record keeps them separate — **and the closing
+sentence dropped.** Below is the placed text, `~/REVIEWED.md` L1246–1250:
 
-⚠ **CITATION CORRECTED before relay — the passage that prompted this package is NOT in the
-register, and I first cited it as though it were.** The observation below came from the jurist's
-**advisory on PENDING-122/123**, relayed by the steward; the *placed* REVIEWED-104 does not contain
-it. Verified by search: the phrase appears in `~/PENDING.md` (where I recorded it) and in this file,
-and **nowhere in `~/REVIEWED.md`.** It is quoted here as **advisory, not as ruled text**:
+> **Notes:** A live-corpus assertion makes one suite depend on chamber-library being present and reachable. Every other suite builds under tmp and is portable; this one will not be. The item does not say what happens on a fresh clone with no chamber beside it, and both obvious answers are wrong. Red on absent is a suite going red for reasons unrelated to the code under test, which trains people to discount fleet red — the worst possible outcome for this particular thread. Skip on absent is the silent net, in the very assertion added to correct an overstatement.
 
-> Note where else that requirement just appeared. PENDING-123's acceptance test independently
-> concludes that the valid-but-never-matching rule *'needs a third state, not a pass or a fail.'*
-> Two subsystems, same day, same finding: **a check that reaches outside its own repo cannot be
-> two-valued.** That is a candidate for doctrine rather than for restating per item — I'd rather
-> rule it once than condition it three more times.
+> 1. CONDITION: three states — bound / drifted / cannot-assess — and cannot-assess must be distinguishable in the fleet summary, never folded into green. A green fleet that includes an unassessed binding case is the same overstatement one layer along.
 
-*Recorded rather than quietly repaired: a package that mis-attributes a quotation to a governed
-record is the exact failure this instrument exists to prevent, and the second time this week I have
-pointed a citation at the wrong entry. The mechanical quote-verification pass caught it — which is
-the argument for running that pass rather than trusting the draft.*
+**The dropped sentence is the one that answers Q2**, and it was in the record all along. See Part VII.
+
+⚠ **BOTH citation errors in this package have ONE cause, and the script cannot diagnose it: I
+quoted the ADVISORY message and attributed it to the PLACED record.** They are different documents
+— placement can add, cut, or re-word — so quoting the advisory systematically loses whatever the
+act of placing contributed. Here it lost precisely the sentence that would have closed a gate
+question without asking. Recorded as the generalizable finding, not as two separate slips.
 
 ### I.3 — `reference-verification-ladder.md`, the silent-net entry (steward-held; executor testimony)
 
@@ -123,9 +115,23 @@ traceback where the honest answer was *"I could not look"*. Closed 2026-08-08 at
 rather than per-site. ⚠ **Closing the first six revealed two more** in suites the first census had
 cleared — the class was wider than the instrument that found it.
 
-⚠ **Instances 1–5 are why I think this is discovered rather than invented.** Five independent
-implementations of the same shape, in three subsystems, by different hands, before anyone proposed
-a rule. A doctrine that has to be argued into existence is weaker than one that has to be *noticed*.
+⚠ **CORRECTED AT THE GATE — the five are NOT one shape, and my *"five … same shape"* was wrong.**
+Tested against this table's own rows: **two are the doctrine's shape** (1 R0's three states; 3
+`test_retrieve`'s named skip — a check reporting it could not assess). **Three belong to an adjacent
+principle**: 2's own row says it refuses two-valuedness *"for a different reason: declared-vs-new"*,
+and a declared failure is **assessed**, not unassessable; 4 is a **marking** shape, detectable
+staleness of declared data; 5 is attested absence of a **finding**, not of an **assessment**.
+
+**So: two pre-existing instances of the shape, three of the adjacent principle, one found at the
+gate itself** (§2 of the ruling — this package's own verifier reporting `verified` on a
+reconstruction; the only instance in the set independent of the advisory that proposed the doctrine).
+
+⚠ **And the adjacent principle is already ratified**, which relocates the proposal rather than
+weakening it: `~/REVIEWED.md` REVIEWED-47, **2026-07-05** — the exclusion path, *"attested absence
+lives in its own honest top-level key `source_excluded`"*, with the `sectionless:` precedent that a
+bare flag is not a safeguard and an attributed attestation is. **I searched for a parent among R0
+(D-1, correctly withdrawn) and Constraint 4, and missed the ratified sibling closest to it in
+content.**
 
 ---
 
@@ -133,9 +139,15 @@ a rule. A doctrine that has to be argued into existence is weaker than one that
 
 ### III.1 — Statement
 
+<!-- own-text -->
 > A check whose subject can be **absent** must report three outcomes, not two: the property holds,
 > the property fails, or **the property could not be assessed** — and the third must remain
 > distinguishable in every aggregate the check feeds.
+>
+> **The third outcome is itself two kinds, and they must not be merged:** unassessable because the
+> **subject** is absent — an environment condition, which must not block — and unassessable because
+> the **check** is broken — a defect, which must. Merging them lets a broken check hide behind an
+> environment excuse.
 
 ### III.2 — Why two values cannot satisfy Constraint 4