[FIX] REVIEWED-86: file the ruling, draft the Constraint 6 amendment, docket Q3

Ruling filed verbatim. Drafting authorized by the steward's placement of
REVIEWED-86; application is not, and ~/CLAUDE.md is untouched.

The amendment adds a second paragraph to Constraint 6 and replaces nothing --
both original clauses survive verbatim, the caution is refined rather than
relaxed, and the L2 deferral stands.

Both jurist conditions welded into the text that would actually land, not left
in surrounding commentary, since a future reader cites the doctrine block and
not the discussion of it. Q2: biases that fail to coincide do not cancel, and
the doctrine may never be cited as assurance something WAS caught. Q3: the
jurist and executor do not differ in formation, their separation is the weaker
kind, and neither the doctrine nor its evidence establishes that pair as a check
in the strong sense -- the doctrine naming the configuration that produced it as
the one it does not vouch for.

Steward ruled the open question on `Status: provisional` sitting inside a section
headed "cannot be overridden": retain it. Constraint 6 already carries a temporal
qualifier, so the section is not free of them.

Paste block prepared separately, indented to continue the numbered list. The edit
is the steward's: Constraint 1 names this file and sits under "cannot be
overridden by any session instruction", and the ruling states the steward's own
act is what nothing substitutes for.

PENDING-89 dockets the Q3 correlation review the jurist declined to leave
hypothetical, with the hazard named -- this is the executor measuring whether the
executor is checked, so criteria must be pre-registered and it may be steward-only
work.

Q4 folded into the existing REVIEWED-85 check-in agenda rather than given its own
cadence, per the ruling's reasoning that a new standing review produces another
unread register.

PENDING-86 amended with its third instance: the jurist could not reach
contamination-problem.md while gating an argument that turns on it.

Convergence question closed. The jurist inferred a common source; the steward
confirmed it -- the exchange was shared as context only, and Document A predates
it, so the jurist's language cannot have shaped the proposal. Neither
contamination nor corroboration.

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

PENDING.md

@@ -638,6 +638,8 @@ Executed as §VII eyeball-after-gate: pages rendered with `pdftoppm` and read, n
 **Awaiting:** Steward authorization — it widens what the jurist can read, which is the steward's call, not the executor's.
 **Amendment 2026-07-29 (PENDING-87 / REVIEWED-84 process note, jurist-raised, not ruled):** a **second, independent** instance of this item's failure, and it sharpens the diagnosis. The jurist's REVIEWED-83 Q3 demanded an outcome REVIEWED-74 had already established was impossible — a ruling **four days older**, in a file the jurist *could* read, but had no reason to open, *"since nothing in the package I ruled on mentioned order or Eichmann at all."* So the gap is not only **"the jurist cannot read the constitution it design-gates"** but **"the jurist cannot discover a relevant prior ruling whose ID it does not already know."** Keyed retrieval cannot fix that; only search can — hence option (d). The jurist directed this be folded here rather than opened as a new item.
 
+**Amendment 2026-08-02 (third instance, jurist-raised in REVIEWED-86):** the jurist could not reach `contamination-problem.md` — *"same gap as the skill files last time, now touching the part of the argument that establishes the doctrine actually has a gap to fill"* — and called this *"a second, independent argument for it"*. So the tally is now three distinct documents the jurist has been unable to read while design-gating work that turns on them: the chamber constitution, the skill files, and now a CapableMind methodology doc. **The workaround was built rather than proposed this time:** `dotfiles/claude/governance/check_containment.py`, positive controls mandatory, which discharged REVIEWED-85's stated precondition (7/7 contained, 5/5 controls absent) and caught a fabricated terminal period in the executor's own package. That is evidence option (b) is *workable*, not merely proposable — and it bears on the (a)/(b)/(c)/(d) choice, which remains the steward's.
+
 ## PENDING-87 — Order attestation: the REVIEWED-83 Q3 precondition is unsatisfiable as written
 **Date:** 2026-07-29
 **Tag:** [PROPOSAL]
@@ -676,3 +678,13 @@ Measured against the register itself before acting. Four corrections; the item's
 **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.**
+
+## PENDING-89 — The Q3 correlation review: are jurist and executor misses clustered?
+**Date:** 2026-08-02
+**Tag:** [HARDENING]
+**Summary:** Run the falsifier the differently-biased-checkers doctrine names against the existing PENDING/REVIEWED record, rather than leaving it hypothetical.
+**Rationale:** REVIEWED-86 left Q3 — *do two Claude instances constitute a check, or only a second reading?* — explicitly unresolved, and the doctrine text placed at Constraint 6 says in its own words that neither it nor its supporting evidence establishes the jurist–executor pair as a check in the strong sense. The package named the test that would settle it: whether jurist and executor errors cluster in the same classes while steward corrections catch a systematically different class. The jurist's ruling notes it is **checkable now**, on the rulings that exist, and should be docketed rather than float. If misses cluster, the doctrine is false for this configuration and must be weakened to *"only the steward supplies genuine independence; jurist review is a second reading, valuable and not a check."*
+**Options:** (a) run it on the four most recent rulings only (REVIEWED-83 to -86) — fast, but n=4 and all from one arc; (b) run it across the full REVIEWED/PENDING record — larger n, but the older entries predate the current three-party discipline and may not be comparable; (c) run (a) now as a pilot with its own pre-registration, and use it to decide whether (b) is worth the cost.
+**Recommendation:** (c). The same shape as the Fool trials and the 2025 archive read: pre-register what counts as a clustered miss *before* reading, or the executor grades its own errors after seeing them. Note the standing hazard — this is the executor measuring whether the executor is checked, which is the contaminated form; the grading criteria must be fixed in advance and the raw classifications left checkable.
+**Files affected:** none yet; a measurement, not a change. Output would be a dated record beside the doctrine package.
+**Awaiting:** Steward direction on (a)/(b)/(c), and on whether the executor is the right party to run a measurement of its own oversight at all — the jurist is no more independent here, so this may be steward-only work.