Execution Steps and Progression with multiple Vectors.

In Intention Space, a step and progression means the transition from a QnA set to another QnA set, and this is referred to as a  software progression; thus while a single vector can bring the transition from one Design Chunk to another, which may not have a QnA associated, but may emit an intention to carry the progression of computation until it reaches a Design chunk that has an associated QnA. The step in Intention Space will be the sequence of vectors that took from a Design Chunk with an associated QnA to another Design Chunk with its associated QnA. 
Looping and Conditionals in Intention Space can be brought into the Design Chunks through the payload in the Intentions, which may indicate to reflect to the originating Objects where the intentions were reflected from. 
Design Chunks themselves can hold an Intention Space and have several sub-Design Chunks. Thereby creating the necessity to have a registry of Intention Spaces. This article will not get into those aspects with multiple Intention Space,however, work at Keybyte Systems is in progress to bring a frame work called Context Flow which shall address those possibilities.

Illustration of Intention Space computation progress actions.

The computation model of Intention Space is illustrated through the accompanying  NodeJS (JavaScript) code in the file attached, which makes the relation between design chunks and code more explicit. The code implements a demo scenario where a guest wants dinner and is served according to the guest's choice. Notice that Intention Space, compared to the traditional approach ,  promotes an inside-out design of the Objects where Objects only have a name, and all the relevant design details about the behaviour or data structure in the code only come out as intentions reflected by the object into a design chunk. As the system is executed, a flow is created for each execution instance that carries the question -answers in each Design chunk.
Let us imagine a scenario where a customer asks for dinner and gets served the kind of dinner he/she wants. Firstly ,let us capture the primary Object, Intention, and Design chunks to start designing a functional system that caters to this scenario  in a JSON data structure holding the objects ,intentions and design chunks.
: