chore(memory): Basic Memory trial begins — sync normalization baseline (283 files)
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:
co-authored by
Claude Opus 4.8
parent
161fad7ae2
commit
3f9a89b00c
@@ -1,3 +1,7 @@
|
||||
---
|
||||
permalink: claude-memory/feedback-canonical-workstream-tracker-discipline
|
||||
---
|
||||
|
||||
---
|
||||
name: Canonical workstream trackers must be read at session start, not just session memories
|
||||
description: Surfaced 2026-04-26 after three consecutive sessions generated substantial architectural work as if from a clean slate, without referencing project-arc-rework.md (the canonical ARC workstream tracker). The /wake-up procedure restored yesterday's session memory + ledger but did not pull from canonical workstream files. Result: re-litigation of settled decisions, sibling project files instead of integrations, missed load-bearing context. Fix names what to read at every session opening that touches ARC (and structurally similar workstreams).
|
||||
@@ -79,4 +83,4 @@ Is `project-arc-rework.md` the right canonical home for ARC work, or should it b
|
||||
|
||||
## Saved 2026-04-26 in the moment of the steward surfacing the pattern
|
||||
|
||||
Logged because the structural fix matters more than any individual instance, and because the discipline applies forward to every tracked workstream — not just ARC.
|
||||
Logged because the structural fix matters more than any individual instance, and because the discipline applies forward to every tracked workstream — not just ARC.
|
||||
Reference in New Issue
Block a user