Coding is a 'Design with Intent'. Let's treat it that way.

There is no doubt in anybody's mind today that AI (Artificial Intelligence) is rising. The possibilities and trepidation are enormous. There are some missing pieces in this puzzle of perceived AI domination; how can human beings with the brilliance and mind-powers of engineers and extraordinary visionaries end up creating so much mistrust, doubt, and possible harm to a society where we face an existential crisis? What are these missing pieces? How the future of Social Computing look like?
Whenever someone writes any software code related to any social activity or a social gadget like a smartphone today, they are inherently engaged in some form of design. Even if the code has been copied and pasted from elsewhere, it carries a built-in intention and specific actions, much like a designed artifact such as a knife or spoon.

Traditionally Intents Are Not Represented In Code or Design.

In the traditional programming model of ' input-process-output ', intentions stay in the coder's mind; it is absent in the code, which means the software code is devoid of intent. As it remains outside of general attention, the significance and implications of intention in software development still need to be considered and accounted for, especially when the software becomes a designed tool in society.
The absence of explicit intent in design, in general, and code in particular, is primarily due to the lack of any formal approach that can expose, analyze and persist intentions, let alone provide a mechanism to ensure that such intentions align seamlessly within a target scenario. Although in the realm of artifact design in society, the ambiguity of intent is taken as an acceptable or even unavoidable part of the design, we shall see that having a software methodology where intent can be explicitly shared brings an unprecedented advantage in knowledge sharing, education and a reliable and safe social computing network.  

Intention Space -Shared Intentions, Objects and Design Chunks

This article introduces the concept of Intention Space, a modern approach to modular software development. It allows its operation within a design space where Intentions become part of the functioning software as an unavoidable inter-component addressing mechanism. The Intention Space framework recognizes the 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 the understanding of a design and execution time computation progression in a system, typically an 'App'. The article outlines ways 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 missed opportunities of being unable to represent Intent as part of the software code.

Design Chunks: Holds Software Code & Proprietary Content

In the context of Intention Space, software components are items in specific  "Design Chunks" (DC) - carefully designed and structured units that embody particular Intentions. These DCs interact within a field of phrase pairs or question-answers (QnA Domain), 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 doesn't 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 triggered by particular Intentions or emitting specific intentions at operation time. A Design Chunk can hold a series of functions with particular names recognizable within the Design Chunk. The Design Chunk in Intention Space concept exhibits a versatile scalability that accommodates both macro and micro levels of software code representation. It can encompass the entirety of an App, encapsulating complex functionalities and interactions while facilitating the containment of specific and granular logic, such as the control of a few transistors.

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. Design Chunks emit Intentions 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 or design thought that any code in the systems of Intention Space must reside only in the Design Chunks. Intentions can be seen as a communication mechanism with other Design Chunks using Objects as intermediaries which can carry payloads.

Objects in Intention Space: Reflector of Intentions Into Design Chunks

Objects give direction to Intentions emitted by Design Chunks, to be received by other Design Chunks. Objects represent things, real or virtual, in people's minds; compared to the traditional approach of putting code inside an object or class, Intention Space puts the code outside of the object but is invokable through Intentions defined in Intention Space. In intention space, Objects , conceptually, don't contain the software code but can be configured to direct Intentions coming from certain Design Chunks to be reflected into 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 mechanism between Design Chunks by carrying the payload initiated by Intentions.

Instruction Execution Path Leading through intentions and Objects (CPUX)