We've cracked the build. Anyone can stand up an impressive single-team agent demo. The run, the ownership, the adoption — that's where it's stalling, and good work is starting to fall by the wayside.

Solving for one business unit is a POC. A real organisation needs a governed, operational platform that lets many BUs run agents without each one reinventing identity, guardrails, ownership and rollback. Deployed and healthy is not the same as live and good.

Drawing on systems I run in production, this talk maps the run-phase operating model: the self-optimising flywheel we had to cage, the adversarial gate that reviews agent work before it ships, and human-in-the-loop approval as a first-class control.
Much of this maps directly onto native primitives in tools like Google Antigravity, so you build the governance, not the plumbing.

The one thing no IDE can decide for you: what counts as evidence in your domain.

Takeaways:
1. Build is solved; Run isn't. A single-BU demo doesn't survive contact with a multi-BU org. The gap is the operating model.
2. Cage the flywheel. Unsupervised self-optimisation quietly automates curve-fitting; supervised, gated, default-OFF is the honest posture.
3. Antigravity-native HITL gates, ask-by-default permissions, hooks and budget monitors give you the controls for free. You supply the domain evidence.

Duration: 30 min (25 + 5 Q&A). Audience: platform leads, architects, engineering leadership. Deck built; scheduled for delivery at SREday London Q3 (Sep 2026). Part 3 of the Build / Secure / Scale signature set.