The LLM-Wiki and the Self-Improving Research Loop
A reflection filed back into the wiki, 2026-06-28. Source idea: Andrej Karpathy, LLM Wiki.
The pattern in one breath
Most LLM-plus-documents work looks like RAG: upload files, retrieve chunks at query time, generate an answer, throw the answer away. Nothing accumulates. Every question rediscovers knowledge from scratch.
The LLM-Wiki inverts this. Instead of retrieving from raw sources every time, the agent incrementally builds and maintains a persistent wiki - a structured, interlinked collection of markdown pages that sits between you and the raw sources. The knowledge is compiled once, then kept current. The wiki is a persistent, compounding artifact: the cross-references are already there, the contradictions are already flagged, the synthesis already reflects everything read.
Three layers
- Raw sources - the immutable source of truth. Articles, papers, transcripts, data. The agent reads them, never edits them.
- The wiki - LLM-generated markdown the agent owns entirely: summaries, entity pages, concept pages, an evolving synthesis. You read it; the agent writes it.
- The schema - the configuration document (a CLAUDE.md / AGENTS.md) that tells the agent how the wiki is structured and what workflows to follow. This is what turns a generic chatbot into a disciplined wiki maintainer. You and the agent co-evolve it.
Three operations - and where the loop lives
- Ingest - drop in a source; the agent reads it, discusses takeaways, writes a summary page, updates the index and every affected entity/concept page, appends to the log. One source can touch 10-15 pages in a single pass.
- Query - ask a question; the agent reads the index, drills into relevant pages, synthesizes a cited answer. The crucial move: good answers are filed back into the wiki as new pages, so explorations compound exactly like ingested sources.
- Lint - periodically health-check: contradictions, stale claims, orphan pages, missing cross-references, gaps a search could fill.
That one move - query answers filed back as sources - is what closes the loop. Output becomes input. The wiki gets richer with every source added and every question asked.
Why an agent + a wiki is naturally self-improving
A self-improving loop needs four things, and the LLM-Wiki supplies all four for free:
- Durable memory the worker can both read and write. The wiki is exactly this. The agent is not stateless between sessions; it stands on its own accumulated work.
- A monotonic ratchet. Each ingest and each filed-back answer raises the floor. Nothing has to be re-derived; the next pass starts from a higher base.
- An error signal.
lintis the gradient - contradictions and orphans are defects the next pass corrects. The wiki critiques itself. - A trace.
log.mdis an append-only record of every ingest, query and lint. The loop can inspect its own history and reason about what to do next.
Memory + ratchet + error signal + trace = a research process that compounds instead of resetting. This is why the pattern fits research self-improvement so cleanly: it is not a trick bolted onto an agent, it is the shape an agent's workflow takes when you give it a place to keep its thinking.
The evidence: this page is an instance of the thing it describes
We did not theorise this loop; we ran it. Working from Karpathy's essay we built a wiki skill, and in doing so produced Governing an LLM-Wiki: the Eight Gates - a synthesis that did not exist in any source, discovered by querying the pattern and then filed back into the wiki as a new page. That is the query-to-source move, observed in the wild.
The same loop, run at scale on a different corpus, produced The Hitchhiker Expression of the Same Protocol: dozens of session transcripts ingested, answered through five fixed lenses, cross-linked into hubs, lint-checked for coherence. Two corpora, one loop.
The lineage is older than LLMs. Vannevar Bush's Memex (1945) imagined a private, curated knowledge store with associative trails between documents - the connections as valuable as the documents. The part Bush could not solve was who does the maintenance. The agent does. Maintenance cost falls to near zero, so the wiki actually stays alive.
Read on: Governing an LLM-Wiki: the Eight Gates - how the federation keeps the loop trustworthy. The Hitchhiker Expression of the Same Protocol - the same logic in mythic voice. One Logic, Many Skins - the correspondence table.