AuraOne / Docs / Robotics Studio Open / Schema
Manifest schema
The episode fields a Robotics Studio Open manifest declares: task, duration, frame rate, embodiment, outcome, review state, sensors and interventions.
At a glance
Robotics Studio Open guide
- Entry
- Manifest 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
An episode is one task attempt. The studio reads the fields your manifest declares: task, duration, frame rate, embodiment, outcome, review state, sensors, phases, and interventions. Fields you leave out stay unknown.
Consent, license, and reviewer identity are not part of the studio record in this release. Keep them in your own capture system.
{
"id": "ep_0001",
"task": "pick_apple",
"duration_s": 12.5,
"frame_rate_hz": 30,
"embodiment": "SO-101",
"success": "failure",
"reviewed": "reviewed",
"failure_cluster": "gripper-slip"
}02
Clip object
An episode can declare its sensor streams, phases, interventions, and anomalies. Robotics Studio Open inspects them and exports a reviewed manifest.
- Raw media is never read or copied; the archive holds metadata only.
- Review state is reviewed, unreviewed, or unknown.
- Sensor QA reports cover the exported episodes.
- The embodiment card summarizes the exported episodes.