Building an LLM Wiki, Part 3
essay · August 2026An agent that runs commands on your laptop runs them as you. Putting it in a container — and the one hole you can decline to punch.
Writing
Occasional field notes — on engineering, economics, and the places they collide.
An agent that runs commands on your laptop runs them as you. Putting it in a container — and the one hole you can decline to punch.
A general model gives you plausible architecture. Connecting a curated, opinionated library over MCP changes where the conversation starts.
What is actually in 442 files, who decided any of it, and where it is weakest — including the parts I would rather not advertise.
From answers in a chat window to documents somebody acts on — decision records, design reviews, runbooks, and a diagram that carries its provenance.
How a design travels. A folder of correct files is not a design — and putting them on one page found problems the folder had been hiding.
A reaction-wheel inverted pendulum designed almost entirely by a language model — what it produced, how fast, and where it stopped being reliable.
The pattern, the plumbing, and the discipline that keeps a language-model-maintained wiki honest.
The additions beyond Karpathy’s gist — schema-as-code, computed staleness, contradictions as data, and a retrieval test harness.
On leaving NASA — what I’d taken for the summit of human spaceflight — and the question it couldn’t ask.