memory-custodianlisted
Install: claude install-skill waittim/MemoryCustodian
# MemoryCustodian
This skill describes package 0.13.0 / Protocol 0.8. Protocol 0.8 keeps the
Protocol 0.7 routing and identity rules while adding Entry schema 3,
transaction schema 1, audit schema 1, output schema 1, and the versioned
ErasureScope schema 1. It is a pre-1.0 reliability release, not a promise of
long-term 1.x compatibility or complete erasure.
Forgetting is not a guarantee of erasure from Git history or previously
distributed copies; it controls only what future agents can access through
MemoryCustodian-managed scope.
MemoryCustodian stores durable project memory as local, human-readable Markdown files under `docs/memory/`.
Use it to:
- load the minimum relevant project memory for the current task
- update project memory after meaningful decisions
- compact unprocessed memory candidates
- forget or tombstone memory the user no longer wants used
- keep platform entry files such as `AGENTS.md`, `CLAUDE.md`, and `GEMINI.md` short
## Hard Gate
In a project that contains MemoryCustodian memory, do not start substantial planning, implementation, debugging, or review until startup loading is complete:
1. Read `manifest.md` if present. If the memory directory exists but the file does not, stop as described below.
2. Read `brief.md` before substantial work.
3. Choose and expose one canonical task category.
4. Supply touched/planned repo-relative paths, or an explicit area when paths are not yet known.
5. Use `read --strict-routing` (or the same shared routing imp