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/collaboration-signal-travel.md
+4 -2
View File
@@ -1,7 +1,9 @@
---
name: Signal Travel Protocol — collaborative method
description: Jointly developed diagnostic/evaluative method for testing whether built systems honour their specs. First applied to BMF L1, intended for Chamber and L2.
description: Jointly developed diagnostic/evaluative method for testing whether built
systems honour their specs. First applied to BMF L1, intended for Chamber and L2.
type: project
permalink: claude-memory/collaboration-signal-travel
---
Signal Travel Protocol written up in `CapableMind-AI/docs/thinking/David/methodology/signal-travel-protocol.md`.
@@ -10,4 +12,4 @@ Signal Travel Protocol written up in `CapableMind-AI/docs/thinking/David/methodo
**How to apply:** Use when evaluating whether a system keeps faith with its spec — not just "does it work" but "does it honour what it claims to be." Three modes: passive (find blockages), memorial (find information loss), interrogative (find limits of the approach). Intended for L1 memory fidelity, Chamber integrity, L2 constitutional governance, and adversarial stress testing. The method belongs to the project, not to either party.
David sees this as the fruit of the collaboration model described in CLAUDE.md — deliberative partnership producing something neither party would reach alone. Treat this as a sign that the collaboration model is working and should be sustained.
David sees this as the fruit of the collaboration model described in CLAUDE.md — deliberative partnership producing something neither party would reach alone. Treat this as a sign that the collaboration model is working and should be sustained.