I agree with this article.
Proponents of blockchain tech argue its revolutionary quality is its ability to act as a decentralized and trustless database. But I don't ever hear them sort through the issue of how to agree on the schema for this trustless database.
For a group of people to use a decentralized DB, they have to agree as to what to store in it, and how to store it. They need to form consensus about how the system will work, and how the data will flow.
For example I've seen people on here mention applications such as a decentralized stock exchange, and a decentralized hotel rooms marketplace.
For either of these, it's necessary to get all the users of the system in a room and agree what is in scope and what is not, and in general what can be done with the system and how. At this point they already have a consensus, they trust each other, they might as well just set up a centralized database run by a 3rd party that manages the system, keeps it up to date and adds upgrades, instead of building it on the blockchain and hoping there are no major bugs in the cloud code and that it will live off gas.
For the stock exchange, that's exactly what we already have. We have institutions that are dedicated to running exchanges, which act as neutral arbiters. They use regular old centralised databases. When they have bugs in their code or the system makes a mistake they can even roll back trades, which they couldn't do on the blockchain.
Essentially this is the same argument as OP. The 3rd party's act of ironing out issues, deciding what the rules are and how they interact is synonymous with OP's term "governance". We agree that using/running the system is different than defining/implementing the system and the latter can't be done trustlessly.
And also governance gets a lot easier when you also run the system centralized ;)