Atomic knowledge
essay · October 2026The smallest unit of an idea that stands on its own: one page, six questions, and a named list of what it rests on — grown inside a MECE tree of everything, with an AI as the tutor that makes it practical.
Writing
Occasional field notes — on engineering, economics, and the places they collide.
The smallest unit of an idea that stands on its own: one page, six questions, and a named list of what it rests on — grown inside a MECE tree of everything, with an AI as the tutor that makes it practical.
Parallel agents burned 40% of a weekly quota in a day. A status-line script, one line of arithmetic, a two-hour check and a restart hook now spend the week evenly — by throttling concurrency, never quality.
One photograph, five passes at working out what is in it — silhouettes, then a fitted camera model, then map, Wikidata and LiDAR projected through it. Including the two confident answers that turned out to be wrong.
Design-as-code makes the geometry a program. The layer that decides whether it holds is provenance — which numbers other numbers depend on, read out of four unfinished machines.
The two classical ways to integrate an orbit — what each is good at, what each costs, and where the crossover sits, measured rather than asserted.
Parts 1 and 2 were one machine; this is five. What the method costs — where the time goes, and which instrument catches which class of error.
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.