Using a document (it can be as simple as a Google Doc) as an “request for comments” (RFC) can be a good way to garner opinion on something asynchronously. Once a decision has been made, the decision should be codified and the document archived. It can then be used a pointer to context in the future regarding why the decision was made.
A similar approach can be taken to meetings, but with a more synchronous approach whereby meeting pseudo-minutes are taken by someone sharing their screen as the meeting happens. Again, any decisions should be codified. The meeting document should be shared afterwards for full transparency and to ensure there is no ambiguity around the decision that has been made.
The two methods above have similarities toamazon’s process of drawing up a document with various options and a recommendation ahead of meetings.
This approach also has some similarities to pull requests in that a PR also serves as a RFC and can act as a pointer to when the course was changed, possibly with added comment and passive-aggressive dialogue for context.