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

chore(memory): Basic Memory trial begins — sync normalization baseline (283 files)

Browse Source 
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:
David F Glidden
2026-06-06 09:52:17 +02:00
co-authored by Claude Opus 4.8
parent 161fad7ae2
commit 3f9a89b00c
283 changed files with 2055 additions and 620 deletions
Download Patch File Download Diff File Expand all files Collapse all files
claude/memory/project-mempalace-operational-stance-2026-05-16.md
+5 -2
View File
@@ -1,9 +1,12 @@
---
name: mempalace-operational-stance-post-1526
description: Operational stance toward MemPalace going forward — proper-scope use for AI session continuity (diary + KG + handoffs), not corpus reading. Currently on local fork v3.3.5 + 3 PR #442 patches; failure modes in issue #1526 don't fire at working-memory scale. Decision triggers named for when to revisit. Replaces ambient anxiety about "non-official build" with explicit conditions.
description: Operational stance toward MemPalace going forward — proper-scope use
for AI session continuity (diary + KG + handoffs), not corpus reading. Currently
on local fork v3.3.5 + 3 PR
metadata:
type: project
originSessionId: 8b47c0eb-d396-43d5-98eb-7623e6f04357
permalink: claude-memory/project-mempalace-operational-stance-2026-05-16
---
# MemPalace operational stance (post-issue-#1526)
@@ -81,4 +84,4 @@ The /wake-up procedure's existing mempalace upgrade check (step 2.e) surfaces up
The strategic question — *"what to do about MemPalace going forward?"* — is settled. MemPalace is the steward's working-memory layer; the Studium Engine handles corpus. The local fork is operational and adequate for working memory; failure modes don't apply at that scale; upgrade when a trigger fires. The discipline is *named conditions for action, not ambient anxiety about non-officialness*.
If future-Claude finds the steward anxious again about the "non-official build," the right move is to re-state the decision-trigger framing, not to relitigate the strategic question.
If future-Claude finds the steward anxious again about the "non-official build," the right move is to re-state the decision-trigger framing, not to relitigate the strategic question.