diff --git a/doc/IDEAS.md b/doc/IDEAS.md
index af1110e..48bbde1 100644
--- a/doc/IDEAS.md
+++ b/doc/IDEAS.md
@@ -99,6 +99,3 @@ The script is the coordinator; agents have no knowledge of each other. Informati
 
 Since agents have access to `execute_code`, a session can write and execute a workflow script without any human involvement. Given a task and knowledge of the filesystem layout, an agent can decompose the work, spawn sessions, write the coordination script, and run it — all in a single turn. The README you are reading is essentially its system prompt. Conductor functionality, for free.
 
-### Persistent Memory
-
-**Memory Recall** — Agent sessions are ephemeral by nature, but some knowledge should outlive them. Memory recall gives an agent the ability to persist and retrieve facts across sessions via two abstract tool contracts: `memory_remember` and `memory_recall`. When the agent learns something worth keeping — a user preference, an architectural decision, a hard-won debugging insight — it calls `memory_remember` with a concise, self-authored summary. On a future session it calls `memory_recall` to retrieve relevant memories before reasoning. Memories are LLM-generated rather than raw chat logs: the agent decides what matters and phrases it canonically, so memories remain meaningful long after the conversation that produced them is gone. The tool contract follows the same pattern as `reasoning_plan`: the agent owns the content, the tool owns the storage.