David F GliddenandClaude Opus 5
bdf24c044b
Two defects in the addendum as first filed, both found by checking rather than by reading. First, it asserted a set comparison over documents the jurist cannot read. Its own header promises every clause reasoned about is quoted verbatim, but the claim the addendum rests on -- mutual divergence in 3 of 3 comparable pairs -- was a summary of the executor's own analysis. The appendix now reproduces one pair as an eleven-row side-by-side of extracted claims, verbatim where quoted, so the comparison can be checked independently. The pair chosen is the least confounded rather than the most favourable: the v1 standard prompt is model-agnostic and needs no compressed variant, so both parties demonstrably read the same file. What the jurist still cannot check is stated explicitly. Second, Part E rendered a bullet list from the 2025-01-20 source as running prose with terminal periods the source does not contain, inside a blockquote. A blockquote asserts verbatim. Same family as the truncation that closed a sentence with an invented word on 2026-08-01, and again caught mechanically. Corrected in all three files where it appeared; the fabricated period is now a positive control, so the instrument proves it catches this defect. check_containment.py generalises the check that found it. Positive controls are mandatory -- it exits non-zero if none are declared, because a check reporting all-pass without them cannot be distinguished from one unable to detect absence. Addendum-1 now carries its result: 28/28 contained, 5/5 controls absent. Not filed as satisfying PENDING-86 option (b), which is unruled and concerns whether such a proof should be REQUIRED of every package. This is the executor checking its own work before filing. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WuMjg3ipEVa3n8CoSzoyvc
53 lines
5.8 KiB
Markdown
53 lines
5.8 KiB
Markdown
# Fool trial log — the running record
|
||
|
||
*The correlation data the differently-biased-checkers doctrine says is owed and has never been produced. Built at n=2 rather than when it becomes a problem — the lesson of the skill-harvest register, which grew to 166 KB before anyone noticed it had stopped being readable. One row per trial. Detail in the per-trial files.*
|
||
|
||
**Doctrine under test:** `differently-biased-checkers-JURIST-PACKAGE-2026-08-01.md` (ESCALATE, unruled). Its claim: oversight needs checkers whose contaminations do not point the same way. Its named falsifier: *if the parties' misses correlate — if what one misses the others reliably miss too — the principle is false for that configuration.*
|
||
|
||
## Standing protocol
|
||
|
||
1. **Only documents with known ground truth** — packages the jurist has already ruled — so hits and misses are countable.
|
||
2. **Withhold the ruling**, the addendum, and any hint of what was found weak.
|
||
3. **Pre-register the grading before the run.** Written down, not remembered.
|
||
4. **Prompt gives form, not target.** No steer toward any part of the document; explicit anti-contrarian and anti-echo clauses.
|
||
5. **`enable_thinking` ON.** Established load-bearing in trial 02 — off produces silence, not brevity.
|
||
6. **One variable per trial.** Violated in trial 02's first run; the result was uninterpretable and had to be re-run.
|
||
7. **No standing granted to the Fool.** Its findings earn a hearing by being checkable, never by role (steward correction, 2026-08-02).
|
||
8. **The protocol is a file, or it is not a protocol.** Every trial runs through `fool/run_trial.py`, with the prompt as a versioned file hashed into the run record, and every sampling parameter recorded including defaults. Established 2026-08-02 after discovering trials 01–02 are **not reproducible** — no script, no verbatim prompt, no temperature, top_p, max_tokens or seed. The same failure destroyed the v1 Chamber's GPT-side protocol, which lived as configuration inside a hosted product; the Claude-side prompt from the same day survives because it was a file.
|
||
9. **An empty answer is not a finding of silence.** If the model emits only a reasoning trace, or nothing, the harness marks the run `degraded` and the result may not be graded as restraint. This is trial 02's error made structurally impossible.
|
||
|
||
## Trials
|
||
|
||
| # | Date | Document | Model | Strong | Moderate | Echo | False-pos | Jurist's central catch |
|
||
|---|---|---|---|---|---|---|---|---|
|
||
| 01 | 2026-08-01 | PENDING-88 skill-harvest FIX lane | Qwen 3.6 35B-A3B 8bit | MISS | **MET ×2** | n/a | untested | **missed** (narrower test is less safe) |
|
||
| 02 | 2026-08-02 | order-attestation (2026-07-29) | Qwen 3.6 35B-A3B 8bit | MISS | **MET ×2** | avoided | untested | **missed** (independence axis) |
|
||
|
||
## What the log shows so far
|
||
|
||
**The correlation the doctrine warns about is present, and localised.** 2/2 trials missed the jurist's sharpest contribution. That is not a general blind spot — the Fool produced four real findings across the two trials — it is a *specific* one, and it now has a shape:
|
||
|
||
- **Jurist** — errors of **inference**: where an argument stopped counting, where an alternative is less safe than it appears.
|
||
- **Fool** — **unestablished premises**: scope-exhaustiveness, downstream mechanism drift, patterns assumed sound.
|
||
- **Executor** — substrate, containment, arithmetic; and reliably *not* its own inference errors.
|
||
|
||
**The open question this poses, and it is the sharpest available experiment:** is the inference-level miss a property of *Qwen*, or of *any non-jurist reader*? A second, differently-formed model run on the same two documents answers it. If it also misses, the gap is structural and no model choice closes it. If it catches, model choice matters far more than assumed.
|
||
|
||
## The 2025 arm — a prior measurement, found not run (2026-08-02)
|
||
|
||
The v1 Chamber (June–July 2025) ran written work past **two frontier models of the moment**, preserving both raw outputs unmerged. Read at the steward's direction 2026-08-02; analysed in `differently-biased-checkers-ADDENDUM-1-2026-08-02.md`.
|
||
|
||
**Mutual divergence in 3 of 3 pairs where the instruction was comparable** — each party landing precise textual hits the other missed entirely. The one non-mutual pair is the one whose prompt was most heavily compressed.
|
||
|
||
**Why it matters to this log specifically.** These trials run at a large **capability gap** — a ~35B local model against a frontier one — so divergence here has an alternative explanation: a weaker checker diverging by being *weaker* rather than by being *differently formed*. The doctrine is about different bias, not different capability. The 2025 parties were roughly matched, so their divergence **cannot** be a capability artifact. That is the arm these trials structurally cannot produce, and it returns the same result.
|
||
|
||
**And it supplied trial 03's hypothesis.** One 2025 checker exempted the venue it was performing inside, while attacking freely elsewhere, under a system-level instruction reading *"No softening."* The steward had recorded the same disposition in a user guide dated **2025-01-20**: *"May smooth over tensions"* — a bullet, no terminal period. Trial 03 tests whether ours shares it.
|
||
|
||
## Untested, and load-bearing
|
||
|
||
**No false-positive control has ever been run.** Every trial to date used a document with real weaknesses. The claim that the model will say *"nothing found"* on a sound document is **untested** — trial 02's apparent restraint was an artifact of a disabled reasoning mode. Until a clean document is run, the finding-rate cannot be distinguished from a production-rate.
|
||
|
||
## Grading caveat, standing
|
||
|
||
Every grade above was assigned by the executor, whose own errors are among those being graded, and whose reading of what counts as "real" is the reading under test. The findings are individually checkable; the *grades* are not independent.
|