Talk
Virtual
The AI mandate came from the top. The blast radius lands on you
The mandate to accelerate AI adoption came from the top, but accountability for the outage rests with the platforms. Let’s examine the structural gaps in the control plane and the developer portal, and who really needs to fix them.
CEST
Meet the speakers
AI adoption mandates often come from the CTO, while the governance gap falls to platform engineering. Many organizations have quietly handed platform teams a problem they lack the authority or organizational position to resolve at its source and have labeled it a platform challenge.
This session examines what that structural gap looks like in practice: control planes that cannot distinguish AI-generated drift from deliberate configuration, developer portals whose adoption metrics collapse when AI assistants become faster than governed golden paths, and post-incident reviews where authorship ambiguity replaces clear ownership. Based on actual field data, the session closes on what CTOs and VP Engineering need to change structurally, and what platform leaders can do in the meantime at the execution layer.
Key takeaways:
• Why AI adoption mandates without governance authority create a platform execution trap
• How control planes lose provisioning intent visibility when AI tools operate outside governed templates
• What platform leaders can do at the execution layer while the organizational structure catches up