And that's still too much "asking permission", to me. We're working on increasingly obscure and niche OtherStuff implementations and I don't see why I have to give someone who has nothing to do with our project veto-rights over biomedical vector analysis or CAN bus communications or refrigerant logistics, etc.

We're the experts. That's why we're building the implementation. 🤷‍♀️ 

And it starts lower down. Why do I need to discuss a publishing spec with people who aren't experienced with publishing or internal auditing? If they were experienced in publishing or internal auditing, they would be writing the spec.

What does their approval even mean? Are they checking for typos?