I know this is a minor point of yours, but I think straightforward extensions of existing web technology could solve the problem of communication between Earth and Moon or Mars, at least when interactivity with another human on earth is not required. CDNs already cache a large % of media your browser downloads. The number of round-trips needed is an optimization target in modern web engineering, and e.g. HTTP/2 introduced many new improvements for that. Compute also can move closer to the user; one can imagine AWS opening a new region “mars-1” with most or all of the same services they offer on earth.
The challenge here may actually be achieving the bandwidth needed to proactively push most data on the internet to Mars. High bandwidth (like fiber between major data centers) helps achieve impressive latency on Earth; I have no idea how difficult or expensive it would be to achieve such bandwidth between Earth and Mars.
Live collaboration is of course harder and the solutions to those seem to be more on the product and process side. Long-form writing, Loom video/screen recordings, and general written-first culture is something remote-first companies rely on today.
I enjoyed this post, especially the concept of an error budget which was new to me.
As an implementation detail, these meta-regulations seem to fit into concept of House Rules, a version of which probably exists in most legislative/regulatory bodies. However, AFAIK these are usually set by the body itself, so perhaps the meta-regulation would need to be written into the constitution or charter of the body.