E.g., something like the indented table of contents outline for a standard FAQ would be useful. Also, email correspondence could try to follow a standard of having the specific requirement or issue identified in the email subject line, in a standard way, so that people can easily see which requirements and issues are being discussed, find other relevant email, etc. Finally, it is clear that there are distinct differences of opinion among the participants about the answers to questions related to requirements for the SUO and its language. This would allow progress to be made on multiple paths when it is not clear to everyone which is the best path to pursue. Knowledge is limited.
Imagination encircles the world.
On the inevitable intertwining of specification and implementation.