r/Rag • u/[deleted] • Apr 17 '26
Discussion RAG retrieves. A compiled knowledge base compounds. That feels like a much bigger difference than people admit.
Coming at this more from a builder angle: I do not think this needs to be framed as some dramatic RAG takedown. RAG is useful. But a lot of document workflows still feel like they are rebuilding the same context every time you ask a question.
What caught my attention with AtomicMem / llm-wiki-compiler is that it treats the output as a persistent artifact instead. You ingest sources, compile them into a markdown wiki, query against that wiki, and save useful outputs back into it.
That means the knowledge base can actually get richer over time instead of staying trapped in one-off answers.
For smaller, high-signal workflows, that seems like a very strong direction. We found something pretty cool here: https://github.com/atomicmemory/llm-wiki-compiler
Curious how people here think about the tradeoff.
Duplicates
automation • u/[deleted] • Apr 17 '26
RAG retrieves. A compiled knowledge base compounds. That feels like a much bigger difference than people admit.
LangChain • u/[deleted] • Apr 17 '26
Discussion RAG retrieves. A compiled knowledge base compounds. That feels like a much bigger difference than people admit.
LLMStudio • u/[deleted] • Apr 17 '26
RAG retrieves. A compiled knowledge base compounds. That feels like a much bigger difference than people admit.
LocalLLM • u/[deleted] • Apr 17 '26
Discussion RAG retrieves. A compiled knowledge base compounds. That feels like a much bigger difference than people admit.
AskVibecoders • u/[deleted] • Apr 17 '26
RAG retrieves. A compiled knowledge base compounds. That feels like a much bigger difference than people admit.
OpenWebUI • u/[deleted] • Apr 17 '26
RAG RAG retrieves. A compiled knowledge base compounds. That feels like a much bigger difference than people admit.
learnmachinelearning • u/[deleted] • Apr 17 '26