David F GliddenandClaude Opus 4.7
119285cf43
The ~/.claude/ directory was previously local-only — a machine wipe
would have lost the accumulated memory, custom skills, and settings.
This commit moves the durable parts into dotfiles with the same
symlink-to-home pattern used for CLAUDE.md, PENDING.md, REVIEWED.md,
and L2-BOOTSTRAP.md.
Preserved (symlinked from ~/.claude/* into here):
skills/audit/ — thinking-folder drift scanner
skills/symmetria/ — practice-of-return discipline
skills/vault-update-people/ — Obsidian People-file maintainer
skills/wake-up/ — session restoration
skills/wrap-up/ — session state capture
memory/ — 55+ memory files (MEMORY.md, sessions,
ledgers, project state, feedback, etc.)
settings/settings.json — user preferences (hooks, flags, no secrets)
Deliberately NOT backed up:
settings.local.json — contains operational secrets (HF_TOKEN,
SSH password in expect scripts); by naming
convention, *.local.* is not synced.
Needs separate review and probable rotation.
sessions/, history.jsonl, caches, telemetry — ephemeral
plugins/, marketplace skills and agents — reinstallable
The working copies at ~/.claude/skills/* and
~/.claude/projects/-Users-davidglidden/memory are symlinks into this
directory, so every write flows here automatically. install.sh
recreates the symlinks on a fresh machine.
FOLLOW-ON (flagged, not in this commit):
settings.local.json contains a HuggingFace token and an SSH password
as plaintext strings inside allowed Bash command patterns. These
should be rotated and moved to secure storage (keychain / pass /
env file outside the settings file).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
14 lines
1.4 KiB
Markdown
14 lines
1.4 KiB
Markdown
---
|
|
name: Signal Travel Protocol — collaborative method
|
|
description: Jointly developed diagnostic/evaluative method for testing whether built systems honour their specs. First applied to BMF L1, intended for Chamber and L2.
|
|
type: project
|
|
---
|
|
|
|
Signal Travel Protocol written up in `CapableMind-AI/docs/thinking/David/methodology/signal-travel-protocol.md`.
|
|
|
|
**Why:** Emerged from a thought experiment (2026-03-10) where Claude traveled as an event through the BMF pipeline. Proved immediately diagnostic (found #36 slot name mismatch). David recognized the deeper framing on 2026-03-13: this is a test of honour — structurally parallel to what the Chamber does with texts. Holds built systems accountable to their stated aspirations.
|
|
|
|
**How to apply:** Use when evaluating whether a system keeps faith with its spec — not just "does it work" but "does it honour what it claims to be." Three modes: passive (find blockages), memorial (find information loss), interrogative (find limits of the approach). Intended for L1 memory fidelity, Chamber integrity, L2 constitutional governance, and adversarial stress testing. The method belongs to the project, not to either party.
|
|
|
|
David sees this as the fruit of the collaboration model described in CLAUDE.md — deliberative partnership producing something neither party would reach alone. Treat this as a sign that the collaboration model is working and should be sustained.
|