Sure, I should make clear: documentation/wikis are best for who/what/when/where of things like

- What permissions do I need to contribute code to this repo

- Where are the telemetry tables for X event

- Who’s the manager for project Y

- When will my commit make it into production

For the whys and hows that often warrant discussion, while I still think you should have basics documented (How do I add a new screen to this app, why do we call into this proxy service, etc) so that folks have a starting place, and then pursue actual discussion.

Even if the wikis are literally just the most basic associations, I still believe that would clear up a ton of repeated and honestly unproductive discussion time.