Available now
Use the current local export formats.
Exports are designed to preserve review decisions while staying portable. A team should be able to leave with the subset, the manifest, the data card, and the evidence needed to reproduce the decision.
Reviewed subset
.json
Selected episode and clip references with review state, rationale, and source context.
Large collections
.jsonl
Line-delimited reviewed records for larger episode and clip collections.
Quality reports
.json
Failure-cluster and sensor-QA results linked to the reviewed records.
Evidence archive
.zip
A local archive containing manifests, reports, checksums, and review metadata.
Media
path references
Source video, depth, state, and action files remain local unless the operator explicitly packages them.
Large media
Exports stream; they do not buffer the dataset.
Large datasets remain local. The exporter writes JSONL records, reports, and artifact manifests without loading all source media into memory or moving it to a hosted service.
Artifact manifest
checksum + source
Each artifact carries size, SHA-256, source segment lineage, and consent or license references.
External delivery
operator controlled
Move the exported archive through your approved transfer or object-storage workflow after local review.
Handoff file
Every export explains itself.
The manifest names the reviewed subset, source dataset, review decisions, QA state, consent/license references, recall linkage, payload roles, checksums, and signature metadata.
{
"manifest_id": "mf_01J...",
"created_at": "2026-05-14T21:22:00Z",
"source_dataset": "sim_rollout_policy_b",
"consent_receipts": ["consent_01J..."],
"license_scopes": ["lic_01J..."],
"recall_linkage": "recall_01J...",
"bundle": {
"format": "rlds",
"sha256": "535553111de1...",
"episode_count": 40,
"size_bytes": 9842322224,
"expires_at": "2026-06-18T21:22:00Z"
},
"payloads": [
"robotics_reviewed_subset_manifest",
"robotics_episode_reference",
"robotics_failure_cluster",
"robotics_intervention_note",
"robotics_embodiment_card",
"robotics_consent_receipt",
"robotics_license_scope",
"robotics_data_card",
"robotics_sensor_qa_report"
],
"signature": "ED25519:VLPS..."
}Delivery manifest
Buyer delivery is object-level and recallable.
Delivery manifests list every object sent or linked to the buyer with destination, status, checksum, provider request id, and delivery time. Recall notifications are generated from that object list so an accepted clip can be traced from capture through export and delivery.
AuraOne Programs
The intake export is explicit.
The public app stages a local manifest before handoff. Actual upload requires user consent and configured intake credentials; the public source-linked repo does not hardcode production secrets or silently send private media anywhere.