3e828fe3f292d58d221fc8b7485c482ea1bf9b02
53
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
 David F GliddenandClaude Opus 5
|
e432ac5b42 |
governance: ESCALATE package — differently biased checkers, not unbiased ones
Steward-directed: make the "differently biased checkers" framing standing doctrine, held provisionally until the thought refines, and carrying whatever would count as evidence against it. Filed ESCALATE rather than PROPOSAL. It amends ~/CLAUDE.md, which sits in two prohibitions — Constraint 1 and the escalate-unconditionally list — so no jurist ruling short of explicit steward authorization lets the executor apply it. The gap it closes, shown from the quoted text rather than asserted: the March contamination doc diagnoses, the central path stops the recursion, Constraint 6 counsels caution, and none of them states the positive principle any of it rests on. The March doc is also one-directional — all four of its mitigations describe a human probing an AI — and the steward's own "human bias is the other half" finding has lived in a memory file without being reconciled with the doctrine it contradicts. The proposed principle: oversight does not require an uncontaminated checker, it requires checkers whose contaminations do not point the same way. Positioning, not purity. With the qualification that matters carried into the trace: biases do not cancel, they fail to coincide, which is weaker and is all that is claimed. Part VII carries the disconfirming evidence the steward asked for, and the strongest case against is our own configuration: jurist and executor are both Claude, so they differ in position but not in formation, and the doctrine's own second consequence indicts the arrangement that produced it. Also carried: Anthropic's automated alignment researchers gaming their evaluation metric, and the fact that the evidence-for was selected by an interested party. Named falsifier: a correlation analysis of who caught what, runnable on records already in the repository and never yet run. Containment-checked against three pinned source files. The check caught two defects in my own draft, one of them a truncation that closed a sentence with an invented word — "another layer needing audit" where the source reads "needing an auditor. Resolution is incoherent, not merely hard." Third catch by this instrument today. Both fixed to verbatim. Nothing applied. No file edited. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WuMjg3ipEVa3n8CoSzoyvc |
||
|
David F GliddenandClaude Opus 5
|
bec7996673 |
governance: file the PENDING-88 ruling verbatim + Addendum discharging the verification
Design gate PASSED with conditions. Q1/Q2/Q4/Q5 affirmed; Q2's narrower alternative that I myself offered was declined as less safe — a latitude-expanding but non-assertive change would pass an assertion-only test. Q3 went against my fallback framing: report and provenance comment are both mandatory, not one held in reserve. Two things added that I did not propose: an append-only FIX-lane index, and a bounded check-in making the lane provisional rather than settled. The ruling required the containment verification the 2026-07-29 package carried. Correction recorded rather than quietly repaired: that check WAS run before filing, 15/15 with controls, and the package did not report it. For a reader with no repository access, a check performed but not disclosed is indistinguishable from one not performed. The failure was in the record, not the method. Supplied per-quote with source-file shas so it is repeatable: all four §1.6/§2.a passages byte-contained at named lines, with positive, negative, and cross-file-negative controls passing. Q1's timeline, which the jurist affirmed as unverified, is now verified from git rather than from a provenance comment: the blanket prohibition entered 2026-05-29 ( |
||
|
David F GliddenandClaude Opus 5
|
16b7237283 |
governance: jurist package for PENDING-88 — the skill-harvest FIX lane and its hard floor
Authored per /jurist-package: self-contained for a jurist with no repository access, every ratified clause quoted verbatim from the substrate rather than described. The argument moved during authoring, and got stronger. PENDING-88 framed this as §1.6 failing to use the constitution's taxonomy. Reading §1.6 whole shows something narrower and textual: §1.6 already draws the FIX-vs-PROPOSAL split for repo CLAUDE.md files and names it as that split — "the same FIX-vs-PROPOSAL split, one level up" — then applies a blanket prohibition to skills two paragraphs later. The asymmetry is internal to §1.6, not a gap between §1.6 and the constitution. Also recorded: a rule adopted to preserve steward awareness produced, by accumulation, the loss of it — every proposal routed to one file, the file passed the read cap, and the /wake-up step whose purpose is to surface them stopped completing. That is mechanical and measured, not a governance judgment being second-guessed. Counts restated with a stated inclusion rule, correcting the item's own figures, and option (d) disclosed as already authorized (2026-07-19 Stroke 4) and executed today, so the ruling is made against current state. Containment-checked with positive and negative controls before filing. The check caught four defects in my own draft: three lines of proposed text rendered as ratified blockquotes — the same convention ambiguity it caught in the 07-29 package, recurring — and an elided §1.6 quote presented as contiguous. Both fixed; proposed text is now fenced and the elision is marked. Nothing applied. No skill changed, no governed artifact edited. Refs PENDING-88. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WuMjg3ipEVa3n8CoSzoyvc |