🙂
The Jarvis demos are always the same: todo lists, calendar, "it just handles my life."
Day 1 it's magic. The clickbait ends there.
Getting it to still work after a week, two weeks, a month, without drifting, repeating itself, or degrading into noise, is a genuine art form. That's the hard part, and it's the part nobody posts about.
‼️ ZELENSKYY: For the first time in the war, an enemy position was captured entirely by ground robotic systems and drones - without any infantry. A robot entered the most dangerous zones instead of a soldier and took the positions.
«The future is here, on the battlefield, and Ukraine is creating it. These are our ground robotic systems. For the first time in this war's history, an enemy position was taken exclusively by unmanned GRS platforms and drones. The occupiers surrendered, and this operation was completed without infantry involvement and without losses on our side. Ratel, Termite, Ardal, Lynx, Zmiy, Protector, Volya and other GRS completed over 22 000 missions at the front in just 3 months. In other words, over 22 000 times lives were saved. A robot went into the most dangerous zones instead of a soldier» - Zelenskyy’s address to the workers of Ukraine’s defense-industrial complex. April 13th, 2026.
Really like the state framework in the writeup and it's a genuinely useful way to think about where the value is actually accumulating.
But the Anthropic-specific read doesn't quite hold up for me. If the play is "capture state behind a closed API," why build MCP which is an open protocol that specifically lets enterprises connect their data without Anthropic sitting in the middle? And Claude Code runs locally. The state lives in the customer's repo, not behind Anthropic's wall. That's the opposite of the lock-in story.
The safety-as-strategic-cover angle is a clean narrative, but maybe too clean. These are people who literally left OpenAI because they didn't think safety was being taken seriously enough. You can acknowledge safety also builds enterprise trust without reducing it to a calculated moat play.
I work in cloud security consulting, and honestly the state ownership question being raised is one I deal with constantly. But when I look at the actual architectural choices: open protocols, local execution, state staying on the customer's side, that's exactly what you'd want to see from a vendor that's serious about letting enterprises own their own data. The architecture tells a different story than the narrative.
The industry-level thesis is sharp though. Enterprises absolutely need to think harder about who ends up owning the state that builds up around their AI systems. That part is spot on!
Introducing Claude Managed Agents: everything you need to build and deploy agents at scale.
It pairs an agent harness tuned for performance with production infrastructure, so you can go from prototype to launch in days.
Now in public beta on the Claude Platform.
@kidehen@asemota 8/After all that, it was an awesome session and I hope we have more with an opportunity to hear from the rest of the speakers gathered.