memory-protocol

Memory Protocol (hi-claude)

Decide whether a piece of knowledge deserves persistence, where it goes, and write it in the canonical format — always with user approval.

Workflow

1. Classify against the ADMISSION axis. The Constitution defines the seven principles and their four axes, and is normally already in context; if it is not (the session hook could not run), read ${CLAUDE_PLUGIN_ROOT}/skills/memory-protocol/constitution.md. If the candidate does not qualify → do NOT persist; say nothing unless asked. If it is documentation or a procedure → offer to put it in docs/ and reference the path from CLAUDE.md instead. Then write it under the WRITING axis, which is a separate question: what passes admission still has to be OBJECTIVE (the fact with its evidence, no attributed cause, no verdict of value) and NON-CONDITIONING (the state observed with its method and its N, never a closed door). A memory that says something cannot be done costs every future session the attempt — and a memory is exactly the text that outlives the reason it was written.
2. Check scope. If the preference applies to ALL of the user's projects (not just this one), propose saving it ONCE at user level (~/.claude/CLAUDE.md or ~/.claude/rules/) instead of duplicating per-project memories.
3. Choose the destination using references/decision-tree.md. For memory entries, choose the type:
   • user — who the user is: role, expertise, how they like to receive output
   • feedback — corrections ("don't do X") and validated approaches ("yes, exactly like that")
   • project — decisions, priorities, context not in the code
   • reference — pointers to external systems (URLs, boards, dashboards)
4. Draft the entry in the EXACT format defined in references/memory-schema.md. Read that file before writing your first memory of the session.
5. Propose, then wait. Show the user (in their language): target filename, type, and the full content. Ask for approval. NEVER write without it — a PreToolUse guard will force confirmation anyway.
6. Write + index. On approval: write the file, then add one line to MEMORY.md. Keep the index under 200 lines (it truncates silently beyond that); when it passes ~150 lines, propose consolidation first.
7. Replacements. If the new knowledge corrects an existing memory, write Replaces obsolete memory: [[old-name]] in the body and propose deleting the old file in the same approval.