Ciaran Hale shares how Deputy moved from fragmented AI experiments to a centralised AI and data foundation on AWS. By standardising infrastructure, introducing governance guardrails, and building reusable components, Deputy enabled teams to scale AI with confidence. This shift also transformed internal adoptionembedding AI into everyday workflowsand unlocked new customer value through Deputy AI, delivering smarter automation and insights in-product. A practical blueprint for building an AI-native organisation.
What this session is about
Playbook
Editorial commentary · what to actually do about this on Monday
The concept
Going from "scattered AI experiments" to "AI-native operating model" requires a centralised platform team, not just decentralised exploration. Standards, governance guardrails, reusable components.
Why it matters
Without standards, every team builds its own broken stack. You end up with five vector DBs, three orchestration frameworks, and zero shared evals.
The hard parts
Platform teams without enforcement get ignored. Platform teams with enforcement become bottlenecks. Both fail.
Playbook moves
(1) Make the golden path so easy that paving your own is the harder option. Reusable components beat policy memos. (2) Embed platform engineers in product teams for the first quarter. (3) Measure platform adoption as the team's KPI.
The surprise
"AI-native" is mistakenly framed as a tech change. It's actually a *procurement* change. Your buying decisions need to weight "agent-friendly APIs" and "structured outputs" as first-class criteria. Half the AI roadblocks come from vendors whose APIs aren't built for this.
---
Independent editorial perspective — not an official AWS or speaker statement. Designed for executives evaluating what to brief their teams on next.
Live updates related to this session LIVE
Sourced via Parallel AI Monitor — continuous web watch on 21 topical streams. Updated .
- cloud.google.com high confidence Agent-native data infrastructure
Introducing Spanner Omni | Google Cloud Blog
Google Cloud announced updates to Firestore designed for agentic development, including native integrations with AI Studio and third-party coding agents (e.g., Claude Code, Cursor, Codex). The update introduces 'Firestore Skills' and a remote MCP service to connect external agent
- mlq.ai Agent-native data infrastructure
Notion launches its first AI agents for data analysis and task ... - MLQ.ai
Matt Shumer announced 'Agent Relay,' a dedicated infrastructure layer for AI agents designed to handle persistent history, real-time events, search, and communication structures including channels, threads, and direct messages.
- cloud.google.com Agent-native data infrastructure
How UKG taps workforce intelligence with the Agentic Data Cloud | Google Cloud Blog
Understanding Data published a detailed blueprint for an 'Event Sourcing for Agents' storage pattern, describing a log-based architecture that stores agent state as an append-only sequence of events to enable deterministic replay, time-travel debugging, and audit trails for produ
- ibm.com high confidence Agent memory & RAG architectures
IBM announcements at Think 2026 to advance the agentic era
IBM introduced 'Real-time context on watsonx.data', which provides AI agents with data that is continuously accessible as it changes. Using a Real-Time Context Engine in partnership with Confluent, the system combines streaming data with semantic enrichment and governance, allowi
- newsroom.ibm.com Agent-native data infrastructure
Think 2026: IBM Delivers the Blueprint for the AI Operating ...
Matt Shumer announced 'Agent Relay,' a dedicated infrastructure layer for AI agents designed to handle persistent history, real-time events, search, and communication structures including channels, threads, and direct messages.
External links matched to this session via topic relevance. The KB does not endorse third-party content; verify before citing.