Yep, I think this project needs an SLD: Service Level Design. Which should be documented by the lead engineers and David.
This should be a diagram that shows all components of the safe network with lines and info on how they relate. I have seen similar stuff put out by MaidSafe in the past but some seem incomplete or are now totally out of date with newer methodologies.
Once that is in place, each component of the SLD needs to be broken out and have technical documentation on how each component accomplishes its job within the network. Basically specs that if another coder came along and had no access to anything they could build out a SAFE Network clone from the specs. It would help reveal what has been solved vs still in progress, just put question marks around a portion of needed logic that hasn’t been solved or accounted for yet. The SLD and specs will also be helpful to maintain as solutions are found inadequate, strike throughs can be made appropriately and updated documentation for newer implementations can be put within them to show the progression of design. Ex: I think we thought parsec could be leveraged to validate certain things that it ended up being too slow or inefficient for, and we are switching to CRDT for those.
The SLD and Specs in Github or somewhere would give those in the technical community the ability to raise issues or questions on the design and hopefully lead to good iterations in open dialog on how things could be improved or where components might be flat our wrong or have bad assumptions etc and need revisions.
And the community Primer is not that, that is way too high level and provides 0 insight to how exactly all the cool stuff mentioned in it gets accomplished in code. Making an SLD and quality specs for something as big as this network encompasses could take a full month or two at this point even, but its honestly something that should have been done 6-7 years ago before folks touch code to iterate on and constantly look back to for progress and whats changed(through markdown revisions etc. in Github history).