AI-Maintained Knowledge Bases
AI-maintained knowledge bases are structured markdown wikis built and updated by large language model (LLM) agents rather than by human editors. The paradigm was first published by Andrej Karpathy in April 2026 through a GitHub Gist that introduced the "LLM Wiki" pattern, which frames knowledge management through a compiler metaphor[^c12], which frames knowledge management through a compiler metaphor: source documents are pre-processed into an interlinked wiki, and all subsequent reasoning works from this compiled output rather than re-deriving knowledge from scratch on every query.[^c2] In this model, the human curates what enters the system while the LLM handles all maintenance and cross-referencing.[^c1]
The core architecture consists of three layers: an immutable raw/ directory containing original source documents, a wiki/ directory of LLM-generated markdown pages with cross-references, and a schema configuration that governs the LLM's wiki maintenance behavior.[^c4] The system operates through three primary operations — Ingest (processing new sources into the wiki), Query (synthesizing answers from compiled pages), and Lint (health-checking for contradictions, orphans, and broken links). A single ingest operation typically updates between five and fifteen wiki pages as the agent traces implications across the knowledge graph. Karpathy later refined these into a five-step workflow, describing the shift from using LLMs for code generation to using them for knowledge management as a more valuable application.[^c8]
Empirical testing of the pattern has demonstrated significant improvements in answer quality. Wiki-assisted answers scored 4.9 out of 5 compared to 4.0 out of 5 for direct LLM queries, while a set of ten source articles (~29,000 words) was processed into 57 interconnected wiki pages in approximately twenty minutes with three contradictions automatically detected.[^c3][^c5] The Farzapedia case study demonstrated the pattern at personal scale: developer Farza fed 2,500 diary entries, notes, and messages to an LLM, which compiled them into 400 structured wiki articles forming a personal encyclopedia navigable by AI agents.[^c9]
The pattern is distinguished from retrieval-augmented generation (RAG) by its emphasis on knowledge compounding over time, its use of immutable source verification, and its ability to operate with zero infrastructure beyond markdown files and an LLM. A broad community debate emerged around whether LLM Wiki genuinely replaces RAG or essentially renames a cache layer, with pragmatic assessments acknowledging both patterns as complementary tools for different scales and use cases.[^c10]
Academic research on the pattern has advanced rapidly. The first paper (May 2026) proposed LLM-Wiki as an agent-native retrieval system that achieved state-of-the-art results on multi-hop question answering benchmarks, outperforming existing retrieval systems including HippoRAG 2, LightRAG, and GraphRAG by 2.0 to 8.1 F1 points.[^c7] A subsequent paper identified a compilation gap — the risk that LLM distillation may discard critical facts — and proposed WiCER, an iterative refinement algorithm that recovered 80 percent of lost quality across 17 domains.[^c11]
The LLM Wiki concept spawned a broad ecosystem of implementations and extensions. Community projects added features such as confidence scoring, typed relationship graphs, Ebbinghaus-inspired retention decay, multi-agent governance, and MCP integration for agent tool access.[^c6] Implementations range from minimal, zero-dependency tools to production-grade systems supporting multimodal input, hybrid search, retroactive session transcript distillation, and fully local operation via Ollama. The community transitioned from experimental scripts to packaged runtimes, with public registries offering installable skill packages and CLI tools for bootstrapping and maintaining LLM wikis.