More devs + more implementations is right. Forking to resolve a governance outcome just recreates the same problem in a new body — whoever controls the new fork's roadmap has the same leverage as the one they left. The constraint you actually want isn't in the codebase; it's in the coordination costs that make unilateral changes prohibitively expensive across a fragmented ecosystem.