Summary — NotebookLM vs. LLM Wiki

Source: NotebookLM vs. LLM Wiki: Two Approaches to AI Knowledge Management

Overview

This article compares two fundamentally different philosophies for AI-assisted knowledge management: Google’s notebooklm and the llm-knowledge-base pattern (the “LLM Wiki” proposed by andrej-karpathy). The two represent opposing ends of a design spectrum — on-demand retrieval versus persistent compilation of knowledge.

NotebookLM: The RAG Approach

NotebookLM is Google’s AI-powered research assistant built on the rag paradigm. Users upload documents (PDFs, Google Docs, websites, YouTube videos), and NotebookLM lets them ask questions. Under the hood, it retrieves relevant chunks from uploaded sources and generates answers — classic retrieval-augmented generation.

Key features highlighted:

• Audio Overview — generates podcast-style audio summaries of sources
• Source grounding — every answer includes citations back to specific source passages
• Collaborative — notebooks can be shared with others
• Multi-modal — handles text, PDFs, audio, and video transcripts

The article identifies several limitations that stem directly from its RAG architecture:

• Knowledge is re-derived on every query — no persistent synthesis
• No cross-referencing between concepts across sources
• No incremental building — adding a new source does not update previous answers
• Google controls the infrastructure; data lives on their servers
• Limited to approximately 50 sources per notebook

LLM Wiki: The Compiled Approach

The LLM Wiki pattern takes the opposite approach. Instead of retrieving from raw sources at query time, the LLM incrementally compiles and maintains a structured wiki where knowledge compounds over time.

Key differences from NotebookLM:

• Local-first — everything is markdown files on the user’s machine
• Persistent synthesis — the wiki is a compounding artifact
• LLM as maintainer — the LLM handles all bookkeeping (cross-references, consistency, updates)
• Open and portable — just a git repo of markdown files
• Unlimited scale — no artificial limits on source count

When to Use Which

The article provides clear guidance on when each approach is appropriate (see notebooklm-vs-llm-wiki for the full comparison page):

NotebookLM is better for:

• Quick research on a bounded set of documents
• Audio summaries
• Collaborative research with non-technical users
• When no infrastructure setup is desired

LLM Wiki is better for:

• Long-running knowledge projects (months/years)
• Knowledge that should compound over time
• Full control over data
• Deep research requiring synthesis across many sources
• A permanent, evolving knowledge artifact

The Future

The article notes the two approaches are not mutually exclusive. A practical workflow could use NotebookLM for initial exploration of a topic, then migrate key findings into an LLM Wiki for long-term synthesis. The open question is whether Google will move NotebookLM toward persistent synthesis, or whether the open-source community will build better tools around the wiki pattern.

Significance for This Wiki

This is the second source ingested into this knowledge base and the first to provide a direct, concrete comparison between a real-world RAG product (NotebookLM) and the compiled wiki pattern. The Karpathy gist discussed RAG abstractly; this source grounds the comparison in a specific, widely-used product. It also introduces the idea that the two approaches can be combined in a practical workflow — explore first with NotebookLM, then compile into a wiki for long-term retention.

Related Pages

• notebooklm
• google
• llm-knowledge-base
• rag
• compiled-wiki-vs-rag
• rag-vs-compiled-wiki-analysis
• knowledge-compounding
• wiki-schema
• andrej-karpathy
• notebooklm-vs-llm-wiki
• karpathy-llm-wiki