How robotics demonstrations are represented for review: sessions, clips, pose, trajectory, safety signals, and provenance.
How robotics demonstrations are represented for review: sessions, clips, pose, trajectory, safety signals, and provenance.
A session is the top-level recording event. A clip is the reviewed training unit. Signals carry quality and safety decisions. Provenance keeps task, device, policy, and reviewer context attached.
{
"session_id": "sess_01J...",
"task_brief_id": "tb_01J...",
"device": { "model": "so101", "control_rate_hz": 30 },
"clips": ["clip_01J..."],
"consent": { "safety_rules_version": "v4.2" }
}Clips carry video, depth, pose, trajectory, environment metadata, and scoring state. Robotics Studio Open can inspect local equivalents and export reviewed manifests.
Media references stay path-based unless the user exports a bundle.
Sensor QA reports stay attached to the clip.
Reviewer overrides require rationale.
Dataset cards inherit reviewed subset evidence.
Keep the clip, the cluster, the QA report, and the export manifest together so every training subset can explain itself.