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-onboarding-vs-steady-state-thresholds.md
+7 -2
View File
@@ -1,9 +1,14 @@
---
name: Onboarding vs steady-state lag — threshold-governance frame
description: Slowness in L1 ingestion is not a bug-or-not-bug binary; it is a threshold-governance question. Two regimes (onboarding / steady-state lag) collapse in current code but are different in kind. Defining the acceptable envelope is L2-shaped work, not engineering verdict.
description: Slowness in L1 ingestion is not a bug-or-not-bug binary; it is a threshold-governance
question. Two regimes (onboarding / steady-state lag) collapse in current code but
are different in kind. Defining the acceptable envelope is L2-shaped work, not engineering
verdict.
type: feedback
originSessionId: a3ddbf34-da48-4129-acba-658f2f869783
permalink: claude-memory/feedback-onboarding-vs-steady-state-thresholds
---
# L1 slowness as threshold-governance, not bug
When evaluating L1 ingestion or recall slowness, do **not** frame it as "is this fast enough or not." Frame it as: *which regime is this, what is the acceptable envelope for that regime, and is the observed behavior inside or outside the envelope?*
@@ -65,4 +70,4 @@ The two-regime distinction is constitutional in nature, not engineering. It conn
- DN-GOV-05 (bounded self-repair) — the four conditions are envelope conditions
- DN-GOV-06 (temporal authorization shift) — threshold crossing as authorization trigger
- ICP-19 / external review — envelope-defining requires external grounding (earned confidence)
- The horizon work on `ground-up-model-horizon` — substrate trust is itself a function of patience-under-defined-bounds
- The horizon work on `ground-up-model-horizon` — substrate trust is itself a function of patience-under-defined-bounds