What to actually do about everything at the Summit, stripped of vendor language. Five cross-cutting themes, 123 per-session strategic notes, and one non-obvious insight per session.
Every per-session entry on this site has the same five blocks, ~150 words each. Designed for executives evaluating where to steer their teams next.
Read these first. If you only have time for the synthesis, this is it. Each theme links to the specific sessions where it surfaces.
Agentic AI is now mainstream enough that the interesting question has shifted from *can it work?* to *can it survive?* Watch for this in: AIM201, DEV313, COP301, DEV205, AIM302, ISV208. The pattern: pilots succeed in 2 weeks, hit reality in month 3. Survival requires evals, observability, cost control, and threat modeling — none of which are glamorous.
Old topic, new stakes. Agents query 10–100× more than dashboards do, against fresher data, with stricter freshness requirements. Watch: ANT301, ARC301, DAT304, PRT110-S, ISV303. The boring truth: chunking strategy beats embedding model. Most teams optimise the wrong axis.
SaaS providers are bolting agents onto existing platforms and discovering tenant isolation in agent state (memory, vectors, tools) is genuinely novel. Watch: ARC305, STP205, AIM204. The trap: tenant-per-index doesn't scale; tenant-aware filtering is the answer most teams resist because it feels less safe.
The framing is shifting from "save money" to "unlock capability." Watch: MAM301, MAM302, MAM303, ISV210. Useful frame for the board: don't sell migration on cost, sell it on what becomes possible after.
Your existing AI risk model was designed for predictive ML (input → score → decision). Agents *plan*, *negotiate*, *act autonomously* — and *fabricate justifications*. Watch: AIM302, AIM303, DEV205, PRT202-S. The under-discussed risk: authorisation confusion (agent inherits user identity but operates with system privileges). It's the new SSRF. ---
Open any of the 123 covered sessions to see the five blocks in full — the concept, why it matters, the hard parts, playbook moves, and the surprise. Each is a short, opinionated brief you can pass to a lieutenant.
This is independent editorial commentary written for executives and engineering leaders. It deliberately omits speaker references and corporate gloss. Where it disagrees with what a presenter says on the day, trust the room — they're seeing the demo. But come back here for sober second thought.