David F GliddenandClaude Opus 4.8
3f9a89b00c
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>
3.3 KiB
name, description, type, originSessionId, permalink
| name | description | type | originSessionId | permalink |
|---|---|---|---|---|
| ARC territory — steward + Claude Code only; Seb is L1/BMF only | 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. | feedback | efda5c2e-ca9a-4e55-9344-64aa9a3c1140 | 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.
How to apply:
- ARC work (the Hakyll site at
~/_Dev/animal-davidglidden-eu/, the AldineXXI specification, content / posts / pages, lex-cluster work, the About page, the typography apparatus, the Chamber publication-face): review and iteration is between steward and Claude Code only. Decisions are authored by steward; executor implements / surfaces / drafts. No third party. - MemPalace (
~/_Dev/mempalace/): separate open-source project the steward uses; not Seb's, not in the BMF/CapableMind orbit at all. When discussing MemPalace upstream / contributors / network / PRs / issues, those are MemPalace's own ecosystem — never refer to it as "Seb's network" or any phrasing that attributes MemPalace's project-context to Seb. Steward 2026-05-01 verbatim: "Seb has nothing to do with mempalace — I am using it to help us while we finish the BMF L1 problems. Mempalace is its own project and I am using it to help me to help you to help me." - chamber-library (
~/_Dev/chamber-library/): steward's library, no Seb involvement. - L1 / BMF (
~/_Dev/CapableMind-AI/+~/_Dev/BetterMemories.io/): Seb is code owner; steward + executor work in support (audit, diagnostic, PENDING drafting, test-branch). This is the only territory where Seb is in the loop. - L2 constitutional governance: steward + jurist (Claude.app) + executor (Claude Code); also no Seb.
When uncertain about territory: ask, don't include. The default for any non-BMF discussion is steward + executor.
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).