Protocols and philosophies that hold across scales —
from org design to agentic infrastructure.
The discipline is the same whether you're designing a 300-person organization or a control plane: name what you actually depend on, admit what doesn't reduce, and build protocols that work on the substrate you have rather than the one the deck wishes you had.
Field Notes
-
Found and Proven
A boundary you observe and a boundary you derive are not the same object. Only one of them holds when the ground moves.
Read → -
Trail and Receipt
A memory system I built accused me of deferral at 0.91 confidence. It was right about my history and blind to my present — in the one way it was structurally guaranteed to be.
Read → -
In Arrears
When a regulator steps back, the risk doesn't leave — it changes venue. And the one defense the new venue accepts is the one you can't buy after the fact.
Read → -
The Unpriced
Replacing people with agents looks like savings. It's a transfer — from a cost you can see to one nobody priced.
Read → -
The Work You Need to Keep
Transactional AI use doesn't fail by producing bad output. It fails when the triage call stops being made.
Read → -
The Scope You Forgot to Name
Mapping the com.apple.macl incident to the governance layer that wasn't there.
Read → -
Constraints live in the substrate. Principles live in prompts.
Mapping the PocketOS incident to the four floor-level layers of an Agentic Control Plane.
Read →