Skip to main content

embodiment-card

embodiment-card validates and renders structured robot embodiment metadata for dataset and vision-language-action release review.

At a Glance

Job Make robot hardware, sensing, action, frame, control, environment, and limitation assumptions reviewable.
Built for Robotics dataset curators, VLA researchers, release reviewers, and documentation owners.
Differentiator Dependency-free schema validation plus Markdown and Hugging Face README rendering.
Produces A validated JSON card or a human-readable embodiment card for release documentation.

Install

python -m pip install "embodiment-card==0.1.2"

Verified Quickstart

Run from a source checkout:

embodiment-card validate examples/mock_so101_card.json

embodiment-card render examples/mock_so101_card.json \
  --hf-readme \
  --out /tmp/SO101-EMBODIMENT.md

The bundled SO-101 fixture validates and renders Hugging Face-compatible YAML tags followed by an embodiment card.

Required Disclosure

The v1 card requires:

  • name and robot morphology;
  • at least one sensor;
  • action-space metadata;
  • at least one coordinate frame;
  • positive control rate;
  • teleoperation method;
  • environment assumptions;
  • safety boundaries and known limitations.

Validation checks required fields and a small set of structural constraints. It does not verify hardware, calibration, units, coordinate transforms, or the truth of a disclosure.

Runtime, Data, and Network Boundary

  • The CLI reads one local JSON file and writes Markdown to a file or stdout.
  • It does not inspect robot media, connect to hardware, contact Hugging Face, or make network requests.
  • --hf-readme formats local text only; it does not create or update a Hub repository.
  • No redaction is applied. Review cards for private paths, operators, sites, or hardware identifiers before sharing them.

Limitations

  • Validation covers required fields and simple structure only. It does not check calibration, coordinate transforms, units, or hardware truth.
  • Rendered cards remain self-reported documentation, not a safety review, hardware certification, or deployment approval.

Compatibility

robostudio-engine exposes a direct robostudio card integration that imports embodiment-card when the package is installed or available in the AuraOne monorepo. The standalone card format can also be embedded in any dataset or model README.

Publication Status

Verified on 2026-07-13:

  • PyPI: embodiment-card==0.1.2
  • GitHub release: v0.1.2
  • Bundled cards describe mock tutorial datasets and do not establish hardware validation or safety assurance.

Next Action

Fill a card from one real dataset's reviewed metadata, have the hardware owner verify frames and control rate, then publish the rendered disclosure beside the dataset.

Release files for embodiment-card 0.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for embodiment-card 0.1.2
File Size Uploaded
embodiment_card-0.1.2.tar.gz 6.8 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for embodiment-card 0.1.2
File Interpreter ABI Platform
embodiment_card-0.1.2-py3-none-any.whl Python 3 none any Details

Total release size: 13.9 kB

Release files / embodiment_card-0.1.2.tar.gz

Download URL embodiment_card-0.1.2.tar.gz
Size 6.8 kB
Tags Source
SHA-256 checksum
How to use checksums
9bcbefac9c3efedb39d76f1e683f68c989f69fe47d8336539764c8dc39e015bb
BLAKE2b-256 checksum
How to use checksums
b13288a0896dae8612f26c736f3051792c61a2595cd5e3e307823ff0c1fb5471
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 13, 2026.

Transparency log

Release files / embodiment_card-0.1.2-py3-none-any.whl

Download URL embodiment_card-0.1.2-py3-none-any.whl
Size 7.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
14fe4169ecb524827c502350b7aa6b2f2f9ce997647ac0e8abcd3878b62b178a
BLAKE2b-256 checksum
How to use checksums
04090592a2884aa73100d80a25405795024d4aad6abb12ea79fc2abe3fe609b4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 13, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.2 This release

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page