This could be a really interesting experiment in Open Source Architecture. The design is currently.... complicated. I wonder what kind of process we could use t

This could be a really interesting experiment in Open Source Architecture. The design is currently.... complicated. I wonder what kind of process we could use to unpack and map out the entire architecture, such that average contributors could make "PRs" about changes to the architecture, in order to slowly simplify and improve the architecture over time. I am imagining a process that involves programmatic architectural diagrams, graphs, estimates of resources, DAGs, documentation, links to source code, etc. Almost like a sub-project, where the architecture itself becomes a project. The end result of that project could tell you rough estimates of cost, performance, complexity, and let you visualize changes. And of course it would become the "map" by which you discover pieces of the system, the place all new devs start to learn about the system or find documentation. (I am not saying the author's system needs to change, I'm just speculating about how to organize a collaborative effort, if change was wanted)