Intention Space -Shared Intentions,Objects and Design Chunks

This article introduces the concept of Intention Space, a modern approach to do modular software development within a design space where Intentions become part of the functioning software as unavoidable  inter component addressing mechanism. The Intention Space framework recognizes a  fundamental role of intention in software development. It aims to provide a structured methodology to capture, analyze, persist, and validate the intentions embedded in code. It exposes a new way to represent understanding of a design and also of  execution time computation progression in a system, typically an 'App'. The article lays out some ways forward that Intention Space can take today's software practices to more socially transparent norms. 
Intention Space is also a software architectural experiment in progress at enterprise software  builders Keybyte Systems Australia to address the issue of missed opportunities of not being able to represent Intent as part of the software code.

Design Chunks: Holds Software Code

In the context of Intention Space, software components are items in specific  "Design Chunks" (DC) - carefully designed and structured units that embody specific intentions. These DCs interact within a field of phrase pairs or question-answers, emitting intentions to objects which reflect intentions to other DCs. Any coded instruction in the systems of Intention Space must reside only in the Design Chunks. Intention Space dont bring any additional syntax or execution framework within a Design Chunk, thus , Design Chunk acts as a scoping mechanism where any traditional piece of software can operate as usual, but can be configured to be  triggering by  certain   Intentions  or emitting certain intentions  at operation time. A Design Chunks can hold a series functions with spcific names that are recognisable within the Design Chunk.

Intentions: Software Component Communication Mechanism Through Human Read-able Statements

The Intention Space unravels intentions as some new kind of communication between codes and objects in people's minds. Intentions are emitted by Design Chunks to coordinate or communicate with another Design Chunk. Design Chunks receives or consumes intention from Objects representing things, real or virtual,in people's mind. Design Chunks can receive intentions reflected by Objects. Intentions can carry a payload , but Intentions exist only by their description . This restriction is necessary to maintain the philosophy that any code in the systems of Intention Space must reside only in the Design Chunks. This way Intentions can be seen as a communication mechanism with other Design Chunks using Objects as intermediaries.

Objects in Intentionspace: Reflector of Intentions Into Design Chunks

Objects give direction to Intentions emitted by Design Chunks, to be received by other Design Chunks. As said , Objects representing things, real or virtual,in people's mind; compared to the traditional approach of putting code inside an object or class, Intention Space puts the code outside of the object but invoke-able through Intentions defined in Intention Space. In intention space, Objects don't have any custom code but can be configured to direct Intentions coming from certain Design Chunks to be reflected to another  Intention reaching another Object or Design Chunk. Objects can also split an Intention into several intentions .Objects participate with Intentions in the communication  and coordination mechansim between Design Chunks by carrying the payload initiated by Intentions.
Intention Space : Design Intention Vs Usage  Intention

Instruction Execution Path Leading to Communication and Service Delivery