[FIX] REVIEWED-122 cond. 9 (as amended): lineage proceeds, ladder entry deferred

The jurist amended condition 9 the same day it was placed, on the executor's
surfacing of PENDING-141, and severed its two actions:

LINEAGE — proceeds now. Touches PENDING-142's kin list, not the ladder; nothing
in PENDING-141 reaches it. Two instances added that predate the three the item
named: Fool trial 03 (harness reported reasoning_present:false / degraded:null on
a run that produced no answer — every field true of the STRING, false of the
RESULT) and Fool trial 04 (degraded guard conflated "opens as deliberation" with
"produced no answer"). Five instances in a fortnight, rediscovered each time as a
fresh coincidence.

LADDER ENTRY — deferred until PENDING-141 is ruled or the trial is graded at 84
transcripts. Not withdrawn: the family is real and the entry is owed. The
argument for waiting is not that one row is smaller than forty-one — PENDING-141
names per-entry reach as a function of ladder length as untested on BOTH sides,
so "one is negligible" is an assumption, not a finding. It is that the finding
does not decay: it lives in REVIEWED-122 regardless, so deferral costs retrieval,
not the record.

OWED-ENTRIES ACCUMULATOR — jurist-proposed, mechanism itself awaiting steward
ratification, appended to PENDING-141's own record rather than to a new file. A
separate register is something a reader might reach INSTEAD of the ladder, which
is a second uncontrolled variable in the same trial. Without somewhere to
accumulate, the freeze silently becomes a loss — which is precisely how this
family came to be rediscovered five times.

Seeded with two entries. OWED-1, the wrong-subject family with all five disguises
enumerated. OWED-2, a discriminator the jurist offered for the literal question
logged unanswered on 2026-08-01 — what separates a real authorization boundary
from a manufactured one at the moment of deciding, when both present as caution
and every available test runs afterwards: can you name the INSTRUMENT that would
be damaged, and does the caution come with an offer to proceed? A manufactured
boundary cites a rule rather than an instrument and terminates in inaction rather
than in a question. n=2 from the executor's own conduct, one of each sign,
recorded explicitly as NOT promoted and with the standpoint disclosed.

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

PENDING.md

@@ -3167,6 +3167,22 @@ So **PENDING-138 and this entry are worded to avoid the bare uppercase token**,
 
 **Awaiting:** Steward direction on (a)–(d). Not urgent — (a) is the null action and is in force by default while this is open.
 
+---
+
+### OWED LADDER ENTRIES — accumulated during the freeze
+*Added 2026-08-17, jurist-proposed, **mechanism itself awaiting steward ratification**. Reason for living here rather than in a file of its own: a separate register is something a reader might reach **instead of** the ladder, which is a second uncontrolled variable in the same trial — the trap one layer along. This list is inert; it changes nothing a reader retrieves. **Without it the freeze silently becomes a loss**, which is how the wrong-subject family came to be rediscovered five times as a fresh coincidence.*
+*Discharge condition: when PENDING-141 is ruled or the trial is graded at 84 transcripts, append these to `reference-verification-ladder.md` and strike this section.*
+
+**OWED-1 — the wrong-subject family.** *Earned across five instances in a fortnight; ordered by REVIEWED-122 cond. 9, deferred by the amendment to that condition the same day.*
+> **A control whose SUBJECT is not the claim's subject is not a weak check — it is not a check.** Ask what proposition the control actually tests before reading its pass as verification. Recurring disguises: a control over *transcription* cited for an *inference over what was transcribed* (2026-08-14); a control at the layer of the decision **rule** cited for the sufficiency of the **signal set** (REVIEWED-83 A1); a **count** cited for a per-item **classification** — which cannot see an error running equally in both directions (PENDING-142; removing 3 false-opens and restoring 3 false-closeds both leave 29); a field true **of the string** cited as true **of the result** (Fool trial 03); a guard conflating *opens as deliberation* with *produced no answer* (Fool trial 04).
+
+**OWED-2 — a discriminator for real vs manufactured authorization boundaries.** *Jurist-offered 2026-08-17, answering the literal question logged unanswered on 2026-08-01 — what distinguishes a real boundary from a manufactured one **at the moment of deciding**, when both present as caution and every available test runs afterwards.*
+> **Can you name the instrument that would be damaged, and does the caution come with an offer to proceed?** A manufactured boundary tends to cite a **rule** rather than an instrument, and to terminate in **inaction** rather than in a question — because its function is to avoid the act, not to protect anything.
+>
+> Evidence, n=2, one of each sign and both from the executor's own conduct: **negative, 2026-08-01** — declined the register split by invoking PENDING-88's *unratified* change-class test, a rule that did not exist, and produced no question. **Positive, 2026-08-17** — declined the ladder entry by naming a specific open item, stating the substantive conflict (ladder size as an uncontrolled variable in a trial that cannot be re-run), taking the null action that item already puts in force, and offering to proceed if overruled.
+>
+> ⚠ **n=2 is not a finding.** The jurist's own words: *"I'd want it tried against more cases before it goes anywhere near the ladder."* Recorded so it is not lost, explicitly **not** promoted. ⚠ And it is offered by one party about another party's conduct, with both instances self-reported by the party under test — the standpoint is disclosed, not corrected for.
+
 ---
 ## PENDING-142 — The open/closed criterion answers "does a REVIEWED header name this id?", not "is this item still awaiting the steward"
 **Date:** 2026-08-17
@@ -3192,6 +3208,12 @@ So closure is signalled **only** by a REVIEWED *header* naming the PENDING id, o
 
 ⚠ **THE FINDING THAT GENERALIZES, and it is the third instance this week.** Removing 3 false-opens and adding back 3 false-closeds leaves **29 — the same number the tool reports.** The change proof cited in `ruled_pendings`'s docstring measured exactly that: a count delta (18 → 19 visible). **A count-based control cannot see a classification wrong in both directions by equal amounts.** The control's subject was the population size; the claim's subject was each item's disposition. Kin to the 2026-08-14 finding (the control tested transcription while the claim was an inference) and to REVIEWED-83 A1 (a control must sit at the layer the defect lives in).
 
+> **KIN LIST — extended 2026-08-17 under REVIEWED-122 condition 9 (as amended the same day).** The condition ruled the lineage longer than this item stated, and severed the lineage addition from the ladder entry: this part proceeds, the ladder entry is deferred behind PENDING-141. Two instances predate all three above:
+> - **Fool trial 03** — the harness reported `reasoning_present: false` and `degraded: null` on a run that produced no answer. Every field was true *of the string* and false *of the result*.
+> - **Fool trial 04** — the degraded guard conflated *opens as deliberation* with *produced no answer*.
+>
+> **Five instances in a fortnight, rediscovered each time as a fresh coincidence.** That recurrence is the argument for naming the family rather than continuing to count it — and the naming is what waits on PENDING-141, not the finding, which lives here regardless.
+
 **Options:**
 - **(a) Match on subject, not on header shape.** Resolve a PENDING↔REVIEWED pair by normalized title when the header carries no id, in addition to the current id match. Closes Class B. Cheap; risks joining two genuinely distinct items that share a title.
 - **(b) Read the ruling's `**Decision:**` and treat design gates as non-closing.** Closes Class C. Requires enumerating which decision verbs close — itself a judgment, and the enumeration is the same "gate on the class, not the instances" trap unless it defaults to *not closed* on an unrecognized verb.