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>
17 lines
1.7 KiB
Markdown
17 lines
1.7 KiB
Markdown
---
|
|
name: methodology-docs-scope-question
|
|
description: Continuity-skill / personal-workflow-with-Claude methodology docs may
|
|
not belong in CapableMind-AI (co-authored with Seb) — scope is open, surface before
|
|
auto-filing
|
|
metadata:
|
|
node_type: memory
|
|
type: feedback
|
|
originSessionId: 6c6e416d-ccea-41f1-b2ab-a2cf916e264b
|
|
permalink: claude-memory/feedback-methodology-docs-scope-question
|
|
---
|
|
|
|
Methodology documents that capture the steward's personal workflow with Claude — e.g., the 2026-05-18 continuity-skill audit cluster (`jurist-brief`, `jurist-shape-review`, `prime-directive-elaboration`) — currently sit untracked in `~/_Dev/CapableMind-AI/docs/thinking/David/methodology/`. The steward has flagged this location as uncertain: *"I am not sure that those should live there as they touch my personal workflow with you."*
|
|
|
|
**Why:** CapableMind-AI is co-authored with Seb (L1 reliability + L2 governance for the BMF runtime). Files in that repo's `docs/thinking/David/` are part of the steward's thinking corpus filed alongside shared technical work, but methodology about continuity skills + steward↔Claude collaboration discipline is a different category. It may belong in a personal-workflow repo, in `~/.claude/`-adjacent location, or in the Obsidian Compass — not in CapableMind-AI proper.
|
|
|
|
**How to apply:** Before proposing to file methodology / continuity-skill / personal-workflow docs into CapableMind-AI, surface the scope question explicitly. Do not bundle them with L1 reliability or L2 governance docs as if they share the same destination. The decision about the right home is pending and worth treating as such. Related: [[live-state-discipline]] — files that should live elsewhere create state-of-record drift even when untracked. |