The essays here work through the operating model that emerges when software-building moves from one human typing into one terminal to many agents coordinating across many repositories. Doctrine engineering as the discipline. Compiled and interpretive doctrine as the two registers. Supervision trees as the pattern for fleet-scale failure recovery. The shape of work that compounds when AI takes the implementation slot and humans move upchain.
Names get coined when existing names don't fit. Historical precedents get cited where they exist: Erlang/OTP, EVE Online fleet coordination, the structural fix for SQL injection, Saltzer and Schroeder's principle of least privilege. The work is critique-first because the consensus framings need it.
Currently building a multi-repo, multi-agent orchestration substrate that runs hundreds of concurrent dispatches across MCP servers, infrastructure deployments, and a doctrine repository that governs the agents that write the code that ships back to the substrate that runs the agents. Recursion all the way down. The essays draw from operating that substrate, not from abstract speculation.
Where
@dangrafham on X for current posts. Field Notes for the essay archive. Glossary for vocabulary used here. RSS and JSON feed for syndication.
How to reach
Public conversation happens on X. Deeper threads and longer questions are best framed there as a reply or quote-tweet so the discussion stays public. Private channels exist but are reserved for active collaborations.