From 8b72b149f9616c4db1bbf416f7046cc54d67b6d8 Mon Sep 17 00:00:00 2001 From: David F Glidden Date: Wed, 5 Aug 2026 22:05:06 +0200 Subject: [PATCH] =?UTF-8?q?docs(memory):=20skill-harvest=20=E2=80=94=205?= =?UTF-8?q?=20proposals=20from=20the=20quoted-tier=20session?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Adjacent-clause reading for /jurist-package (jurist-caught: containment passes an omission every time); two ladder entries (uniform-offset-as-instrument-artifact; pre-register the effect before building); a /wake-up patch for the decorative Symmetria line I printed without invoking; and superseded-head disclosure for enumerated document access. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01AB3Kryoy6b1pm2Nz1DYdLh --- claude/memory/skill-harvest-register.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/claude/memory/skill-harvest-register.md b/claude/memory/skill-harvest-register.md index 76bf66c..b0ea756 100644 --- a/claude/memory/skill-harvest-register.md +++ b/claude/memory/skill-harvest-register.md @@ -247,3 +247,13 @@ The single place proposed skills live so they don't evaporate between sessions. | **Symmetria §3 flag: `the-fix-for-an-overclaim-is-an-overclaim-candidate`** | Symmetria §3 flag | When you repair an overclaim, **the replacement inherits the frame that produced the original.** Replacing the engine's *"genuine silence, not a gap"* with *"the index is complete and current"* reproduced the identical defect one size down — "complete" is true of document coverage and unverified of query-matching, and a reader without that distinction collapses the two exactly as the engine did. Caught by the jurist, not by me. **Re-reading a replacement as a stranger is a separate act from writing it**, and it is the act that gets skipped because the repair feels like the careful part. | Symmetria §3 | PROPOSED | | **Widen `assert-from-derivation-not-substrate` with the null-result case** | Symmetria §3 patch | A **null** from an instrument you have not positive-controlled is a fact about your instrument, not about the world. Probed `resolve_archived_source` with *engine* `source_id`s against the *chamber's* `canonical_slug` key space; got `None` three times **including the nonsense control** — which should have been the tell — and was one sentence from reporting a healthy 349/349 resolver dead. The existing flag covers asserting *presence* from a derived form; it does not name **asserting absence from an un-controlled probe**, which is the more seductive half because a null feels like an observation rather than a claim. | Symmetria §3 (widen the existing consolidated flag) | PROPOSED | | **`/wake-up` patch — a tracker marked THE GOVERNING FRAME is read ENTIRE, not as its pointer** | patch | **Earned at a measured cost of ten days.** `MEMORY.md` carries *"[Chamber as versioned releases] — **THE GOVERNING FRAME for all library work.** Scope every library bite through this"* — and the file itself held the resolution to the paralysis the steward named at this wrap (*purpose choice and corpus scope are ONE decision, not sequential*), written 2026-07-28 and unopened since. The index entry cannot carry a reframe; only the file can. Proposal: where a tracker line declares itself governing, `/wake-up` opens the file rather than trusting the one-liner — the same logic as the telos-conditional already wired in §2.a. Kin to `feedback-resurface-banked-notes-before-rederiving`, one level up: not *re-deriving* a banked note but *never opening* it. | `/wake-up` §2.a | PROPOSED | + +## New proposals (2026-08-05 wrap — the quoted-tier measurement; awaiting steward) + +| Target | Kind | Proposal | Earned by | PROPOSED? | +|---|---|---|---|---| +| `/jurist-package` | patch | **Require reading the clauses ADJACENT to every quote, and stating in the package that you did.** Strongly earned and jurist-caught: PENDING-99's Grounding quoted §II.3 verbatim, passed containment 16/16 with 9/9 controls absent — and omitted the sentence *one line later* (*"What remains genuinely open… the marker's exact syntax"*) that dissolved the whole question. It was in the executor's own read output. **A containment proof passes an omission every time, because nothing is misquoted.** The limit is now written into `check_containment.py`'s docstring; the *procedural* half belongs in the skill. Add to the Grounding step: quote the clause, read its neighbours, and record "adjacent clauses read" beside the containment line. | 2026-08-05, jurist-caught on first substrate access | PROPOSED | +| verification ladder | new entry | **A suspiciously UNIFORM offset is a constant masquerading as a measurement.** A forward-window locator reports the window START, not the match location — so it returns the window size as an offset. Shipped twice in one session (Δ−30, then Δ−25) before the definition was fixed; the truth was Δ−1. The tell was not a failing test — no test covered it — but that the number was identical across every hit. Sibling of `count-first-then-look`. Rule: when an offset/delta is constant across independent items, suspect the instrument before the data. | 2026-08-05, twice in one session | PROPOSED | +| verification ladder | new entry | **Pre-register the expected effect BEFORE building the change.** `fidelity_equivalence@3`'s effect was filed in the jurist package as 3/17→6/17 before any code existed; the post-build measurement returned exactly 6/17. Had the number been computed first and reported second, a partially-correct implementation would have been indistinguishable from a correct one, because whatever it produced would have become the claim. The census pre-registration discipline, transferred from audits to code changes. | 2026-08-05, applied and held | PROPOSED | +| `/wake-up` §4 | patch **[candidate FIX]** | **Do not print the Symmetria line unless Symmetria was invoked.** This wake's briefing ended *"Symmetria active. Practice of return foregrounded"* and Symmetria was never invoked; no ledger exists for the day. The claim was output, not act — the decorative-maxim failure `~/CLAUDE.md` asks be flagged, occurring inside the instrument whose job is to foreground the practice. Either invoke in the same step that prints the line, or print what is true. **Classified PROPOSED not FIX**: it changes what the executor must DO at wake, not only what it records, so the two-clause test routes it to the loop. | 2026-08-05, self-caught at wrap | PROPOSED | +| `governance-mcp` / doc-access generally | patch | **A document whose head is superseded must disclose that at the point of access.** The chamber constitution's first ~330 lines are obsoleted version headers; a default `limit=400` read lands entirely inside them. Granting access without disclosure would have *caused* the misruling the access exists to prevent. Handled here by putting the warning in the key's own description plus a negative control proving the trap is real. Generalize: any enumerated document whose operative content does not start at line 1 carries the offset in its description. | 2026-08-05, caught while building PENDING-86 (a) | PROPOSED |