session 2026-07-04: Chamber spec v2.0 ratified+shipped (a10d6bf); new session memory + ledger + skill-harvest (/spec-amendment build-ready, wrap-up §4.a patch)

2026-07-04 11:13:20 +02:00
parent 33e19e87ce
commit 62fa6d857e
4 changed files with 208 additions and 1 deletions
@@ -298,3 +298,12 @@ The single place proposed skills live so they don't evaporate between sessions.
 | **per-claim citation verification (don't let a sub-agent's blanket "verified" ride)** | feedback memory or verification-ladder note | Caught by the jurist: I cited arXiv 2605.24229 for a claim it didn't support, having let a sub-agent's aggregate "4/4 papers verified" stand without per-citation checking. Verify each citation against the SPECIFIC claim it carries; never let an agent's blanket verification substitute for per-claim checking. | feedback memory / ladder | PROPOSED |

 *(Three, all earned. The first is the session's real return — a drift I hit three times and the jurist turned into a standing rule; it should become a Symmetria flag AND a ladder entry AND a feedback memory. The second is a genuine future skill but correctly deferred to after its first real use. The third is a concrete citation-integrity guardrail from a real miss. None manufactured.)*
+
+### Harvest 2026-07-04 (Chamber spec v2.0 drafted spine-first + ratified + shipped)
+
+| Element | Kind | One-line | Where it lands | Status |
+|---|---|---|---|---|
+| **`/spec-amendment`** (proposed 2026-07-03, DEFERRED-until-first-use) | **BUILD — deferral condition NOW MET** | The 2026-07-03/04 v2.0 drafting IS its first real exercise — the empirical spec now exists. Codify the proven procedure so the next constitutional amendment doesn't re-derive it: **(1)** source-check before drafting (read the CURRENT spec end-to-end + the ruling docs — source-not-derived, the near-miss caught my own header overclaim); **(2)** draft **spine-first** in dependency order (substrate section first), not front-to-back; **(3)** each section **surfaced for the jurist's editor-gate** before the next; corrections applied in-place; **(4)** tag every clause `[CARRIED]`/`[REVISED]`/`[NEW]` + forward-notes for cross-section mechanisms; **(5)** **coherence-revise** any carried section that *summarizes* a revised one (don't silently carry — §VIII/§X/§XI); **(6)** assemble self-contained + reorder; **(7)** supersede via RFC pattern — archive prior to `-vN.md` with an OBSOLETE banner (immutable), promote new to the canonical filename, fix internal version refs, commit (=logchain supersession record) + push; **(8)** the **FIX-class errata lane** for post-ratification exactness fixes (no version bump). Yardstick met: a whole constitution was drafted this way in one sitting; the procedure is the skill. | new `/spec-amendment` skill | **PROPOSED (build — first-use condition met)** |
+| **`/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.)*