Menu
GitHub ↗

ARCHITECTURE · RUNTIME

ADOPTED

The canonical repository stops before physical execution.

OpenRGD/openrgd owns the standard, contracts, validation, compilation and static interoperability tooling. Physical execution belongs to an independently governed embodied runtime and hardware-specific Body Adapters.

STATUS BOUNDARY

This separation is adopted repository policy. The canonical rgd toolchain deliberately does not ship a physical embodied runtime or hardware adapter implementation.

CANONICAL SEPARATION

Description and execution have different owners.

01

OpenRGD core

Specification, cross-component contracts, validators, compilers and static import/export tooling.

02

Embodied runtime

Intent ingestion, somatic translation, safety gating, execution, runtime lifecycle and learning mediation.

03

Body adapters

Hardware-specific buses, device IDs, units, middleware messages and actuator behavior.

EXECUTION PATH

A proposal never becomes a motor command by implication.

01CognitionProposal→
02ActionIntent→
03Somatic Translator→
04CapabilityPlan→
05Operation Safety Gate→
06DecisionTrace→
07Body Adapter→
08Hardware

FAIL CLOSED

Historical runtime commands remain visible but blocked.

The canonical CLI can report runtime status, while legacy physical adapter commands are retained only as a compatibility boundary. They fail deterministically instead of importing middleware libraries, opening device connections or issuing actuator commands.

SOURCE MATERIAL

01OpenRGD Runtime Boundary↗02Canonical repository structure↗