The autonomy gap
Why connecting a model to enterprise systems is not the same as creating an autonomous operation.
Publications
What we observe designing, deploying and operating controlled autonomous systems. Field notes, research, operating principles and deployment notes — written from the work rather than about the category.
Latest
Why connecting a model to enterprise systems is not the same as creating an autonomous operation.
Mapping a fragmented operation rarely finds the bottleneck where the process document says it is.
A prompt expresses intent. A permission decides what is possible. Only one of them holds when the model is wrong.
The failures are rarely the reasoning. They are idempotency, partial writes, and success that was never achieved.
On what actually accumulates value when the execution layer can be replaced in an afternoon.
It records what was decided. It is not where deciding happens — and the difference sets the ceiling on what you can automate.
Doctrine lives in Approach
Control-first methodology, Agentification Contracts and model independence are standing positions rather than observations, so they live where they can be maintained as canonical. Publications reference them; it does not restate them.