1
0
forked from jason/echo
Files
chorus/chorus-memory.plugin.src/skills/chorus-memory/scaffold
jason d366ca4032 Phase 1: mechanical echo→chorus rename with back-compat shims
Identity rename, no behavior change (CHORUS-PLAN.md Phase 1):
- Plugin echo-memory → chorus-memory: manifest (v2.0.0-alpha.1), skill dir,
  16 scripts (chorus.py, chorus_config.py, …), EchoError → ChorusError,
  /chorus-* commands, hook paths, docs, scaffold seeds, eval harness,
  build.py. Docs endpoint → chorusapi.mpm.to.
- Env ECHO_* → CHORUS_*; config → ~/.claude/chorus-memory/config.json;
  state dir → ~/.chorus-memory/; marker → _agent/chorus-vault.md.

Back-compat shims (one major version):
- chorus_config aliases legacy ECHO_* env at import; reads a legacy
  echo-memory config.json when no CHORUS config exists (writes never
  land there); doctor/config report the legacy source.
- State dir honors an existing ~/.echo-memory when the new dir is absent
  (offline queue not stranded).
- Marker dual-probe in load/doctor/bootstrap/lint/sweep/migrate: a
  pre-fork _agent/echo-vault.md counts as bootstrapped; bootstrap repair
  won't write a second marker; routing gains agent-marker-legacy (GET).

Verified: 25/25 unit tests, scaffold + routing-sync checks, 4 mock e2e
suites, run_eval metrics unchanged, +6 shim smoke tests green.
Rebuilt chorus-memory.plugin (79 entries).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-21 13:35:51 -05:00
..

CHORUS Memory Vault

This Obsidian vault is the persistent memory substrate ("second brain") for its operator. It is read and written across Claude / CoWork sessions through the Obsidian Local REST API.

This vault holds data, not logic. All operating procedure — how the vault is bootstrapped, how notes are routed, the taxonomy, frontmatter conventions, and safety rules — lives in the chorus-memory plugin, which is the single source of truth. There are intentionally no CLAUDE.md / BOOTSTRAP.md / STRUCTURE.md control docs in this vault; updating or porting CHORUS means updating or installing the plugin, not editing files here.

  • Layout: see the plugin's references/vault-layout.md.
  • Operating contract & safety: see the plugin's references/operating-contract.md.
  • Bootstrap / repair: see the plugin's references/bootstrap.md.
  • Version marker: _agent/chorus-vault.md records the schema version and bootstrap date.

Folders: inbox/, journal/ (daily + weekly/monthly/quarterly/annual rollups), projects/, areas/, resources/, decisions/, and the agent subtree _agent/.