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

session 2026-07-12: PENDING-56 (canonical-format decision, jurist-ratified) + in-flight sidecar build report + session memory/ledger/REVIEWED-drafts

Browse Source 
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015jYS1tpR4P4NBxui4FSgfv
This commit is contained in:
David F Glidden
2026-07-12 12:15:15 +02:00
co-authored by Claude Opus 4.8
parent 043a4b1836
commit 0a424aa6b3
9 changed files with 200 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
claude/memory/skill-harvest-register.md
+8
View File
@@ -423,3 +423,11 @@ The single place proposed skills live so they don't evaporate between sessions.
| **verification-ladder: retroactively re-verify everything landed under a weaker standard when a stronger gate lands** | ladder entry | The jurist's Q1b principle, proven load-bearing: a stronger check existing and NOT pointed at canon that shipped under the weaker one is the exact gap-shape the discipline exists to close. Today's retroactive sweep (end-to-end verify over all footnote-covered books → 45/87 fail) is the instance. Reusable whenever a new gate supersedes an old one. | `reference-verification-ladder.md` | **PROPOSED** |
| **verification-ladder: structural safety = PROVISIONAL FIX; end-to-end proof on real, representative books = FINAL** | ladder entry / Symmetria §3 | The jurist's generalization after nested-block: "same risk as (a)" was true of the *matching* logic and silent on the *rendering* logic. No widen/transform gets ruled final on structural reasoning alone — it earns provisional-FIX; only verbatim-clean proof on real books makes it final. Caught two FIX-assumptions this arc ((c), nested-block). | `reference-verification-ladder.md` or Symmetria §3 | **PROPOSED** |
| **Symmetria §3 flag: lost-the-forest-in-a-long-execution-arc** | Symmetria §3 flag | A long, productive execution session that costs the whole-program altitude is contamination shape (composition-over-consideration at the *session* scale, not the task scale). Antidote: keep the open-work register in view; re-surface it when a workstream has run deep for a while. Steward-named 2026-07-12. | Symmetria §3 | **PROPOSED** |
### Harvest 2026-07-12 (the Docling reframe — building a solved domain our own register already mapped)
| Element | Kind | One-line | Where it lands | Status |
|---|---|---|---|---|
| **check-the-register-before-a-substantial-build** | `/wake-up` §2 patch OR `/pre-build-audit` step OR Symmetria §3 flag | Before starting substantial INFRA/tool building (a converter, a pipeline, a substrate), read the **tooling-register + landscape-register + prior scans** for an existing adopt-candidate first — the studium-engine-scan-register (2026-05-27) already named Docling+Surya/OCR4all/TEI/DTS as THE substrate answer, and we hand-built ~20 bespoke tools over ~6 weeks anyway. The two-week "every breakthrough → new obstacle" feeling was the tell of reimplementing a solved domain. **Yardstick met, painfully:** the steward had to re-surface that extant tools exist ("are there no epub tools? … TEI?") — our own register carried that six weeks earlier. Kin to [[feedback-resurface-banked-notes-before-rederiving]], specialized to the build-infra decision. | `/wake-up` §2 (when the thread is a build) or `/pre-build-audit` (its natural home) or a Symmetria §3 flag (solving-at-the-wrong-level / build-a-solved-domain) | **PROPOSED** |
*(One proposal, load-bearing — the drift cost ~6 weeks and recurred at pipeline scale; a standing "check the register before building infra" reflex would have surfaced Docling at the outset. Surfaced for steward authorization; not auto-applied. The paired KG drift-patterns are already appended (solving-at-the-wrong-level · didn't-consult-our-own-tooling-register).)*