This site is built on a simple but powerful idea: a living wiki that an AI helps maintain, but that I edit and control. It’s inspired by Andrej Karpathy’s “LLM Wiki” pattern and the way digital gardens work.

The three layers

The garden is built in three layers, and the difference between them is who’s allowed to touch what.

The three layers and who may edit each

Raw sources are read-only inputs the AI may read but never change. The wiki is the published product, drafted by the AI and approved by me. The schema is the rulebook that governs how the AI maintains the wiki.

  1. Raw sources Articles, notes & ideas I drop in: immutable inputs. AI reads only
  2. The wiki The interlinked pages you're reading, written & cross-linked by the AI. AI drafts · I approve
  3. The schema AGENTS.md: how the AI maintains the wiki: conventions, linking, logging. Governs the AI
Three layers, three permission levels: the schema governs how the AI turns raw sources into the wiki.

Why it’s different from a normal blog

A blog is a stream. A wiki compounds: pages get revised as my thinking changes, contradictions get flagged, and connections between ideas become as valuable as the ideas themselves. Nothing is re-derived from scratch; the knowledge is kept current.

Who’s in the loop

I am. 🧑‍✈️ I curate the sources, ask the questions, and approve edits (every change is a git commit, like Wikipedia’s edit history). The AI does the bookkeeping no human enjoys: summarizing, filing, and keeping links consistent.

It’s all open

  • The content and the renderer (Quartz) live in one public repo: FVossebeld/FVossebeld.github.io.
  • Every page has a full version history.
  • Anyone can propose an edit via pull request; I merge what I agree with.

How a page gets published

flowchart LR
  A[Write or update<br/>a markdown file] --> B[AI drafts<br/>on a branch]
  B --> C[I review<br/>and merge]
  C --> D[GitHub Action<br/>builds the site]
  D --> E[Site is live]

No database, no admin panel: just markdown in git.