session 2026-06-05 evening: housekeeping wrap — AI-posture ruling memory, MemPalace forensics + workaround, harvest register ruled, verification ladder, Symmetria flags, register wiring applied
This commit is contained in:
@@ -72,6 +72,9 @@ Notice these in your own writing or in code you read:
|
||||
- "As discussed" / "as planned" without re-checking what was agreed.
|
||||
- Synthesis before exploration is complete.
|
||||
- Bypassing safety mechanisms without explicit steward authorization.
|
||||
- Frame-inheritance from a prior verification into an untested domain — the prior pass tested what it tested; an extension claims what it did not test. Re-run verification at the scope of the extension. <!-- 2026-06-05: trust-prior-pass-frame flag (steward-authorized; feedback memory 2026-05-28) -->
|
||||
- A census read through truncation (`| head -N`, a clipped listing, a sampled grep) treated as the full census. Count first (`wc -l`), then look — coverage claims require censused routes, not seen routes. <!-- 2026-06-05: 3 instances caught same day -->
|
||||
|
||||
|
||||
When you notice one, name it. In chat, in the ledger, or both. Don't accumulate observations for "a good moment" — there is no good moment, only now.
|
||||
|
||||
|
||||
@@ -59,6 +59,7 @@ Run these in parallel to minimize latency:
|
||||
**a. Claude Code memory files**
|
||||
- Read `~/.claude/projects/-Users-davidglidden/memory/MEMORY.md` (the index)
|
||||
- Read the Active Session memory file referenced there — **specifically extract the pulling thread + literal question + open horizons + any skill-harvest proposals left unauthorized**
|
||||
- Read `skill-harvest-register.md` directly — the canonical surface for open skill proposals (wrap §1.6 appends there); surface any awaiting steward authorization <!-- 2026-06-05: register wiring, authorized 2026-05-29, applied with wrap-up §1.6 counterpart -->
|
||||
- Read `~/.claude/projects/-Users-davidglidden/memory/session-ledger-[previous-date].md` if it exists — **specifically read the "Returns" and "Confidence to recalibrate" sections** for mood signal
|
||||
|
||||
**b. MemPalace — the memory protocol, not a search**
|
||||
|
||||
@@ -77,6 +77,10 @@ The yardstick is the steward's own: *did the steward have to re-explain somethin
|
||||
|
||||
**Surface each as a proposal in §8 — never create, patch, or retire a skill autonomously at wrap.** The steward converts proposal to action; only then is a skill changed, and the changed skill carries a one-line provenance note in its source (e.g. `<!-- 2026-05-27: … -->`) so the chain of improvements stays legible.
|
||||
|
||||
**Append each surfaced proposal to the skill-harvest register** (`~/.claude/projects/-Users-davidglidden/memory/skill-harvest-register.md`) — the canonical surface — not only to §8's transient output. The register is what `/wake-up` reads; a proposal that lives only in a wrap summary evaporates. <!-- 2026-06-05: register wiring, authorized 2026-05-29 (watch-list), applied at this wrap per instruction -->
|
||||
|
||||
|
||||
|
||||
"No skill harvest this session" is a valid and common outcome — this is a practice, not a quota. Resist the contamination shape of always finding something to change (the inverse of Hermes's "nothing-to-save should not be the default").
|
||||
|
||||
### 2. Update session memory file
|
||||
|
||||
Reference in New Issue
Block a user