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/feedback-bmf-health-vs-recall.md
+6 -2
View File
@@ -1,9 +1,13 @@
---
name: BMF module health does not measure recall correctness
description: Modules reporting status=ready / system_status=healthy in BMF measures pipeline liveness only — not whether recall produces correct results. Verify recall directly. Never trust the health endpoint as a proxy for "the system works."
description: Modules reporting status=ready / system_status=healthy in BMF measures
pipeline liveness only — not whether recall produces correct results. Verify recall
directly. Never trust the health endpoint as a proxy for "the system works."
type: feedback
originSessionId: a3ddbf34-da48-4129-acba-658f2f869783
permalink: claude-memory/feedback-bmf-health-vs-recall
---
# Module health is decoupled from recall correctness
When evaluating BMF state — for any session, any audit, any "is it working" question — **never use module health (`status: ready`, `system_status: healthy`) as evidence that recall produces correct results.** The two are structurally decoupled.
@@ -48,4 +52,4 @@ H1–H4 from the 2026-04-19 audit are not four independent bugs; **they are four
Steward verbatim, after the recall baseline test revealed the decoupling:
> *"So my joy at reaching the milestone was premature I now understand... I can accept that. Now to make this work."*
Yesterday's milestone (2026-04-18 evening): connector completed 7,220 items, 14,355 entities extracted, 0 failed, all modules ready, single-query recall returned confidence 1.0 → steward called it "the foundation." That reading was true about substrate-bytes-flowed but premature about recall-works. The foundation in the deeper sense (the system can be used as cognitive memory) requires recall correctness, which today's audit shows is not yet present.
Yesterday's milestone (2026-04-18 evening): connector completed 7,220 items, 14,355 entities extracted, 0 failed, all modules ready, single-query recall returned confidence 1.0 → steward called it "the foundation." That reading was true about substrate-bytes-flowed but premature about recall-works. The foundation in the deeper sense (the system can be used as cognitive memory) requires recall correctness, which today's audit shows is not yet present.