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 (fffcf17), the change-class clause 2026-07-05 (9ca673f) — 37 days later, not carried back. That makes the factual premise checkable; it does not rescue the lean from being the interested party's reading, and the jurist's alternative stands on its own. Parts I-IX preserved unrewritten as the text ruled on. Nothing landed: the §1.6 edit awaits steward placement of REVIEWED-85. The accompanying steward-jurist exchange is read as background and deliberately not filed — per the jurist's own direction that making it doctrine would be its own item, ruled on rather than absorbed by inclusion. Refs PENDING-88, REVIEWED-85 (drafted, awaiting placement). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WuMjg3ipEVa3n8CoSzoyvc
2026-08-01 19:54:21 +02:00
parent 8303b48796
commit bec7996673
2 changed files with 108 additions and 0 deletions
@@ -194,3 +194,61 @@ If any of those falsifiers lands, **option (a) — status quo — is the correct
 ---

 *Filed by the executor 2026-08-01. Companion entry: `~/PENDING.md` PENDING-88 (with its 2026-08-01 amendment, which corrects the item's counts and records that option (d) was already authorized and is now executed). No code was run, no skill was changed, and no governed artifact was edited in the authoring of this package.*
+
+---
+
+# Addendum — design-gate ruling received, and the required verification supplied (2026-08-01)
+
+**Parts I–IX above are preserved unrewritten as the text the jurist ruled on.** This Addendum layers disposition; it does not revise history. Ruling filed verbatim at `skill-harvest-fix-lane-JURIST-RULING-2026-08-01.md`.
+
+## The ruling in force
+
+Design gate **PASSED, conditioned**. Q1, Q2, Q4, Q5 affirmed — Q2 with the executor's own narrower alternative **declined** as *less* safe (a latitude-expanding but non-assertive change would pass an assertion-only test). Q3 answered against the executor's fallback framing: report and provenance comment are **both mandatory**, not one with the other in reserve. Register split (option (d)) untouched — separately authorized 2026-07-19 and correctly executed by the split method.
+
+## Corrections that supersede the drafted design
+
+1. **A third instrument, not proposed:** a running **append-only FIX-lane index**, one line per applied change (skill · what changed · date), separate from wrap narratives — on the same live-index pattern as today's register split, and for the same reason: to stop this proposal's own failure mode recurring one level up, on the *changes* instead of the *proposals*.
+2. **The floor's catch-all gets an operational form.** *"Anything that would reduce what is surfaced to the steward"* becomes: **any change that removes, defers, or narrows the visibility of an open item, or that could cause a future item to land somewhere the steward's surfacing tools don't read, stays PROPOSAL regardless of the test's outcome.** Checkable against the failure Part II measured, rather than a standing judgment call.
+3. **The lane is provisional, not settled.** After the first FIX-lane batch or one month, whichever comes first, steward and jurist review the index together before the lane is treated as settled.
+
+## The required verification — supplied
+
+The ruling: *"Required before landing: the same mechanical containment-with-positive-control verification the 2026-07-29 package carried, applied to these quotes specifically."*
+
+**Executor's correction first, because it bears on how this should be read.** The check *was* run before filing — 15/15 quotes contained, positive and negative controls passing — and the package **did not report it**. The jurist noticed its absence. For a reader with no repository access, a check performed but not disclosed is indistinguishable from one not performed; the failure is in the record, not the method, and it is the say–do seam running in the less familiar direction. Supplied now per-quote, with the file identity pinned so the check is repeatable:
+
+| Source file | sha256 (first 32) | bytes | lines |
+|---|---|---|---|
+| `~/.claude/skills/wrap-up/SKILL.md` | `37a31595298b13645e7389197a76ceab` | 19,696 | 215 |
+| `~/.claude/skills/wake-up/SKILL.md` | `2341552bd137fa329bbc5ade2908a53f` | 18,487 | 161 |
+
+**Per-quote containment — exact byte substring, no normalisation, no fuzzy matching:**
+
+| Quoted passage | File | Line | Result |
+|---|---|---|---|
+| §1.6 change-class clause (*"Mechanical updates … the same FIX-vs-PROPOSAL split, one level up"*) | wrap-up | 75 | **contained** |
+| §1.6 blanket prohibition (*"never create, patch, or retire a skill autonomously at wrap"*) | wrap-up | 80 | **contained** |
+| §1.6 event-based sentence (*"This is event-based, not change-count …"*) | wrap-up | 75 | **contained** |
+| §2.a register read (*"Read `skill-harvest-register.md` directly …"*) | wake-up | 63 | **contained** |
+
+**Controls:** positive (a known-present clause is found) **pass**; negative (an invented clause, *"the executor may patch any skill without reporting it"*, is absent) **pass**; cross-file negative (the §2.a text does **not** appear in the wrap-up file, confirming the two sources are distinct and not one file matched twice) **pass**.
+
+**Q1's timeline, affirmed by the jurist as "unverified directly" — now verified directly, from git rather than from a provenance comment:**
+
+- The **blanket prohibition** entered `wrap-up/SKILL.md` on **2026-05-29** (`fffcf17`).
+- The **change-class clause** entered on **2026-07-05** (`9ca673f`) — **37 days later**, carrying its own `<!-- 2026-07-05: CLAUDE.md-freshness check, steward-authorized -->` provenance comment at line 75.
+
+So *"the distinction was drawn later and simply not carried back"* is a **git-verified fact**, not a timeline inference. It does not rescue the lean from being the interested party's reading — the jurist's coherent alternative stands or falls on its own — but the factual premise it rested on is now checkable by anyone with the repository.
+
+## What proceeds now
+
+1. **Steward places REVIEWED-85.** Not yet placed; the block is in the ruling file, plain-fenced and paste-ready.
+2. **Then** land the §1.6 edit: two-clause disjunctive test · sharpened floor per correction 2 · all three instruments per correction 1 · provenance comment in `/wrap-up` SKILL.md · **no change to `~/CLAUDE.md`**. Tag commits **REVIEWED-85**.
+3. **Then** apply today's four proposals (ledger `## What held` section, `prevention` KG predicate, the wake line, the reframed standing question) as the **first FIX-lane batch**, each recorded in the new index — the material for the check-in.
+4. **Then** the bounded check-in, at the first batch or one month, whichever comes first.
+
+**Nothing at steps 2–4 is done.** The landing awaits placement; this Addendum discharges only the verification condition.
+
+## A note the executor is deliberately not folding in
+
+A steward–jurist exchange accompanied the ruling (contamination, Anthropic's published position on recursive self-improvement, and *"differently biased checkers rather than unbiased ones"*). It has been read as background. Per the jurist's own direction it carries **no governed weight** and is not filed with the ruling: making any of it doctrine would be *"its own item: what exactly gets added, where it lives, and why now, ruled on rather than absorbed by inclusion."* Recording that here so its absence is a decision rather than an oversight.