recalllisted

# Recall: Retrieving Session Memory ## Context **Project:** !`basename $(git remote get-url origin 2>/dev/null | sed 's/\.git$//' | xargs basename 2>/dev/null) 2>/dev/null || basename $(pwd)` **Vault:** !`sqlite3 $(memex path 2>/dev/null)/_index.sqlite "SELECT (SELECT COUNT(*) FROM fts_content) || ' documents indexed'" 2>/dev/null || echo "(index unavailable)"` --- ## Step 0: Classify the Query Before doing anything, classify the user's question into one of four modes: ### TEMPORAL — date-based browsing **Triggers:** "yesterday", "last week", "today", "what did I do on Monday", "show me recent work", "last 3 days", "this week's sessions", any date reference without topic keywords. **Action:** Go to → [Temporal Recall](#temporal-recall) ### KEYWORD — topic/decision lookup **Triggers:** "why did we...", "find the memo about...", "what was the decision on...", "remind me about the retry pattern", any question with specific technical terms or project names. **Action:** Go to → [Keyword Recall](#keyword-recall) ### DEEP — cross-project synthesis **Triggers:** "what patterns do we use across...", "how has our approach to X evolved...", "compare how we handle X in different projects", questions spanning multiple sessions or projects, complex why/how questions needing synthesis. **Action:** Go to → [Deep Recall](#deep-recall) ### LOAD — direct file retrieval **Triggers:** "load the X topic", "pull up project Y", "show me the memo about Z", explicit topic or memo names, "w