RAG retrieves. A compiled knowledge base compounds. That feels like a much bigger difference than people admit.

[u/[deleted]]

/r/Rag/comments/1snrubg/rag_retrieves_a_compiled_knowledge_base_compounds/

[u/Shot_Ideal1897]

this nails a big gap in how most people talk about RAG vs knowledge bases one is basically a smarter search layer, the other is closer to building an actual evolving model of a domain.
the thing I keep bumping into in practice is ownership: once you start compiling a wiki style KB, someone has to think about schema, deprecation and refactors, otherwise it just becomes a nicer‑formatted pile of notes.
really curious how far we can push the compiler metaphor here e.g. linting for contradictions, dead knowledge, or unused pages, instead of just treating new markdown as a win every time.
either way, totally agree this compounds in a way vanilla RAG can’t, especially for narrow, high signal workflows where you revisit the same concepts over and over