FWIW, this has long been the policy in Rust. No RFC decisions are made in meetings, and all rationale must be discussed on thread, and given an opportunity for response, before a decisions is reached. The rfcbot tooling also formalizes this, since proposals to reach a decision must be made on thread, and each team member must mark their consent on thread.
a lot of the core discussion happening in synchronous communication
Personally I would like to see if every team or working group post a bi-weekly or maybe monthly announcement of what’s going on
Could you say more about what gives you this impression? Most meetings are "triage" oriented, getting a quick temperature from the team and taking some immediate action items back on the thread. Deeper dives receive detailed writeups on irlo (here's one example).
We've done various newsletters in the past -- and the domain WGs are doing a great job with that currently! -- but for the "core" teams the idea is that TWiR should cover everything that's "going on". So again, I'd love to get more examples/insights into what you feel is missing!