LLM Wiki
Why the Library reads like a wiki, what Mem does on its own, and what you stay in charge of.
The Library now reads as a wiki, not a file pile. The wiki you are reading is the same knowledge Mem has been collecting in the background; the difference is that you can finally read it page by page, click through the connections, and ask a single concept the question you actually had.
Andrej Karpathy described the underlying pattern very clearly: many small markdown pages, each focused on one entity or one topic, cross-linked with [[wikilinks]], with an index.md as a directory. The LLM does the bookkeeping; you curate. Mem implements that idea on top of your knowledge graph.
First useful action
- Open the Library and switch to the Wiki tab.
- Pick a topic that already has memories under it. Read its summary, click into one of the listed entities, then click into a related entity.
- From an entity, crystal, or topic page, click Investigate. The Knowledge Graph opens with that node (or the whole cluster) already selected.
You should be able to navigate three or four pages without typing once. That is the first signal that the wiki is yours to read.
What Mem does for you
The bookkeeping side of a personal wiki is exactly what kills most attempts at one. Mem treats it as the system's job, not yours.
- Topic clustering. Background Intelligence groups your knowledge into topics and gives each topic a name. The Wiki tab is the index for those topics.
- Entity pages, derived live. Each entity has a wiki entry built from the graph: where it sits in your topics, when it was first seen, the agent's confidence in it, aliases it picked up, the memories that mention it, the entities sitting next to it. There is no second copy you have to maintain.
- Crystals as reference articles. When three or more memories converge on the same idea, Mem synthesises a Crystal: a stable reference page with
[[Entity]]wikilinks already woven in. Every Crystal lists the source memories it was built from. - Evolution and contradictions. EVOLVES edges track when newer knowledge replaces or refines older knowledge. Crystal pages show the older memories they grew out of and the newer ones they grew into.
- Last-touched and recent activity. Each topic page carries a "Recent on this topic" rail, so the wiki reflects what you have actually been thinking about lately.
What you stay in charge of
The wiki is built around a clear division: Mem handles the bookkeeping, you handle the thinking.
- Picking sources. Drop in the document, conversation, or note. The wiki only grows from what you decide is worth feeding it.
- Asking the questions. The Knowledge Graph Agent and the Library's "Study with AI" both wait for you to point at something. They do not wander.
- Deciding what to keep. "Study with AI" proposes memories and Crystals; you tap Save 1, Save all, or Skip. Nothing auto-saves.
The wiki sits on top of the writing path
Mem already had a writing path in place: ingest, parse, classify, extract entities, detect EVOLVES edges, synthesise Crystals, cluster into communities, all happening in the background as you use the tool. The Wiki tab is a reading path layered on top, not a new datastore.
That has a few useful consequences:
- Pages are derived, not stored. Edits happen at the data layer (memories, sources, crystals), and the wiki page refreshes from there. There is no parallel copy to drift out of sync.
- Export is a snapshot, not a sync target. Wiki Export gives you a one-shot folder of markdown files cross-linked with
[[wikilinks]]. Re-export when you want a fresh copy. Editing inside Obsidian does not flow back into Mem. - Investigate keeps you on the same canvas. When you click Investigate, you stay in Knowledge Graph overview mode, the cluster is highlighted, and Graph Intelligence Agent reads the same selection you do. Anything the agent saves comes back to the topic page in Library.
Where to go next
- Library: the day-to-day surface where you read the wiki and run "Study with AI".
- Crystals: how stable reference pages get synthesised.
- Background Intelligence: the work that keeps your wiki current without you asking.
- EVOLVES: how Mem tracks the way your understanding moves.