It's 1:53 AM and I'm asking my CRM's chatbot: "what's the total amount we have parked in the Proposal stage?" Three seconds later it answers: $3,134.90. I follow up with just "and in prospecting?" — no context — and it breaks down the 10 open opportunities with amounts, close probability and estimated dates. A week earlier, this system was an n8n flow that only knew how to count contacts.
This is the second part of the series about running IRC-A — my decentralized multi-agent protocol — in production. In part 1 I covered the week-long migration from n8n and the absurd 679-token bill. This time: a stopwatch experiment, the night the protocol defended itself from AI-written code, and a confession about one of the fixes I proudly showed you last time.
The experiment: how long does it take to add a capability? Let's time it
The trigger was a failure. I asked the system "how much did we sell in July?" — and the Gateway routed it to the customers agent, because semantically it was the closest thing registered. There was simply no sales domain in the network. (That false positive is why we're adding a configurable similarity threshold to /discover.)
But instead of patching it, I saw the perfect experiment: create a sales-reports specialist agent and plug it into the live system — with a stopwatch running.
