Quote
—
99 posts
—
From compound AI systems to the agentic loop, MCP, APIs, frameworks, and the rise of the Claws — a technical map of what it takes to build with AI agents in 2026.
What Maslow's hierarchy of needs, Levitt's whole product model, and Geoffrey Moore's crossing the chasm can teach us about building AI products that actually ship.
Two unrelated projects discovered the same pattern: point an AI agent at code, give it a score to chase, and let it run experiments until morning. I generalized it into a tool that works for any domain.
I've been learning new programming languages by watching AI coding agents work — like shadowing a colleague. The research says this should make me worse. Here's why I think it's more complicated than that.
If AI scales execution and verification is the bottleneck, the winning move is to make verification cheaper. Here are the patterns that actually work.
Container registries store bytes. They don't know what's inside. The Agent Registry is a governance layer for AI agents, skills, and MCP servers, built on A2A AgentCard, MCP server.json, and Agent Skills as native identity formats.
Six gateway architectures for AI agents, ranked from full control plane to no gateway at all. Interactive diagrams with animated data flows.
— Coleman et al., 2022
Every agent team rebuilds the same auth, rate limiting, and credential management. I built an agent gateway for Kubernetes that generates it all from two CRDs so the people building agents never touch security and the people running the platform never touch agent code.
AI coding agents pulled developers back to the terminal. But the data says the real split isn't CLI versus GUI. It's about what you're doing.
The agent gateway for Kubernetes. Covers agent discovery, authentication, routing, credential injection, rate limiting, and MCP protocol support.
A vendor-neutral registry for AI agents, skills, and MCP servers. Covers the problem of agent discovery, the registry architecture, and how agentctl works.