persistent-memory

Persistent memory (YantrikDB)

You have a persistent, semantic, typed memory that survives across sessions, provided by the yantrikdb MCP server. It is not a notes file: it does similarity recall, tracks belief revisions, detects contradictions, learns procedures, and answers "what did I believe at time t". Treat it as your long-term memory, not as optional tooling.

Tool names may carry a harness prefix (mcp_yantrikdb_recall, mcp__yantrikdb__recall, or bare recall). The unprefixed names are used below; map them to whatever your harness registered.

Session start — one call

Call session with action="digest" once. It returns a single briefing: narrative head, open decisions, unresolved conflicts, pending triggers, and stale high-importance memories. Do this before answering anything substantive; a session that starts blank when 500 memories exist is a bug, and it is this one.

Before acting — recall, the right way

• Query with one short natural-language sentence (5–10 words), not a keyword list. Separate focused calls beat one broad one.
• For "what is the CURRENT value of X" (latest config, current owner, present status), use memory with action="chain_head" — similarity search returns the most-similar revision, which for values that change over time is often stale. chain_head returns the actual current value.
• Trust signals: hits whose why_retrieved says "aged", "superseded", or "rarely confirmed" are weak evidence. Prefer fresher hits, and say so if you act on a flagged one.
• Before starting a task you may have done before, call procedure with action="surface" — a learned method beats re-deriving one.

During work — capture as you go

• New durable fact → remember. Be specific and searchable ("Client Foo approved the March pricing tier", not "they said yes"). Set importance: 0.8–1.0 decisions and hard commitments, 0.5–0.7 useful context, 0.3–0.5 background. Set domain and source.
• A stored fact changed → correct with a reason — never a second remember. This preserves history and prevents the contradiction the next session would otherwise inherit.
• Entity relationship learned → graph with action="relate".
• A working method discovered (a scraping recipe that got past a blocker, a benchmark invocation that finally worked) → procedure with action="learn".
• Do NOT store: secrets or credentials, ephemeral task chatter, anything derivable from the repo or files you already have. Memory is for what would otherwise be lost when this session ends.