unified-memory

原文涵盖的主题

• Unified Memory
• Runtime Prerequisite
• When To Use
• Vault Scopes
• Workflow
• 1. Recall before writing
• Recall is evidence, not certainty
• 2. Save context

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. 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: 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. 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. | Scope | Location | Use | |---|---|---| | project | /.ecc/memory/project/ | Repo-local context protected by a fail-closed .gitignore | | team | /.ecc/memory/team/ | Context intended

这里只展示节选，请以完整原文和当前要求为准。