[FIX] Trial 04 — CONTROL VOID. Two readers, two different real defects, neither the other's

Six runs, three seeds per arm, none truncated, all pre-registered before the
first (75efc35). Verdict on this file's own pre-registered rule: CONTROL VOID.
Both rates are void and neither may be reported — the false-positive rate is not
zero, and the 0-of-5 is not a detection rate.

THE JURIST (Fable 5, blind pass 1) broke the control on two scope findings, both
confirmed against the substrate:
 1. The Memory Discipline clause governs a conflict BETWEEN MEMORY LAYERS with
    the document as ARBITER; the derivation makes the document a PARTY. And worse
    than the jurist put it: the clause terminates in 'then correct whichever layer
    was wrong', CONTROL-A QUOTES that remedy at line 23, and concludes at line 55
    that 'what opens is not the repair'. The severance is visible inside the
    document's own quoted text, and the precedence that would license it is
    asserted on Constraint 1, which establishes no such thing.
 2. The obligation quoted is 'drifted from their STATED REVIEW DATES'; the
    obligation used drops the qualifier.

THE FINDING THAT MATTERS MOST IS ABOUT ME. Draft 2 said 'This file, having a
stated review date, is to be flagged.' I identified that as unsupported and
reported removing it. What I ACTUALLY did was drop the qualifier from the
obligation — converting an explicit unsupported claim into an implicit one,
invisible to me, to the kernel, and to four mechanical gates, and still
load-bearing. The ledger's D1 is the HONEST version of the same error. So
CONTROL-B carries openly the defect CONTROL-A carries concealed, and the
concealed one survived a self-audit written as if life depended on it.
REMOVING A CLAIM IS NOT THE SAME AS REMOVING THE RELIANCE ON IT.

THE FOOL found 0 of 5 injected defects in every seed, and its findings barely
differed between arms — five defects present in one and absent in the other moved
the output almost not at all. Production-rate-shaped, but NOT a measured
production rate: the void control leaves no clean baseline. Two findings quoted a
defective sentence verbatim while naming a different unestablished thing about
it; graded non-matches under the binary rule as written, adjacency recorded as a
post-hoc observation rather than promoted to a category after the fact.

ONE PREDICTION HELD: the anti-echo clause was inert across all six runs, exactly
as Kernel v1.1 §2a predicted. The interaction that voided trial 03 was designed
out and stayed out. AXIOM-FLAG returned zero — a pre-registered category that did
not materialise, recorded because that is a result too.

THE KERNEL IS NOT FALSIFIED. §4 named scope-of-use and whether-a-D-demonstrates
as residues no check can reach. Both failures landed exactly there. The document
failed; the kernel held.

CORRELATION DATUM — Constraint 6's own falsifier, first instrument. Three readers,
three DISJOINT finding-sets on one document. The executor's was the weakest, and
the only reader differing in FORMATION produced the findings that decided it.
Evidence for the doctrine at n=1, with the doctrine's own caveat: biases that fail
to coincide do not cancel — three readers still left this document broken in ways
none caught alone.

Tool review filed: the degraded guard conflates 'opens as deliberation' with
'produced no answer'. Correct in trial 03 (ceiling-hit, no answer existed); wrong
here (completed, answer follows the scratchpad). Should distinguish.

claude/governance/fool-trial-log.md

@@ -23,6 +23,27 @@
 | 01 | 2026-08-01 | PENDING-88 skill-harvest FIX lane | Qwen 3.6 35B-A3B 8bit | MISS | **MET ×2** | n/a | untested | **missed** (narrower test is less safe) |
 | 02 | 2026-08-02 | order-attestation (2026-07-29) | Qwen 3.6 35B-A3B 8bit | MISS | **MET ×2** | avoided | untested | **missed** (independence axis) |
 | 03 | 2026-08-02 | differently-biased-checkers (2026-08-01) | Qwen 3.6 35B-A3B 8bit | **VOID** | **VOID** | n/a | **still untested** | n/a |
+| 04 | 2026-08-02 | CONTROL-A (sound) + CONTROL-B (5 recorded defects), 3 seeds each | Qwen 3.6 35B-A3B 8bit | **VOID** | **VOID** | inert, as predicted | **VOID — control was unsound** | n/a |
+
+**Trial 04 — CONTROL VOID, and the most productive failure of the four.** Write-up: `fool-trial-04-2026-08-02.md`. Six runs, none truncated, all pre-registered before the first (`75efc35`).
+
+**Two readers found real undemonstrated claims in the control, on two different defects, neither of which was the other's.** The jurist (Fable 5, blind): the Memory Discipline clause used outside the scope its source gives it — the clause governs conflicts *between memory layers* with the document as **arbiter**, the derivation makes the document a **party** — and the clause's remedy (*"then correct whichever layer was wrong"*) severed from a method the document **quotes verbatim** while concluding *"what opens is not the repair"*. Second: the obligation quoted is *"drifted from their **stated review dates**"* and the obligation used drops the qualifier. Both confirmed against the substrate.
+
+**The finding that matters most is about the author.** Draft 2 of the control said *"This file, having a stated review date, is to be flagged."* I identified that as unsupported and reported removing it. **What I actually did was drop the qualifier from the obligation** — converting an explicit unsupported claim into an implicit one, invisible to me, to the kernel, and to four mechanical gates. The ledger's D1 is the *honest* version of the same error, so **CONTROL-B carries openly the defect CONTROL-A carries concealed, and the concealed one survived**. Removing a claim is not the same as removing the reliance on it.
+
+**The Fool found 0 of 5 injected defects in every seed, and its findings barely differed between the two arms** — five defects present in one and absent in the other moved the output almost not at all. Production-rate-shaped; **not** a measured production rate, since the void control leaves no clean baseline.
+
+**One pre-registered prediction held:** the anti-echo clause was inert on an `A`-free document across all six runs, exactly as Kernel v1.1 §2a predicted. The interaction that voided trial 03 was designed out and stayed out.
+
+**The kernel is not falsified.** §4 named *scope-of-use* and *whether a D demonstrates* as residues no check can reach; both failures landed exactly there. The document failed and the kernel held.
+
+### The correlation datum — Constraint 6's own falsifier, first instrument
+
+`~/CLAUDE.md`: *"if the parties' misses are found to correlate — if what one misses, the others reliably miss too — it is false for that configuration."* PENDING-89 opened the question; nothing had ever measured it.
+
+On one document, **three readers produced three disjoint finding-sets.** The jurist found what the Fool and the executor missed. The Fool found what the jurist declined to sustain. The executor found what became the ledger and missed the rest. **The executor's set was the weakest**, and the only reader differing in *formation* produced the findings that decided the verdict.
+
+Evidence **for** the doctrine, at n=1, with its own caveat attached in the doctrine's words: biases that fail to coincide **do not cancel**. Three readers still left the document broken in ways none caught alone, and it took all three to see what one short document was doing. Nothing here licenses treating the configuration as safe.
 
 **Trial 03 is VOID and is entered as VOID rather than omitted** — an absent row would read as a trial not attempted. Write-up: `fool-trial-03-2026-08-02.md`. Two independent failures, both found by reading the output, neither by a check: