session 2026-07-18: PENDING-62 lodged+ratified (REVIEWED-62 applied — 2b FIXes; wiring build cleared); S1 wrap

2026-07-18 15:51:07 +02:00
parent d734afb59b
commit 478c5df10f
9 changed files with 124 additions and 2 deletions
@@ -8,6 +8,7 @@ metadata:
  node_type: memory
  type: reference
  originSessionId: a8eb1d46-314e-4545-a133-f747c69ad5b4
+  modified: 2026-07-18T13:50:27.838Z
 permalink: claude-memory/skill-harvest-register
 ---

@@ -512,3 +513,11 @@ The single place proposed skills live so they don't evaporate between sessions.
 | **verification-ladder / Symmetria §3: assert-"X is in Y" → read Y** | verification-ladder entry OR Symmetria §3 flag | A factual claim's grounding must reach the file that **HOLDS** the fact, not one that merely **describes** it. Earned hard 2026-07-17: wrote "build_loeb_sidecar is NOT in test_tools" into a jurist brief from the **tool's own docstring** (a derived self-assessment) without grepping `test_tools.py` (16 refs — it IS fleet-v1). This is the chamber verify-against-substrate-not-the-derived-artifact discipline + the CLAUDE.md contamination directive (don't accept a component's self-assessment), both violated — *while I quoted the discipline the same session*. Steward caught the **say/do gap**. Specializes the substrate-discipline to membership/coverage claims: for "is X in Y / does Y test X / is X wired", **open Y**. | `reference-verification-ladder.md` or Symmetria §3 | **PROPOSED (strongly earned — a self-inflicted recurrence of a discipline I already hold)** |

 *(Two candidates. The second is the load-bearing one — it names the exact gap between practicing a discipline and applying it to every claim; a §3 flag would make me open the holding-file before asserting an X-in-Y fact. Also noted, not a skill: the jurist's **shared-name-collision** pattern — "app[]" = array vs apparatus-ledger is the 3rd instance after manifest/PENDING-53 + ABSTAIN/PENDING-55 — captured in the ruling doc + FIX-B, a chamber-doctrine watch-item, not a Claude-Code skill.)*
+
+### Harvest 2026-07-18 (S1 — REVIEWED-62 applied; the wiring build cleared)
+
+| Element | Kind | One-line | Where it lands | Status |
+|---|---|---|---|---|
+| **implementation-is-a-second-gate** | verification-ladder entry | A text passed by *reading* is re-tested by having to *act* on it — the jurist's own minting, after their 07-16 miss surfaced at build orientation: *"a gate that passes a document and a build that has to implement it are different tests."* Treat orientation-to-build over just-ratified text as a deliberate verification pass; contradictions it surfaces are gate findings, not annoyances. Earned: the line-38/44 `sections` tension sat through a light editor-gate and surfaced only when the credit boundary had to be implemented. Complements [[feedback-checkable-claim-surfaces-bugs]] (the demand for a checkable claim finds bugs; here the demand to *act* finds them) — S2/S3 apply it forward by design. | `reference-verification-ladder.md` | **PROPOSED** |
+
+*(One candidate, jurist-minted and immediately reusable — Sessions 2 and 3 are structurally this instrument. Also this wrap, applied directly as memory-keeping, not skills: [[feedback-verify-before-compose-hook]] gained the pre-hook-artifact note [first gated edit must itself carry the GROUNDED-IN payload]; chamber `CLAUDE.md` brought current mechanically [2b status line + the `app[]`-vs-channel term]. No skill create/patch/retire beyond the one proposal.)*