Custom action & semantic annotation
Define labels and delivery rules around your model. Choose an automated pipeline, a human labeling team or a hybrid workflow after a sample review.
Custom annotation through automated pipelines, human teams or hybrid review, with quality rules and traceable delivery set to your brief.

Your tasks define the labels, not a fixed template. Agree the schema, ontology, review rules and output format, then select an automated pipeline, human labeling team or hybrid workflow against a representative pilot.
Inventory files, verify formats and identify corrupt frames, incomplete episodes, missing channels and timing issues.
Specify which labels can be generated or checked automatically, which need human judgment and which require both. Test the proposed workflow on customer-approved samples.
Describe objects, locations, goals and outcomes in clear language. Maintain a versioned ontology and representative examples.
Calibrate reviewers against agreed samples. Track disagreements, corrections and exclusions with a customer-defined acceptance rubric.
Map fields, units and coordinate conventions to LeRobot, RLDS or your own loader after a compatibility check.
Deliver stable IDs, manifests, checksums and release notes. Agree access controls, redaction, retention and deletion requirements for the project.
Define labels and delivery rules around your model. Choose an automated pipeline, a human labeling team or a hybrid workflow after a sample review.
Organize, validate and release datasets with reproducible manifests. Make exclusions, missing signals and transformations visible before training.
Map episodes into your training schema, document coordinate conventions and test the loader before committing a full dataset conversion.
Yes. Share your task definitions, ontology, target format and acceptance rules. We can scope an automated pipeline, a human labeling team or a hybrid process; a pilot determines the appropriate mix and review coverage.
Yes, subject to a sample review, supported formats and confirmation of your right to share the recordings for processing.
These are additional scopes requiring appropriate sensor coverage and validation. We do not infer metric 3D quality from ordinary video alone.
No. Format conversion reorganizes available data. Retargeting to a different embodiment requires a separate mapping, feasibility and validation scope.
Choose the unit and thresholds in the pilot: episode validity, segment boundary tolerance, label agreement, missing data and review coverage. The delivery report uses those definitions.