Every successful pattern over time gets cargo culted.

The nuance is hard to communicate in language, and each replication caricatures it more and loses nuance.

A repeated photo copy, losing detail each time.

Bezos's stance is something like "the presence of a cross-functional meeting indicates a failure to make the right APIs".

When you make an API, the nuance / responsibility might drop out if you aren't careful.

It's important to make sure the API captures the nuance and emergence of the system.

If not, you'll get a hollowing out of the system that leaves it incapable of navigating existential problems that the formal system can't understand, let alone address.

This is part of what happened with Boeing; sub-contracting out key components to save money according to the spreadsheets, but meanwhile losing all of the internal antifragility of the system that could evolve, adapt, and grow.