Step 2

Install the LLM Wiki Pattern

Karpathy's pattern says only a small, curated slice of your raw knowledge belongs in the wiki. The rest stays raw. The wiki stays alive because the model keeps operating on it.

Get the Pattern

Get the LLM Wiki Pattern

Read the original concept, then adapt the pattern inside your own WIKI.md so the system fits your world.

Get the LLM Wiki Pattern →
Original LLM Wiki gistReference EJ's GitHub org

Overview

Why 5% beats 100%

If you try to promote everything, the wiki becomes a landfill. The 5% rule forces editorial judgment: only the most durable, reusable, and structurally useful knowledge gets promoted into pages.

This is the layer that turns documentation from a passive archive into a maintained knowledge surface.

Deep Dive

Expand the operating model

The pattern is small enough to teach in one breath and deep enough to run forever.

The 4 operations

INGEST, QUERY, HARVEST, and LINT are the verbs that keep the wiki alive.

Expand

INGEST processes new sources and proposes updates. QUERY lets you retrieve answers from curated pages. HARVEST mines real work for facts the wiki missed. LINT keeps structure healthy by catching stale pages, broken links, and schema drift.

INGEST -> new source arrives
QUERY  -> someone asks a question
HARVEST -> a session produced something durable
LINT -> the wiki needs housekeeping

Why this makes the wiki alive

A static wiki only reflects the moment it was written.

Expand

The alive part comes from repeated operation. The model keeps returning to the wiki as a working surface, not a museum exhibit. Pages improve because they are exposed to new evidence, new sessions, and new contradictions.

  • INGEST keeps it current.
  • QUERY tests whether it is useful under pressure.
  • HARVEST catches what normal note-taking misses.
  • LINT prevents slow structural rot.

What belongs in the curated 5%

Store durable structure, not every passing thought.

Expand

Pages should hold concepts, people, projects, playbooks, and recurring facts that help future work move faster. Scratch notes, half-formed brainstorms, and low-signal fragments can stay in raw memory until they prove durable.

Good wiki material:
- project definitions
- glossary concepts
- reusable process notes
- people context
- stable decisions

Keep raw:
- temporary fragments
- speculative scraps
- duplicate observations

Installation

Step-by-step

Install just this

Set up a wiki process even if you are not ready for the full Palace stack yet.

  1. Create a root wiki folder with a small schema document.
  2. Define the four operations in plain language.
  3. Write a tiny index page so the model has a catalog to maintain.
mkdir -p Wiki
touch WIKI.md index.md log.md

# WIKI.md should define:
# - page types
# - naming rules
# - update rules
# - what INGEST / QUERY / HARVEST / LINT mean

Install as part of the full system

Keep the wiki schema compatible with the raw memory and later HARVEST outputs.

  1. Map each raw source class to likely page destinations.
  2. Choose a folder taxonomy before scaling.
  3. Reserve log.md for operational visibility.
Wiki/
  Projects/
  People/
  Concepts/
  Infrastructure/

index.md
log.md
WIKI.md
Previous: MemPalaceNext: EJ's Palace Wiki