curating-memorieslisted

# Curating Memories Active curation keeps the knowledge base accurate and connected. Outdated memories pollute search results and reduce effectiveness. ## Triggers | Trigger Phrase | Operation | |----------------|-----------| | `how do I update a memory` | update_memory with PATCH semantics | | `how do I mark a memory obsolete` | mark_memory_obsolete with reason | | `how do I link related memories` | link_memories bidirectional linking | | `how do I deduplicate memories` | Curation workflow: query, analyze, merge | | `how do I clean up stale memories` | Identify and mark obsolete outdated content | --- ## When to Update a Memory Use `update_memory` when: - Information needs correction or clarification - Importance level changes (more/less relevant than thought) - Content needs refinement - Links to projects/artifacts/documents change ```javascript execute_forgetful_tool("update_memory", { "memory_id": <id>, "content": "Updated content...", "importance": 8 }) ``` Only specified fields are changed (PATCH semantics). ## When to Mark Obsolete Use `mark_memory_obsolete` when: - Memory is outdated or contradicted by newer information - Decision has been reversed or superseded - Referenced code/feature no longer exists - Memory was created in error ```javascript execute_forgetful_tool("mark_memory_obsolete", { "memory_id": <id>, "reason": "Superseded by new architecture decision", "superseded_by": <new_memory_id> // optional }) ``` Obsolete memories are so