David/dotfiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

session 2026-07-04: skill-harvest — CI-for-ESCALATE ladder entry + model-handoff reinforced

Browse Source
This commit is contained in:
David F Glidden
2026-07-04 22:54:21 +02:00
parent 67a720c1d1
commit 3ae21f9047
1 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
claude/memory/skill-harvest-register.md
+9
View File
@@ -307,3 +307,12 @@ The single place proposed skills live so they don't evaporate between sessions.
| **`/wrap-up` §4.a** | **patch** | The §4.a drawer-filing step instructs passing `tags:` to `mempalace_add_drawer` — **the tool rejects it** (`MCP error -32602: Unknown parameter 'tags'`). Misfired in use this wrap. Fix: drop the `tags:` param from the §4.a instruction; fold retrieval keywords into the drawer **content** (a `[tags: …]` line) instead, since content is the semantic surface. One-line correction; caught live. | `~/.claude/skills/wrap-up/SKILL.md` §4.a | **PROPOSED (patch — caught in use)** | | **`/wrap-up` §4.a** | **patch** | The §4.a drawer-filing step instructs passing `tags:` to `mempalace_add_drawer` — **the tool rejects it** (`MCP error -32602: Unknown parameter 'tags'`). Misfired in use this wrap. Fix: drop the `tags:` param from the §4.a instruction; fold retrieval keywords into the drawer **content** (a `[tags: …]` line) instead, since content is the semantic surface. One-line correction; caught live. | `~/.claude/skills/wrap-up/SKILL.md` §4.a | **PROPOSED (patch — caught in use)** |
*(Two, both earned in use. `/spec-amendment`'s deferral condition [first real use] is genuinely met — this session was that use, so it's a build not a re-propose. The §4.a patch is a real tool-instruction mismatch that cost one failed drawer call this very wrap. Neither manufactured; source-not-derived-as-drafting-method is NOT re-proposed as a skill — it's already a discipline-named KG fact + reinforces the existing trusted-derived-artifact §3 flag.)* *(Two, both earned in use. `/spec-amendment`'s deferral condition [first real use] is genuinely met — this session was that use, so it's a build not a re-propose. The §4.a patch is a real tool-instruction mismatch that cost one failed drawer call this very wrap. Neither manufactured; source-not-derived-as-drafting-method is NOT re-proposed as a skill — it's already a discipline-named KG fact + reinforces the existing trusted-derived-artifact §3 flag.)*
### Harvest 2026-07-04 (Seam-1 ESCALATE + engine deep-research day)
| Element | Kind | One-line | Status |
|---|---|---|---|
| **verification-ladder: CI-upper-bound + drop-one-robustness = STANDARD for every ESCALATE** | verification-ladder entry | The jurist RULED (2026-07-04) that grading on the one-sided 90% Clopper-Pearson **upper bound** (not the point estimate) + the **drop-one-confirmed-case robustness check** are standing practice for *every* ESCALATE, not a one-off. A point estimate at n=40 can't tell 1% from 5% (P(0or1\|.05,40)=0.399); the CI does the real work. → `reference-verification-ladder.md`. | PROPOSED |
| **`/model-handoff`** (premium-model scope-charter) | REINFORCED (existing proposal, 2026-06-12) | Used tonight end-to-end: produced `studium-engine/docs/stage-1-replan-scope-charter-2026-07-05.md` on Opus (§0 discipline / §1 settled / §2 already-read / §3 bounded-reading / §4 deliverable / §5 report-and-stop) as the Fable-5 handoff; clear+wake not switch-in-place; artifacts-are-the-handoff. Second clean use → strengthens the standing proposal. | PROPOSED (reinforced) |
*(Both genuine, both recurring-shaped. The CI-for-ESCALATE is a jurist-ruled standing practice worth a ladder entry; the model-handoff is its second proven use. No NEW skill emerged — the chamber-specific instruments (exclusion-path, archive-audit, Instrument-B hardening) are corpus work, not skills.)*