I totally agree, it is a layman's discussion. The idea is to engage more people to think of problems and solution, even these who were not directly in touch with low level technicalities. If i throw a bunch of bayesian probabilities and calculations, it's unlikely for most of people to understand, unless they are from our niche.
On another side, making a full 'by the book' documentation would require a full time job. It's also no strange that even in my full time job, I do expose a draft models to layman's discussions, in order to pass or fail. If a draft model fails such one, then obviously thinking of it further is a waste of time. Sometimes, people who are not educated in niche could shows very high level of 'common logic' (even beyond the educated ones) as we are all sometimes vulnerable to 'thinking the right way'.
As for the understanding, I fully admit I am treating the symptoms, not the diagnosis :)
Fully agree, the first step towards making a model out of draft model is proper documentation and performing a deep theoretical analysis. (that should probably move to more specialized place such as github).
On the other side, if solutions that we have in place shows good enough, this shall only stay as 'to think of' once we encounter another problem.
While it is treating of symptoms, doing it systematically usually eliminate the root cause as well.
And if you ask me, the root cause is using boost libs and other third parity gigs of code that none of us understand. It was time saver at the beginning but it leads to effects such the ones we have. In my opinion, no good system was ever good enough unless it it uses no more then iosocket and stdout. :)
If you ask me, the root cause of forking is single threaded network stack, that increases latency, that leads to possibility for multiple node to generate the same block...and so on (among many other factors that I also don't understand, nor I would be able to without reading gigs of code).