Back to Openvino

Architecture

docs/articles_en/physical-ai/explanation/architecture.md

2026.2.11.6 KB
Original Source

Architecture

The Physical AI runtime has a small set of layers with clear boundaries between exported packages, inference, runtime orchestration, and hardware IO.

text
exported package
    -> InferenceModel
    -> PolicyRuntime
    -> Robot and cameras

Components

ComponentResponsibility
Manifestdescribes exported artifacts and the inference pipeline
InferenceModelloads artifacts and computes actions
PolicyRuntimeruns the robot control loop
Executiondecides where inference runs
ActionQueuebuffers and merges action chunks
Robotreads state and sends commands
Camerareads image frames

Package Boundary

physicalai is the runtime package. It should not require training dependencies in order to import or run deployment workflows.

Training packages can add commands through CLI entry points when they need to extend the runtime CLI.

text
physicalai
  infer
  run
  serve

training package
  fit
  validate
  test
  predict
  export

Design Rules

  • Config objects remain passive data structures.
  • Orchestrators are responsible for executing workflows.
  • InferenceModel does not own robot timing.
  • PolicyRuntime does not own policy math.
  • Manifests describe exported packages.
  • Workflow configs describe the desired execution before it starts.