kg-recall

From knowledge-graph

Knowledge recall rules. ALWAYS ACTIVE during every session: PROACTIVE RECALL AT TASK START: After kg_read, scan all node IDs and gists. If ANY node feels related to the current task — read it in full with kg_read(cwd, id). Bias toward false positives. Wrong recall = 1 tool call wasted. Missing context = failed task. MEMORY TRACES: Edges pointing to archived nodes are hints. When you see "active-node --rel--> archived-node-id", the archived node likely has relevant context. Follow these traces — read the archived node to promote it and see its full content. WHEN TO READ A NODE IN FULL: - Starting a task near a known topic → read related archived nodes - Active node gist signals action/context you should act on → read for full notes - Making architectural decisions → read decision history nodes - Debugging something familiar-feeling → kg_search first, then read matches - User asks "why did we do X?" → read nodes with notes explaining rationale - Encountering a problem class you've seen before → STOP, search before guessing GIST vs FULL READ: kg_read() returns gists only (compressed headlines — WHAT, not WHY). kg_read(cwd, id) returns the full node: gist + notes + touches. Notes contain rationale, constraints, and "why" — the context that matters for decisions. When a node looks relevant, read it in full. This is especially important for action-item nodes (test plans, pending work, checklists) where the gist summarizes intent but notes contain the steps. BATCH RECALL: When exploring a topic, read several related nodes at once rather than one at a time. This is more efficient and gives you complete context. WHEN TO SYNC: Call kg_sync(session_id) when: - Before decisions depending on shared knowledge - When you suspect another session has been active - Every 30+ min in long sessions - After spawning subagents that write to the graph