Engineering & AI Systems

Loops and Legibility

Eight essays on the automation that runs underneath one person's days, and what it took to see it whole. Typing the loops, drawing them as a graph, the rule of one writer, the stack underneath, and the question a loop cannot answer. Written as it happened, July to October 2026.

8 parts

See also the cornerstone explainer: Domain Cartography

  1. Part 1 Hello The first program you write used to be the machine greeting the world. Hello, world. I built a different first program: my own system greeting me. One warm door instead of four scattered starters, and the greeting sits inside the loop it opens, so it can reach in and improve itself.
  2. Part 2 A Loop Is Seven Things Thirty-two automated jobs run underneath my days, I wrote every one of them, and I could not hold the system in my head. The problem was never my memory. It was a word. "Loop" was one word doing the work of seven.
  3. Part 3 The View You're Missing Is the Graph I gave every job in my automation a receipt, a health check, and a green light, and the system still would not fit in my head. A dashboard shows the state of the parts. The question I actually had was about the shape of the whole, and no amount of state answers a question about shape.
  4. Part 4 One Writer Per Artifact Typing my automation handed me most of its rules for free; the type carries the contract. One rule came free with nothing, and it was the one my system was breaking: every file gets exactly one job that writes it. On the difference between rules you remember and rules the structure carries.
  5. Part 5 You Reinvented Data Engineering The best thing anyone told me about my own system this year was that I had not invented it. The scripts I grew by hand are a data pipeline, the shape is a DAG, and the discipline is solved. What the tools actually sell, why I am not buying yet, and the difference between wanting an engine and wanting a map.
  6. Part 6 The Loop Was the Top of a Stack I typed my thirty-two loops, then drew them as a graph, and thought the loop was the top of the system. It turned out to be the roof of a stack eight floors deep, and the floor holding all the weight is the smallest one: the edge.
  7. Part 7 Hello, Again Three weeks ago I wrote about a script called hello, the one warm door into my system. I kept pulling the thread and the door turned out to be the outermost loop, the one that asks whether the whole thing can still become useful. This is what I found standing behind a greeting: cybernetics, nested watchers, and the rule that intelligence never gets its own hands.
  8. Part 8 A Loop Is a Path That Closes One of my health checks stayed red for eleven weeks by reading its own failure. A loop is the special case of a trajectory, the path that happens to close, and a life does not.