Architecture

One pipeline.
No bypass.

NEURIX is organised around a single motion pipeline and a strict separation between skills and bodies. Every command, every sensor reading, every decision passes through the same path.

The Stack

A NEURIX deployment is three boundaries: what the skill knows, what the runtime enforces, and what the body requires.

SKILLS portable, versioned, signed ↓ NEURIX RUNTIME safety, leases, dispatch, world model ↓ EMBODIMENT ADAPTER body-specific kinematics, sensors, control ↓ ROS / SDK vendor-native interface to the robot

Layers of the Runtime

Each layer has one job. Layers do not reach around each other.

Identity
Ed25519 keypair, sealed bundle, Control-Plane authoritative. A corrupted identity refuses to start.
Safety Gate
Synchronous, blocking, fail-closed. Every dispatch passes through. If safety cannot answer in time, the command does not run.
Lease
CP-authoritative lease tokens. Guarded skills require an active lease to act.
Artifact Trust
Signed manifests, SHA-256 file hashes, quarantine and recovery. Code that runs on the robot is cryptographically accounted for.
Dispatch
Eleven-step pipeline — emergency, manifest, trust, slot, safety, lease, caps, resources, execute. No step is optional.
Tasks
Nine-state machine, SQLite persistence, approval gate, recovery on restart. The robot remembers what it was doing.
Workflows
DAG execution, conditional routing, pause and resume, failure branches. Complex jobs are composed, not scripted.
Perception
sensor → provider → facts → evaluation → planner → proposal → approval → execution. One canonical cycle.
Concurrency
Four slots, sub-millisecond emergency stop, supervisor. Bounded parallelism is a safety property.
Telemetry
Buffer, retry, deliver to CP. Works offline — spool and drop with back-pressure. Nothing observable is silently lost.

The Dispatch Pipeline

Every motion request traverses eleven steps. The pipeline is the single source of truth for whether a command can run.

  1. Emergencyglobal stop state checked first.
  2. Manifestskill declares inputs, outputs, capabilities.
  3. Trustartifacts verified against signatures and hashes.
  4. Slotconcurrency slot acquired or request waits.
  5. Safetysafety gate evaluates — fail-closed.
  6. Leaseguarded skills require an active lease.
  7. Capsrequired capabilities present on this embodiment.
  8. Resourcesresources reserved or request rejected.
  9. Executethe skill runs under runtime supervision.
  10. Telemetryevents emitted to the Control Plane.
  11. Releaseslot, resources, and lease released on completion or failure.

Contracts

NEURIX is held together by explicit contracts. A skill and a body communicate only through them.

Action contracts describe what a skill demands from a body — reference frames, control authority, saturation limits. Observation contracts describe what the body exposes — sensor channels, facts, rates. Profile bundles pin a specific embodiment to a specific contract set, resolved by the Control Plane.

If the body does not satisfy the contract, the skill does not run. There is no graceful degradation across contracts by default.

The Two Laws

Everything above exists to uphold two invariants.

Law #0
Simulator = reality. No cheating.
Law #1
Never deviate from the NEURIX architecture.

The robot sees only through sensors. What is impossible in reality is impossible in simulation. Every motion — real or simulated — travels the canonical pipeline. Anything that tries to go around is wrong, not clever.

Implementation

Python, FastAPI, asynchronous. MuJoCo for simulation. Unitree G1 as the canonical humanoid. Gemini Robotics-ER for vision-language reasoning. A Control Plane that is the source of truth for identity, profiles, and policy promotion.

Runtime is OS-neutral. Deployments today include a Surface edge node over WSL and a headless VPS instance — both running the same codebase under the same pipeline.

Continue

← Work → Contact contact@neurix.industries