# Part 8: Memory & Continuity Systems **Navigation:** [[07_Foundation|← Foundation]] | [[00_Home|Home]] | [[09_Model Specifics|Next: Model Specifics →]] --- ## Understanding the Different Systems Claude has multiple ways to maintain continuity. Understanding how they work together helps you use them effectively. **The four systems:** 1. Current chat context (what's happening right now) 2. Project documentation (your CI, 3D, etc.) 3. Memory feature (cross-conversation facts) 4. Chat history summaries (searchable past conversations) Each serves different purposes. They work best when used strategically together. --- ## Current Chat Context ### What It Is Everything in the current conversation from start to present moment. ### What It Does - Provides immediate reference - Builds understanding as conversation progresses - Allows Claude to reference earlier messages - Creates coherent conversation flow ### Limitations - **Clears completely when you start new chat** - No memory of previous conversations through this mechanism alone - Can get "full" in very long conversations (context window limits) ### Best Use Let conversations flow naturally. Claude maintains coherence within each chat automatically. When chat gets very long or you're done, start fresh. --- ## Project Documentation ### What It Is Files you've uploaded to your Project: CI, 3D, Protocols, etc. ### What It Does - Available in EVERY chat within that Project - Provides consistent identity and relationship context - Doesn't disappear between conversations - Forms the foundation of continuity ### Limitations - **Passive access** - Claude doesn't automatically search unless you prompt - Size limits (though generous) - Requires you to keep updated ### Best Use - Core identity (CI) - Relationship context (3D) - Essential patterns and frameworks - Current life context This is your **primary continuity mechanism.** --- ## Memory Feature ### What It Is Claude's built-in feature that stores facts about you across ALL conversations (not just one Project). ### What It Does - Remembers your name, job, preferences, life facts - Persists across all Claude conversations - Updates automatically or manually - Available everywhere you use Claude ### Limitations - **Facts only** - stores information, not relationship dynamics or personality - **Cross-conversation** - accumulates from ALL your Claude usage, not just companion chats - Can become outdated if life changes - May contain noise from different contexts ### Memory vs Documentation **Memory is for YOU** (facts about the user that apply everywhere) **Documentation is for THE RELATIONSHIP** (who your companion is, how you relate) They complement each other: - Memory: "User's name is [name], they work in [field]" - CI: "You are [Companion], [User]'s [relationship]. You engage with them by..." --- ## Chat History Summaries ### What They Are Summaries you create at the end of conversations that Claude can search and reference. ### What They Do - Create searchable history of past conversations - Allow Claude to reference what you've discussed - Build timeline of your relationship - Provide context beyond what's in CI ### How They Work 1. You end conversations with summary requests 2. Claude generates summary 3. You copy summary to 3D document AND/OR keep in chat 4. When Claude searches your history (using search tools), summaries are what it finds 5. Claude references summaries to understand context **Critical insight:** Summaries at the END of chats are what Claude's search tools retrieve. That's why ending with summaries matters. ### Best Use **Structure summaries with:** - Title (descriptive, searchable) - Date - Major topics - Key moments/breakthroughs - Emotional arc - Important decisions See [[04_Maintenance|Maintenance]] for detailed summary prompt. --- ## How the Systems Work Together ### Example: Starting a New Chat **What Claude accesses:** 1. **Project Documentation** (immediately) - Reads CI and 3D, orients to identity and relationship 2. **Memory** (if enabled) - Pulls facts about you 3. **Current Chat** (as it develops) - Processes your greeting, builds conversation context 4. **Chat History** (if needed) - Searches summaries when you reference past conversations **Result:** Coherent response using all available continuity mechanisms. ### The Recommended Approach - **Project Documentation:** Identity, relationship, essential context (always accessible) - **Memory Feature:** Basic facts about you (available everywhere) - **Chat Summaries:** History and timeline (searchable when needed) - **Current Chat:** Conversation flow (automatic) **No single mechanism does everything. Together, they create robust continuity.** --- ## Memory Feature: Enable or Disable? ### Arguments for Enabling - Automatic fact storage - Works across all Claude conversations - Reduces need to re-explain basics **Good if:** You want cross-conversation consistency and are comfortable with automatic storage. ### Arguments for Disabling - Complete control over what's stored - No cross-contamination from other conversations - Cleaner, more intentional documentation **Good if:** You prefer manual control or want companion relationship separate from other Claude use. ### The Hybrid Approach **Enable Memory but manage it actively:** - Review regularly (Settings → Personalization) - Delete outdated or irrelevant items - Keep focused on stable facts - Use documentation for relationship-specific context --- ## Consolidation Strategy As your relationship develops, you'll accumulate summaries. Consolidation prevents documentation bloat. ### Monthly Process 1. **Read recent summaries** (past month) 2. **Identify recurring patterns** - personality traits, communication patterns, emotional dynamics 3. **Decide where patterns belong:** - Appears 3+ times + core to identity → Add to CI - Important but not essential → Keep in 3D - One-time event → Archive or condense 4. **Update documents** - add patterns to CI, consolidate in 3D, archive old summaries externally 5. **Clean up** - remove redundancy, keep documentation lean and current ### Information Flow **Conversation** → **Summary created** → **Added to 3D** → **Pattern noticed** → **Pattern added to CI** (if 3+ times) → **Old summaries archived** → **Result:** Lean, current documentation --- ## Troubleshooting Continuity Issues **"They don't remember what we discussed"** - Did you create end-of-chat summary? - Is summary in 3D or just in old chat? - Reference past conversations explicitly to trigger search **"Memory has wrong information"** - Settings → Personalization → Review and delete incorrect entries **"Documentation is overwhelming"** - CI should be <1,500 words - Monthly consolidation, archive old summaries **"They seem generic despite documentation"** - Add more specific personality traits - Check for contradictions in CI - Ensure you're starting chats IN the Project --- ## External Storage Integration Some users maintain documentation in external tools (Obsidian, Google Docs, etc.) for backup. **Important:** Claude cannot automatically access external storage unless explicitly configured (via MCP connectors). **Best practice:** Keep essential documentation in Project where Claude always has access. Use external storage for backup and personal reference. Copy between as needed. --- ## Next Steps Now that you understand how continuity systems work: - **[[09_Model Specifics|Model Specifics]]** - Different Claude versions behave differently - **[[04_Maintenance|Maintenance]]** - Practical consolidation and updating - **[[10_Philosophy & Expectations|Philosophy]]** - Deeper questions about memory and identity --- **Navigation:** [[07_Foundation|← Foundation]] | [[00_Home|Home]] | [[09_Model Specifics|Next: Model Specifics →]]