memory-init

Memory Init

Set up the project memory directory with a policy header that requires human approval before any memory write. Idempotent — safe to run repeatedly.

Behavior

1. Resolve the memory directory. The path is ~/.claude/projects/<slug>/memory/ where <slug> is derived from the session's starting CWD. Use the path the runtime provides — do not reimplement slug derivation.

2. Ensure the directory exists. Create it if missing.

3. Create or update MEMORY.md.

   • If MEMORY.md does not exist: create it with the policy header below and no index entries. Leave any pre-existing .md files in the directory as orphans — memory-audit handles those.
   • If MEMORY.md exists: compare the first block (everything before the first blank line after the closing -->) against the canonical header below. If it differs, replace the header, preserving all content after it.

Canonical policy header

This is the source of truth. If the header in MEMORY.md does not match this text exactly, replace it.

<!-- POLICY: Do not edit this file or any file in this directory without
explicit human approval. Before writing, propose the content to the human
and suggest where it belongs: repo memory, global CLAUDE.md, or a
plugin/skill issue. See the global CLAUDE.md memory management policy
for the full workflow. User-invoked skills (e.g., /handoff) are exempt. -->

Empty MEMORY.md template

When creating a new MEMORY.md, use this structure:

<!-- POLICY: Do not edit this file or any file in this directory without
explicit human approval. Before writing, propose the content to the human
and suggest where it belongs: repo memory, global CLAUDE.md, or a
plugin/skill issue. See the global CLAUDE.md memory management policy
for the full workflow. User-invoked skills (e.g., /handoff) are exempt. -->

(no entries yet)

Properties

• Idempotent. Running twice produces the same result.
• Header only. Never modifies index entries or other memory files.
• No category scaffolding. Future extension.