How To Read This Book
This book can be read in more than one direction.
CPUX has a philosophical ground, a runtime architecture, a UI contract, and a developer practice. A reader does not need to absorb all of them at once.
The best path depends on what kind of question brought you here.
If You Are New To CPUX
Begin with the human ground.
Read first:
- human analytic mind
- situational reality
- perception before intention
- Stabilising Intelligence
This path explains why CPUX exists before explaining how it runs.
The central idea is simple:
software should not erase the human perceptual loop that gives action its meaning.
Once that is clear, the technical vocabulary becomes easier to understand.
If You Are A Developer
Begin with the smallest practical unit:
Pulse -> Signal -> Design Node -> reflected Signal
Then move outward:
- Intention Container
- O_holder and O_reflector
- Field
- Visitor
- GridLookout Cell
- direct result path
- subscription path
The important point is that CPUX does not ask every developer to abandon ordinary programming. A Design Node can still be written in familiar code. What changes is the way that code is placed inside an explicit field of intention and perception.
If You Build User Interfaces
Begin with GridLookout.
GridLookout treats the UI as a native perceptual surface. A Cell is not just a widget. It is a place where a Pulse becomes visible, where human action becomes a Signal, and where an IC result can return directly to the originating human-facing component.
The current demonstrations begin with ReactJS and Android. The same contract is meant to mature across other rendering platforms such as iOS, Flutter, desktop UI systems, and embedded screens.
The UI question becomes:
What perception is this surface reflecting?
not only:
What event handler should this component call?
If You Work With AI
Begin with Stabilising Intelligence.
Modern AI systems expose the importance of context, memory, continuation, and coherent response under perturbation. CPUX approaches this from the application side: it asks how human intention, machine reasoning, and software execution can occupy a shared field where Signals remain explicit.
In this frame, an AI model can be treated as a Design Node.
It can absorb a Signal, reason over its Pulses, and emit a reflected Signal. The surrounding CPUX structure keeps that participation visible, bounded, and auditable.
If You Are Reading For Research
Follow the concepts in this order:
situational reality
-> closed perceptual algebra
-> Pulse
-> Signal
-> Intention
-> CPUX Field
-> Stabilising Intelligence
This path keeps the philosophical argument close to the computational one.
The book's research claim is not that CPUX solves intelligence. The claim is more careful:
CPUX gives software a way to represent the situational structures through which human and machine intelligence can coordinate.
A Practical Reading Rule
Whenever a chapter feels abstract, ask:
What would this become as a Pulse, a Signal, a Cell, or a Design Node?
Whenever an example feels technical, ask:
What human perception or intention is this preserving?
The living book belongs in the movement between those two questions.