[PROPOSAL] Re-aim the Fool at the seating question; input-dependence arm pre-registered

The steward restated the original intent: the Fool was trialled to see
what a different model, local on the M4, adds or subtracts in the fool
role. That is a deployment question. The trial log's stated subject is the
differently-biased-checkers doctrine and its falsifier. They are not the
same question and almost the whole programme serves the second.

The jurist's correction is adopted and it changes what the instrument
measures. The add and the subtract may be one mechanism rather than two
columns: a reader that pattern-matches surface structure without close
reading produces both the distinctive finding-class — distinctive because
the other two read closely and are looking elsewhere — and the
insensitivity to what is on the page. So the executor's closing option,
seat it for the class and treat the noise as cost, is incoherent as posed
and is withdrawn. You cannot keep the class and fix the noise if the noise
is what produces the class.

The instrument is blind A/B arm-matching over five document pairs. It
needs no sound control, which is what voided trial 04 and what the whole
Control Kernel exists to supply: a differential criterion needs only that
documents differ in known ways. Matching within a pair rather than across
documents, because the Fool quotes text verbatim and a cross-document
matcher would succeed on topic alone with zero real reading. Executor-
authored defect injection is conservative here, unlike trial 04, since an
error in the base appears in both arms and can only reduce measured
tracking. The matcher is the jurist or the steward, never the executor.

Three dispositions fixed before the run at the steward's direction, the
executor's binary declined as having no middle when the middle is the
likeliest result. The harvest runs in every branch: if the output does not
track input the Fool is producing a checklist, so extract it as a static
artefact and the programme closes with a deliverable rather than a null.

Corrections carried: the parking list was wrong. The jester replacement
run names the run authorized by Q1 of the ruling on PENDING-148, not a
programme item, and parking it would have disposed of a live authorization
by side effect. Trials 05-08 and the Fool's D-2 gate have never existed as
documents anywhere, so parking them abandons a numbering, not work.
PENDING-89 is told that the re-aim starves it, rather than being starved
quietly. And placing REVIEWED-124 will make PENDING-148 read closed while
the OP-02 question is live — Class E arriving in real time.

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

PENDING.md

@@ -825,6 +825,16 @@ Constraint 6's own doctrine does not claim to guarantee and which `D:memory.conf
 prescribes. Recorded as evidence bearing on PENDING-140 as well: on this instance the two axes of
 checker independence did not save the reading; the substrate did.
 
+⚠ **Second note, same day — this item is about to LOSE its evidence source, and is told so rather
+than starved quietly.** The Fool programme is being re-aimed from the doctrine question (*do the
+parties' misses correlate?*) to the steward's deployment question (*does seating a local model on
+the M4 in the fool role add or subtract value?*). **PENDING-89 IS the doctrine question** — the
+correlation review REVIEWED-86's Q3 asked to be docketed, with PENDING-140 feeding it. After the
+re-aim, no trial feeds it. Remaining sources, all retrospective: (i) the trial-04 correlation
+datum, n=1; (ii) the 2026-08-20 FL5 datum immediately above; (iii) the 2025 arm, recorded as
+found-not-run. **No new instrument currently feeds this item.** Named by the jurist, 2026-08-20,
+and recorded here at its direction — the gap is created by the re-aim, not discovered later.
+
 ## PENDING-90 — First L2 transfer: checker position in the calibration loop
 **Date:** 2026-08-02
 **Tag:** [ESCALATE]
@@ -3621,3 +3631,56 @@ item exists to report. Routed back for a second gate.
 **Scope of that finding, so it is not over-read:** these are distinctive-term markers and a
 paraphrase would evade them. Strong for FL5's mechanism (a named theorist plus two technical
 terms); weaker for FL4, whose substance is ordinary-language and paraphrasable.
+
+### RE-AIM 2026-08-20 — the programme was answering an adjacent question
+
+**Steward, restating the original intent:** the Fool was trialled *"to see what value would be
+added or subtracted by having a different model, and local on the M4, assume the role of the fool
+within our tripartite governance structure."* That is a **deployment** question. The trial log's
+stated subject is the `differently-biased-checkers` **doctrine** and its falsifier. They are not
+the same question, and almost the entire programme serves the second.
+
+**Jurist finding, adopted — the add and the subtract may be one mechanism, not two columns.** A
+reader that pattern-matches surface structure without close reading produces *both* the distinctive
+finding-class (distinctive because the other two read closely and are looking elsewhere) **and** the
+insensitivity. *"Landed on the sentence, named something else"* is the signature of the disposition
+that generates the class. **The executor's closing option — seat it for the class, treat the noise
+as cost of doing business — is therefore incoherent as posed**, and is withdrawn. You cannot keep
+the class and fix the noise if the noise produces the class.
+
+**Instrument filed:** `claude/governance/fool/input-dependence-01-PREREGISTRATION.md`, sha256
+`d41e1d5754fd0eef994616a89a3b95296516a4819737cd4e8ebdd3ae6bbf47db`. Blind A/B arm-matching, N=5
+pairs, p ≤ 0.031 at all-correct. **Requires no sound control** — a differential criterion needs
+only that documents differ in known ways, so the failure that voided trial 04 cannot recur, and
+executor-authored defect injection is *conservative* here because an error in the base appears in
+both arms and can only reduce measured tracking. Matching is done by the jurist or steward, never
+the executor.
+
+**Three dispositions fixed before the run, per steward direction** — the executor's binary is
+declined as having no middle, and the middle is the likeliest result: (a) **tracks** → separable,
+seat it; (b) **does not track** → decisive about a named proposition, that the Fool may occupy no
+role where its output stands as a finding until refuted, because no-information treated as a check
+is an unfalsifiable green light; (c) **partial** → one further arm at higher N, or close as
+unresolved, chosen from these two only. **The harvest runs in every branch**: extract the recurring
+question-set as a static checklist artefact, so the programme closes with a deliverable rather than
+a null. **Steward testimony is solicited before the run and recorded as testimony**, being the one
+input no instrument here can produce.
+
+⚠ **DISAMBIGUATION — the executor's parking list was wrong and is withdrawn as written.** "The
+jester replacement run" names **the run authorized by Q1 of the ruling on this item**, not a
+pre-existing programme entry. Parking it would have disposed of a live authorization by side
+effect, and the authorization is not yet in the register. Parkable: trials 05–08, the Fool's D-2
+gate, the reduction arm. **Not parkable: the Q1 replacement run.** Note that **trials 05–08 and D-2
+have never existed as documents anywhere** — searched dotfiles, CapableMind-AI, the vault and the
+memory tree; every on-disk `D-2` belongs to another workstream. Parking them is formal abandonment
+of a numbering, not of work.
+
+⚠ **ORDER: rule this item before the re-aim lands.** Per the jurist — a void that is never recorded
+is worse under a reframe than without one, because parking leaves a compromised instrument in the
+record unmarked and citable by someone who does not know why it stopped. Trial 09's void is
+currently recorded in the fool tree and the trial log **but not in `~/REVIEWED.md`**. REVIEWED-124
+is drafted and awaits the steward's hand.
+
+⚠ **CLASS E, arriving live (PENDING-146).** Placing REVIEWED-124 will make this item read **CLOSED**
+while the OP-02 reopened question — a second gate the ruling never saw — is still live. The draft's
+Notes carry it; `governance_state()` reads headers, not Notes.