I agree there is a reason for styles and standards. No one has proposed to eliminate them. To disregard them or make radical changes to the concept. At the same time, there are reasons why the styles say we do not forbid. We intentionally put wiggle room to allow users flexibility to try new things.
If there are no exceptions, and we do not want anyone to be creative or experimenting (as you say). Then we need to remove the word recommendation and say the proper order is indicated below, and any other order is a violation of the rules and standards.
And then we need to modify the styles page to say that if a rule is stated as mandatory or required, the user must follow that rule. There are no exceptions, because this may cause conflict later if team members do not follow the rule. If a rule is stated as a recommendation or best practice, the user may experiment or collaborate with the community.
Otherwise, it will lead to conflict and people leaving the site (see
https://www.gensoftreviews.com/?p=1247). You have your interpretations, and I respect that, but simultaneously you ignore the parts that you don't want to acknowledge that would allow differences you do not like or chose not to do.
Recommendations are not a way to say something is required. I have never encountered anyone, anywhere, who believed a recommendation was mandatory, before. To avoid conflict, we need clear, concise language for everyone.
Is anything I'm saying unreasonable?