Hyperion combines product leadership with scoped model engineering and cybersecurity work. A technical mission defines the configuration, adaptation, integration and handover to be delivered; specialist testing and independent qualification are agreed explicitly.
A proposal is not authority to move
01
Observe
Sensors, state and uncertainty
02
Propose
Learned policy with bounded authority
03
Constrain locally
Controller limits and independent protective functions
04
Act and observe
Verify physical outcome before continuing
Control, stopping and recovery require robot-specific qualification. Cybersecurity is a separate assurance scope.
Architecture view
Observe
Propose
Constrain locally
Act and observe
Control, stopping and recovery require robot-specific qualification. Cybersecurity is a separate assurance scope.
Observe → Propose → Constrain locally → Act and observe
A robot that works in a demo is not one you can deploy. From perception to action: select and qualify models, control interfaces and protective functions for the actual robot and operating context. Hyperion leads the product decisions and acceptance criteria. A scoped Mission may include named implementation work by Hyperion. The proposal allocates the remaining engineering, specialist assurance and operating responsibilities.
Separate sensing, learned proposals, control and protective functions. Define each interface, its owner and its qualification evidence. Control, stopping and recovery require robot-specific qualification. Cybersecurity is a separate assurance scope.
ROS 2; vision-language-action policies (π-family, SmolVLA, NVIDIA Isaac GR00T) and VLMs; LeRobot for data, training and evaluation; teleoperation for demonstrations; simulation (Isaac Sim/Lab) and sim-to-real; fine-tuning (LoRA/QLoRA) and closed-loop evaluation; runtime safety monitor, operating envelope and emergency stop.
Separate learned proposals from control and protection
VLMs and VLAs serve distinct roles; the architecture depends on the task and controller. A model proposal needs an authorised interface, defined control limits and robot-specific safety evidence before physical use.
Input
Sensors
Cameras, depth, force-torque, proprioception
Input
Perception
Fusion, SLAM, 6-DoF pose
Learned
VLM
Grounds the goal — "what am I looking at?"
Learned
VLA
Action representations matched to the robot and controller
Configured control
Planner & Control
Trajectory and control budgets qualified on the target
Safety
Safety monitor
Independent protective functions; stopping and recovery tested in context
Output
Actuators
Motion in the physical world
Separate learned proposals from control and protection
Control, stopping and recovery require robot-specific qualification. Cybersecurity is a separate assurance scope.
Closed loop: actuator and environment state feed back to the sensors.
Measure the exact model, runtime, hardware and control integration
VLMs and VLAs serve distinct roles; the architecture depends on the task and controller. A model proposal needs an authorised interface, defined control limits and robot-specific safety evidence before physical use. Control, stopping and recovery require robot-specific qualification. Cybersecurity is a separate assurance scope.
VLM and VLA: different output contracts
Compare the output contract, embodiment fit and integration evidence. Neither model class, by itself, establishes readiness for physical deployment.
Control, stopping and recovery require robot-specific qualification. Cybersecurity is a separate assurance scope.
Dimension
VLM — Vision-Language Model
VLA — Vision-Language-Action
Output
Text / structured language
Robot actions / action chunks
Question it answers
"What am I looking at?"
"What should the joints do now?"
Role
High-level perception, reasoning, grounding
Action representations matched to the robot and controller
Timing validation
Measure the exact model, runtime, hardware and control integration
Measure the exact model, runtime, hardware and control integration
Training evidence
Verify the release: modalities, data rights and task coverage
Verify the release: demonstrations, embodiments and action representation
Failure mode
Hallucinated plan
Incorrect or unsafe action proposals; test limits, refusal and recovery
What we measured
Measured
68.71 GB
π0.5 full fine-tune — peak memory
Measured
1.08 → 0.13 (300 steps)
Real fine-tune (LIBERO, language-conditioned) — loss
Fine-tuned policy: 48/50 episodes (96%). Ten LIBERO-Spatial tasks seen in training, new simulator starting positions, official LeRobot evaluator. One training seed, a separate 1,000-step fine-tune. This is a pilot result on its own; it is not presented as a gain over a baseline.