Practical writing on building and operating AI agents at scale — architecture, channels, retrieval and how agencies run agent fleets for their clients.
One agent is a project. Three hundred across twenty organisations that must not see each other is an architecture, and the difference is not scale. Five boundaries that decide whether a platform can be operated as a fleet.
What a ten-minute onboarding looks like from the operator's seat: what the client inherits instead of receiving, what you cap before they start, and the test that decides whether their agent goes live at all.
Three questions about your own fleet that most operators cannot answer, the record that makes them answerable, and why retirement is the lifecycle step that nobody builds.
The gap between ten minutes and three days is not labour, it is waiting on people. What a fully scripted tenant onboarding actually does, minute by minute, and the one step that turns the whole thing back into a ticket.
The user's question is under one percent of what you pay for. An arithmetic model of fleet inference cost denominated in tokens, the four multipliers that hide inside it, and the one term that grows quadratically.
Provider outages last hours, not minutes, and a fallback chain three deep can still be one provider. A teardown of what actually has to be in place, minute by minute, and what failover costs you when it works.
Prompt injection is one entry point out of five, and the input filter everyone installs guards exactly one of them. Seven manipulation classes, why the obvious defence fails in each, and where the check has to sit.