---
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.