Every “done” should be backed by actions, supporting evidence and an accountable decision. We are building NEXUS to connect them in one history — from the first action to an accepted outcome.
This diagram explains the principle; it is not connected to Core. Dashed SEE and AI links are development directions.CommandRead state
Act from Companion or World. Core determines the state.
Both interfaces can send commands to Core within participant permissions. Core validates the action and records an allowed change. After refreshing, Companion and World read one authoritative state, with shared rules and history.
Parts of one model
Each component has a role. Expand a row to see how it relates to the rest of the system and what its current boundary is.
CoreState and allowed actionsFoundation
Holds process state and validates participant commands. In P-204, an allowed transition changes the stage; an attempt to edit a protected field is rejected. A recorded decision alone does not establish a physical outcome.
How it works
01
CommandA participant proposes an action
02
ValidationCore checks permissions and rules
03
New stateAn allowed transition enters the history
CompanionThe human workspaceWeb / PWA
Shows processes and available actions. Sends commands to the core and reads the state again. Server workspaces require sign-in; the public examples on this page run locally.
How it works
01
PersonChooses an available action
02
CoreValidates and processes the command
03
InterfaceReads the process state again
WorldThe same process in spaceSpatial / P-204
Represents the process through a spatial client. An action follows Core rules; the next stage is also visible in Web. Minecraft is the spatial client used here, not a required interface for every NEXUS customer.
How it works
01
WorldAn action in the spatial client
02
Shared CoreThe same process permissions and rules
03
CompanionShows state after refresh
SEEObservations from external environmentsIn development
A direction for connecting video and other sources to processes: evidence, provenance, observations and uncertainty. Video analysis research exists separately; its complete operational connection is not demonstrated here.
Concept · not an end-to-end feature yet
01
SourceVideo or other evidence
02
ObservationWhat is visible and what is uncertain
03
ReviewAn observation does not mean acceptance
AIA participant with scoped permissionsIn development
The intended role of AI is to analyze observations, propose actions or perform authorized work. Its output needs validation and state changes go through Core. This page does not demonstrate an autonomous AI executor.
Concept · not an end-to-end feature yet
01
ContextAI receives a task and observations
02
ProposalChooses an action within its permissions
03
Core validationChanges follow the shared rules
LIVEObserve an environment over timeResearch
LIVE explores persistent presence in an environment. Its connection to a shared process and practical value still needs verification.
Concept · not an end-to-end feature yet
01
EnvironmentThe subject of observation
02
TimeA sequence of changes
03
HistoryMaterial for further analysis
LEARNImprove decisions through experiencePlanned
A future direction: use action histories, observations and outcomes to improve decisions. This capability is not implemented yet.
Concept · not an end-to-end feature yet
01
ExperienceAction and outcome histories
02
AnalysisLook for causes of success and failure
03
ImprovementProposals for future decisions
01 / SHARED STATE
Try one transition
Accept a stage in World, refresh Companion and try a protected change. Both views refer to the same P-204 process.
An interactive model in this tab. No commands are sent to Core and no physical equipment is connected.
P
Pump P-204 commissioning
The first commissioning stage
Local simulation
1Action
2Shared state
3Protection
YOUR NEXT STEP
Accept the pressure test
In this scenario, the test has finished. Accept it as a participant in World.
The second example shows an executor report, review criteria and an acceptance decision. It is a separate product prototype. It does not continue P-204 or share an operational session with it.
The goal is to connect work with an observable outcome. A source supplies evidence, a participant or AI forms an observation, an authorized reviewer decides, and the interfaces reflect the consequences.
Today, P-204, acceptance and research directions support separate parts of this model. The next milestone is one reproducible scenario connecting the required parts around a customer workflow.
Applications of the shared approach
Separate applications for commerce, legal work, energy and missions. Their existence does not mean they already share one end-to-end Core process.
01
Online store + WMS
Sport Commerce
An order reserves stock, the warehouse sees movement, and the owner sees the economics.