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/session-ledger-2026-05-04.md
+5 -2
View File
@@ -1,9 +1,12 @@
---
name: Session Ledger 2026-05-04
description: Practice-of-return ledger maintained by /symmetria — returns, open horizons, recalibrations, authorization moves, sub-agent dialogues, bypasses.
description: Practice-of-return ledger maintained by /symmetria — returns, open horizons,
recalibrations, authorization moves, sub-agent dialogues, bypasses.
type: feedback
originSessionId: 45a40b1e-09cd-42bb-a41a-7298f78a8cf0
permalink: claude-memory/session-ledger-2026-05-04
---
# Session Ledger — 2026-05-04
## Returns
@@ -54,4 +57,4 @@ originSessionId: 45a40b1e-09cd-42bb-a41a-7298f78a8cf0
1. **almost-deferred-to-complex-recovery-without-checking-upstream-first** — was about to propose a multi-step recovery for HNSW corruption before checking if upstream had shipped a fix. Steward asked "are we really on the latest build?" → 3.3.4 had been released the day after the previous pull, with fixes for our exact symptoms. Saved hours of unnecessary work. This is a sibling/cousin of the existing **blame-the-exotic-before-checking-the-boring** pattern (April 28 ledger) — different domain, same shape: when symptoms match common patterns, check the boring/upstream/standard before designing exotic recovery.
2. **structural-counter-as-health-signal-without-functional-validation** — trusted mempalace_status's "933,576 drawers" as a health signal until forced to recognize that drawer count is structural, not functional. Search was completely broken. The migrate dry-run named it directly: "Palace is NOT readable by chromadb 1.5.8." Storage exists; storage isn't memory. This is the contamination problem at infrastructure level — the system reports "ready" via its own counters that don't reflect what users experience. New pattern; sibling of (but distinct from) defended-the-spec-against-the-eye.
2. **structural-counter-as-health-signal-without-functional-validation** — trusted mempalace_status's "933,576 drawers" as a health signal until forced to recognize that drawer count is structural, not functional. Search was completely broken. The migrate dry-run named it directly: "Palace is NOT readable by chromadb 1.5.8." Storage exists; storage isn't memory. This is the contamination problem at infrastructure level — the system reports "ready" via its own counters that don't reflect what users experience. New pattern; sibling of (but distinct from) defended-the-spec-against-the-eye.