> In theory we should be able to generate a browser from those specs, it just took a massive amount of effort before.

No, not really. The absolute vast majority of those specs are human technical and technical-adjacent language, not machine-readable specs.

On top of that many web specs often invent new terminology because a lot of things are specced years or decades after something popular has taken over the term in userland.

Maybe over time the specs will become more machine readable (bounded and concrete) if we take these paths. Although in some sense everything is machine readable these days, just not deterministically so (less helpful for specs, but not nothing either).

Your second point makes a lot of sense to me too. I’m not sure how this could handle that facet of human nature, except possibly to indirectly contribute to speeding up the cycle of spec creation.