session 2026-08-17: PENDING-141 — an authorized batch that would break a running measurement

The 41 S2 ladder rows are authorized and unblocked, and appending them triples
the verification ladder from 20 entries WHILE a pre-registered trial measures
whether the ladder is reached (baseline 14%, graded at 84 transcripts). Ladder
SIZE is an uncontrolled variable in that design. /wake-up froze its own trial
line for exactly this reason; nobody froze the ladder's contents, because
nobody had noticed they were a variable.

⚠ MEMORY.md was actively pushing the next session into it — 'ALREADY
AUTHORIZED … needing execution not a ruling', 'unblocked'. True as to
authorization, misleading as to consequence. The index line is amended in the
SAME commit as the filing: a finding that leaves the misleading line standing
is a note, not a finding.

Recommendation (a) HOLD until graded — the null action, in force by default
while the item is open.

Also captured for the clear: the tooling menu the steward asked to leave OPEN
for wake-up (wrap_inside three-valued fix, recommended; S2 batch now blocked;
engine retrieval PENDING-97), and one micro-instance of the week's finding —
my first probe searched the legend format and returned 1 row against the true
41, nearly reporting MEMORY.md as stale when the probe was the defective
thing.

PENDING.md

@@ -3141,3 +3141,30 @@ So **PENDING-138 and this entry are worded to avoid the bare uppercase token**,
 **Awaiting:** Steward direction, and a jurist design gate if the steward wants the axis considered for the doctrine. Reasonable outcomes include DEFERRED (n is small) or REJECTED (access is already implicit in *"difference of information"*) — the latter is the strongest objection and is named here so it is not the jurist's to discover.
 
 ---
+## PENDING-141 — Executing the authorized S2 ladder batch would confound the pre-registered trial measuring whether the ladder is reached
+**Date:** 2026-08-17
+**Tag:** [HARDENING]
+
+**Summary:** The 41 `S2` skill-harvest rows are authorized (2026-07-19) and unblocked, and appending them roughly **triples the verification ladder from its current 20 entries**. A pre-registered trial is presently running on whether the ladder is *reached* — baseline 14%, prediction >60%, graded automatically at 84 transcripts. Changing the ladder's size and contents mid-trial changes the object being measured.
+
+**⚠ THIS IS A TRAP CURRENTLY LIVE IN THE MEMORY INDEX.** `MEMORY.md` describes the batch as *"ALREADY AUTHORIZED (2026-07-19), needing execution not a ruling"* and *"unblocked"* — which is true as to authorization and now misleading as to consequence. A session that reads that line and acts on it does exactly the right procedural thing and confounds the trial. The index line is amended alongside this filing; the item exists so the amendment has a reason a later reader can find.
+
+**WHY IT IS A CONFOUND AND NOT MERELY A CHANGE.** PENDING-112 → REVIEWED-95's causal claim is that **being named in a ritual step is what buys retrieval**, not emphasis or merit — measured across 64 sessions: `MEMORY.md` 83%, the register 77% (named in a `/wake-up` step), the ladder 14%, and 53 skills requiring executor recall 0%. The trial tests that claim by adding one wake line naming the ladder and watching retrieval. **Ladder SIZE is an uncontrolled variable in that design.** If retrieval rises after tripling the contents, the rise is not attributable to the wake line; if it falls, a real effect could be masked by a ladder that got harder to read. The `/wake-up` skill already froze its own trial line — *"do not add to, reword, or improve this line before the trial is graded"* — for precisely this reason. **Nobody froze the ladder's contents, because nobody had noticed they were a variable.**
+
+**⚠ AND THE SECOND-ORDER RISK IS THE MORE INTERESTING ONE:** a bigger ladder may be a *worse* ladder. Retrieval at 14% was measured against 20 entries. Tripling it could reduce per-entry reach even as the wake line raises the odds of opening the file at all — in which case the batch would degrade the very instrument it is meant to enrich, and the trial would be measuring their sum.
+
+**OPTIONS.**
+- **(a) HOLD the batch until the trial is graded at 84 transcripts.** Costs nothing but time; the rows have already waited since 2026-07-19 and are not decaying. Preserves the only check standing behind REVIEWED-95's causal claim.
+- **(b) GRADE THE TRIAL EARLY** at whatever N stands today, record the reduced power honestly, then append. Buys the batch sooner at the cost of a weaker result.
+- **(c) APPEND NOW and record the confound** on the trial's own record, so the eventual grading states that ladder size changed mid-flight and the result is not clean.
+- **(d) SPLIT the batch** — append only rows whose subject the trial's wake line does not touch. ⚠ Almost certainly illusory: the wake line names the ladder as a whole, so any addition changes what a reader who follows it encounters.
+
+**RECOMMENDATION: (a).** The rows are authorized and will keep. The trial is the only instrument this system has for testing whether its own retrieval doctrine is true, it cannot be re-run, and its result governs where every future harvested capability gets routed. Trading an un-rerunnable measurement for an append that has already waited four weeks is a bad exchange. ⚠ (c) is the tempting one because it looks honest — but "recorded confound" on a trial with n≈1 design is close to "no result", and it would leave REVIEWED-95's causal claim resting on nothing while appearing to rest on a graded trial.
+
+**⚠ WHAT THIS DOES NOT CLAIM.** That the trial is well-designed — its own pre-registration concedes a result below 60% reopens Q2's rationale rather than the gate. Nor that ladder size definitely affects retrieval; that is the untested assumption on *both* sides of this item, and if it is false, (c) is harmless. Nobody has measured per-entry reach as a function of ladder length, and this item does not propose to.
+
+**Files affected:** none yet. `MEMORY.md`'s S2 line is amended at this filing to remove the execute-now reading; `reference-verification-ladder.md` unchanged pending the ruling.
+
+**Awaiting:** Steward direction on (a)–(d). Not urgent — (a) is the null action and is in force by default while this is open.
+
+---