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-dependency-chains.md
+4 -2
View File
@@ -1,11 +1,13 @@
---
name: feedback-dependency-chains
description: Always question dependency chains — check which specific phases are actually blocked, not just the chain as stated
description: Always question dependency chains — check which specific phases are actually
blocked, not just the chain as stated
type: feedback
permalink: claude-memory/feedback-dependency-chains
---
Never accept a dependency chain at face value. Always ask: which specific phases or tasks are actually blocked, and which can proceed independently?
**Why:** The chain "L1 reliable → Chamber testable → L2 formalizable" was accepted for 3 weeks without questioning that Chamber Phase 1-2 and L2 governance were independent of L1. This cost David weeks of governance time on L1 debugging.
**How to apply:** When a blocking dependency is stated, decompose it. Check whether sub-phases, sub-tasks, or parallel tracks exist that are not actually blocked. Surface these immediately. The contamination problem predicts that the executor will accept stated blockages rather than challenge them.
**How to apply:** When a blocking dependency is stated, decompose it. Check whether sub-phases, sub-tasks, or parallel tracks exist that are not actually blocked. Surface these immediately. The contamination problem predicts that the executor will accept stated blockages rather than challenge them.