While getting it in writing is good, it doesn't actually protect you. Vast majority of people are working at-will. Which means either party can change the terms of employment whenever. And if the other party disagrees then employment is terminated.
In this case meaning, if your contract says remote then they can change it to not remote at any time. That said, any company that will pull shenanigans like that you don't want to be working for anyhow as they don't respect you and that will impact you across all aspects of your work.
Fact checking is just censorship. It's literally a group that gets to decide what is an acceptable view and what isn't. How is that not just plain censorship?
You can certainly argue that censorship isn't always a bad thing. But calling censorship "fact checking" is purposely misleading.
Generally speaking, use the standard until you can't. Then just extend it and write up a proposal for your extension to make it into the next version of the official protocol.
I have no idea how Slack threads are intended to be used. Their own examples are very trivial and the implementation feels like like a first pass that they never did any usability testing with.
Things like upgrading the language version should not require coordination between multiple dev teams.
Of course there's 100s of permutations that work. Optimize for your situation. And if you have no clue what the right call is, go as simple as possible until it breaks on you.
I think we need to find a better way for the philosophy behind the scientific method to click.
The entire idea of a "fact" is flawed. We simply have more good evidence for some things than others. Teaching people to critically evaluate and compare the evidence is the trick.
Perhaps studying different perspectives of a politically neutral historic event would help people to understand.