What about concurrency in such loop architecture?

[0x41gawor]

Execute will get ram decision and execute commands immediately. What about cpu then? Execute should wait for all input tags in this loop iteration before it will send commands.

Actually it's not Execute that has to wait. Execute will receive commands and execute them immediately. The "last" Decide has to gather all its input data and come up with ultimate set of commands.

This conversation converges into the General Conversation about "Data".

[0x41gawor]

Ok, maybe such architecture is non-sense? And it should be done like this:

In this approach all of the decision logic will be placed in a single element, and the actions will operate on data object.

First we will focus on such approach, to develop robust system of Data fields manipulation.

Later we will rethink what to do about multiple input types representing managed-system state.

[0x41gawor]

There is no concurrency. Let's agree on one Decide element and plenty of chain of Actions performed on Data in it.