...
Not just the code as part of the team’s external API, but also its documentation, onboarding processes, interactions with other teams, etc.
Conway’s Law
Team structures must match the required software architecture or risk producing unintended designs. Restructuring teams and facilitating (or potentially deliberately limiting) communication between teams have a much better chance of building systems that work well in production and feel natural to evolve over time.
Thinnest Viable Platform (TVP)
This TVP could be just a wiki page if that's all you need for your platform - it says we use this cloud provider and we only use these services from a cloud provider and here's the way we use them. That might just be a wiki page - that might be your platform.
If that's all you need don't build anything else, you're still running on a platform but you don't make it any thicker than necessary, so that's why it's kind of thinnest viable platform. Obviously, as you enterprise gets bigger and bigger or you've got more complicated challenges you'll need to build some stuff out, but the focus is always on stream-align teams as the customer: what's the developer experience, making sure we're using agile software delivery practices within the platform to build it itself.