yeah, perhaps we should consolidate these into a single 'execution order' discussion, I suspect they will come up frequently, as its going to be the most common 'bug' in advanced patches.
I could do with improving the help pages on this, needs a bit more 'meat' to it....
one other observation...
I think the object/wire metaphor encourages you to think of wires as flowing data, and I consciously have to stop this thinking in Axoloti.
(in Max/pd/Reaktor, due to be being event driven, its closer to reality, though still has its pitfalls)
In Axoloti wires have no influence on the order thing are processed in, Axoloti processes objects one at a time, in the order they are on the canvas.
if you remember this, then this usually makes things pretty obvious, but sometimes I do visually find it 'counter intuitive'
I think, perhaps the numbering scheme might work if it was context sensitive.
i.e. if you highlighted an object, and then it number the execution path from there, this also opens up a really nice metaphor for feedback
e.g. number the chain black on white for the same exec cycle, and white on black for the next execution cycle..... the white on black will often be the 'bugs' in the code