The proposed method by which processing spreads on a quantum network is instantiation, an object orientated design method that allows screen objects to inherit processing from a source class. For example, if many buttons on a screen look and work the same, there is no point repeating the same code for each. It is more efficient to define a general program class that every button calls. The buttons then all look the same because they instantiate the same code. We say they are instances of the same class process and this logic works for any on screen “object” like a drop-down menu or a mouse-over pop-up.
Quantum instantiation works the same way, except that what is instantiated is a dynamic process not static information, so a photon is seen as a spreading cloud of quantum processing instances. Each instance once started begins the “task” of completing a transverse circle at its given rate. The limiting factor is the photon server that divides its processing among the spreading instance. One can think of two people sharing a shovel where in the time one person can dig one hole, two people sharing a shovel can only dig half a hole each and if the shovel is shared among more people, each goes even more slowly. In this analogy, the “shovel” shared by a photon is a server capable of one basic quantum process per quantum cycle.
Although a photon is envisaged as a cloud of instances spreading on the quantum network, the rate of each instance is limited by server capacity. While a physical wave reduces in amplitude as it spreads, a processing wave just slows down because processing distributed runs slower not less. As a quantum wave spreads, its frequency reduces not its amplitude. A quantum wave is a processing wave spreading on the quantum network.