Thanks. I don’t see significant enough benefits here to distract the core team, do you?
I think most engineers who want to assess this would do as well to generate that understanding themselves - a summary only speeds up the early stages of this. I agree a summary would help the see more quickly if the system is vaporware, but we know that’s not going to be the outcome so your idea would be that it might encourage some to dig in and contribute.
Obviously that’s desirable but not more than getting the network to MVP asap. Some will see the progress and may dig in because of that, or for other reasons.
Same with the other benefits really. TLDR: I see benefits but nice to have rather than crucial at this stage unless the team have resources to spare from MVP tasks.
BTW They were doing some work of this kind not that long ago - the Wiki on GitHub - so we know they are aware of it and I expect will do more when the time is right.