Menu

I added verbatim memory to my .NET AI library : here's why it outperforms extraction
🖼️

I added verbatim memory to my .NET AI library : here's why it outperforms extraction

DEV Community: blazor·Aftab Bashir·5 months ago
#eoYbBaMd
#dev#verbatim#facts#blazormemory#article
Reading 0:00
15s threshold

There is a paper called MemPalace that stores conversations verbatim instead of extracting facts from them. It scores 96.6% on LongMemEval. Most extraction-based approaches sit around 70-80%.

That got my attention.

BlazorMemory has always used AI extraction. You send a conversation, an LLM pulls out discrete facts ("User is a software engineer"), and those facts get stored as vector embeddings. It works well. But it is lossy by design. The LLM decides what matters, and sometimes it gets that wrong.

Verbatim mode skips the extraction step. The raw conversation chunk goes straight into storage with an embedding. Nothing is thrown away.

How it works

Smart mode (the original approach):

Conversation -> LLM extraction -> facts -> embeddings -> storage

Enter fullscreen mode

Exit fullscreen mode

Verbatim mode (new):

Conversation -> embedding -> storage

Enter fullscreen mode

Exit fullscreen mode

That is it.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.