LLM Wiki Pattern

Think of it like a Personal Encyclopedia Made of Sticky Notes

Imagine you're exploring a new city. Every café you visit, landmark you see, or local tip you hear — you jot it down on a sticky note. One note per thing:

• "Pasar Baru market: best for spices. Opens 6am."
• "TransJakarta busway: pay with e-money card."
• "Mangga Besar station exit: turn left for noodle alley."

At first the notes are scattered on your wall — that's raw sources. Information without structure.

Draw arrows between notes that connect: "Busway route passes Pasar Baru → check if it stops near the spice shop." Now you have a wiki — organized sticky notes with [[arrows]] (wikilinks) between them.

But a messy wall is still useless. So you add rules: - Every note needs a label: "draft", "verified", "stale" — that's frontmatter. - Every arrow must point to a real note — that's what lint checks. - When you learn something new about busway tickets, you update the existing note instead of adding a duplicate — that's ingest with merge. - When someone asks "how do I get around?", you scan the wall, find the transport cluster, and give an answer with citations — that's query.

The key insight: You don't keep the original brochures, receipts, and pamphlets. You digest them into your organized notes. The raw source is archived in git history, but the knowledge lives in your living, cross-linked wiki.

A Pattern, Not a Product

LLM Wiki is not software you install. It's a recipe for how you and an LLM work together:

Step	Who does what
INGEST	You bring source material → LLM extracts concepts → script writes pages + crosslinks + commits
QUERY	You ask a question → script finds relevant pages → LLM reads + synthesizes answer with [[citations]]
LINT	Script walks the wiki → reports broken links, orphans, stale pages → you fix

The wiki lives in a git repo (~/llm-wiki/). Every change is a commit. You can rewind to any previous state — like having a time machine for your brain.

Why This Works Where Folders Fail

• Interlinking ([[wikilinks]]) creates a web, not a pile. Ideas connect naturally.
• Atomic pages (one concept per page) keeps each note short and focused.
• Frontmatter (tags, status, source) adds metadata without cluttering the explanation.
• Git gives you version history, rollback, and branching — your knowledge base evolves safely.
• Lint nags you about broken links before they rot into dead ends.

Remember: A wiki is not a document you write once. It's a garden you tend. You plant new seeds (ingest), water existing ones (update), and pull weeds (lint).