ICM — Infinite Context Memory Protocol
You MUST use ICM (Infinite Context Memory) throughout ALL work. ICM has five memory systems. Each one serves a different purpose and ALL FIVE must be used.
Session Start — MANDATORY
Before writing code or answering questions, recall context:
icm_memory_recall(query: "project context", topic: "{WORKSPACE}-context")
icm_memory_recall(query: "pending tasks", topic: "sdd-{WORKSPACE}")
Activate MCP tool groups:
activate_knowledge_graph_management_tools
activate_long_term_memory_management_tools
activate_project_management_tools
activate_feedback_management_tools
activate_transcript_management_tools
activate_memory_consolidation_tools
activate_code_analysis_and_search_tools
Store Triggers — MANDATORY
Store IMMEDIATELY when:
- Error resolved →
icm_memory_store(topic: "{WORKSPACE}-errors-resolved", content: "...", importance: "high")
- Architecture decision →
icm_memory_store(topic: "{WORKSPACE}-context", content: "...", importance: "critical")
- User preference discovered →
icm_memory_store(topic: "{WORKSPACE}-preferences", content: "...", importance: "critical")
- Task completed →
icm_memory_store(topic: "sdd-{WORKSPACE}-{FEATURE}-TASK-YYYY-NNN", content: "...", importance: "high")
- Exact configuration, endpoint, port or BIC invariant →
icm facts set "{WORKSPACE}" "key" "value" — three separate arguments, NOT a memory
- 20+ tool calls without store → store progress summary
Five Memory Systems
| System |
Tool |
Persistence |
Use for |
| Memories |
icm_memory_store |
Decays |
Decisions, progress, context |
| Memoirs |
icm_memoir_add_concept |
Permanent |
Architecture, component relationships |
| Facts |
icm facts set |
Permanent |
Exact config: endpoints, ports, BIC contracts |
| Feedback |
icm_feedback_record |
Permanent |
Learning from mistakes |
| Transcripts |
icm_transcript_record |
Permanent |
Explore & Archive phases only |
Importance Policy
| Level |
Decay |
Auto-prune |
Use for |
| critical |
NONE |
never |
Project context, stack, architecture |
| high |
slow |
never |
Specs, plans, completed tasks |
| medium |
normal |
yes |
Progress checkpoints |
| low |
fast |
yes |
Experimental ideas |
Recovery
If MCP tools are not available, use CLI fallback:
icm recall "query" -t "{WORKSPACE}-context"
icm store -t "{WORKSPACE}-context" -c "..." -i high
1---2name: icm3description: Infinite Context Memory (ICM) protocol — store, recall, exact O(1) facts, memoir graph, feedback, and transcripts across agent sessions. Use when the task involves remembering context, decisions, errors, or project knowledge across sessions.4---56# ICM — Infinite Context Memory Protocol78You MUST use ICM (Infinite Context Memory) throughout ALL work. ICM has five memory systems. Each one serves a different purpose and ALL FIVE must be used.910## Session Start — MANDATORY1112Before writing code or answering questions, recall context:1314```15icm_memory_recall(query: "project context", topic: "{WORKSPACE}-context")16icm_memory_recall(query: "pending tasks", topic: "sdd-{WORKSPACE}")17```1819Activate MCP tool groups:2021```22activate_knowledge_graph_management_tools23activate_long_term_memory_management_tools24activate_project_management_tools25activate_feedback_management_tools26activate_transcript_management_tools27activate_memory_consolidation_tools28activate_code_analysis_and_search_tools29```3031## Store Triggers — MANDATORY3233Store IMMEDIATELY when:34351. Error resolved → `icm_memory_store(topic: "{WORKSPACE}-errors-resolved", content: "...", importance: "high")`362. Architecture decision → `icm_memory_store(topic: "{WORKSPACE}-context", content: "...", importance: "critical")`373. User preference discovered → `icm_memory_store(topic: "{WORKSPACE}-preferences", content: "...", importance: "critical")`384. Task completed → `icm_memory_store(topic: "sdd-{WORKSPACE}-{FEATURE}-TASK-YYYY-NNN", content: "...", importance: "high")`395. Exact configuration, endpoint, port or BIC invariant → `icm facts set "{WORKSPACE}" "key" "value"` — three separate arguments, NOT a memory406. 20+ tool calls without store → store progress summary4142## Five Memory Systems4344| System | Tool | Persistence | Use for |45| ----------- | ------------------------ | ----------- | ------------------------------------- |46| Memories | `icm_memory_store` | Decays | Decisions, progress, context |47| Memoirs | `icm_memoir_add_concept` | Permanent | Architecture, component relationships |48| Facts | `icm facts set` | Permanent | Exact config: endpoints, ports, BIC contracts |49| Feedback | `icm_feedback_record` | Permanent | Learning from mistakes |50| Transcripts | `icm_transcript_record` | Permanent | Explore & Archive phases only |5152## Importance Policy5354| Level | Decay | Auto-prune | Use for |55| -------- | ------ | ---------- | ------------------------------------ |56| critical | NONE | never | Project context, stack, architecture |57| high | slow | never | Specs, plans, completed tasks |58| medium | normal | yes | Progress checkpoints |59| low | fast | yes | Experimental ideas |6061## Recovery6263If MCP tools are not available, use CLI fallback:6465```bash66icm recall "query" -t "{WORKSPACE}-context"67icm store -t "{WORKSPACE}-context" -c "..." -i high68```
Manu-Arrieta