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/ungovernable-threshold.md
+5 -2
View File
@@ -1,7 +1,10 @@
---
name: DN-DRAFT Ungovernable Threshold
description: Exploratory design note — governance systems digest challenge rather than being changed by it. Earned confidence principle extends to governance vocabulary itself. Hold open — premature resolution repeats the error.
description: Exploratory design note — governance systems digest challenge rather
than being changed by it. Earned confidence principle extends to governance vocabulary
itself. Hold open — premature resolution repeats the error.
type: project
permalink: claude-memory/ungovernable-threshold
---
## DN-DRAFT: The Necessity of the Ungovernable Threshold (2026-04-09)
@@ -17,4 +20,4 @@ Emerged from External Auditor review (Absorption Trap finding). Four lines of in
**Why:** This is potentially the central unresolved architectural question of L2. It connects the External Auditor's Absorption Trap, CD-03, earned confidence, Chamber genealogy, and Derrida's archive fever into a single structural problem.
**How to apply:** When evaluating any new governance mechanism, ask: does this create conditions for genuine challenge, or does it domesticate challenge into procedure? The test is whether the system could be *changed* by the input, not merely *annotated*.
**How to apply:** When evaluating any new governance mechanism, ask: does this create conditions for genuine challenge, or does it domesticate challenge into procedure? The test is whether the system could be *changed* by the input, not merely *annotated*.