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-arc-territory-steward-and-claude-code-only.md
+6 -2
View File
@@ -1,9 +1,13 @@
---
name: ARC territory — steward + Claude Code only; Seb is L1/BMF only
description: ARC architecture, implementation, review, iteration is between steward and Claude Code; Seb has no role in ARC. Distinct from L1/BMF where Seb is code owner.
description: ARC architecture, implementation, review, iteration is between steward
and Claude Code; Seb has no role in ARC. Distinct from L1/BMF where Seb is code
owner.
type: feedback
originSessionId: efda5c2e-ca9a-4e55-9344-64aa9a3c1140
permalink: claude-memory/feedback-arc-territory-steward-and-claude-code-only
---
ARC is steward + Claude Code. Seb has nothing to do with ARC. Don't propose "Seb reviews," "let Seb confirm," "steward + Seb iterate," or any similar inclusion of a third party in ARC dialogue or implementation.
**Why:** Steward verbatim 2026-04-27: *"Seb has nothing to do with ARC. This is only me and you"* — surfaced after I said *"steward + Seb iterate"* about an ARC SCSS implementation. Seb's territory is L1/BMF (CapableMind backend / BetterMemories.io runtime); ARC is the publishing platform / Hakyll site, with architecture authored by the steward and implementation between steward and executor. Pulling Seb into ARC creates false authority-loops and territory confusion.
@@ -19,4 +23,4 @@ When uncertain about territory: ask, don't include. The default for any non-BMF
**Subtler drift to watch for:** beyond the obvious *"Seb reviews this"* error, also catch *generic technical-context attribution* — phrasing like "Seb's network," "Seb's circle," "the team," when the project at hand has its own community/ecosystem entirely separate from Seb's orbit. Recurring instance 2026-05-01: said *"discussion with Seb's network"* about a MemPalace upstream PR. The drift is the same shape (false authority-loop) at a more diffuse scale.
This feedback is one of several ARC-specific behaviors held in the working memory; cousin to `feedback-canonical-workstream-tracker-discipline.md` (ARC tracker discipline) and `feedback-trust-contract-drift-pattern-tracking-is-the-discipline.md` (bidirectional trust).
This feedback is one of several ARC-specific behaviors held in the working memory; cousin to `feedback-canonical-workstream-tracker-discipline.md` (ARC tracker discipline) and `feedback-trust-contract-drift-pattern-tracking-is-the-discipline.md` (bidirectional trust).