ABOUT OPENRGD

Open infrastructure for cognitive embodiment.

OpenRGD is an open standard and toolchain for representing embodied systems in a machine-readable graph. The project focuses on semantic grounding, provenance, interoperability and explicit authority boundaries between description, cognition and physical execution.

What is OpenRGD? →Governance →Canonical repository ↗

CITATION RECORD

Canonical source ↗Citation guide →

MATURITYPROJECT REFERENCE · PUBLIC IDENTITY

LAST VERIFIED27 Sep 2026

SOURCE VERSIONOpenRGD standard bundle 0.2.0 · canonical governance and repository structure

EVIDENCE BOUNDARYPublic project summary derived from canonical repository documents; this website does not override the specification or governance record.

PROJECT

A standard and reference toolchain, not a robot operating system.

The canonical OpenRGD repository owns the modular specification, accepted and candidate contracts, deterministic compilation, evidence-only importers, static exporters and the governance records around those artifacts.

BOUNDARY

Physical execution remains separately governed.

OpenRGD does not own Body Adapters, hardware orchestration or the canonical physical embodied runtime. A valid profile can provide context to those systems without becoming actuation permission.

OPERATING PRINCIPLES

Make evidence, maturity and responsibility explicit.

Evidence first

Imported facts should remain traceable to their source and unsupported values should remain unknown.

Declared maturity

Candidate, accepted, deprecated and historical material must remain distinguishable.

Human accountability

AI systems may assist with analysis and drafting; human maintainers remain accountable for normative acceptance and releases.

Interoperability

OpenRGD is designed to complement established robot-description and runtime technologies rather than replace all of them.

Non-actuation

Canonical tooling validates, compiles and exports static artifacts without silently taking control of physical hardware.

Public provenance

Important changes are intended to leave reviewable evidence through pull requests, RFCs, decisions, hashes and releases.

CURRENT PROJECT STATE

Different artifacts mature independently.

Standard bundle0.2.0Draft

Python toolchain0.1.1Working alpha

Agent Contracts0.1.0Candidate

Matching version numbers do not imply equivalent maturity. Standard, toolchain and contract releases are governed as separate axes.

STEWARDSHIP

Normative acceptance remains a human responsibility.

Current steward

The canonical governance record names Pasquale Ranieri (@phate6872) as the current project steward.

Contribution model

Changes are expected to enter through reviewable pull requests, with RFCs or decision records when meaning, compatibility, governance or physical boundaries change.

Open source record

Specification, governance, release policy, contribution rules and implementation evidence are published in the canonical GitHub repository.

WEBSITE BOUNDARY

This page explains the project. It does not define the standard.

If website copy and canonical repository material ever differ, the declared repository authority model and maturity state take precedence.

PROJECT TRUST

Read the rules behind the project, not only the project description.

Governance →Security →Contributing ↗