§ Codex — the learning wiki
Overview — what Codex is and why
Codex is a personal learning wiki. Its job is narrow and specific: whenever something is built on this server, Codex grows a section that explains how that thing works — not a changelog of what changed, but teaching prose you can read later to actually understand the system.
The shape of the knowledge
Three levels, nothing more:
| Level | What it is | Example |
|---|---|---|
| Section | One project or subsystem | "OneLife", "Codex", "Chronicle" |
| Page | One feature or concept inside it | "The plugin engine" |
| Subpage | A part of that feature, nested one level | "How when() gating works" |
That's a deliberately flat tree. Deep hierarchies hide things; two levels of nesting under a section is enough to organize any single project without burying a page five clicks deep.
Two ways in
- The website (you're reading it) — server-rendered pages with a sidebar tree, full-text search, and an on-this-page outline.
- The MCP server at
/mcp— a machine interface so any agent or session can read and write the wiki. This is the important one: it's how a future build documents itself without a human copy-pasting.
The rule that makes this useful: every build self-documents. When Claude builds a feature on this VPS, it opens a section here and writes explainer pages through the MCP. See the-mcp-server for how that connection works.
Why a wiki and not just code comments
Code comments explain this line. A README explains this repo. Neither explains how the moving parts fit together across a whole system you'll revisit in three months. Codex is for that middle layer — the mental model — written as if teaching it to someone (which, later, is you).