David F GliddenandClaude Opus 5
25cf5a38eb
The parent ESCALATE package was filed 2026-08-01 and never sent. Filing is not sending, and the addendum written the next day is unintelligible without it, so both go as one self-contained artifact. Assembled by concatenation rather than by hand so the parent is provably unmodified: verified by substring, all three components byte-intact (17,938 + 16,740 + 6,773 chars). Containment re-run against the assembled document -- 28/28 quoted claims contained, 5/5 positive controls absent. The cover catches a naming collision the executor did not see until packaging. In the house pattern an "Addendum" is the POST-ruling layer, appended so the ruled-on text is preserved rather than rewritten. ADDENDUM-1 is pre-gate evidence and no ruling has occurred, so a jurist reading the title by house convention would infer a ruling that does not exist. Flagged prominently in the cover rather than by renaming the filed document, which would break the audit trail of what was filed when. The cover consolidates the five gate questions and states plainly what the addendum changes: Q4 sharpened from record-when-observed to a retrieval obligation, Q2 extended with the reading-vs-scope distinction, and Q3 left untouched with the executor's lean still explicitly none. It also states what the jurist cannot check -- the completeness of the executor's extractions, and the two comparable pairs not reproduced. Nothing applied. No ratified document edited. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WuMjg3ipEVa3n8CoSzoyvc
6.7 KiB
title: "Differently biased checkers — design-gate request, with the correlation evidence" date: 2026-08-02 type: ESCALATE · design gate · executor drafts → jurist design-gates → steward authorizes audience: "The jurist, who has NO repository access. This document is self-contained: every clause reasoned about is quoted verbatim within it." status: "DRAFT for the design gate. Nothing in this document is built, run, or landed. The proposal amends ~/CLAUDE.md, which is on the escalate-unconditionally list — so no ruling short of explicit steward authorization permits the executor to apply it."
How to read this
This is one design-gate request in two documents, sent together because the second is unintelligible without the first.
Document A — the package (filed 2026-08-01, never sent, never ruled). It proposes a positive doctrine to sit beside the existing contamination doctrine: that oversight does not require an uncontaminated checker, but checkers whose contaminations do not point the same way. Its Part VII carries the disconfirming evidence the steward asked for, including the strongest argument against the proposal, which concerns this system's own configuration.
Document B — supplementary evidence (2026-08-02). Document A states its own central evidentiary gap in Part VII: "What would actually test the doctrine is the rate of correlated misses, and no such measurement exists." A measurement now exists for one of the two independence categories A distinguishes. Document B files it, bounds it, and asks that two of A's gate questions be narrowed.
A NOTE ON THE WORD "ADDENDUM". Document B is titled Addendum 1. In this system's house pattern an Addendum is the post-ruling layer — the disposition applied after a jurist ruling returns, appended so the ruled-on text is preserved rather than rewritten. Document B is not that. No ruling has occurred. It is supplementary evidence filed before the gate, and the naming is a collision the executor did not catch until packaging. Read it as evidence, not as disposition.
Document A is reproduced exactly as filed on 2026-08-01, unmodified. Document B was written the following day and does not alter it. Where B disagrees with A, A's text stands as the record of what was proposed, and B says what should now be read differently — which is the same discipline the post-ruling Addendum pattern exists to protect.
The one-sentence claim to test: the contamination doctrine currently says what to stop doing and never says what to do instead, and the missing positive principle is that oversight does not require an uncontaminated checker — it requires checkers whose contaminations do not point the same way.
What the jurist is asked to rule
Document A's Part VIII poses five gate questions. Document B does not add a sixth; it narrows two and supplies evidence bearing on a third. Consolidated:
| Question | Status after Document B | |
|---|---|---|
| Q1 | Is the diagnosed gap real — is the existing doctrine purely negative? | Unchanged. |
| Q2 | Is the proposed doctrine text correct, or does it overclaim? | Unchanged, but see B's Part F.1: the doctrine addresses correlated blind spots in reading and offers nothing against correlated failures of scope. B asks whether Part IV's dangerous-misreading caution should absorb that. |
| Q3 | Do two Claude instances constitute a check, or only a second reading? | Still open, and B does not answer it. B measures two differently-formed commercial models — category (ii) in A's Part IV. It contains no Claude-to-Claude pair. The executor's lean remains explicitly none. |
| Q4 | Should the doctrine carry a standing obligation to measure, or is "record evidence against when observed" sufficient? | B asks that this be sharpened, and from an unexpected direction — see below. |
| Q5 | Where should the doctrine live? | Unchanged. Steward's call. |
On Q4 specifically. Document A leans that passive recording is "weaker than it looks — the failure it must catch is one all parties are disposed to miss." Document B supplies a case that supports the lean by inverting its diagnosis. The steward had recorded the relevant observation — in the right words, in a durable, indexed file — eighteen months before the doctrine that needed it, and it took an explicit instruction to retrieve. Passive recording was not the failure. Passive retrieval was. B asks whether any obligation should therefore specify who reads the record, and when — not only that it be written.
And Part VII's stated gap should now read, if the jurist agrees: partially closed for formation independence between differently-formed models; open for category (i), and open for Q3.
What this handoff does NOT do
- It does not modify Document A. A is reproduced as filed.
- It does not apply any change to
~/CLAUDE.mdor tocontamination-problem.md. Nothing is built, run, or landed. - It does not answer Q3, and does not offer a lean on it.
- It does not claim the contamination problem is solved, or that the loop may be narrowed anywhere.
- It does not treat Document B's evidence as sufficient. B's Part D bounds what it licenses; B's Part F carries what argues against it, including that the divergence it measures is real while its attribution to formation is not established.
Verification carried
Every passage quoted in Document B from a source the jurist cannot open was checked mechanically against that source before filing: 28/28 contained verbatim, 5/5 positive controls absent, instrument verified. The controls are near-miss strings that must not be found; without them, an all-pass result cannot be distinguished from a check unable to detect absence.
That check caught one defect that reading had missed twice — a quotation reflowed from a bullet list into prose with terminal periods the source does not contain, inside a blockquote. Corrected before filing, and reported in B's own containment section rather than quietly fixed.
What remains uncheckable by the jurist, and is stated in B's Appendix rather than buried: the completeness of the executor's extractions from the 2025 outputs, and the two comparable pairs not reproduced. A reader with repository access could falsify them in minutes. The jurist cannot, and should weigh the claim accordingly.