Edit: sorry, re-reading your coup plot I see you wanted the owners of {A..M}.ROOT-SERVERS.NET to collude in direct action. It’s not an implausible idea at all, if the worst comes to the worst, even if it’s quite extreme. My original comment misses your point a bit...
...
If you want to fix this by direct action on the root servers, rather than ORG’s nameservers, the it doesn’t matter who owns the current root servers.
Their config is baked into your resolver’s installation files or source code, and my naive understanding is that it takes only one patch to change each one:
...though the changes would be fragmented until the patch had been rolled out to 100% of resolver codebases and all instances of each resolver updated and restarted. Not an easy solution without coordinating people as well as software.
It takes two to tango. Once you get majority support then the holdouts are the ones forking the TLD, and since forks are not in anybody's interest a consensus would be reached.
...
If you want to fix this by direct action on the root servers, rather than ORG’s nameservers, the it doesn’t matter who owns the current root servers.
Their config is baked into your resolver’s installation files or source code, and my naive understanding is that it takes only one patch to change each one:
https://gitlab.isc.org/isc-projects/bind9/blob/master/lib/dn...
...though the changes would be fragmented until the patch had been rolled out to 100% of resolver codebases and all instances of each resolver updated and restarted. Not an easy solution without coordinating people as well as software.