Ive seen many scaling issues so far as well.
However I tend to think that this is a problem with coherence in discipline of the hierarchy. Person A always breaking the build now just becomes Team A breaking the build.
So even still why not simply just use process despite its drawbacks of rigidity since it will still at least solve your problems.
The answer is that just like corruption no finite set of laws will ever be enough to curb an underlying behavior.
This is why things like mandatory code reviews are pointless unless people take them seriously
For small groups there is little difference between firing a person for not following cultural and authoritative norms vs constructing process around those and then firing when those are violated. The written process is merely a concrete representation for what is already known by the nominal parties.
So even still why not simply just use process despite its drawbacks of rigidity since it will still at least solve your problems.
The answer is that just like corruption no finite set of laws will ever be enough to curb an underlying behavior. This is why things like mandatory code reviews are pointless unless people take them seriously