---

Date & time

17:00

When an engineering standard changes, or a new tool is purchased, the pressure is on platform teams to provide an “easy button” that guides developers into compliant pathways. But every shortcut leaks eventually. When only the handful of people who built it can troubleshoot, everyone else is left waiting for a fix. That gap is widening as AI absorbs the routine debugging work that junior and mid-level engineers used to cut their teeth on. How can platform engineers streamline compliance without building a future bottleneck?

This panel walks through how to open your platform up the way an open-source project would: letting developers read it, debug it, and submit a fix instead of filing a ticket and waiting. You’ll leave knowing how to make your code, configs, and documentation readable to outsiders, and how to extend trusted-contributor rights to those who prove themselves.

This panel brings together platform, security, and engineering leaders to explain how to redesign workflows so that AI can’t absorb judgement calls, how to weigh compliance risk against skill development, and which systems are suited to shared ownership between platform and developer teams.

Key takeaways:

• Tell whether an easy button is closing a compliance gap or quietly becoming the next single point of failure
• Design contribution paths that keep developers debugging instead of ticket-waiting
• Extend trusted-contributor rights without handing over the guardrails that keep compliance and security intact