Technical specification of Intention Space

Design Chunks in Intention Space embodies any computation large or small. In Intention space a Design Chunk is a small content in any form that makes sense to the human user. In the coding world a single function or a collection of functions can be a design chunk. The domain of operation of Design Chunks are however, not just numbers and strings ,but they are question answer pairs that make sense to a human. 
Intention Space takes computation as an act of taking a set of  of question answer pairs and producing another set of question answer pairs ,instead of traditional notion that a  computation step has an input, generating an  output,a Design Chunk acts on a set of question -answer pairs and passes question -answer pairs to another Design Chunk as computation proceeds. The 'function  parameters',a foundational element in traditional  definitions of functions in computation, is looked upon as a question answer pair received or generated by the Design Chunks ;e.g instead of just declaring a parameter variable called 'apple' and assign a value say $5 as the price of apple  e.g var apple = 5, Intention space equivalent will be  question answer pair, represented as a JSON object : {'what is price of apple':'$5' } . Any operation in Intention Space is looked upon as operating over a set of JSON question answers, a Design Chunk passes question -answer pairs to another Design Chunk through some rules of operation in Intention Space as computation proceeds.
The rules of operation of Intention Space is built through two more operators along with the Design Chunks ; these two are Object Phrases and Intention Phrases. Each Design Chunks has a name ,we can refer to it as a  Design Chunk Phrase. Intention Space maintains three dictionaries of phrases corresponding to each category of phrase in Intention Space as defined below.

Categories Of Phrases in Intention Space

i. Design Chunk Phrases(dp)
ii. Intention Phrases (ip)
iii. Object Phrases (op)
Intention Space holds three dictionaries ,each corresponding to one of the phrase categories above. The  Intention Space is built as vectors of triples of phrases  [op, , ip , dp] with the restriction that there is no more than one occurrence of certain op-ip  pair. joining to any  dp in the whole of Intention Space, this in turn also disallows multiple occurrences of the same triplet. This also accommodates the concept of reversing an operation in a design chunk that is associated through a particular object and intention,i.e if the design chunk emits the same intent it received from an object back to the same object then what ever changes in the design chunk  has initiated will be nullified.
The word vector implies certain direction. In Intention Space this direction is the progression of computation,by producing the resulting question-answer sets from a starting question-answer set in the model of computation described below. If we could draw these in the three dimensional space of object,intention,design chunk ,possibly we shall end up with weird looking snake like convolutions.

Model Of Computation in Intention Space

In Intention Space a computation is  firstly triggered by an intention received by a Design Chunk,is  seen as a consumption of question-answer set by a design chunk ,which either produces a question-answer as a result or  continue the computation by emitting an intention phrase from a set of enumerable intentions ,aka  dictionary,  which is reflected by an object phrase chosen from an enumerable set  of object phrases and is subsequently consumed by another Design Chunk , and the process continues as shown in Fig 1. As mentioned , Design Chunk names also come from an enumerable set of Design Chunk names, aka Design Chunk dictionary.
I shall illustrate the computation model through some NodeJS (Javascript) code implemented to demo a scenario where a guest wants a dinner and is served according to his choice. You shall notice that Intention Space promotes an inside out design of the Objects where Objects only have a name ,all the relevant design details about the behavior or data structure of the object  only comes out as intentions reflected by or received by an object. 
Lets imagine a scenario where a customer is  asking for a Dinner to be served and gets served by the kind of dinner he/she wants. Lets capture the basic Object ,Intention and Design Chunk for starting to design a system that caters for this scenario.
We first recognize that the intention that triggers the system ,hence a minimum  functional design chunk we call 'Requesting dinner for guest FC'.  This design chunk is fed with a question-answer { question: "what is your name", answer: "Simon" },{ question: "do you have veg or non veg", answer: "non veg" }. The design chunk 'Requesting dinner for guest FC' in turn reflects the intention 'I want dinner' to the object 'Dining Space' . The object 'Dining Space' in turn reflects  Schedule a dinner plate, which is received by the unique Design Chunk ' '
{
objects: [
{ name: "Dining Space", reflectors: [{ receives: "I want dinner", reflects: "Schedule a dinner plate" }] ,reflects: [{ intention: "Schedule a dinner plate", Object: 'Dining Space' }},
{ name: "Weekly schedule", reflectors: [{ receives: "Schedule a dinner plate", reflects: "Prepare a dinner plate" }] },
{ name: "Dinner Plate", reflectors: [{ receives: "Prepare a dinner plate", reflects: "Presenting a dinner plate" }] },
],
intentions: [
{ name: "I want dinner", QnA: [] },
{ name: "Schedule a dinner plate", QnA: [] },
{ name: "Prepare a dinner plate", QnA: [] },
{ name: "Presenting a dinner plate", QnA: [] },
],
fcs: [
{ name: "Requesting dinner for guest FC", emits: [{ intention: "I want dinner", Object: 'Dining Space' }], receives: null ,QnA:
[{ question: "what is your name", answer: "Simon" },{ question: "do you have veg or non veg", answer: "non veg" }],},
{ name: "Requesting a drink guest FC", emits: [{ intention: "I want a drink", Object: 'Dining Space' }], receives: null },
{ name: "Scheduling a dinner plate FC", emits: [{ intention: "Schedule a dinner plate", Object: 'Weekly schedule' }], receives: [{ intention: "Schedule a dinner plate", Object: 'Dining Space' }],invoke:'generateRandomDish' },  .. same intention different dc's
{ name: "Preparing a dinner plate FC", emits: [{ intention: "Prepare a dinner plate", Object: 'Dinner Plate' }], receives: [{ intention: "Prepare a dinner plate", Object: 'Weekly schedule' }] },
{ name: "Presenting a dinner plate FC", emits: null, receives: [{ intention: "Presenting a dinner plate", Object: 'Dinner Plate' }] },
],
}
Repeating Patterns in Computing , Breaking the Complexity of Design through What and Why.
Patterns has been the fore-runer of computing. Computing exist because patterns exist. But at the same time pattern throws a challenge of complexity in the name of re-usability. The fact that a Design Chunk can be used in multiple circumstances can mean we shall loose the thought process and design decesions that lead the designer to the design-chunk  in the first place. 
Intention Space tackles this hard problem of managing reusability , modularity and context maintenance over time by bringing the other two  dimension phrases, the object phrases and the intention phrases while also persisting the the sequence of  the  trio as the computation progreses(the context of the actual usage of the design chunk at execution time) .
The rationality of bringing the object phrases and intention phrases as coordinates of Design Chunk occurrence in a design space comes from the observation that we ,as humans have the tendency of being driven by a visceral perception of things around us mentaly, virtually or in reality  - expressed as 'What'  or the Object phrase ,which triggers a motivational question of 'Why' or the Intention Phrase , which in turn , is followed up with more reflective analysis of the situation,leading to  ,the 'How' of  of a design around that object of 'What' ,which the Design Chunk holds together. So in effect Intention Space makes room for multiple objects ('Whats') with different intentions can point to the same design chunk ,but by imposing the rule that a pair of object and intention always point to a single how i.e a single design chunk ,which also implies there can be only one occurrence of a particular trio in Intention Space.

Computing with phrases  :Limited Phrases with ever growing computing reach

..Context Algebra
An algebraic space typically refers to a mathematical structure where operations and relationships among elements are defined and adhere to certain properties. In the context of your model, we can identify the following elements: