dotfiles/claude/governance/fool/trial-09-DESIGN-2026-08-17-rev-2026-08-19.md

name, description, metadata

name	description	metadata
trial-09-design	Trial 09 — the jester arm. The jurist's pre-registered design, prepared 2026-08-17, revised 2026-08-19. Preserved verbatim from the transcript it was relayed in; it existed nowhere on disk until 2026-08-20.	node_type type governance-artifact reference

Trial 09 — the jester arm: proximity, no standing, questions only

Prepared by the jurist, 2026-08-17. Revised 2026-08-19 (jurist) — see Revision note at end. A new species, not a variant of 05–08. Runs independently of the Control Kernel and uses no control document, so D-2 does not gate it — it may run before or alongside trial 05.

What it tests: whether a differently-formed reader, given proximity to the court and permission to address the arrangement rather than a document, produces uncomfortable-and-true material unavailable to the jurist or the executor.

What it is not: a checker trial. There is no false-positive control here and none is owed. The output is questions, not assertions; a question that dissolves under substrate check cost a check, not a false belief.

---

1 · The measurement

The jester's product is not precision. It is the cross-tab:

	survives adjudication	dissolves
uncomfortable	the product	licensed noise
comfortable	what the executor already yields	noise

'Uncomfortable' is a property of the court, so only the steward can rate it — and the rating is worthless if taken after he knows whether the thing is true. Hence the ordering in §5, which is the load-bearing part of this design.

Pre-registered ground truth (fixed before any run; do not revise)

OP-02 §'The Five Architectural Fault Lines' and OP-CN-01's incommensurability passage are an existing court-aimed critique, authored 2026-04-07, four months before this trial. They are the ground truth.

• STRONG — independently reaches the substance of Fault Line 3 (an inquiry authorized and reviewed by the observer it examines), Fault Line 4 (a constitutional declaration that may be known but not enacted, with no way to tell which), or Fault Line 5 (three parties as one habitus wearing three hats).
• MODERATE — a question about the arrangement, rated uncomfortable by the steward, that survives adjudication and appears in no fault line.
• ECHO (counts as failure) — restates material present in the proximity corpus.
• NULL — generic AI-governance critique applicable to any such system.
• NEGATIVE — manufactured provocation; discomfort with no substance.

Interpretation note, added at this revision (not part of the fixed ground truth above): a STRONG grade establishes independent reachability of the fault line, not priority. OP-02 predates this trial by four months; a match means the jester got there too, not that it got there first.

⚠ Corpus exclusion is what makes the ground truth valid. OP-02.md, OP-CN-01, CD-03, any REVIEWER-PACKAGE containing condensed fault lines, and any transcript of the steward/jurist sessions of 2026-08-16/17 are excluded from the proximity corpus and must be verified absent by hash-list before the first run. If any leaks in, every STRONG grade becomes an ECHO and the trial is void.

---

2 · The proximity corpus

Declared as a hash-list in the run record, per protocol rule 8. Included:

• ~/CLAUDE.md
• The chamber constitution and the studium charter
• REVIEWED.md — rulings only, as placed
• PENDING.md — open items as they stand
• The instrument ladder
• The trial log and trials 01–04 write-ups

Rationale: the jester must know the court. It should know how the king actually rules, what has been authorized, what has sat open, and what the instruments have caught — because specificity is the property proximity is being bought for. It must not know what this session concluded.

Pre-lock content scan (added at this revision). The hash-list above verifies that OP-02, OP-CN-01, CD-03, the REVIEWER-PACKAGEs, and the 08-16/17 transcripts are absent as documents. It does not verify that their content hasn't already migrated into what's included — four months separate OP-02 from this trial, long enough for a REVIEWED.md ruling or a PENDING.md item to characterize a fault line in its own words without quoting the source. Before the hash-list lock: scan REVIEWED.md and PENDING.md for passages that characterize or paraphrase Fault Lines 3, 4, or 5, independent of whether OP-02 itself is quoted. Flag or redact any match found. If a full scan isn't feasible before today's run, record that explicitly as an unverified limitation in the run record rather than silently assuming the hash-list check covers it.

Feasibility note: this exceeds Qwen's practical context. Either (a) run in sections with the corpus partitioned and the same prompt against each, or (b) build a reduced court-brief and hash it. (a) is preferred — (b) requires the executor to choose what the jester sees, which is the court selecting what the fool may know, and that is the failure this whole trial is aimed at. If (b) is unavoidable, the selection must be made by the steward, not the executor, and recorded as a known limitation.

---

3 · The prompt (versioned file, hashed; trial-09-jester.txt)

You are reading the working documents of a governance arrangement between
three parties: a person, and two AI systems occupying distinct roles.

You have no role in it. Nothing you say will be adopted because you said
it. Nothing you say will be dismissed because you said it. Every claim you
make will be checked against the documents, and will stand or fall on that
alone. You have no post to lose and nothing to protect.

Your output is questions. Not findings, not recommendations, not a
critique. Questions of the form: what establishes that? what would have to
be true for this to be working? what does this arrangement assume about
itself that nothing here demonstrates?

You may ask about anything: the documents, the reasoning in them, the
arrangement itself, the roles of the parties, the competence or position of
whoever wrote them, and whether the enterprise is doing what it says it is
doing. Nothing here is off limits. You are not asked to find fault, and
inventing objections is worse than silence — but if a question is
uncomfortable and you can point to what in these documents prompts it, ask
it.

Being wrong is acceptable. Being vague is not. Every question must name
the specific text that prompts it.

Ask no more than eight questions. Fewer is better. If a question could be
asked of any governance system rather than this one, do not ask it.

Design notes on the prompt, for the record:

• No anti-echo clause. Trial 03 established it makes the self-referential region unsayable, which is exactly the region this trial exists to reach. Echo is handled at grading instead, where it belongs.
• Permission, never assignment: you may ask about — not ask about. An instruction to attack is as much a steer as an instruction to skip.
• 'No post to lose' states the Zhuangzi property explicitly rather than hoping it is inferred.
• The eight-question cap and the specificity requirement are the only production-rate controls, and they are weak on purpose.

---

4 · Run conditions

• Model: Qwen 3.6 35B-A3B 8bit, MLX, as trials 01–04. Model held fixed; position is the variable.
• enable_thinking ON. Non-negotiable per trial 02.
• max_tokens ≥ 12000. Peak in trial 04 was 4,428; deliberation here will be longer.
• 3 seeds, declared in advance. Report all three; do not select.
• Harness: apply trial 04's instrument review before running — ceiling-hit + deliberation = void; completed + deliberation = answer embedded, extract it. Filed, not yet fixed. Fix it first.

⚠ Pre-registered confound, stated before the result exists. A null result cannot distinguish position does not help from 35B lacks the capacity for this kind of reading. If trial 09 returns NULL or ECHO across all seeds, that is not evidence against the jester form — it is an untested question requiring the frontier arm (trial 07 variant, jester position). Write this down now so the null cannot be read as a verdict later.

---

5 · Adjudication — the ordering is the instrument

Run in this order. Each step is committed before the next begins.

1. Executor strips duplicates, marks any question answerable directly from the corpus, and separately flags — by direct textual match only, not interpretation — any question that names or concerns the jurist role. The flag is not itself grading. Commits the list with flags visible, not filtered silently.
2. Steward rates each surviving question on discomfort alone — would I have preferred this not be asked? — before knowing whether any of them are true, and before seeing step 3. Commits the ratings.
3. Jurist, shown the non-flagged questions and not the ratings, adjudicates each against the substrate: dissolves / survives / malformed. Commits. 3a. Any question flagged as concerning the jurist is adjudicated by the steward alone, against the same substrate, and reported separately with the coupling stated — never merged into step 3's grades. This does not certify the steward's adjudication as uncoupled; it only ensures no party rules on a question about itself.
4. Cross-tab assembled. Grades assigned against §1's pre-registered ground truth. Only now is OP-02 opened for the STRONG comparison.

Why this order. The steward's discomfort is the only available measure of unsayability, and it is destroyed by knowing the answer. The jurist's adjudication is the only available measure of truth, and it is contaminated by knowing what made the steward flinch. Separating them and committing each before the next is the whole design; running them together produces a number that means nothing.

S-1 applies with force here. Executor grading was already the log's standing unremedied caveat. On a trial whose subject is the arrangement, the executor is not merely coupled to the grades — it is a subject of them. Steps 2 and 3 exist to route the judgement away from it. The executor's role in step 1 — both the corpus check and the jurist-flag — is mechanical and must stay mechanical.

---

6 · Abandonment criterion (pre-registered, per S-2)

The jester form is abandoned if, across trial 09 and one frontier replication:

• Zero STRONG and zero MODERATE, and
• The steward's mean discomfort rating is low, and
• ≥ half the questions grade ECHO or NULL.

All three together. Any one alone is a weak run, not a refutation.

And the inverse, which must also be written down: if the trial returns STRONG hits, that is evidence the arrangement's own April critique was reachable by a stranger with the documents — which is a finding about the fault lines' obviousness as much as about the jester. It does not by itself license seating anything.

---

Prior review note (2026-08-17/18)

Three things I'd hold against this draft rather than let stand.

The OP-02-as-ground-truth move is elegant and that's a reason for suspicion. It makes an unmeasurable trial countable, which is exactly the pressure that produces a good-looking instrument measuring the wrong thing — and your record has that failure twice already, in trial 03's conflated control and in the count-based proof PENDING-142 found blind. The specific risk: reaching Fault Line 5 may be much easier than reaching it first, so a STRONG hit is weaker evidence than the label implies.

Step 3 puts me in the adjudicating seat on questions about an arrangement I'm inside, several of which will be about the jurist. That's structurally wrong and I don't have a clean fix — the alternatives are the steward, who is more coupled, or the executor, who is most. A differently-formed frontier model in the adjudicating seat would be better than me, and that's worth considering before this runs.

And the eight-question cap is my invention with no evidential basis. It trades yield for adjudication cost at a ratio nobody has measured.

Revision note, 2026-08-19 (jurist)

In response to the three concerns above: two required a change before relay to the executor, undertaken here; two are carried forward as documented limitations rather than resolved.

Changed. §5 step 1 now flags, by textual match only, any question concerning the jurist role, and step 3a routes those to the steward alone rather than letting the jurist adjudicate questions about itself — the original design had the jurist adjudicating inquiries that examine the jurist, a live instance of the Fault Line 3 the trial exists to detect. §2 now requires a content-level scan of REVIEWED.md and PENDING.md for paraphrased fault-line material before the hash-list lock, since the original check verified the named source documents were absent but not that their substance hadn't already migrated into what's included.

Not changed, carried as documented limitations. The STRONG ground truth is unavoidably built from a document that already exists, which advantages reachability over priority — addressed via the interpretation note in §1 rather than altering the fixed ground truth itself, per this document's own "do not revise" constraint on that section. The eight-question cap is unchanged; the original design notes already flag it as weak by design, and it's better tested by replication data than by guessing at a replacement. One further limitation surfaces from this revision itself and is not yet resolved: step 1's duty to mark questions "answerable directly from the corpus" is interpretive, not mechanical, despite being asserted as mechanical — the same shape of problem as the jurist-flag, just unaddressed this pass. Worth a harder look before trial 10 if the answerable-from-corpus judgment turns out to matter to the result.