At a glance
Overlap and shared capabilities
The LLM Wiki pattern (popularized by Andrej Karpathy and demonstrated in project Farzapedia) and Wazoo Worlds take the same position on agent memory: it should be compiled, structured, and interlinked rather than stored as flat, opaque vector databases. Both approaches organize knowledge into navigable graph nodes where links between concepts matter just as much as raw text search. Where they overlap and build on each other:- LLM Wiki defines the human-and-agent readable workspace, where agents
continuously summarize, synthesize, and interlink Markdown articles
(
[[wikilinks]]). - Worlds provides the underlying schema-checked fact engine. It takes those compiled articles and frontmatter assertions, enforces SHACL shape validation, and lets agents execute SPARQL graph queries across the knowledge graph.
When Worlds fits
- You need strict schema validation (SHACL) to prevent metadata drift and hallucinated facts in your knowledge base.
- You require deterministic graph queries (SPARQL) across connected entities rather than manual link-following.
- You want an append-only ledger that tracks when facts were asserted and by whom.
When LLM Wiki fits
- You want a human-in-the-loop personal knowledge base (Obsidian/Logseq format) where both humans and agents read and edit markdown articles.
- You are starting with raw transcripts and want agents to summarize and interlink information organically.
Coexistence and integration
The LLM Wiki pattern is complementary to Wazoo context infrastructure. You can run an LLM Wiki directly using the Wiki toolchain, as demonstrated in the officialllm-wiki starter template,
where agents continuously garden Markdown articles while Wiki CLI validates RDF
shapes.
To scale agent knowledge across multi-agent fleets and production environments,
we recommend pairing your LLM Wiki with Worlds as the
underlying context engine, so agents maintain human-readable Markdown while
querying Worlds via SPARQL for deterministic fact verification.