Chapter 3: The Data Flywheel: Humans, Robots, Simulation, and Failure Logs

Overview

A manipulation flywheel is an operating loop in which humans demonstrate, robots repeat, simulation perturbs, and QA labels the failures. This chapter rewrites the problem as a factory-cell data contract. The promise of large robot datasets in ^[1] and ^[2] matters, but in manufacturing an episode becomes valuable only when it is attached to inspection and process outcomes.

A factory data contract is wider than a demo file. It binds who demonstrated, which hand was used, where the fixture slipped, which defect code the inspector emitted, and which replay set blocks the next model release. The data is therefore not just a camera stream. It includes hand choice, force-torque, tactile patches, controller mode, operator intervention, and inspection result. ^[3] and ^[4] show why human-to-robot transfer loses critical signals unless the capture interface is designed around embodiment and contact.

After reading this chapter... - Explain factory manipulation as a data contract rather than a model score. - Separate two-finger, suction, custom, and five-finger choices by collection cost and failure observability. - Read papers, company releases, and deployment claims through evidence tiers. - Design the replay set and QA trace required for a first manufacturing PoC.

Core Map

Visual Argument

Figure 3.1. Factory data flywheel. Source: reused local survey asset or author-created illustration.

Figure 3.2. Factory data contract schema. Source: reused local survey asset or author-created illustration.

Figure 3.3. UMI-FT adds force observability to in-the-wild demonstrations. Source: reused local survey asset or author-created illustration.

Demonstrations Are Only the Start

The practical meaning of demonstrations are only the start is that process variables must be left in a learnable form. ^[1] shows how scale can broaden embodiment and task families, yet a factory cell is narrower and stricter. A pick that looks identical to a person can become a different distribution when fixture tolerance, surface contamination, cycle pressure, or reject code changes.

In the concrete scenario, A factory data contract is wider than a demo file. It binds who demonstrated, which hand was used, where the fixture slipped, which defect code the inspector emitted, and which replay set blocks the next model release. Human demonstrations alone are not enough. Even when an interface such as ^[2] makes collection easier, a policy will repeat the same release failure if contact force and failure cause are absent. The episode schema must bind observation, action, contact state, QA outcome, and operator note under one key.

The evidence tier matters. A source such as ^[3] gives a method and benchmark that can be inspected. A company source can reveal deployment direction, but usually exposes less about data rights, recovery handling, and operating metrics. Manufacturers should place both in the same comparison table but never read them with the same confidence.

From a control perspective, the learned policy should not be the whole system. Force limits, guarded motion, fixture state, collision zones, and rollback conditions have to sit around the model. Without that boundary, collecting more data can create more safety stops and more rework instead of a more deployable robot.

From an operating perspective, the reproducibility of failure matters more than a headline success rate. A failure has to enter a replay set, the next update has to pass that replay set, and the deployed cell has to show a lower rate for the same failure code. The question is not only how to describe demonstrations are only the start, but which missing log would make the claim collapse on a line.

What Robot-Native Rollouts Add

The practical meaning of what robot-native rollouts add is that process variables must be left in a learnable form. ^[4] shows how scale can broaden embodiment and task families, yet a factory cell is narrower and stricter. A pick that looks identical to a person can become a different distribution when fixture tolerance, surface contamination, cycle pressure, or reject code changes.

In the concrete scenario, A factory data contract is wider than a demo file. It binds who demonstrated, which hand was used, where the fixture slipped, which defect code the inspector emitted, and which replay set blocks the next model release. Human demonstrations alone are not enough. Even when an interface such as ^[5] makes collection easier, a policy will repeat the same release failure if contact force and failure cause are absent. The episode schema must bind observation, action, contact state, QA outcome, and operator note under one key.

The evidence tier matters. A source such as ^[6] gives a method and benchmark that can be inspected. A company source can reveal deployment direction, but usually exposes less about data rights, recovery handling, and operating metrics. Manufacturers should place both in the same comparison table but never read them with the same confidence.

From a control perspective, the learned policy should not be the whole system. Force limits, guarded motion, fixture state, collision zones, and rollback conditions have to sit around the model. Without that boundary, collecting more data can create more safety stops and more rework instead of a more deployable robot.

From an operating perspective, the reproducibility of failure matters more than a headline success rate. A failure has to enter a replay set, the next update has to pass that replay set, and the deployed cell has to show a lower rate for the same failure code. The question is not only how to describe what robot-native rollouts add, but which missing log would make the claim collapse on a line.

Simulation as Distribution Perturbation

The practical meaning of simulation as distribution perturbation is that process variables must be left in a learnable form. ^[7] shows how scale can broaden embodiment and task families, yet a factory cell is narrower and stricter. A pick that looks identical to a person can become a different distribution when fixture tolerance, surface contamination, cycle pressure, or reject code changes.

In the concrete scenario, A factory data contract is wider than a demo file. It binds who demonstrated, which hand was used, where the fixture slipped, which defect code the inspector emitted, and which replay set blocks the next model release. Human demonstrations alone are not enough. Even when an interface such as ^[8] makes collection easier, a policy will repeat the same release failure if contact force and failure cause are absent. The episode schema must bind observation, action, contact state, QA outcome, and operator note under one key.

The evidence tier matters. A source such as ^[9] gives a method and benchmark that can be inspected. A company source can reveal deployment direction, but usually exposes less about data rights, recovery handling, and operating metrics. Manufacturers should place both in the same comparison table but never read them with the same confidence.

From a control perspective, the learned policy should not be the whole system. Force limits, guarded motion, fixture state, collision zones, and rollback conditions have to sit around the model. Without that boundary, collecting more data can create more safety stops and more rework instead of a more deployable robot.

From an operating perspective, the reproducibility of failure matters more than a headline success rate. A failure has to enter a replay set, the next update has to pass that replay set, and the deployed cell has to show a lower rate for the same failure code. The question is not only how to describe simulation as distribution perturbation, but which missing log would make the claim collapse on a line.

QA Labels and Failure Mining

The practical meaning of qa labels and failure mining is that process variables must be left in a learnable form. ^[10] shows how scale can broaden embodiment and task families, yet a factory cell is narrower and stricter. A pick that looks identical to a person can become a different distribution when fixture tolerance, surface contamination, cycle pressure, or reject code changes.

In the concrete scenario, A factory data contract is wider than a demo file. It binds who demonstrated, which hand was used, where the fixture slipped, which defect code the inspector emitted, and which replay set blocks the next model release. Human demonstrations alone are not enough. Even when an interface such as ^[11] makes collection easier, a policy will repeat the same release failure if contact force and failure cause are absent. The episode schema must bind observation, action, contact state, QA outcome, and operator note under one key.

The evidence tier matters. A source such as ^[12] gives a method and benchmark that can be inspected. A company source can reveal deployment direction, but usually exposes less about data rights, recovery handling, and operating metrics. Manufacturers should place both in the same comparison table but never read them with the same confidence.

From a control perspective, the learned policy should not be the whole system. Force limits, guarded motion, fixture state, collision zones, and rollback conditions have to sit around the model. Without that boundary, collecting more data can create more safety stops and more rework instead of a more deployable robot.

From an operating perspective, the reproducibility of failure matters more than a headline success rate. A failure has to enter a replay set, the next update has to pass that replay set, and the deployed cell has to show a lower rate for the same failure code. The question is not only how to describe qa labels and failure mining, but which missing log would make the claim collapse on a line.

Release Gates and Rollback

The practical meaning of release gates and rollback is that process variables must be left in a learnable form. ^[13] shows how scale can broaden embodiment and task families, yet a factory cell is narrower and stricter. A pick that looks identical to a person can become a different distribution when fixture tolerance, surface contamination, cycle pressure, or reject code changes.

In the concrete scenario, A factory data contract is wider than a demo file. It binds who demonstrated, which hand was used, where the fixture slipped, which defect code the inspector emitted, and which replay set blocks the next model release. Human demonstrations alone are not enough. Even when an interface such as ^[14] makes collection easier, a policy will repeat the same release failure if contact force and failure cause are absent. The episode schema must bind observation, action, contact state, QA outcome, and operator note under one key.

The evidence tier matters. A source such as ^[15] gives a method and benchmark that can be inspected. A company source can reveal deployment direction, but usually exposes less about data rights, recovery handling, and operating metrics. Manufacturers should place both in the same comparison table but never read them with the same confidence.

From a control perspective, the learned policy should not be the whole system. Force limits, guarded motion, fixture state, collision zones, and rollback conditions have to sit around the model. Without that boundary, collecting more data can create more safety stops and more rework instead of a more deployable robot.

From an operating perspective, the reproducibility of failure matters more than a headline success rate. A failure has to enter a replay set, the next update has to pass that replay set, and the deployed cell has to show a lower rate for the same failure code. The question is not only how to describe release gates and rollback, but which missing log would make the claim collapse on a line.

Manufacturing Cell Checkpoint

Start a PoC by writing the data contract before selecting the model. A factory data contract is wider than a demo file. It binds who demonstrated, which hand was used, where the fixture slipped, which defect code the inspector emitted, and which replay set blocks the next model release. The contract should include episode ID, operator or teleop ID, hand or tool ID, contact channel, controller mode, quality decision, defect code, override reason, and rollback condition. If a vendor hides or cannot export these fields, the manufacturer cannot explain why model improvement happens.

The second checkpoint is evidence tiering. Papers with arXiv or DOI links support method claims; official company pages support product-direction claims; press and watchlist items should not become load-bearing claims. PI, Generalist, Skild, Figure, Covariant, Dexterity, Chef Robotics, Sunday, Config, and CarbonSix all fit under data-driven manipulation, but they expose very different evidence about manufacturing readiness.

Open Questions and Failure Modes

First, large data without contact state leaves insertion, wiping, deformable handling, and tool use under-observed. Second, when data rights stay entirely with the vendor, the manufacturer does not own the cause of process improvement. Third, worker video and process IP are learning assets and governance risks at the same time. Fourth, sim-to-real data does not guarantee factory performance unless it is tied to real QA labels.

Data Contract Addendum

The important unit is not the model name but the observable attempt. To a human, two factory cycles can look like the same task; to a robot, they may differ in surface friction, initial pose, contact order, force limit, and inspection rule. Data strategy is therefore an operating system for connecting failures to process variables, not a campaign for collecting success clips.

Factory data is slower and messier than benchmark data, but it carries more decisive labels. Defect codes, rework, operator intervention, line stops, and safety stops are not noise to be hidden from learning. They are the labels that decide whether a policy can be deployed. If those labels are detached from episodes, model curves can improve while process KPIs stay flat.

Large-data driven manipulation is therefore not a choice of one VLA. It is a joint design of task schema, hand choice, controller boundary, replay set, QA trace, and update governance. Without that design, a foundation model may produce impressive demonstrations without becoming repeatable replacement labor in manufacturing.

Operating Loop Addendum

The important unit is not the model name but the observable attempt. To a human, two factory cycles can look like the same task; to a robot, they may differ in surface friction, initial pose, contact order, force limit, and inspection rule. Data strategy is therefore an operating system for connecting failures to process variables, not a campaign for collecting success clips.

Factory data is slower and messier than benchmark data, but it carries more decisive labels. Defect codes, rework, operator intervention, line stops, and safety stops are not noise to be hidden from learning. They are the labels that decide whether a policy can be deployed. If those labels are detached from episodes, model curves can improve while process KPIs stay flat.

Large-data driven manipulation is therefore not a choice of one VLA. It is a joint design of task schema, hand choice, controller boundary, replay set, QA trace, and update governance. Without that design, a foundation model may produce impressive demonstrations without becoming repeatable replacement labor in manufacturing.

Deployment Governance Addendum

The important unit is not the model name but the observable attempt. To a human, two factory cycles can look like the same task; to a robot, they may differ in surface friction, initial pose, contact order, force limit, and inspection rule. Data strategy is therefore an operating system for connecting failures to process variables, not a campaign for collecting success clips.

Factory data is slower and messier than benchmark data, but it carries more decisive labels. Defect codes, rework, operator intervention, line stops, and safety stops are not noise to be hidden from learning. They are the labels that decide whether a policy can be deployed. If those labels are detached from episodes, model curves can improve while process KPIs stay flat.

Large-data driven manipulation is therefore not a choice of one VLA. It is a joint design of task schema, hand choice, controller boundary, replay set, QA trace, and update governance. Without that design, a foundation model may produce impressive demonstrations without becoming repeatable replacement labor in manufacturing.

What to Learn Next

The next chapter applies the same principle to hands and end-effectors. Some cells are best served by suction or two fingers; others cannot close the data loop without five-finger hands and tactile or force-rich data.

References

1. Ha, Huy (2024). Universal Manipulation Interface: In-The-Wild Robot Teaching Without In-The-Wild Robots. arXiv.
2. Choi, Hojung (2026). In-the-Wild Compliant Manipulation with UMI-FT. arXiv.
3. Xu, Mengda (2025). DexUMI: Using Human Hand as the Universal Manipulation Interface for Dexterous Manipulation. arXiv.
4. Fang, Hao-Shu (2025). DEXOP: Passive Exoskeleton for Direct-contact Dexterous Demonstration. arXiv.
5. Si, Zilin (2025). ExoStart: From 10 Exoskeleton Demos to Dexterous Robot Manipulation. arXiv.
6. Khazatsky, Alexander (2024). DROID: A Large-Scale In-The-Wild Robot Manipulation Dataset. arXiv.
7. O'Neill, Abby (2023). Open X-Embodiment: Robotic Learning Datasets and RT-X Models. arXiv.
8. AgiBot World Team (2025). AgiBot World Colosseo: A Large-Scale Manipulation Platform. arXiv.
9. Dasari, Sudeep (2019). RoboNet: Large-Scale Multi-Robot Learning. arXiv.
10. Ebert, Frederik (2021). Bridge Data: Boosting Generalization of Robotic Skills with Cross-Domain Datasets. arXiv.
11. Mandlekar, Ajay (2021). What Matters in Learning from Offline Human Demonstrations for Robot Manipulation. arXiv.
12. Feng, Ruoxuan (2025). AnyTouch: Learning Unified Static-Dynamic Representation across Multiple Visuo-Tactile Sensors. arXiv.
13. Yang, Fengyu (2023). Touch and Go: Learning from Human-Collected Vision and Touch. arXiv.
14. Yu, Wenhao (2025). ForceVLA: Enhancing VLA Models with a Force-aware MoE for Contact-rich Manipulation. arXiv.
15. Li, Xingyu (2024). Evaluating Real-World Robot Manipulation Policies in Simulation. arXiv.
16. NVIDIA (2025). Isaac Lab: A GPU-Accelerated Simulation Framework for Multi-Modal Robot Learning. NVIDIA Research.
17. Toyota Research Institute (2024). Large Behavior Models for Robot Manipulation. Company technical post.
18. Covariant (2024). RFM-1: Robotics Foundation Model. Company technical post.
19. Dexterity (2025). Dexterity Foresight: AI Platform for Industrial Robot Workcells. Company product page.
20. Chef Robotics (2025). ChefOS: AI Robotics Platform for Food Manufacturing. Company product page.
21. Black, Kevin (2024). pi0: A Vision-Language-Action Flow Model for General Robot Control. arXiv.
22. Octo Model Team (2024). Octo: An Open-Source Generalist Robot Policy. arXiv.
23. Brohan, Anthony (2022). RT-1: Robotics Transformer for Real-World Control at Scale. arXiv.
24. Brohan, Anthony (2023). RT-2: Vision-Language-Action Models Transfer Web Knowledge to Robotic Control. arXiv.