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

session 2026-07-17: constitution block drafted-whole — #2/#4/#5 RATIFIED (REVIEWED-60/61, PENDING-60/61), verify-before-compose hook + memory, MEMORY.md compacted

Browse Source
This commit is contained in:
David F Glidden
2026-07-17 16:11:58 +02:00
parent 4bf7f1ad67
commit ed43422bbb
9 changed files with 171 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files
claude/memory/skill-harvest-register.md
+8
View File
@@ -495,3 +495,11 @@ The single place proposed skills live so they don't evaporate between sessions.
| **Symmetria §3 flag / ladder: "closable-now" is itself a claim to check** | Symmetria §3 flag OR verification-ladder entry | The jurist named it a standing habit: the closable-vs-blocked partition on a work-list must be *reviewed*, not asserted — the named-dependency discipline only protects if the closability judgment is itself checked. Caught this session: I bucketed #2 (citation amendment) as ordinary-closable-now when it was PROPOSAL-class with a CTS-boundary precondition + schema-touching + a data migration. Kin to assert-from-a-partition / census-through-a-pattern, one level up (the *list's own* closable/blocked split). | Symmetria §3 or `reference-verification-ladder` | **PROPOSED** |
*Watch-list (not yet a proposal): chamber `CLAUDE.md` may want pointers to the new **candidates register** (`docs/candidate-constitutional-principles-register.md`) + the **constitution-close-block-map** once the block CLOSES — held mid-block (event-based CLAUDE.md-freshness: the class-of-thing changed [a new governance surface], but land the pointer when the block seals, not mid-flight).*
### Harvest 2026-07-17 (constitution block drafted-whole + verify-before-compose hook)
| Element | Kind | One-line | Where it lands | Status |
|---|---|---|---|---|
| **verify-before-compose HOOK + protocol clause** | hook (settings.json) + repo CLAUDE.md discipline | The recurring `re-derived-from-training` / compose-before-verify failure got a STRUCTURAL fix: `~/.claude/hooks/verify-before-compose.sh` (PreToolUse Write\|Edit) DENIES un-grounded writes to chamber constitutional artifacts unless they carry `GROUNDED-IN:` + a Grounding section; protocol clause added to `chamber-library/CLAUDE.md`; memory `feedback-verify-before-compose-hook.md`. Proven firing in-session. | DONE (steward-directed 2026-07-17) | **BUILT + AUTHORIZED** |
| **`/jurist-package`** (create) | new skill | Draft a **self-contained jurist package** for a repo-blind reviewer: inline the ratified spec clauses verbatim (jurist gates the *words*, not recollection) + `GROUNDED-IN:` attestation + amendment content shaped "already-ratified → what-#N-adds" + editor-gate questions. Recurred 2× this session; **jurist explicitly endorsed the method** ("noted as method worth keeping"). Recurs for every constitution amendment. | new `.claude/skills/jurist-package/` | **PROPOSED** |
| **ladder: reconcile against the AUTHORITATIVE source before any "closed/complete/finally" claim** | verification-ladder entry OR Symmetria §3 flag | Before claiming a block/scope closed or complete, reconcile against the **authoritative source** (the roadmap `stage-1-rebuild-plan §4/§7`; the spec's own named-open items) — NOT the derived close-list. The verify-before-compose HOOK covers constitutional *writes*; this covers *chat claims*, where the "finally" overclaim slipped past it. Caught F-5 + "finally" (steward, twice, same session). Kin to the 07-16 "closable-now is a claim to check", one level up (the *close-list's own completeness* is a claim to check). | `reference-verification-ladder.md` or Symmetria §3 | **PROPOSED** |