Model Of Computation Progression: An Intention starts a computation in a Design Chunk.
Computation in a Design Chunk
In Intention Space, a computation triggered by an intention instance (i.e. a particular intention phrase) is captured by a Design Chunk, which consumes a QnA set and the design chunk either produces a question-answer set as a result or continues the computation by emitting an intention phrase from a set of enumerable intentions, aka dictionary in the Intention Space. However, this emitted intention does not reach another design chunk directly, instead, it has to be directed or reflected by an object. This rule brings the decoupling effect of two Design Chunks; their code is never hard bound with each other at execution time.
Computation continues by reflecting an Intention from an Object.
Intentions emitted from a Design chunk, in turn, are reflected by an object instance (i.e. a particular Object phrase) , chosen from an enumerable set of object phrases (aka dictionary of objects) and is subsequently consumed by another Design Chunk. The process continues, as shown in Fig 2. As mentioned, Design Chunk names come from an enumerable set of Design Chunk names, aka Design Chunk dictionary in Intention Space.
The special benefit,from the perspective of software engineering in large are :
The sequence of steps can identify any use case of the system.
A Design Chunk is not forced to implement specific intentions but can achieve desired result by using its intentions in the Intention Space
The intentions from one design chunk can be joined with any other design chunk by joining open intentions and objects chain.
Intention Space Computation Vector: from one Design Chunk to another