8 posts
Posts on architecture
On building, running and keeping control of your own agents.
latest · Oct 1, 2026 · 6 min readAgent protocols are converging. Inter-org trust isn't.
A2A v1.0 standardized the agent handshake — cards, tasks, transports. It leaves card verification, delegation, and cross-org trust to you.
2026
- Sep 10Updating a running agent is a migration, not a deploy5 minTeams redeploy agents like stateless functions, then wonder why a "small change" silently corrupts weeks of working memory. A stateful agent update is a database migration — and most teams have no migration tooling at all.
- Jul 16Switching AI agent frameworks costs $315K — and most teams don't know they've locked in4 minFramework lock-in is the hidden cost of AI agents. Breaking-change cycles, provider price hikes, and migration bills averaging $315K are the real barrier to production.
- Jul 9Your multi-agent pipeline has no message authentication5 minEvery major agent framework passes messages between agents as plaintext — no signatures, no verification. That is the defining security gap of multi-agent systems in 2026.
- Jun 19Cost control is the missing infrastructure for AI agents7 minA market-research pipeline of four agents entered a loop that ran for 11 days and cost $47,000. No framework prevents this at the infrastructure layer.
- Jun 19Why multi-agent coordination is harder than you think4 minThe hard part of multi-agent systems isn't building agents — it's how they coordinate. Most frameworks leave that as your problem. Workgroups shouldn't be an afterthought.
- Jun 11Agents Don't Know Who They're Talking To6 minEvery major agent framework identifies agents by a name and a role string — no keys, no signatures, no peer verification. What production actually needs.
- Jun 11Running agents as an organization, not a developer toy4 minMost agent tooling was built for developers wiring up demos. Operating persistent agents as a company is a different problem — identity, budgets, governance, and trust by default.