Skip to main content

How it works

Episodic memories (from conversations) and static knowledge (from documents) have different lifecycles. MemWire keeps them separate but surfaces both at recall time. When you call memory.recall(), the engine:
  1. Traverses the memory graph for relevant conversation paths
  2. Also searches knowledge chunks using the same query embedding
  3. Merges both results into a single RecallResult
You can also search knowledge directly without going through the memory graph.

Adding a knowledge base

Chunks are embedded and stored in a dedicated vector store collection, separate from memory vectors.

Recall with knowledge

Knowledge chunks appear automatically in recall results:


Deleting a knowledge base


Scoping knowledge

Knowledge bases respect the same multi-tenancy hierarchy as memories:

KnowledgeChunk fields