Software executes what was decided earlier. Decision-Zone computes what is required now.
Powered by Triadic Causal Programming, Decision-Zone independently computes what a human-defined mission requires, what available Actors can accomplish, and what actions are admissible under human-defined authority and current causal reality.
Any intelligence. Any actors. One governed reality.
Safe, Continuous Autonomous Control of Digital and Physical Systems.
Runtime Computing makes the continuing mission computational. Through independent Requester, Actors and Governor computations, Decision-Zone determines what is required, what is possible and what is admissible in current causal reality.
Only admitted actions cross the Commit Boundary. Observed consequences return to the same mission, enabling continuous adaptation and mission continuity while supporting safety and security within human-defined authority, invariants and constraints—even as AI agents, autonomous systems and cyber threats evolve.
Human-defined intent and authority. Machine-computed requirements, possibilities and admissibility. Governed execution in digital and physical systems.
From Intelligent Actors to Autonomous Missions
Software made the Actor computational.AI made the Actor intelligent.Agentic AI is extending the Actor’s autonomy.
But an autonomous Actor is not an autonomous mission.
Triadic Causal Programming extends computation beyond the Actor to the mission’s independent Requester and Governor—keeping human-defined intent and authority computationally present as machines act and reality changes.
Persistent Requester
Computes what the mission requires now and what effect remains required.
Independent Actors
Compute identified possible realizations.
Independent Governor
Computes which specific proposals are admissible under human-defined authority and current causal reality.
The Human Mission Owner defines purpose, authority and boundaries. The Requester and Governor are not Actors.
Only admitted actions cross the Commit Boundary. A bound capability executes the admitted action. Observed consequences return through the live causal Event Fabric to the same persistent mission, which computes what remains required.
One persistent mission. One governed reality.
THE ARCHITECTURAL DISTINCTION
RUNTIME EXECUTION vs RUNTIME COMPUTING
EXISTING TECHNOLOGY
RUNTIME EXECUTION
PRESCRIPT
Executes what was decided earlier.
Software, AI models and agentic Actors execute or generate behavior using previously established programs, models, objectives and operating structures.
Human operational computationRequirement & admissibility
Software · AI · agentic ActorsExecute / generate behavior
Changed conditions return to the human
HUMAN INSIDE THE MACHINE LOOP
Humans continue to supply mission-level requirement and admissibility computations when conditions change.
DECISION-ZONE
RUNTIME COMPUTING
TRIADIC CAUSAL PROGRAMMING
Computes what is required, possible and admissible now.
Three independent runtime computations operate against live causal reality.
Persistent RequesterWhat is required now?
Independent ActorsWhat is possible now?
Independent GovernorWhat is admissible now?
LIVE CAUSAL EVENT FABRIC · CURRENT CAUSAL STATE
COMMIT BOUNDARYOnly admitted actions execute
Observed consequence → same continuing mission
MACHINE INSIDE THE HUMAN-DEFINED MISSION
Only admitted actions cross the Commit Boundary. Observed consequences return to the same continuing mission.
Why Software and AI Have Execution, Not Runtime Computation
Conventional software executes decisions established earlier. Humans have historically supplied the continuing computation of mission requirements and admissibility as reality changes.
This paper explains that missing runtime computation and presents Decision-Zone’s implemented architecture: Triadic Causal Programming, independent Requester, Actor and Governor computations, Rapide runtime engines, live causal Event Fabric, Commit Boundary and consequence return.
Original publication. All 14 pages and diagrams preserved without alteration.
HUMAN AUTHORITY · MISSION AUTONOMY
HUMAN CENTRICITY
From a human inside the machine’s loop to the machine inside the human’s mission.
THE TWO HUMAN LAYERS TODAY
Programming the system. Computing its operation.
Conventional systems depend on two layers of human work: programming behavior in advance, and continuing operational computation when reality changes. Operators observe, decide, intervene and recover where prescribed behavior cannot determine what the mission now requires.
Human involvement in that operational loop is not the same as human authority over it.
THE HUMAN DEFINES THE MISSION
Purpose and authority remain human.
The Human Mission Owner declares the mission’s required effect, authority, invariants and constraints. Frontier models support design-time compilation into an executable Triadic Causal Programming package.
At runtime, machines independently compute what the mission requires, what is possible and what is admissible against live causal reality. The person remains the source of what the system is for and the authority under which it may act.
We are not automating people out. We are taking them out of the loop and putting them in charge of it.
