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

session 2026-06-18 evening: skill-harvest — /wake-up surface-the-why proposal

Browse Source
This commit is contained in:
David F Glidden
2026-06-18 18:03:06 +02:00
parent e328c53e00
commit 659763edc7
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
claude/memory/skill-harvest-register.md
+8
View File
@@ -212,3 +212,11 @@ The single place proposed skills live so they don't evaporate between sessions.
| **glyph-outline → SVG from a woff2** | method note (ladder or `/measure-render`) | Build a typographic SVG asset *from the real font glyphs*: `fontTools` `SVGPathPen` (path) + `BoundsPen` (bbox) over the woff2, y-flip into SVG space. Used to draw the cul-de-lampe from EB Garamond U+E001/E002. Reusable for any future glyph-derived ornament/mark; pairs with the mask note above. | `reference-verification-ladder` | **PROPOSED** |
*(Five, all earned in use; `/version-essay` is the load-bearing one — a steward-flagged gap a skill would close. The four ladder/method notes are concrete instruments from the cul-de-lampe build; the mask-luminance one alone cost the most debug time and would have been a one-line save.)*
### Harvest 2026-06-18 (evening — engine telos & steward formation disclosed)
| Element | Kind | One-line | Where it lands | Status |
|---|---|---|---|---|
| **`/wake-up` patch — surface the *why* when the thread touches the engine's purpose** | patch | When the active workstream is studium-engine / The Making / ARC-as-public-proof (the engine's reason-for-being), `/wake-up` should **actively weave the load-bearing telos + steward-formation "why"** into the briefing — not just leave the pointers in MEMORY.md. **Yardstick met, explicitly and painfully:** the steward had to re-disclose the chamber's childhood origin *"many times, across many threads … it clearly needs to be said again"* — the memory failing at its one job. Concrete: add to §2.a a conditional read of [[project-studium-engine-telos-chamber-of-voices]] + [[user-formation-flamenco-substrate]] when the thread is engine/Making/ARC-purpose, and one line in §3 holding the why. **Caveat (honest):** the prominent MEMORY.md pointers added this session may already largely close the gap, since wake reads MEMORY.md — so this is belt-and-suspenders, low-urgency, for steward judgment. Do NOT recite the why every wake (decorative); only when the thread touches it. | `/wake-up` §2.a + §3 | **PROPOSED** |
*(One proposal, low-urgency. The pain it answers is real — losing the most important thing across threads is the exact failure the engine exists to end — but the file-prominence fix landed this session may suffice; surfaced for the steward to judge whether the wake-up patch adds enough over the pointers to be worth the weight.)*