LLM wiki pattern

The LLM wiki pattern is the idea that an LLM should maintain a persistent markdown wiki as an intermediate compiled knowledge layer between raw source documents and future queries.

Contrast with ordinary RAG

In ordinary RAG, the model repeatedly rediscovers relevant context from source fragments at query time. In an LLM wiki, the synthesis is compiled forward over time. The model updates pages, cross-references, summaries, and contradictions as new material arrives.

Structural layers

1. raw immutable source documents
2. an LLM-maintained markdown wiki
3. an instruction file that teaches the LLM how to ingest, update, query, and lint the system

Adapted for Shanepedia and Codex

In this environment the pattern becomes:

1. raw/ as the evidence layer
2. wiki/ as compiled founder/operator memory
3. Obsidian as the human IDE for browsing the graph
4. Codex as the primary maintainer writing durable updates
5. OpenClaw child lanes as feeder systems that should improve the parent wiki

That means good answers should usually leave a file behind. The system should gain pages, links, maps, dashboards, and clarified contradictions, not just terminal output.

Why the pattern is powerful

• knowledge compounds instead of resetting every query
• useful analysis can be written back as durable pages
• cross-links and contradictions can be maintained incrementally
• the human gets a browsable system instead of a pile of uploads
• Obsidian becomes a real IDE for thought instead of just a note browser

Shanepedia implication

Shanepedia should explicitly act like this pattern, not merely resemble it. That means every ingest, question, and synthesis should be treated as an opportunity to improve the compiled wiki itself.

Codex implication

Codex should behave less like an ephemeral assistant and more like a wiki maintainer:

• parent wiki first
• child lane second
• raw source only when the compiled layer is missing or needs verification
• durable markdown output by default for reusable insight
• index, lint, and navigation upkeep as part of the task, not optional polish

Product implication

This is also one of Shanepedia Studio's strongest possible offers: an agent-maintained founder wiki that compounds context over time and becomes a durable operating system for projects, relationships, travel, research, and decisions.