AI Engineer World's Fair 2026

Robot Demos Are Easy. Reliability Is Hard — Jason Ma, Dyna Robotics

Read the talk

Robot Demos Are Easy. Reliability Is Hard

Jason Ma explains how Dyna Robotics combines broad robot training with targeted recovery demonstrations—and why learning what to do after a mistake matters as much as learning the task itself.

From a talk by Jason Ma

At a glance

Ideas worth remembering

  • Commercial reliability includes recovering from mistakes and meeting customer quality criteria, as well as completing the nominal task.

  • A video-based reward model helps locate failures through changes in estimated progress. Humans collect recovery demonstrations for those cases, then fine-tune and repeat.

  • The reported 99.4% result concerns napkin folding over 24 hours. Task mastery and transfer to a new customer site require separate evidence.

  • Broad pre-training can supply recovery knowledge from other tasks; task-specific post-training and active learning turn that foundation into a useful commercial workflow.

Deployment gives research a useful problem

A robot that can perform a useful physical task once has cleared an important hurdle. A robot that can keep doing it in a customer's workplace faces a different test: changing conditions, imperfect hardware, and mistakes that alter what happens next. Jason Ma, co-founder and CTO of Dyna Robotics, introduces the company's goal as one platform that can perform many economically useful tasks with enough reliability for commercial use.

Source frame: Deployment gives research a useful problem
Source frame: Deployment gives research a useful problem

The research and deployment cycle starts with what the models and hardware can already do. Those capabilities determine which customer workflows Dyna can attempt. Deployment then supplies both training data and a sharper diagnosis: which parts of the model or hardware still fail? Ma reports more than five deployment sites at the time of the talk. Their value goes beyond demonstrating progress; they help choose which of robotics' many research problems deserve attention next.

0:160:18
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

0:12 · section reference included

Broad data supplies knowledge; robot data supplies precision

The basic manipulation pipeline begins with demonstrations. A human controls the robot to perform a task, such as folding a T-shirt, and the resulting data trains a neural network. At execution time, the network receives a representation of the scene—in Ma's introductory example, a camera view of the table—and outputs joint positions or torques that move the robot. Learning the visual task and learning the physical action are connected through those demonstrations.

Source frame: Broad data supplies knowledge; robot data supplies precision
Source frame: Broad data supplies knowledge; robot data supplies precision

Scaling that pipeline runs into a data problem: robot demonstrations are scarce. Dyna's pre-training data pyramid combines three sources with different jobs:

  • Off-robot data: Human-worn camera recordings and public datasets provide diverse experience without requiring every example to be collected on a robot. Simulation data is described as something the team is considering.
  • Robot-task data: Demonstrations across industrial, household, laundromat, and hotel tasks teach the precise actions that off-robot observations alone cannot supply.
  • Deployment data: Experience from customer environments helps close the gap between training in a laboratory and operating somewhere else.

Ma reports more than 200,000 hours of data in the training pipeline, across these sources.

The architecture pairs a high-level reasoning model with a low-level world action model. The reasoning component supplies semantic understanding of the situation; the action component produces fine-grained, high-frequency movements. Physical work requires both: understanding what should happen does not by itself supply the precise interaction needed to complete a fold or recover from a bad grasp. The talk gives this division of responsibility without specifying the interface or control frequency.

A useful pre-trained model makes new tasks cheaper to learn. Ma presents two dexterous tool-use examples trained with less than one hour of task-specific data, including tasks absent from pre-training. The office gallery also includes cleaning trash, opening a box, and folding towels and T-shirts. These examples establish the appeal of a general foundation: each new task can build on capabilities already learned. But repeated commercial work raises the next question—how often does the robot fail, and what happens when it does?

2:272:30
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

2:16 · section reference included

An impressive success rate can still interrupt the workflow

Ma places deployed generalist manipulation models at roughly 80–90% success. That leaves frequent interruptions in a repetitive job. To see the compounding effect, under an illustrative assumption of independent attempts with constant success probability (p), ten consecutive successes have probability (p^{10}): about 10.7% at 80% success and 34.9% at 90%. The recording's captioned figure of less than 0.1% for ten repetitions is inconsistent with that calculation, so it cannot support the numerical comparison. The underlying concern remains: reliable individual attempts and long uninterrupted runs are different requirements.

Source frame: An impressive success rate can still interrupt the workflow
Source frame: An impressive success rate can still interrupt the workflow

Specialized systems offer another path: build a robot and learning pipeline for one operation, such as pick and place. The tradeoff is reuse. A pipeline built around one task cannot necessarily adapt quickly to an arbitrary new one. Dyna's goal is to retain the generalist model's range while reaching the reliability a customer needs for a specific workflow.

Restaurant napkin folding gives that goal a concrete test. Employees fold napkins individually in the back of the restaurant, and customers Dyna spoke with wanted to automate the work. The task is repetitive, commercially useful, and difficult enough to expose weaknesses in manipulation. Narrowing the research to this workflow makes the desired result tangible: keep producing napkins the restaurant will accept.

6:256:27
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

6:09 · section reference included

Napkin folding tests grasping, quality, and recovery

Dyna-1, a generalist robot foundation model fine-tuned for napkin folding, achieved a reported 99.4% success rate over a 24-hour run. Ma also presents four distinct 24-hour office trials. In the time-lapse, daylight arrives around 7 a.m. and changes the lighting while the robot keeps folding. These are speaker-reported results; the supplied material gives neither evaluation sample sizes nor independent verification, so the percentage should remain attached to this napkin-folding evaluation rather than become a reliability claim for every task or site.

Source frame: Napkin folding tests grasping, quality, and recovery
Source frame: Napkin folding tests grasping, quality, and recovery

The operation has three nominal steps: pick exactly one napkin from the stack, fold it, and place it in a bin. The first step already creates trouble. Parallel-jaw grippers may pull out extra napkins, leaving the robot with a scene that differs from a clean demonstration. The fold also has to meet a customer's quality standard. Ma contrasts an acceptable grade-five fold with an unacceptable grade-three fold, separated by roughly one inch in the position of the second fold seam. Moving cloth into a folded shape is only part of success; the final geometry matters.

Dyna's initial pre-training and post-training recipe reached roughly 80% success on this task. The recurring problem appeared after a mistake: the robot entered an unfamiliar state, got stuck, and could not recover. More successful demonstrations would teach the normal path, but the missing behavior was what to do after leaving that path. Reliability therefore required training on the situations the robot created through its own errors.

8:568:58
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

8:55 · section reference included

Progress scores turn rare mistakes into training targets

Dyna adds a reward model that watches robot video and estimates progress toward completing a task. In the examples, progress moves from zero toward one as the operation finishes. A successful napkin fold produces a roughly rising estimate; mistakes produce dips. During the ninth napkin in one autonomous run, the estimate stops rising monotonically as the robot makes an error. The useful signal is the change in progress, which helps identify where the operation went wrong.

Source frame: Progress scores turn rare mistakes into training targets
Source frame: Progress scores turn rare mistakes into training targets

Once the policy succeeds around 90% of the time, having a person watch every attempt is an inefficient way to find the remaining failures. The reward model runs in the background and directs researchers or operators to the video cases that need attention. Humans then collect targeted demonstrations of recovery from those states, and Dyna fine-tunes the policy again. This is a human-in-the-loop active-learning cycle: autonomous operation finds the gaps, progress scoring helps locate them, and human demonstrations supply the missing actions.

Where does the progress signal change the training process? The diagram follows the loop from a napkin-folding attempt back to an improved policy. Its key relationship is the handoff from detecting trouble to collecting recovery data: the reward model helps choose what to teach, while the policy learns how to act. Ma reports that repeated cycles produced a model able to recover from a wider range of errors.

How it fits togetherFrom a progress dip to a better recovery policy

The policy acts while producing video of its attempts.

Video scoring selects difficult cases for human recovery demonstrations; fine-tuning changes the policy used in the next autonomous run.

11:3811:42
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

11:38 · section reference included

A bad grasp becomes a recoverable state

Return to the single-napkin pickup. In a recovery highlight, the robot accidentally takes more than one napkin. Instead of remaining stuck with the extra cloth, it separates the napkins and continues making progress. The observable change is from a failed selection to a state in which folding can proceed. Targeted recovery training addresses precisely this gap: the policy needs useful actions for the aftermath of a bad grasp, as well as actions for the clean pickup.

Source frame: A bad grasp becomes a recoverable state
Source frame: A bad grasp becomes a recoverable state

Cloth makes exhaustive recovery coverage impractical. A napkin can deform into an enormous range of configurations, so the team cannot demonstrate every possible error. Ma reports that repeated active learning produced recovery behavior that generalized to new mistakes. The strongest example is a robot pulling over the entire napkin stack, then using pulling and stretching movements to recover and keep working. Continuous operation depends on handling the mess the robot creates, rather than assuming the table always remains in its expected state.

The commercial examples move the same recipe into customer workflows. Dyna deploys napkin-folding robots in restaurant back offices and fine-tunes a model for towel folding at a Sacramento laundromat. In the laundromat example, a worker repeatedly replenishes the bin while the robot folds stacks of towels. The automation handles the folding operation within a workflow that still includes human material handling.

10:0710:09
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

14:08 · section reference included

Task mastery and site generalization are separate tests

The restaurant and laundromat examples come with an important qualification: Dyna collected data at the customer sites used for those deployments. Mastering a task in one location does not automatically establish that the model will perform it somewhere unfamiliar. Collecting and adapting at every new site adds work to expansion, so the next objective is to preserve task performance without additional site data.

Source frame: Task mastery and site generalization are separate tests
Source frame: Task mastery and site generalization are separate tests

Ma describes a diverse-task data recipe intended to enable that transfer, then presents T-shirt folding at CoRL 2025 in Korea as the example. The robot arrived at an exhibition booth and began folding different T-shirts without additional site data. It faced attendees, including people who deliberately covered its camera with a shirt, and reportedly continued folding over three days at the conference. This tests environmental transfer and resilience to disruption; it does not establish the same 99.4% figure reported for napkin folding.

A Red Bull partnership extends the examples to opening cans at live events. Ma describes repeated operation at a music festival despite changing background lighting, but the demonstration video did not play properly during the presentation. This example rests on his account. Together, the deployments point toward the desired product experience: bring a robot to a site and have it start useful work, while retaining the ability to perform a chosen commercial task well.

16:2716:29
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

16:27 · section reference included

Enterprise deployment comes before a household product

The audience questions clarify what Dyna is building now and what remains an ambition:

  • Developer tools: Dyna is building its own hardware stack and is not currently working on a developer kit. A kit may become part of the roadmap later.
  • Education: Teaching children to train robots is an interesting future direction for Ma, but Dyna has not explored that use case.
  • Consumer robots: The long-term goal includes a model and hardware platform usable by anyone, including households. The current go-to-market focus is enterprise customers.

Enterprise customers let Dyna deploy and iterate at the site. A consumer product would need more polish, tolerate fewer mistakes, and address privacy and safety concerns that the company is not taking on at this stage. Ma treats commercial environments as a useful testing ground for the immediate bottleneck: getting the AI and hardware to work well together. The sequencing follows the research cycle introduced at the start—choose a workable deployment, learn from it, and improve the system.

Voice commands could fit above the manipulation stack. Ma sketches an approach in which onboard speech-to-text converts a person's speech into text, then the reasoning and world models interpret the instruction and produce actions. He offers this as a possible integration rather than a demonstrated voice system. Recognizing the command would still leave the harder capability problem: Dyna's models and other robot foundation models are not ready to execute arbitrary instructions. A robot that anyone can teach or steer through language remains the goal; low-level manipulation is still a limiting step.

19:5820:01
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

19:51 · section reference included

Recovery draws on experience beyond the chosen task

The final question asks how intelligence should be divided between general pre-training, task-specific training, and adaptation at a deployment site. Ma adds a consequential explanation for the recovery demonstrations: some of the behavior came from interpolating recovery experience gathered on other tasks. A model exposed to thousands of tasks can draw on physical knowledge that a model specialized from the outset would miss.

That gives the three training stages distinct purposes. General pre-training builds semantic and physical understanding, including experience with recovery. Post-training adapts that foundation to the chosen job. Active learning then concentrates demonstrations on the mistakes that remain during operation. For napkin folding, the resulting policy needs both a precise routine and enough transferable physical knowledge to find a way forward when the routine goes wrong. Dyna's intended reusable product is this recipe across tasks, rather than a separate learning pipeline for each one.

24:1424:16
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

24:14 · section reference included

Read the complete timestamped transcript
  1. 0:01

    [music]

  2. 0:12

    >> Thanks for the kind introduction. So,

  3. 0:13

    I'm Jason, co-founder of Diana.

  4. 0:16

    Today, I'll talk about how we're

  5. 0:18

    developing high-performance and very

  6. 0:20

    robust generalist robotics policies.

  7. 0:23

    Yeah.

  8. 0:24

    So, let's jump into it. So, today's talk

  9. 0:27

    will focus on, you know, how we're

  10. 0:28

    bringing robots into commercial grade

  11. 0:30

    and what we are doing to make these

  12. 0:32

    models, like I said, very

  13. 0:33

    high-performance and robust. So, just a

  14. 0:35

    brief introduction to our company. So,

  15. 0:37

    our mission is to build very robust

  16. 0:40

    foundation model autonomy in the real

  17. 0:41

    world. So, we want to train models and

  18. 0:43

    these days also hardware to have a

  19. 0:46

    single platform that can do many

  20. 0:48

    economically useful physical tasks in

  21. 0:50

    the real world, like the ones we're

  22. 0:52

    showing here. So, the company the

  23. 0:54

    company was founded in September 2024.

  24. 0:56

    We are a series A company, have raised

  25. 0:58

    about $120 million, and we

  26. 1:03

    And our thesis is that to actually bring

  27. 1:05

    robots into the real world, being at

  28. 1:08

    commercial grade doing useful tasks, the

  29. 1:10

    company needs to combine doing frontier

  30. 1:12

    research with a lot of commercial

  31. 1:14

    deployments, so we can build what we

  32. 1:16

    consider a research and deployment

  33. 1:18

    flywheel.

  34. 1:19

    Uh which is that the research and

  35. 1:21

    hardware we do in-house, the R&D informs

  36. 1:24

    the kind of tasks, the kind of workflows

  37. 1:26

    in the real world that we can

  38. 1:27

    commercialize. So, we actively try to

  39. 1:29

    deploy. So, these days we have more than

  40. 1:31

    five deployment sites doing a bunch of

  41. 1:33

    different tasks, which I will talk about

  42. 1:35

    in a bit. And then by building product

  43. 1:38

    and by deploying robots, it does several

  44. 1:40

    things. One is that it can help us

  45. 1:42

    gather high-quality deployment data, and

  46. 1:45

    it can also tell us what our models and

  47. 1:47

    what our hardware is not good at yet.

  48. 1:48

    So, it helps us sharpen our research

  49. 1:50

    focus to figure out what is the right

  50. 1:52

    problem to work on in robotics. Because

  51. 1:55

    if you're familiar with the robotics

  52. 1:57

    field, there are too many problems.

  53. 1:58

    There are too many different fields you

  54. 2:00

    can spend your effort on. And by

  55. 2:02

    deploying and by building a product, we

  56. 2:04

    know exactly the right kind of problems

  57. 2:05

    that we need to focus to actually make a

  58. 2:08

    robotics not just a demo or videos you

  59. 2:10

    see on YouTube, but rather in the real

  60. 2:12

    world impacting millions of people's

  61. 2:14

    life.

  62. 2:16

    So, before I jump into what we

  63. 2:18

    specifically work on at covariant, just

  64. 2:19

    a very quick introduction on the kind of

  65. 2:22

    models we're training for robotic

  66. 2:24

    manipulation. So, at a high level, uh we

  67. 2:27

    do data collection where you know,

  68. 2:28

    there's a lot of data being collected.

  69. 2:30

    So, here's a video of me uh manipulating

  70. 2:33

    a robotic hardware to, you know, fold a

  71. 2:35

    t-shirt. And once you collect enough of

  72. 2:37

    this kind of data, you can put all of

  73. 2:40

    them in a large neural network. And a

  74. 2:42

    neural network essentially takes in a,

  75. 2:45

    you know, representation of the world,

  76. 2:47

    in this case just camera feed of what

  77. 2:49

    the, you know, a table looks like, and

  78. 2:51

    the outputs robot's, you know, joint

  79. 2:53

    positions or torque to actually control

  80. 2:55

    the robot to do the task that you have

  81. 2:57

    collected data on.

  82. 2:59

    Right?

  83. 3:00

    So, you know, this is the high level of

  84. 3:03

    how you robot models in the real world

  85. 3:06

    function. So, how are we actually

  86. 3:08

    scaling this up to actually create

  87. 3:10

    models that's generalizable and it can

  88. 3:12

    do a lot of different tasks. So, at

  89. 3:14

    covariant we focus on what we call the

  90. 3:16

    pre-training data pyramid for the real

  91. 3:17

    world, where we gather a lot of diverse

  92. 3:20

    off-robot data, just because robotics

  93. 3:22

    data is very scarce. So, we have data

  94. 3:24

    captured from humans wearing cameras, uh

  95. 3:27

    from public data sets, and these days

  96. 3:29

    we're also considering some simulation

  97. 3:31

    data. But if you only have off-robot

  98. 3:33

    data, it's not actually enough to get

  99. 3:35

    robots to do very precise actions. So,

  100. 3:38

    on the robot themselves, we also collect

  101. 3:40

    diverse tasks collected in many

  102. 3:41

    different scenarios, on many different

  103. 3:44

    types of tasks, like industrial tasks,

  104. 3:46

    household, uh in the laundromat, and uh

  105. 3:48

    you know, hotels. And then finally,

  106. 3:50

    because we're also deploying robots, we

  107. 3:52

    can collect very high-quality deployment

  108. 3:55

    data, which helps the model to close

  109. 3:57

    train and test distribution gap. Because

  110. 4:00

    when you're developing robots, you know,

  111. 4:02

    most of the time your robots are in your

  112. 4:03

    facility, in your laboratories. But if

  113. 4:05

    you're deploying robots, it's in a very

  114. 4:07

    different environment. So, we found that

  115. 4:09

    by combining these three data sources,

  116. 4:11

    we can actually train large-scale

  117. 4:12

    foundation models that work very well in

  118. 4:14

    the real world. And so far, we have more

  119. 4:16

    than 200,000 hours of data in our

  120. 4:18

    training pipeline.

  121. 4:20

    And the model architecture roughly

  122. 4:22

    follows a high-level reasoning model

  123. 4:25

    with a low-level world action model that

  124. 4:27

    can actually output dexterous actions at

  125. 4:30

    fine-grained high frequency, right? So,

  126. 4:33

    this is the kind of architecture we have

  127. 4:35

    because in the real world, if you think

  128. 4:36

    about a robot doing physical tasks, it

  129. 4:39

    needs to have a semantic understanding

  130. 4:41

    of the world, but also needs to

  131. 4:43

    understand physical interaction at a

  132. 4:45

    fine-grained level to be actually able

  133. 4:47

    to, you know, recover from mistakes and

  134. 4:49

    do very precise actions to complete the

  135. 4:51

    task.

  136. 4:52

    So, once you combine,

  137. 4:54

    you know, this architecture with a lot

  138. 4:56

    of data, what happens is that the model

  139. 4:58

    can be rapidly fine-tuned to do a bunch

  140. 5:00

    of different tasks in the real world.

  141. 5:03

    Yeah, so here are just a gallery of the

  142. 5:05

    kind of benchmark tasks we're doing in

  143. 5:07

    the office. So, it spans from, you know,

  144. 5:09

    like cleaning trash, opening a box, to,

  145. 5:12

    you know, things like folding towels,

  146. 5:14

    folding t-shirts, and also just a bunch

  147. 5:16

    of other tasks our researchers have

  148. 5:17

    thought about.

  149. 5:19

    And what's really interesting is that

  150. 5:20

    with a good pre-trained model, even

  151. 5:23

    without any,

  152. 5:24

    you know, for some of these tasks I'm

  153. 5:26

    showing you here, they're not in the

  154. 5:28

    pre-training data at all. But with a

  155. 5:30

    good pre-training, you can actually

  156. 5:31

    post-train the model to do these kind of

  157. 5:33

    highly dexterous tool use tasks with

  158. 5:36

    very little amount of data. So, both of

  159. 5:38

    the videos you're seeing here have only

  160. 5:40

    been trained on with less than 1 hour of

  161. 5:42

    task-specific data. But you can see that

  162. 5:45

    the robot can repetitively

  163. 5:47

    do these tasks over and over without

  164. 5:49

    failure. And I think this is a stepping

  165. 5:51

    stone towards actual commercial grade

  166. 5:54

    real world deployment because in the

  167. 5:56

    real world physical tasks need to be

  168. 5:58

    done by humans and by robots over and

  169. 6:00

    over. And if your models are not

  170. 6:02

    reliable enough, then yes, you can shoot

  171. 6:04

    these kind of pretty demos, but it's

  172. 6:06

    still very far away from actual

  173. 6:08

    deployment.

  174. 6:09

    So that actually brings us to what I

  175. 6:12

    consider the current status quo for

  176. 6:14

    training large-scale foundation models

  177. 6:16

    for manipulation, which is that the

  178. 6:18

    generous models that can do many many

  179. 6:20

    tasks like the ones I've been showing

  180. 6:22

    you. Even though they make pretty

  181. 6:23

    videos, but what I would tell you is

  182. 6:25

    that the success rate is actually

  183. 6:27

    not super high.

  184. 6:29

    You know, when these models are actually

  185. 6:31

    deploying, they're about 80 to 90%

  186. 6:33

    success rate. But if you're stuck at 80

  187. 6:36

    to 90% success rate, then you know, the

  188. 6:38

    chance that you can do the same task 10

  189. 6:40

    times in a row is actually less than

  190. 6:42

    0.1%.

  191. 6:44

    And on on the flip side, in the history

  192. 6:46

    of robotics, we have had very

  193. 6:48

    specialized robots and a very

  194. 6:49

    specialized machine learning pipelines

  195. 6:52

    to do singular tasks like pick and

  196. 6:54

    place. But this kind of pipeline, which

  197. 6:56

    is what I consider specialist models,

  198. 6:58

    aren't aren't very scalable, meaning

  199. 7:00

    that you can't take the same pipeline to

  200. 7:02

    just do a new task and do an arbitrary

  201. 7:04

    task very fast. So our mission is to

  202. 7:06

    resolve the status quo and you know,

  203. 7:08

    this kind of like dichotomy by training

  204. 7:11

    general purpose models that can both do

  205. 7:13

    many many tasks and also be reliable

  206. 7:15

    enough for commercial deployments.

  207. 7:18

    So how do we actually do that? In

  208. 7:19

    today's talk, I'll briefly talk about

  209. 7:21

    some of our progress on mastering very

  210. 7:23

    complex tasks very reliably and also

  211. 7:26

    taking the same skills to be performant

  212. 7:29

    not only in the environments in the

  213. 7:31

    laboratory environments that we're

  214. 7:32

    training, but also being able to deploy

  215. 7:34

    to arbitrary customer sites without

  216. 7:36

    fine-tuning or without fine-tuning

  217. 7:38

    adaptation.

  218. 7:40

    Okay, so let me get to this. Right, So,

  219. 7:43

    the first question we want to answer is

  220. 7:45

    can we take, you know, the general

  221. 7:47

    pre-training and post-training recipe

  222. 7:48

    that we had, but then turn these models

  223. 7:50

    into models that can be almost close to

  224. 7:53

    100% robust on uh any task. So, this is

  225. 7:57

    the first research result we published

  226. 7:59

    last year. Uh for detail, you can check

  227. 8:01

    out our blog post. But, at a high level,

  228. 8:04

    you know, if we want to make a model

  229. 8:05

    100% robust on many, many tasks, I think

  230. 8:08

    it's very good to first narrow down on a

  231. 8:10

    commercial use case that's reasonably

  232. 8:12

    hard, which allows you to make research

  233. 8:14

    progress, but also has commercial value.

  234. 8:17

    So, when we first started the company uh

  235. 8:19

    last year, what we discovered is that if

  236. 8:21

    you go to any, you know, uh restaurant,

  237. 8:23

    you know, uh fancy restaurant or dim sum

  238. 8:25

    places in the US, you'll see nicely

  239. 8:27

    folded napkin on the table, right, for

  240. 8:29

    you, right? If you go to a Cheesecake

  241. 8:31

    Factory, you'll see those napkins. And

  242. 8:33

    what happens is that in the back office

  243. 8:35

    of the restaurant, there's usually uh

  244. 8:36

    workers or, you know, restaurant

  245. 8:38

    employees that's folding these napkins

  246. 8:40

    one by one by hand. And that's a very

  247. 8:43

    mundane process, and a lot of the

  248. 8:45

    customers we have talked to are looking

  249. 8:47

    into robots that can actually do the

  250. 8:49

    same task. So, this is one of the

  251. 8:51

    earliest case study we did on how to

  252. 8:53

    train models to be very robust.

  253. 8:55

    So,

  254. 8:56

    our research result is a model called

  255. 8:58

    the Dyna-1, which is a generalist robot

  256. 9:00

    foundation model that's fine-tuned to do

  257. 9:02

    napkin folding. They can actually

  258. 9:04

    achieve 99.4% success rate over a

  259. 9:07

    24-hour span. So, here is a time lapse

  260. 9:10

    of the model, you know, doing the task.

  261. 9:12

    And uh you know, it's sped up about a

  262. 9:14

    thousand times, so you can see the clock

  263. 9:16

    in the back running very quickly to show

  264. 9:18

    the progress. And uh my favorite part of

  265. 9:21

    the video is when the clock, you know,

  266. 9:23

    hits about like right now, right? Like

  267. 9:25

    7:00 a.m. in the morning, so the lights,

  268. 9:27

    you know, actually come out in the

  269. 9:29

    outside. So, the environments are

  270. 9:30

    actually, you know, shifting over time

  271. 9:32

    due to the lighting as the robot folds

  272. 9:34

    the napkin, but the model's robust

  273. 9:36

    enough, and it just keeps going.

  274. 9:38

    So, how do we actually get to a model

  275. 9:40

    that can do this?

  276. 9:41

    And uh first of all, you know, this uh

  277. 9:43

    video we put out is not a one-time

  278. 9:46

    occurrence. The model can do this many,

  279. 9:48

    many times

  280. 9:50

    uh in the office, you know, so these are

  281. 9:51

    four distinct trials of 24-hour runs.

  282. 9:55

    So, before I dive into the technical

  283. 9:57

    detail, just to highlight how difficult

  284. 9:59

    the task is. So, you see that in the

  285. 10:01

    napkin folding task, you start out with

  286. 10:03

    a stack of napkin on the side, and what

  287. 10:05

    the robot has to do is like be very

  288. 10:07

    precise about picking out exactly one

  289. 10:09

    napkin from the stack, and then fold it,

  290. 10:11

    and then put it into a bin. And then a

  291. 10:13

    lot of the

  292. 10:14

    failure cases just come from the fact

  293. 10:15

    that these, you know, parallel jaw

  294. 10:17

    grippers we're deploying, you know, the

  295. 10:18

    gripper may not be precise enough to be

  296. 10:20

    able to pick out exactly one napkin. And

  297. 10:23

    in these situations, the model has to

  298. 10:25

    learn how to recover from the mistakes

  299. 10:27

    of pulling out extra napkins.

  300. 10:29

    And then secondly, the in commercial

  301. 10:32

    environment, different from a lab demo

  302. 10:34

    where the researchers like me are

  303. 10:36

    thinking of task success, there's

  304. 10:38

    actually very

  305. 10:40

    well-defined success criteria for these

  306. 10:42

    tasks. So, on the right, you see the

  307. 10:44

    difference between what we consider a

  308. 10:46

    grade five fold, which is a fold quality

  309. 10:48

    that the restaurant would accept versus

  310. 10:51

    a grade three, which is something that's

  311. 10:53

    below the acceptance criteria. And what

  312. 10:55

    you see is a barely like 1-in difference

  313. 10:57

    in how, you know, low the you know, the

  314. 10:59

    second fold seam of the napkin is.

  315. 11:03

    So, how do we actually get to a model

  316. 11:05

    that works really well? So, our internal

  317. 11:07

    attempt was kind of like the

  318. 11:09

    pre-training

  319. 11:10

    many, many hours of data and then

  320. 11:13

    post-training recipe that I told you

  321. 11:14

    about in the beginning. And doing this

  322. 11:16

    roughly gets you about 80% success rate.

  323. 11:19

    And what happens is that the model, you

  324. 11:21

    know, is doing fine in the beginning,

  325. 11:23

    but as soon as it makes a mistake, it'll

  326. 11:25

    typically go out of distribution, get

  327. 11:27

    stuck, and unable to recover.

  328. 11:30

    So, we have to do something more than

  329. 11:31

    the standard pre-training and

  330. 11:32

    post-training idea that's very popular

  331. 11:35

    in robotics and also in other fields.

  332. 11:38

    So what we did is that we developed what

  333. 11:40

    we consider

  334. 11:42

    reward models for complex long horizon

  335. 11:44

    manipulation tasks. So these are models

  336. 11:46

    that can, you know, look at a robot

  337. 11:48

    video and accurately score its progress

  338. 11:51

    towards solving a task. All right, so

  339. 11:53

    let me just play these videos again. So

  340. 11:55

    here's the same model, you know, being

  341. 11:57

    able to score how well the robot is

  342. 11:59

    doing these long horizon complex tasks

  343. 12:02

    as it's, you know, going from

  344. 12:04

    you know, starting of the task to

  345. 12:06

    finish. So you see that as the robot's

  346. 12:08

    completing a task, it's able to go from

  347. 12:10

    zero to one. And if you squint at these

  348. 12:12

    videos enough, you also see that

  349. 12:14

    whenever the robot is actually making

  350. 12:16

    some mistakes, there will be like slight

  351. 12:18

    dips in the reward model. And that

  352. 12:20

    actually becomes a very important

  353. 12:23

    insight into how to make these models

  354. 12:25

    very robust. So here's what happens when

  355. 12:28

    you run such model during like a

  356. 12:30

    autonomous run out of the robot. So you

  357. 12:32

    see that when the robot is doing fine

  358. 12:34

    folding napkins, the progress estimation

  359. 12:37

    is roughly monotonic going up, right?

  360. 12:39

    Because the robots are not messing up.

  361. 12:41

    But what's really interesting is is that

  362. 12:43

    let me just for fast forward a bit.

  363. 12:45

    Whenever the model starts to make

  364. 12:47

    mistakes, so here it is. This is the

  365. 12:50

    ninth napkin is folding. So you see that

  366. 12:52

    when the model is like making mistake,

  367. 12:54

    that's when the progress estimation, you

  368. 12:56

    know, starts to like, you know, show

  369. 12:57

    non-monotonic sign indicating that the

  370. 12:59

    robot is messing up. Right? And this is

  371. 13:01

    very important because once your model

  372. 13:03

    is like good enough in the 90% uh

  373. 13:06

    range, then it's very inefficient for

  374. 13:08

    humans to manually oversee the robot to

  375. 13:11

    detect its failure and then try to

  376. 13:12

    recover. But once we have this reward

  377. 13:15

    model, we can actually do what I

  378. 13:17

    consider uh scalable supervision. So you

  379. 13:19

    can just have the robot trying to fold

  380. 13:21

    napkins and then run this reward model

  381. 13:23

    in the background. So whenever a model

  382. 13:25

    does make a mistake, uh we as

  383. 13:27

    researchers or operators can immediately

  384. 13:30

    know the kind of video case that the

  385. 13:31

    model is struggling on and then do very

  386. 13:34

    targeted data collection and error

  387. 13:36

    recovery data for the model, then we can

  388. 13:38

    fine-tune the model again. So, the

  389. 13:40

    overall pipeline looks like a

  390. 13:42

    human-in-the-loop active learning

  391. 13:44

    process where we can use the reward

  392. 13:46

    model to help us catch the the kind of

  393. 13:48

    mistake the model is bad at and then do

  394. 13:51

    targeted collection to make the model

  395. 13:52

    better and iterate.

  396. 13:54

    And what we found is that once you

  397. 13:55

    iterate on this

  398. 13:57

    uh couple cycles, then you start to get

  399. 14:00

    a model that's extremely robust and can

  400. 14:02

    recover from all kinds of errors and

  401. 14:04

    finally bringing us closer to a

  402. 14:06

    commercial grade robots. So, here is

  403. 14:08

    just uh some of the

  404. 14:10

    uh

  405. 14:11

    you know

  406. 14:12

    uh

  407. 14:13

    highlights, I guess, during the 24-hour

  408. 14:15

    trial. So, what you saw there was the

  409. 14:17

    robot accidentally picked out more than

  410. 14:19

    one napkins and the model is able to,

  411. 14:21

    you know, separate the napkins and uh

  412. 14:24

    you know, here it's kind of doing that

  413. 14:26

    and uh

  414. 14:26

    be able to continue progressing. And

  415. 14:30

    what we found very interesting is that

  416. 14:32

    uh

  417. 14:33

    napkin folding is a deformable object

  418. 14:34

    manipulation task, right? So, there is

  419. 14:36

    almost infinitely many possible states

  420. 14:39

    or configuration that a napkin can get

  421. 14:41

    to. So, it's impossible to exhaustively

  422. 14:43

    collect data for all the error cases.

  423. 14:45

    But once we had done the active learning

  424. 14:47

    many, many times, we saw the model able

  425. 14:49

    to generalize to new ways of recovery

  426. 14:52

    from the mistakes made and continue to

  427. 14:53

    make progress. And that contributed to

  428. 14:56

    its ability to be able to uh fold that

  429. 14:59

    uh 99.4% success rate. So, here's uh

  430. 15:02

    what I found the most impressive bit

  431. 15:04

    from the trial. So, typically, if you

  432. 15:07

    look at robot videos, you know, they

  433. 15:08

    only show you the successful cases. But

  434. 15:10

    here, I wanted to highlight that even

  435. 15:12

    where a model accidentally pulled the

  436. 15:14

    entire napkins stack over, it's able to

  437. 15:16

    demonstrate this kind of error recovery

  438. 15:18

    behavior. That was very surprising to us

  439. 15:20

    when we were developing the model and it

  440. 15:22

    contribute to how it's able to just

  441. 15:23

    continuously run, right? So, here

  442. 15:27

    he made a

  443. 15:28

    big mess, but he's able to just do all

  444. 15:30

    kind of like very impressive like

  445. 15:32

    pulling you know, stretching behavior to

  446. 15:35

    recover from his mistake and then

  447. 15:36

    continuously going.

  448. 15:39

    Yeah, so you know, after developing such

  449. 15:41

    technology, we actually are successful

  450. 15:44

    at deploying our models at many many

  451. 15:46

    restaurants in the US. So, here's a real

  452. 15:49

    restaurant deployment of our robot

  453. 15:51

    folding napkins for the customers in

  454. 15:53

    their back office.

  455. 15:56

    And in addition to folding napkin,

  456. 15:58

    because the recipe is quite

  457. 15:59

    generalizable, now we also have models

  458. 16:01

    doing bunch of commercial tasks. So,

  459. 16:03

    here's at a real laundromat in

  460. 16:06

    Sacramento, and this time we fine-tune

  461. 16:09

    our model to do

  462. 16:10

    towel folding for the customer. So, you

  463. 16:13

    can see you know, there's a restaurant I

  464. 16:15

    guess a laundromat worker coming here to

  465. 16:17

    fill the bin over and over, and the

  466. 16:19

    robot just kept folding stacks of towels

  467. 16:22

    to serve the customer.

  468. 16:27

    So, now let's talk about we have a

  469. 16:29

    recipe to master very complex tasks.

  470. 16:32

    But, the caveat here is that in all the

  471. 16:34

    videos I've shown you so far, we have

  472. 16:35

    also collected data at the exact

  473. 16:38

    customer site where location that the

  474. 16:40

    robot is deployed. But, if you think

  475. 16:41

    about scaling robots to any task or to

  476. 16:45

    any customer site, then it'll be much

  477. 16:47

    better or more ideal if the models can

  478. 16:49

    readily generalize the environments they

  479. 16:51

    haven't seen before. So, this is what we

  480. 16:54

    have worked on in the

  481. 16:56

    I guess the end of last year where we

  482. 16:58

    figured out a data recipe to collect a

  483. 17:00

    lot of diverse tasks to allow the robots

  484. 17:02

    to be able to deploy at a new site

  485. 17:04

    without any additional data while

  486. 17:06

    maintaining the task performance. So,

  487. 17:09

    here's a demo we did at Coral 2025. So,

  488. 17:12

    Coral is the premier academic conference

  489. 17:14

    on robot learning, and it's held in

  490. 17:16

    Korea last year. So, you know, bringing

  491. 17:19

    a robot from the US to Korea was its

  492. 17:21

    whole challenge that I can talk about

  493. 17:23

    offline. But, the recipe we discovered

  494. 17:26

    was able to, you know, we just brought

  495. 17:28

    the robot to our, you know, exhibition

  496. 17:30

    booth and just dropped it there, and the

  497. 17:32

    robot can start folding many, many

  498. 17:34

    different t-shirts. And you see that the

  499. 17:36

    robot is facing the, you know, the

  500. 17:38

    conference attendees. So, many, many

  501. 17:40

    times there were people just

  502. 17:42

    deliberately trying to mess with the

  503. 17:43

    robot, use the t-shirt to cover up the

  504. 17:45

    robot's camera, then, you know, all kind

  505. 17:47

    of fancy stuff that you see at academic

  506. 17:49

    conferences. But, the model is able to

  507. 17:51

    continuously fold t-shirts over and over

  508. 17:53

    for 3 days straight at the conference

  509. 17:55

    just to demonstrate the ability to, you

  510. 17:58

    know, solve this task at environments

  511. 18:00

    it's never seen before, bringing it, you

  512. 18:02

    know, much closer to the kind of, you

  513. 18:04

    know, ideal, you know, go-to-market that

  514. 18:07

    you want to have for robotics company,

  515. 18:09

    which is just putting the robot to a

  516. 18:10

    site and it just starts working.

  517. 18:13

    And recently, we have also ventured into

  518. 18:16

    many different tasks. Like, we have a a

  519. 18:18

    partnership with Red Bull where we're

  520. 18:20

    opening Red Bull cans at, you know, Red

  521. 18:23

    Bull events. So, here's a video of our

  522. 18:28

    uh

  523. 18:28

    robot. Again, uh I guess this video

  524. 18:31

    won't play properly. So, but you get the

  525. 18:33

    point. We brought the robot to a Red

  526. 18:35

    Bull event and it's able to

  527. 18:37

    uh open uh these Red Bull drinks for,

  528. 18:40

    again, conference attendees over and

  529. 18:42

    over without failure, even though in

  530. 18:44

    this particular deployment, it's at a

  531. 18:46

    music festival, so the lighting's always

  532. 18:48

    changing in the background, but the

  533. 18:49

    model can continue. Yeah, but due to

  534. 18:52

    yeah, I guess the

  535. 18:54

    video will not play.

  536. 18:56

    So, just to summarize, uh our mission at

  537. 18:59

    AINA is to be able to build

  538. 19:01

    general-purpose models and robots that's

  539. 19:03

    both competent at many tasks, but also

  540. 19:06

    being able to focus and attain really

  541. 19:08

    high performance on commercial tasks.

  542. 19:11

    And I have demonstrated some of our

  543. 19:13

    recent progress on mastering complex

  544. 19:15

    tasks and also generalizing the skills

  545. 19:17

    to environments is the robots have never

  546. 19:19

    seen before. So, we are a series A stage

  547. 19:22

    company actively growing and hiring and

  548. 19:24

    if you're also interested in partnering

  549. 19:26

    with us for deployments and other

  550. 19:28

    things, feel free to reach out and then

  551. 19:30

    talk to me after the talk and thank you

  552. 19:32

    for listening.

  553. 19:33

    >> Awesome. Thank you, Jason. Really

  554. 19:34

    appreciate.

  555. 19:36

    If you guys haven't seen the data robot

  556. 19:37

    in life in real life, have you check it

  557. 19:39

    out? I will say see as very impressive

  558. 19:41

    performance.

  559. 19:43

    Do we have any question or want to ask?

  560. 19:46

    Okay, cool.

  561. 19:51

    >> Thank you for sharing the presentation.

  562. 19:54

    I wanted to ask if you are already doing

  563. 19:57

    kind of like

  564. 19:58

    providing developer kits with robots,

  565. 20:01

    SDKs, frameworks, etc. for your

  566. 20:03

    commercial partners?

  567. 20:05

    >> Yeah, so we haven't been working on

  568. 20:07

    develop developer kit, but you know,

  569. 20:10

    at the current moment we're building our

  570. 20:12

    own hardware stack. So, maybe at some

  571. 20:15

    point it's on our road map, but

  572. 20:17

    not as of not as of now. Yeah.

  573. 20:26

    >> I'm curious if you have ventured into

  574. 20:28

    education like teaching kids

  575. 20:32

    elementary maths or any such use case

  576. 20:35

    you tried.

  577. 20:36

    >> Yeah, so we haven't looked into

  578. 20:37

    education use case, right?

  579. 20:40

    But I think in the future, you know,

  580. 20:41

    once our

  581. 20:43

    full stack robotics pipelines mature,

  582. 20:45

    once we have our own hardware, our data

  583. 20:46

    collection, you know, toolkit, I think

  584. 20:49

    it's possible and I think it'll be very

  585. 20:50

    interesting to venture into education

  586. 20:53

    use cases because I also think robotics

  587. 20:55

    will only get bigger in the future. So,

  588. 20:57

    I think it'll be really really

  589. 20:58

    interesting to get children and young

  590. 21:01

    kids into the field and the learning how

  591. 21:03

    to actually train models to do tasks.

  592. 21:07

    >> Thank you for the presentation, really

  593. 21:08

    good. Uh

  594. 21:09

    my question is like is there do you guys

  595. 21:11

    have a plan for uh kind of taking this

  596. 21:14

    technology direct to consumer? Like I

  597. 21:16

    saw the use case for the laundry folding

  598. 21:19

    laundry.

  599. 21:20

    A lot of people don't like folding

  600. 21:21

    laundry. I think this is a great use

  601. 21:23

    case. So, is that something that you

  602. 21:25

    guys thinking about? And obviously

  603. 21:27

    there's a cost and all those aspects,

  604. 21:29

    but what's what's your plan in the long

  605. 21:31

    term on this technology?

  606. 21:33

    >> Yeah, so our long-term plan is to

  607. 21:35

    develop, you know, like a robot model

  608. 21:37

    plus hardware platform that can be

  609. 21:39

    deployed anywhere for anyone. So, that

  610. 21:40

    would include, you know, like going

  611. 21:42

    directly to consumers. And you know, our

  612. 21:44

    models today are able to just fold, you

  613. 21:46

    know, uh many kinds of garments. But uh

  614. 21:49

    in terms of like go to market strategy,

  615. 21:51

    our current focus is on enterprise use

  616. 21:53

    cases because I think the distribution

  617. 21:55

    channel is like I think it's easier to

  618. 21:58

    uh work with uh

  619. 22:00

    enterprise customers. Like we can deploy

  620. 22:02

    right away and iterate at customer

  621. 22:04

    sites. But for consumer product, I think

  622. 22:07

    uh I would imagine that it has to be

  623. 22:09

    very very polished and it's less

  624. 22:10

    tolerant for mistakes. And there is a

  625. 22:12

    lot of privacy safety concerns that we

  626. 22:14

    think uh we are

  627. 22:17

    trying to not get into at the current

  628. 22:19

    moment to

  629. 22:20

    uh unblock us from deployments because

  630. 22:23

    we think that the bottleneck for AI

  631. 22:25

    robot is getting AI and hardware

  632. 22:28

    co-working together very very well. And

  633. 22:29

    I think commercial environments provide

  634. 22:31

    ideal testing ground uh for companies

  635. 22:34

    and for the entire field at this stage.

  636. 22:38

    >> Thank you, Jason.

  637. 22:40

    Uh my name is Ahmed and I work in a

  638. 22:43

    in voice AI in in the voice space. And

  639. 22:46

    at least for consumer robots, uh

  640. 22:49

    where I believe humans will want to

  641. 22:51

    issue voice commands to robots, uh can

  642. 22:54

    you talk about how to integrate uh

  643. 22:57

    traditional voice stacks, you know,

  644. 22:59

    which are intent-driven and uh uh

  645. 23:01

    different kinds of models from uh uh

  646. 23:04

    robotic, you know, VLA models.

  647. 23:06

    >> Yeah, that's a great question. So, we

  648. 23:08

    think uh robot human interactions really

  649. 23:11

    important, and it at the end of the day,

  650. 23:13

    right? We want to develop models that

  651. 23:14

    are teachable. So, it'd be really nice

  652. 23:16

    if humans can speak to it, and the robot

  653. 23:18

    does the task. So, the way I think about

  654. 23:20

    it, so I'm not I don't have a speech or

  655. 23:22

    audio background, so what I can think of

  656. 23:23

    is like there is very mature

  657. 23:25

    speech-to-text models, right? So, you

  658. 23:27

    can use that running the on-board to

  659. 23:30

    translate human intent or human speech

  660. 23:33

    into text very quickly, and then, you

  661. 23:36

    know, that's where our reasoning model

  662. 23:38

    and our world model comes into play,

  663. 23:39

    because both of them are able to

  664. 23:41

    interpret text commands. So, that will

  665. 23:43

    allow the model to translate instruction

  666. 23:46

    into actions. But, I think in the

  667. 23:49

    overall stack, the bottleneck is still

  668. 23:51

    on the robot foundation models, because

  669. 23:53

    models today our models and other

  670. 23:56

    people's model are not ready to just

  671. 23:57

    execute any arbitrary commands. So, I

  672. 23:59

    think there's still a gap in terms of

  673. 24:01

    low-level robotic manipulation to get

  674. 24:03

    there. But, I think that's the eventual

  675. 24:05

    goal that we want to get to. Just a

  676. 24:07

    model that can be steerable, that can be

  677. 24:09

    taught by anyone. Yeah.

  678. 24:12

    Okay. Thank you.

  679. 24:14

    >> Um how do you think about, I guess, the

  680. 24:16

    split of intelligence between

  681. 24:19

    the general foundation models that you

  682. 24:21

    all are training, I guess, something

  683. 24:23

    like a task-specific model for something

  684. 24:24

    like laundry folding, and then kind of

  685. 24:26

    some of the on-site specific training

  686. 24:29

    that needs to happen for a specific

  687. 24:30

    deployment in a particular environment?

  688. 24:33

    >> Yeah, I think both are very very

  689. 24:36

    important, right? So, the kind of recipe

  690. 24:38

    that we have is, you know, we have

  691. 24:39

    pre-training, post-training, then we

  692. 24:41

    have some of the sort of active

  693. 24:43

    learning, right? I I think

  694. 24:45

    uh

  695. 24:45

    if you think about, you know, humans,

  696. 24:47

    right? You know, we have like basic

  697. 24:49

    level of like semantic and physical

  698. 24:51

    understanding that allows us to adapt

  699. 24:53

    any physical task very fast, and I think

  700. 24:55

    the best way to even build commercial

  701. 24:57

    grade robots today is by doing that.

  702. 25:01

    Because by doing a lot of generalist

  703. 25:03

    model training have a general

  704. 25:04

    understanding of physical world that's

  705. 25:06

    very useful. And what we have seen, so

  706. 25:08

    this is something I didn't talk about in

  707. 25:10

    the talk is that when the model was

  708. 25:12

    recovering from all kind of errors that

  709. 25:14

    you saw, a lot of that also just came

  710. 25:16

    from interpolating different error

  711. 25:18

    recovery behavior that is gathered from

  712. 25:20

    doing other tasks, right? Just because,

  713. 25:22

    you know, the model has seen thousands

  714. 25:23

    of tasks we had some data to recover

  715. 25:26

    from all kinds of mistakes is able to

  716. 25:29

    just execute that kind of like uh on

  717. 25:32

    demand on a new task it hasn't seen

  718. 25:33

    before. But if you're only specializing

  719. 25:35

    a model from the get-go on one task,

  720. 25:37

    then it's actually missing out on a lot

  721. 25:39

    of the physical knowledge that allows

  722. 25:40

    the model to be more robust than if you

  723. 25:43

    only train on one task. And that's what

  724. 25:44

    we have seen consistently. That's why,

  725. 25:47

    you know, in the beginning of the talk I

  726. 25:48

    also emphasize on having that general

  727. 25:50

    pre-training backbone and then doing

  728. 25:52

    post-training and active learning on top

  729. 25:54

    of that to get to actual commercial

  730. 25:55

    grade usability, not on just one task,

  731. 25:58

    but also the same recipe that can be

  732. 26:00

    repeated across many many tasks.

  733. 26:03

    >> Awesome. Thank you, Jason. Really

  734. 26:04

    appreciate. Um that's a wrap for uh data

  735. 26:07

    session. Uh if you have more questions,

  736. 26:09

    feel free to catch Jason after the

  737. 26:10

    session as well. Uh but yeah, this wrap

  738. 26:13

    our morning session. Uh this afternoon

  739. 26:15

    we have Unity, Skydio, Zoox, uh Waymo,

  740. 26:17

    DeepMind. Um so we'll catch you and see

  741. 26:19

    you AI as well. So we'll see you in the

  742. 26:21

    afternoon. Thank you, everyone.

  743. 26:39

    >> [music]