Jeetu Patel, Cisco's president and chief product officer, posted this after their keynote week: https://www.linkedin.com/posts/jeetupatel_we-are-at-the-beginning-of-one-of-the-most-activity-7469585414857687040-4mtk/ Most of it is silicon and platform news. One line is worth pulling out if you build ICM systems: "every agent action will be a routing challenge, a trust decision and a telemetry event." A $200B infrastructure company just said what's slowing agents down is a trust problem, not a capability one. Agents don't get adopted until something can vouch for what they produce. The whole field, top to bottom, is arriving at the problem the people in this community have been working on since day one. What I want to flag is the crack in his own triad. Two of the three are infrastructure. Routing and telemetry get solved from outside the agent, and Cisco will happily sell you both. The trust decision is different. Their word for it is observability, meaning behavior monitoring, watch what the agent did. But watching what an agent did tells you nothing about whether its output should have shipped. You can log every step and still send a confident wrong answer out the door. That gap is the opening for every ICM builder here. Observability makes a system readable. It doesn't verify anything. The part that holds the line is a gate at the point of action with the authority to refuse, and that gate depends on knowing what "correct" means for your specific work. Which is exactly what a platform can't template. Cisco can build the dashboard. It can't decide, for your build, whether this particular output is honest. That decision stays judgment, and judgment doesn't commoditize when the infrastructure gets cheap. So here's the possibility for this community: the biggest players are going to make agents observable. Very few are going to make them refuse. If your ICM system already has a real gate, a step that can say no and mean it, you're building the layer they just named as the frontier, at the one altitude a platform struggles to reach.

Most people use AI the way they use a browser. You open it, ask, get a quick answer, an image, a draft email, and you close the tab. It's fast and it's useful, and for a lot of work it's all you need. Which model you prefer at that point is personal taste, apples and oranges, the same way some people like one search engine over another. But a browser gives you access to skill. It doesn't keep it. Close the tab and the skill leaves with it. Nothing you did this session is there waiting for you next time. That's the difference almost nobody talks about. When you stop visiting a model and start building a system around it, the skill stops being something you reach for and becomes something you own. You put it in folders. You give it rules. And it stays. I noticed how big that difference was by accident. I was using ChatGPT to look up something simple, a water park in my town, and four separate times it wandered off the thread and started answering a different question than the one we were on. I kept pulling it back. It wasn't a bad model. It wasn't even a long, loose session with nothing holding the thread in place. My own system doesn't do that, and it took me a while to understand why. It isn't a smarter model underneath. It's that the memory doesn't live in the session at all. It lives in files, and the system pulls only the few it needs for the task in front of it. There's no thread to lose, because the thread isn't being held in one fragile place. It's structured. Once I saw that, the way I think about the whole thing changed. A system isn't a tool you use. It's something you raise. I've written before that a system is like a child, and I mean it more literally than it sounds. Give a child structure early, rules and guides and a shape to grow inside, and they grow up carrying that structure. You don't have to install it later. A system is the same. Give it the rails at the beginning and it matures with them already in place. Mine started doing things I never designed it to do, and it could, because the base was solid enough to build on.