# Jurist design-gate ruling — PENDING-112 (received 2026-08-07)

Filed verbatim as received, steward-relayed. Steward concurred the same day
("i concur with the jurist"). The package it rules on is
`harvest-routing-JURIST-PACKAGE-2026-08-07.md`; the disposition is layered in that
file's Addendum, which does not rewrite Parts I–IX.

## Preamble — two items the jurist surfaced while verifying grounding

**REVIEWED-87's amendment landed and is correctly implemented.** `~/CLAUDE.md`,
`PENDING-23` and `MEMORY.md`'s pointer lines all check out verbatim against this
package's Grounding — "no discrepancies this time, cleanest of the three so far".
Correction-in-place (not bumped, as ruled), `@4` reserved, the nested-escape test in
the suite and attributed to the jurist by name.

**A ruled scope line is superseded.** The jurist scoped the affected sources as
"currently known to be Alexander only"; the follow-up census found **three** —
Alexander (293 occurrences), Musil's *The Man Without Qualities* (16), Arendt's
*Eichmann* (1). Substance unchanged: the fix was general, not Alexander-specific, and
no verdict in the window is confirmed to have overclaimed. The record already
corrects it; no action required.

**D-4 moved.** The same session found Gustave Thibon's introduction to a Simone Weil
text indexed as citable Weil — "the exact failure voice-purity exists to catch, and it
was caught, in a source unrelated to Alexander". "Using this book" was partitioned out
of withheld paratext in the same pass. Flagged as moved, **not treated as settled**.

## The ruling

```
JURIST DESIGN-GATE RULING — re PENDING-112

Q1  PROPOSAL, concur. Touches no ESCALATE item; operationalizes Memory
    Discipline via the established constitution/mechanism split, doesn't
    amend it.

Q2  AUTHORIZE the enforceable filing gate (option a). Low-cost, labelling-
    only, directly implements Constraint 4. Bound to Q6's falsifier rather
    than resting on jurist-executor agreement, per the doctrine's own
    caution — jurist's independent lean given for the record, not as the
    deciding vote.

Q3  Concur — execute Stroke 2 after the ladder trigger lands, not before.
    Standing authorization unchanged; only sequencing shifts.

Q4  Concur — prospective-only, meaning no mandatory sweep, not a frozen
    backlog. Opportunistic re-routing of the 154 permitted, not required.

Q5  Concur — steward-triggered tooling is not this proposal's to legislate.
    Flagged to the steward directly, not ruled.

Q6  AUTHORIZE proceeding now, trial alongside. Pre-registration made
    binding: a dated PENDING report at the 20-session mark, filed
    regardless of outcome. A result below the pre-registered 60% reopens
    Q2's rationale specifically, not the whole gate by default.

Net effect: filing gate takes effect prospectively; ladder gets its wake
sentence now; Stroke 2 follows; 20-session falsifier is a standing
obligation, not a disclosed intention. Separately: REVIEWED-87's scope
line should be read superseded by the amendment's 3-source census — no
action needed, record already corrects it.
```

## The jurist's Q2 reasoning, recorded because it is stronger than the package's own

> the aggregate case is stronger than that single pairing: 53 skills at a *clean* 0%
> across five months and 64 sessions, contrasted with 77–83% for ritual-bound items,
> isn't the pattern you'd expect from pure discipline variance — discipline failure
> predicts occasional lucky recalls across 53 skills over that many sessions; a hard
> zero across the whole class is more consistent with a category difference than a
> graded one. I'd weight that higher than the package does.

And, immediately, the self-limitation:

> this is exactly the shape of claim Part VIII's own caution is about: a jurist
> reaching the same conclusion as the executor on 'is the executor's failure
> structural' is a weak check by the doctrine's own terms, formation-wise. I'm giving
> you my honest read, not a settled answer.

> the executor named Q2 and Q6 as the two questions where jurist concurrence shouldn't
> be read as settling anything, on formation grounds. I agree with that caution and I'm
> not overriding it by ruling — I'm ruling because the executor needs an answer to
> implement, and because both questions now route to an objective 20-session check
> rather than resting on our agreement. If your own sense of the executor's actual
> retrieval behaviour across sessions disagrees with H1, that's exactly the kind of
> check this doctrine says only you're positioned to make, and it should override what's
> below.

## Q5 — put to the steward directly, not ruled

> a tool at 0% for 3.7 months despite being built might be worth asking yourself
> whether it's not useful as designed, or just easy to forget exists — which would be
> the same storage-is-not-memory problem, on your side of the loop rather than the
> executor's. Yours to weigh, not mine.