session 2026-08-02 pm: PENDING-90 (first L2 transfer) + PENDING-91 (vignette jurist gate)

PENDING-90 [ESCALATE] carries Constraint 6 into CapableMind's calibration loop —
the AdaptationChain records who initiated an adaptation but never who checked it,
and when authorization.required is false (the whole self-adjustment case) no
checker is in the record at all.

PENDING-91 [PROPOSAL] is the vignette Phase-1a design gate, leading with the
structural problem that the dwell-test is assigned to a jurist who cannot see
the render — third instance of the gap docketed at PENDING-86 and PENDING-82.

Session record, ledger, KG (+6: two drift-patterns, two preventions, the
Notre-Dame anchor, the superseded gitea diagnosis), and four skill-harvest
proposals. One FIX-lane application indexed (ARC CLAUDE.md freshness).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WuMjg3ipEVa3n8CoSzoyvc

claude/memory/skill-harvest-register.md

@@ -223,3 +223,16 @@ The single place proposed skills live so they don't evaporate between sessions.
 | 180 | `normalize_ocr.py` (chamber fleet) | patch **[FIX-class]** | **Silent degradation with no disclosure.** `dict_state` reports only the static word list, so a `--lang fr` run with **wordfreq absent** falls back to its own documented *"old, weaker behaviour"* — validating French de-hyphenations against `/usr/share/dict/words` (English) — and says nothing. §VII: *a measurement carrying a known reliability caveat states it on its own output, every time*. Fix: report wordfreq active/absent and the effective language on every run. (wordfreq installed into `~/.local/chamber-tools-venv` 2026-08-01.) | 2026-08-01 (Derrida conversion) | PROPOSED |
 | 181 | `/jurist-package` | patch | **Filing is not sending, and the skill has no step that distinguishes them.** The 2026-08-01 ESCALATE doctrine package sat filed-and-unsent for a day; the executor could not determine its state from the repository and had to ask. Add a send-state line to the package footer (`filed <date> · sent <date|not yet>`) and a §1.6-style check at wrap. Cheap, and it is the difference between a package that is waiting on the jurist and one nobody has moved. | 2026-08-02, found while packaging | PROPOSED |
 | 182 | `/jurist-package` | patch | **Require the mechanical containment proof the skill's own discipline implies.** The skill states *quote, never paraphrase* but carries no check. Built and used twice on 2026-08-02: it caught a fabricated terminal period inside a blockquote in the executor's own package (read past twice), and discharged REVIEWED-85's stated precondition where the jurist could not verify skill-file quotes itself. Tool: `dotfiles/claude/governance/check_containment.py`, positive controls mandatory. **PROPOSAL, not FIX** — this changes gate criteria, which the §1.6 hard floor reserves. Bears directly on PENDING-86 option (b), which is unruled; route with that item, not ahead of it. | 2026-08-02 | PROPOSED |
+
+## New proposals (2026-08-02 pm wrap — the vignette build; awaiting steward)
+
+| # | Skill / instrument | Kind | One-line | Status |
+|---|---|---|---|---|
+| A | **verification-ladder: render-and-LOOK outranks the check suite for any rendered output** | ladder entry | **Strongly earned — three instances in one session.** Every substantive vignette defect was found by rendering the artifact and looking; *none* by the mechanical checks, which were good checks and all passed: a field colour bound to a class no element carried (Layer 3's whole mode mapping would have inherited the panel's ink and looked correct); a hand-rolled palette violating §III's sacred-palette clause, collapsing dark-mode contrast; interval clearings reading as smudges. The general shape: **an instrument can certify a property of the *code* while the claim being made is about the *result*.** For visual/rendered work the gate is the render, and the check suite is necessary-not-sufficient. Kin to `measure-toolchain-before-spec`, one level over. | PROPOSED |
+| B | **`/measure-render` — RE-REINFORCED (5th+ instance)** | create skill | Headless-Chrome capture used again today, and this time it was *decisive* rather than diagnostic: the screenshots are what exposed the dark-mode contrast collapse and the interval smudges. Previously proposed 2026-06-09, reinforced 06-09 pm, 06-11. The pattern is now: build → emit → shoot → **read the PNG back and look at it**, which is a step a skill should carry because it is the step most easily skipped. | PROPOSED |
+| C | **Implementing a spec is a spec-audit instrument — the under-determination census** | ladder entry OR skill | New method, proven today. Building Phase 1a produced **nine findings** about where the vignette spec fails to determine its output — none findable by *reading* the spec, because from inside an implementation a silence does not feel like a decision, it feels like the obvious reading. Output shape: per finding, *what the spec says · what it under-determines · how the implementation silently resolved it*. Deliverable committed at `docs/AldineXXI-Codex/drafts/vignette-spec-under-determination-census-2026-08-02.md` as the worked exemplar. Warrant is in the spec's own Part II: *"if the visual result doesn't work, the spec needs revision before proceeding."* | PROPOSED |
+| D | **Symmetria §3 flag: applying a doctrine where it does not govern** | Symmetria §3 flag | Steward-caught today. Asked whether to send a spec to Fable, the executor reached for Constraint 6's independence framing and attached a corroboration caveat — but it was a **design** task, not a checking task, so independence never arose and the caveat was empty. The flag: **before invoking a governing principle, name the question-type it governs and check the task is that type.** A live maxim applied off-domain is the decorative failure `~/CLAUDE.md` asks us to flag, and it *feels* like rigour from inside. | PROPOSED |
+
+**Applied at this wrap under the §1.6 FIX lane** (mechanical repo-CLAUDE.md freshness; classification test: changes neither executor latitude nor a governed artifact's assertion — it removes a claim the substrate contradicts; hard floor not engaged, no open item's visibility reduced): ARC `CLAUDE.md` asset-structure listed `js/ # JavaScript (theme toggle)`; the directory **does not exist** and the toggle was retired with the JS pipeline at Stage M (2026-06-01). Replaced with a note recording the retirement. Indexed in `skill-harvest-fix-lane-index.md`.
+
+**Noticed, not fixed (needs steward/jurist — vignette Phase 4 scope):** `vignette-specification.md` Part II Phase 4 prescribes moving `assets/js/glyphs/` to `assets/js/glyphs-archived/`; that tree no longer exists, so part of the quarantine phase is already moot. And `AldineXXI-specification.md` §IX still says genomes are *"Generated by a local model via Ollama"*, which the companion superseded (Part II, *Engine evolution*). Both recorded in the under-determination census; §IX is sealed-spec.