AuraOne / Docs / Robotics Studio Open / Schema

Capture schema

How a demonstration is represented for review. Sessions, clips, and the rights record behind them.

At a glance

Robotics Studio Open guide

Guide overview
Entry
Capture schema
Reading
8 min
Sections
2
Applies to
Applies to the current Robotics Studio Open source release and its supported JSON or JSONL manifest workflow. Check the product page and repository for the latest setup details.

01

Session, clip, signals, provenance

A session is the recording event. A clip is the reviewed training unit. Signals carry the quality and safety decisions. Provenance keeps the consent receipt and license scope attached.

{
  "session_id": "sess_01J...",
  "task_brief_id": "tb_01J...",
  "device": { "model": "so101", "control_rate_hz": 30 },
  "clips": ["clip_01J..."],
  "consent": { "receipt_id": "consent_01J..." },
  "license": { "scope_id": "lic_01J..." },
  "safety_rules_version": "v4.2"
}

02

Clip object

A clip carries its video, its depth and pose, and its scoring state. Robotics Studio Open inspects local equivalents and exports reviewed manifests.

  • Media references stay path-based unless the user exports a bundle.
  • Consent receipts and license scopes stay attached to reviewed clips.
  • Sensor QA reports stay attached to the clip.
  • Reviewer overrides require rationale.
  • Dataset cards inherit reviewed subset evidence.