The AI Control Plane Spectrum
Vendors sell five different things as an AI control plane. A four-level spectrum to tell token routing from a substrate that keeps your methodology.
Notes on building the collaboration layer for agents and operators.
Vendors sell five different things as an AI control plane. A four-level spectrum to tell token routing from a substrate that keeps your methodology.
AI workflows are replacing SaaS tools, but the workflow lives inside the vendor. The lock-in is worse than the product it replaced.
Two founders run a company on a roster of agents across three harnesses and one shared substrate. The real workflow, plus five primitives to build your own.
Smarter models won't unlock the next productivity step. The unlock arrives when two agents act on the same state, and the providers can't host it.
Model portability is the easiest layer to solve. Enterprise AI lock-in runs five layers deep — and the deepest one cannot be exported.
We built an agent that does not live on our servers. Three memory layers, two operators, one imprint. Here is the architecture and what surprised us.
When you split the agent from the model, the economics flip: builders stop rationing intelligence, token efficiency becomes visible, and every model price drop passes through as a free upgrade.
AI agents should not live inside the runtime that executes them. Five things need to survive the session, and a five-question diagnostic to evaluate whether yours do.