I've spoken with Jan about this a while back, what I have found is that each cloud layer that appears further down the node tree than the FINAL one, that plugs into the planet, will not move with the planet translation. Only the last layer moves.
The only way I have found around it is to first move the planet then, visiting each cloud layer that feeds it, systematically plug each one directly into the planet node. This resets each cloud's coord's to the position of the planet and then you have all of them in the correct location, you can then link them up again in series.
The problem is, if you move it again, still, only the final layer moves with it. You have to re-plug in each cloud layer to the planet to reset their coord's.
This way, it can be moved anywhere but, it takes a lot more time than it should, when you have to manually reset each layer to the planet coordinates. I've not come across a way yet to pull around multiple cloud layers with a single planet handle. One layer can be moved around fine(which is why Jan's bow has the final layer closest to the planet, apparently, off-centre, when actually, it's all the other layers above it in the network that are out of sync). It's a shame it needs all this replugging at each planet translation but, it can be moved anywhere.
I haven't downloaded the clip but a good primary bow can be made from 4 layers; red/yellow/green/blue with blending cloud altitudes creating the colour transitions(e.g. red mixed with yellow creates the orange band so it isn't necessary, etc...). A secondary bow could take this to 8 nodes, instead of the 14, I think was used in this file.
That's if it can indeed only come down to re-plugging each layer to reset its position, the less nodes to plug in each time, the better. It's a great technique but a clumsy transform control. I'll post back if I find a way to move everything at once, although, I think it's not possible just now.
