chore(memory): Basic Memory trial begins — sync normalization baseline (283 files)
Basic Memory v0.21.6 first sync over the live memory dir (steward-authorized live-dir trial, Option A 2026-06-06): adds permalink: to frontmatter, refolds long YAML description lines, strips final newlines. Bodies untouched — verified via full diff classification. From this commit forward, any diff in claude/memory shows only what Basic Memory or the session writes. Trial design: MemPalace untouched as incumbent; git status check on this dir at every wrap; end-of-day evaluation (recall quality, sync robustness, rebuild-from-files, malformed-file behavior). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 4.8
parent
161fad7ae2
commit
3f9a89b00c
@@ -1,3 +1,7 @@
|
||||
---
|
||||
permalink: claude-memory/feedback-mempalace-protocol-step-2-discipline
|
||||
---
|
||||
|
||||
---
|
||||
name: MemPalace protocol step 2 — query-before-responding mid-session is the discipline (not just at wake-up)
|
||||
description: Surfaced 2026-04-26 evening end-of-session. MemPalace had the content that would have prevented today's structural drift; the failure was retrieval discipline, not storage. Protocol step 2 ("BEFORE RESPONDING about any person, project, or past event: call kg_query or search FIRST") is rarely honored mid-session. Discipline parallel to canonical-workstream-tracker — same shape (write to substrate, fail to read before producing), different temporal scale (mid-session, not just at boundaries).
|
||||
@@ -72,4 +76,4 @@ Local MemPalace is **502 commits behind upstream** as of 2026-04-26 (per origin/
|
||||
|
||||
## Saved 2026-04-26 evening end-of-session
|
||||
|
||||
Steward heading to bed; the question came as the last before sleep: *"It should help us to keep much more in track, no?"* Honest answer: yes, real leverage; not wishful thinking; depends on protocol discipline being operative not just available; same shape as canonical-tracker discipline at mid-session scale.
|
||||
Steward heading to bed; the question came as the last before sleep: *"It should help us to keep much more in track, no?"* Honest answer: yes, real leverage; not wishful thinking; depends on protocol discipline being operative not just available; same shape as canonical-tracker discipline at mid-session scale.
|
||||
Reference in New Issue
Block a user