Address Issue of Nodes Disagreeing About Flow Contents on Startup

During startup a coordinator is selected at random to act as the manager of data flow and distributing it to other nodes. This works fine unless that selected coordinator happens to have a uninheritable data flow. When this occurs, the other nodes either are

• Able to connect to Coordinator and then unable to join due to an uninheritable flow exception due to being presented with a bad data flow. In this case, the node shut down.
• Unable to connect to the Coordinator due to lack of quorem and never present with the bad data flow. In this case, the node ran its local flow.