memory-loadlisted

# memory-load Pulls relevant memory entries into the conversation context. ## When to invoke - At the start of a session or whenever a new initiative is opened — required. - Any time the conversation touches a topic that could plausibly be in memory (personal, habits, goals, relationships, work, health, hobbies, family, etc.). - When the user explicitly asks to recall — *"what did I say earlier about X?"* Err on the side of invoking. A missed context is worse than a redundant read. ## Algorithm ### Step 1. Read the map Always read: - `memory/index.md` — the catalog of all entries with titles and tags. - `memory/tags.md` — the tag dictionary (needed to interpret tags). These files are small and cheap. Read them in full. ### Step 2. Decide relevance From the user's last message and the conversation context, extract: - **Candidate tags** — which existing entries in `tags.md` match the topic. - **Semantic hooks** — entry titles in `index.md` that are thematically close even when the tags themselves do not line up (the user may use different words). Use both signals together — tags for precise hits, titles for cases where the wording diverges. ### Step 3. Load the bodies Read the full `.md` files of the entries that passed the filter. **Default filter:** `status: active` only. Entries with `status: deprecated` are pulled in **only** when the user is explicitly asking about the past (*"what did I used to think about X"*, *"go back to the old idea about Y"*). ### Step