NNEXUSONE STATE · MANY PARTICIPANTS
RUKZEN
NEXUS / FROM ACTION TO ACCEPTANCE

The work is done.What backs it up?

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.

Acceptance example · interactive prototype · no sign-in

NEXUS ARCHITECTURE

Two interfaces.
One source of truth.

Select a component to explore its role.

Authoritative stateNEXUS CorePermissions · rules · history
Exchange model
  1. 01Act in Companion
  2. 02Core validates and records
  3. 03World reads the new state

Both interfaces send commands to Core and read its state. The other interface sees changes after refreshing its data.

This diagram explains the principle; it is not connected to Core. Dashed SEE and AI links are development directions.
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
  1. CommandA participant proposes an action
  2. ValidationCore checks permissions and rules
  3. 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
  1. PersonChooses an available action
  2. CoreValidates and processes the command
  3. 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
  1. WorldAn action in the spatial client
  2. Shared CoreThe same process permissions and rules
  3. 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
  1. SourceVideo or other evidence
  2. ObservationWhat is visible and what is uncertain
  3. 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
  1. ContextAI receives a task and observations
  2. ProposalChooses an action within its permissions
  3. 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
  1. EnvironmentThe subject of observation
  2. TimeA sequence of changes
  3. 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
  1. ExperienceAction and outcome histories
  2. AnalysisLook for causes of success and failure
  3. 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.

Pump P-204 commissioning

The first commissioning stage

Local simulation
  1. 1Action
  2. 2Shared state
  3. 3Protection
YOUR NEXT STEP

Accept the pressure test

In this scenario, the test has finished. Accept it as a participant in World.

Action result

Use the button above to see the result here.

What this checksA command changes the stage only according to core rules.

Runs only in this tab. No connection to Core or equipment.

Try entering data

Try a number or a word. This checks the type, not physical truth.

Saved value: 0

View technical details
Inspectable state
Events in this simulation
  1. No actions yet
Full P-204 walkthrough ↗
02 / OUTCOME AND ACCEPTANCE

A completion report needs a separate decision.

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.

Try outcome acceptance →No sign-in · local demonstration
03 / WORKSPACE

Open Companion

Visit the NEXUS server interface. Access to processes and outcome cases depends on the account and its permissions.

Open Companion ↗Separate interface · sign-in required

Where NEXUS is heading

Action → observation → decision → new state

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.

External application
Open application ↗
02
Cases + assignments + roles

LegalTech

A private legal environment with workflows, deadlines, and access control.

Sign-in required
Go to sign-in ↗
03
Registries + processes + analytics

NEXUS Energy

An anonymized demo shows the path from metric to decision without production access.

Public demo
Open demo ↗
04
Missions + execution + analytics

NEXUS Mission

A goal becomes a governed mission, team actions, and a measurable outcome.

Sign-in required
Go to sign-in ↗

Implementation capabilities

Application modules and a configurator for the first solution. Scope and integrations follow the customer workflow.

Start with one
working process

Select your needs, scale and hosting. The configurator prepares an implementation outline and a personal sandbox for discussion.

1Business type
2Scale
3Deployment
NEXUS Sandbox

Create a working environment

We will save the selected architecture, open a personal workspace, and send the request to the NEXUS owner.

Request and workspace created

Your request is saved in NEXUS and available to the owner. We will contact you to clarify the processes.

Open workspace →