unified-memorylisted

# Unified Memory Use the ECC Memory Vault as the common context layer between harnesses. The vault stores portable `ecc.memory.v1` Markdown documents rather than harness-specific transcripts or inboxes. ## Runtime Prerequisite This skill is guidance, not the Memory Vault executable. Skill-only, minimal, manual, and Claude plugin installs do not create the required commands on `PATH`. Install the `ecc-universal` npm runtime separately before using the CLI or MCP examples: ```bash npm install -g ecc-universal ecc memory --help command -v ecc-memory-mcp ``` A repository checkout may instead run the CLI as `node scripts/ecc.js memory ...`, but MCP configurations that name `ecc-memory-mcp` still require that binary on `PATH`. ## When To Use - Save durable context that another agent or later session will need. - Hand work from Claude to Codex, Hermes to Claude, or any other harness pair. - Resume a task and search for prior decisions, facts, lessons, or handoffs. - Diagnose malformed memories, broken links, duplicate IDs, or skipped symbolic links. Do not use the vault as a task tracker, secret store, policy engine, or substitute for governed project documentation. ## Vault Scopes | Scope | Location | Use | |---|---|---| | `project` | `<repo>/.ecc/memory/project/` | Repo-local context protected by a fail-closed `.gitignore` | | `team` | `<repo>/.ecc/memory/team/` | Context intended for human review and version-controlled sharing | | `user` | `~/.ecc/memory/` | Operator