TODO: prepare as independent package.
(for now it's only unprepared for use fragment of Stitie Processor Model technology's hidden branch).
Click to download.
We could use 'raw' strategies to move state and strategy, but we prefer to abstract such operations.
It's easier to think in abstract terms like this:
* move state/strategy from coords (x1, x2, x3) by (n1, n2, n3),
* then execute reporting strategy at destination node.
* then execute key re-generation strategy at destination node.
* then initiate new 4 maneuvers from this node, for example sending public keys to appropriate nodes.
* and so on....
of course maneuvers open more possibilities than just movement, as any strategy can be implemented as maneuver or it's part. this lets us to think using common simple words, instead of talking constantly in obscure machine-like language. that is, we get to think in terms of 'maneuvers' performed in space, instead of pieces of code to execute at one-dimensional address and registers.
we can think strategically instead of thinking like programmers.
it's faster, less code and errors once we get used to this.
maneuvers are easy to understand when named properly and used in collections / iterations, and we get to reap benefits of higher-level languages, being able to react faster to world's changes, because programmer's time is precious commodity.
'Cascade' can be used this way too: by initiating a maneuver(s) at destination node that send state(s) and/or strategy(-ies), as part of maneuver, complex or not. This also can happen many times. Let's remember that maneuvers are realized as strategies.
Maneuvers enable functionality similar to MATEN mnemonic's and more.
Once they are ready, can be used with Stitie Machine Sunsail in any application using this (computational) engine.