AI Engineer World's Fair 2026

The Best Models Still Reason Like Toddlers — Andrew Dai, Elorian

Read the talk

The Best Models Still Reason Like Toddlers

Andrew Dai traces counting and video-tracking failures to the gap between recognizing a scene and reasoning through its details, then explains Elorian’s approach to visual thinking and its proposed uses in robotics, construction and mechanical design.

From a talk by Andrew Dai

At a glance

Ideas worth remembering

  • Recognizing an object can supply the wrong answer when a task requires inspecting its visible parts. The partial chessboard and Catan examples show familiar patterns replacing direct counts.

  • Visual reasoning includes tracking changes over time. A robot video requires retaining earlier actions and noticing later ones, beyond identifying the objects in view.

  • Evaluate whether the image’s detailed relationships are necessary to answer the question. Tiny visual tasks and questions answerable from text or rough recognition do not establish readiness for complex visual work.

  • Visual intermediate steps can keep reasoning attached to the scene: locate hotel candidates with boxes, then narrow the selection to red hotels.

  • The proposed applications connect visual reasoning to an existing checking or action system: robot planners and controllers, written construction policies, or programmatic and simulation validation for mechanical designs.

A familiar chessboard becomes the wrong answer

Show a model part of a chessboard and ask how many white squares are visible. In Andrew Dai’s example, the answer is 32: the number on a complete board. The model recognizes the object, supplies a familiar fact about it, and answers a different question from the one asked. Dai, Elorian’s co-founder and CEO, opens with this gap between recognizing a scene and inspecting its contents. These are examples he reports from frontier models, rather than a measured failure rate across all models or prompts.

Source frame: A familiar chessboard becomes the wrong answer
Source frame: A familiar chessboard becomes the wrong answer

The shortcut has a clear causal structure: identify a chessboard, recall that a complete chessboard has 32 white squares, then treat the partial image as though it contained the whole board. Pattern matching makes models useful at identifying plants, animals and flowers. Here, that same strength overrides the evidence needed for counting. The category is correct; the answer about the visible scene is wrong.

Board games make the distinction unusually easy to test. Dai, an enthusiastic collector, challenges the audience to put chess pieces in random positions and ask a model to locate all of them. Recognizing chess does little to solve that task: every piece needs a position grounded in this particular arrangement.

Catan exposes another way to avoid looking closely. Asked how many roads the blue player has on the board, one model response counted 10 blue roads off to the side and inferred that five must be on the board. Dai reports seven when the placed roads are counted directly. The inferred inventory supplies a plausible answer, but the question concerns the pieces actually placed. Extensive thinking does not help if the reasoning starts from a substitute for the visual evidence.

Suggest correction

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

0:13 · section reference included

Video needs remembered changes, not just recognized objects

The next example adds time. A robot arm manipulates a cup and a cooker, lifts a lid, and later turns on the stove. Dai reports that models miss both the lid lift and the stove activation. Identifying the objects is insufficient: an account of the sequence must retain what changed earlier and notice what changes now. He calls the failure “context amnesia”—losing track of events and consistency across a long video.

Source frame: Video needs remembered changes, not just recognized objects
Source frame: Video needs remembered changes, not just recognized objects

Dai’s practical test for separating visual understanding from visual reasoning is to ask how long a person would need to answer. Naming the game, identifying a flower, or counting only three chess pieces can happen in less than a second. Inspecting a crowded board and checking its detailed arrangement takes longer. The one-second test is a design heuristic: it distinguishes a quick recognition task from a task that requires deliberate inspection, rather than establishing a universal timing threshold for model capability.

That distinction matters when designing an application. A prompt that sounds simple can still demand several visual operations: find the relevant objects, distinguish them from nearby objects, inspect their locations, and preserve those distinctions while answering. Dai’s immediate advice is to keep visual tasks simple when relying on existing frontier models. A request for more detailed inspection can move the task into precisely the territory where his examples fail.

Suggest correction

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

3:24 · section reference included

What a visual benchmark actually makes the model do

High benchmark scores can obscure this distinction. In the benchmark discussion, Dai names ARC-AGI and objects to treating reported scores of 85% or 90% as a percentage of progress toward AGI. His resolution criticism concerns tasks he describes as using 32 × 32 or 64 × 64 pixel images: success on a tiny visual problem does not establish an ability to handle the detail in a complex real-world scene. Those dimensions are Dai’s characterization of the tasks, not a verified specification of the benchmark. This is a criticism of transfer from the benchmark to deployment, not a demonstration that small visual puzzles have no reasoning value.

Source frame: What a visual benchmark actually makes the model do
Source frame: What a visual benchmark actually makes the model do

A multimodal science exam can have a different weakness. Dai introduces an evaluation rendered as “MMU” in the captions and describes it as a multimodal extension of MMLU; its exact name remains uncertain. Adding images to text questions does not necessarily make detailed image inspection necessary. Dai describes questions that can be answered without the image, or with only a rough recognition of what it depicts. Such a test can reward scientific knowledge and category recognition while leaving counting, geometry and spatial relationships largely untested.

The proposed change is to evaluate abilities that visual applications actually need, including geometric alignment and spatial intelligence. A useful test must make the relevant relationship in the image necessary to the answer. This is a call for better industry benchmarks; the presentation does not define a consensus process or a completed shared evaluation framework. Dai connects this measurement gap to an opportunity: AI adoption has concentrated on coding, mathematics and documents, while many industries organized around visual work still lack systems that can handle their detailed requirements.

Suggest correction

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

5:44 · section reference included

Generation and detection leave a reasoning gap

Dai calls the missing capability visual thinking. Two established kinds of visual AI explain what he means:

  • Generation: High-fidelity images and videos can look convincing while lacking physical grounding and causal logic. Dai uses explosions and collapsing buildings as examples: Hollywood-style results may reproduce the disaster imagery found in films and game engines. His explanation is that the training distribution rewards that appearance; it is not an analysis of a particular generator’s training corpus.
  • Understanding: Tools such as Google Lens and object detectors map pixels to labels, objects or segmented regions. Dai uses Lens to identify plants and flowers, and names YOLO as an object-detection example. These tools perform useful recognition, but their outputs alone do not answer a complex question about what should happen next.
Source frame: Generation and detection leave a reasoning gap
Source frame: Generation and detection leave a reasoning gap

Visual thinking adds active reasoning about space and time. The intended output is logic useful for planning, agent workflows and physical execution. This follows directly from the earlier failures: a system needs to inspect which objects are present, track their relationships and changes, and turn that information into something an action system can use.

8:038:05
Suggest correction

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

8:03 · section reference included

Make the intermediate steps visual

Elorian’s approach combines four parts:

  • Task-specific data: Collect and generate multimodal data aimed at visual reasoning. Dai says the needed data cannot simply be obtained online.
  • A synthetic data flywheel: Use evaluations, agents, supervised fine-tuning (SFT) and reinforcement learning (RL) to improve the model.
  • Architecture changes: Make improvements on top of a transformer-based architecture.
  • Visual chain of thought: Let intermediate reasoning happen in visual space, rather than expressing all intermediate steps as text.

The presentation gives a concrete example of the last part, but leaves the architecture changes and the detailed operation of the training flywheel unspecified. These ingredients describe the approach without establishing their comparative contribution to performance.

Source frame: Make the intermediate steps visual
Source frame: Make the intermediate steps visual

The concrete question is: how many red hotels are built in this photo? The first step identifies hotels, drawing boxes around hotels and other objects. The next step narrows that visual selection to the red hotels. The observable change is from a photo containing many objects, to boxed candidates, to the subset relevant to the question. Unlike the chessboard shortcut, the intermediate steps remain attached to objects in this image.

What changes between the original photo and the red-hotel selection? The diagram follows the visual intermediate steps, with the bounding-box annotations carried into the narrowing step. Object identification comes before color filtering, so the system can narrow a set of located candidates rather than jump directly from the scene’s general appearance to an answer. The example explains the mechanism; it does not supply a final hotel count or an accuracy result.

The team background connects this proposal to experience building language and multimodal models. Dai describes 12 years at Google Brain and DeepMind, first authorship of work introducing pretraining and fine-tuning, and leadership roles on GLaM, PaLM 2 pretraining and Gemini data. Elorian has roughly 20 people at the time of the talk, including chief reasoning architect Dustin Tran, previously a post-training lead at xAI. This is the experience behind the research direction, rather than evidence that the proposed visual capabilities are already solved.

How it fits togetherFrom a photo to the relevant hotel subset

How many red hotels are built?

The visual chain-of-thought example locates candidates before narrowing them by color. The boxes are visual annotations connecting the located candidates to the red-hotel selection; the diagram does not specify an internal annotation format.

Suggest correction

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

9:48 · section reference included

Connect visual evidence to actions and written rules

Robotics brings the temporal problem back into an action loop. Dai identifies complex, real-time physical actions in dynamic environments as a bottleneck. Static images and directed videos do not provide the same experience as active physical interaction, and he describes existing methods as overengineered and brittle. Elorian’s proposed API would deliver action-relevant scene understanding into existing robot planning and control systems. It is an integration point for better perception and reasoning, rather than a replacement for the entire control stack. At the June 2026 presentation, release by the end of the year was a plan.

Source frame: Connect visual evidence to actions and written rules
Source frame: Connect visual evidence to actions and written rules

Construction adds written rules to the visual scene. Safety requirements can vary by zone and change over time. Detecting a worker or a helmet is only part of the job: a system must connect policy language to the situation at the site and understand the spatial relationships that make the rule relevant. Dai’s examples include counting workers wearing helmets and checking whether construction follows previously defined plans.

The maintenance burden is important. Dai describes training separate models for different use cases and repeatedly retraining them as requirements change. The proposed alternative is a model that handles both language and vision: ground a video stream in written safety regulations, interpret the site policy, and use the camera infrastructure already installed. The practical promise is that policy text can participate directly in the reasoning task; the presentation describes this as a capability being built.

12:2412:27
Suggest correction

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

12:24 · section reference included

Mechanical design needs geometric reasoning and a way to check it

Architecture and mechanical design make counting errors consequential. A house with four bedrooms instead of the requested three is wrong even if it looks like a perfectly plausible house. The board-game problem returns at a larger scale: the system must preserve quantities and spatial constraints while working through a design.

Source frame: Mechanical design needs geometric reasoning and a way to check it
Source frame: Mechanical design needs geometric reasoning and a way to check it

Dai recounts a conversation with a mechanical engineering company: designing one small part of a robot testing platform took 100–200 hours, and he estimated 2,000–3,000 human hours for the whole platform. Those are figures from a reported company conversation, not an industry-wide productivity study. The obstacle he describes is detailed visual context across blueprints, 3D CAD and CAM files. Companies trying frontier models encountered errors in that context, leaving much of the constraint reasoning manual.

The proposed workflow pairs multimodal reasoning with validation. First, extract the geometric logic that matters to the design. Then use programmatic checks or simulation to test whether the mechanical device would work. Dai compares this to running code against unit tests: a design needs a checking mechanism beyond its apparent plausibility. He also suggests that the approach could extend to other design work, including the web and fashion, while keeping mechanical design as the concrete validation example.

Where does checking enter this proposed design workflow? The diagram separates extracting geometric logic from validating it. A simulator provides a test of the mechanical proposal, much as a unit test checks a program; generating or interpreting the design and checking its behavior are distinct jobs.

CAD and CAM quality control is another proposed application. Dai closes with the ambition of using visual reasoning to help produce faster cars, more efficient rockets and better batteries. Software remains useful for testing, but the objects being designed have geometry and physical constraints that must be understood. That is the opportunity the talk leaves open: bring the discipline of reasoning and validation into work whose essential content is visual.

How it fits togetherGeometric reasoning followed by validation

Blueprints, 3D CAD and CAM files.

The proposed workflow connects visual design context to a separate programmatic or simulation check.

Suggest correction

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

14:46 · section reference included

Read the complete timestamped transcript
  1. 0:01

    [music]

  2. 0:13

    Hi, thanks for coming everyone. Um, I'm

  3. 0:17

    the co-founder and CEO of Elorium and

  4. 0:20

    I'm here to talk about some of the

  5. 0:23

    issues with current models, current

  6. 0:26

    frontier models. This includes um Claude

  7. 0:30

    Chat GBD and Gemini um and how they

  8. 0:33

    handle visual problems and um uh this

  9. 0:37

    might be new to some of you who don't

  10. 0:40

    work in the visual space but actually

  11. 0:42

    there's quite a big gap between how

  12. 0:44

    these models handle visual reasoning and

  13. 0:47

    how humans deal with it. And you will

  14. 0:50

    see that we're actually quite far away

  15. 0:52

    from any definition of AGI for visual

  16. 0:56

    reasoning.

  17. 0:58

    So here are some examples of where uh

  18. 1:02

    how easy it is to find where models

  19. 1:04

    break down. And um you can find these

  20. 1:07

    examples yourself. Just takes a few

  21. 1:09

    minutes. Uh in this first example uh we

  22. 1:12

    have a chessboard hallucination and we

  23. 1:16

    give the models um this picture and ask

  24. 1:20

    how many white squares are in the image

  25. 1:23

    and any ordinary person uh who doesn't

  26. 1:26

    hallucinate would probably not say it's

  27. 1:29

    32. So 32 of course the models say this

  28. 1:33

    because they see part of the chessboard

  29. 1:35

    and they hallucinate the complete board

  30. 1:38

    and as a result they give the wrong

  31. 1:40

    number and you see this quite a lot that

  32. 1:43

    models rely a lot current models rely a

  33. 1:45

    lot on pattern matching. That's what

  34. 1:47

    makes them so good at identifying plants

  35. 1:50

    and animals and flowers uh in the real

  36. 1:52

    world. But when it comes to like complex

  37. 1:55

    questions that part hurts them. So the

  38. 1:58

    pattern matching is actively hurting

  39. 1:59

    them in this case. Um so in their in

  40. 2:04

    what's going on in their reasoning is

  41. 2:05

    that oh this is a chess board. Chess

  42. 2:07

    boards all have 32 squares. Therefore

  43. 2:09

    this one must have 32 Y squares too. On

  44. 2:13

    the right example um I'm a big board

  45. 2:16

    game player. Have quite a collection. Um

  46. 2:19

    so you can see there's a a board game

  47. 2:21

    theme going on here. And actually you

  48. 2:22

    can uh reproduce this outside if you

  49. 2:25

    just go to you know outside the talks.

  50. 2:27

    It's a ball game area there. There are

  51. 2:29

    chess boards. Um I will bet if any of

  52. 2:32

    you uh place the pieces in some kind of

  53. 2:35

    random position, no frontier model will

  54. 2:38

    be able to tell you where those pieces

  55. 2:40

    are located, where all those pieces are

  56. 2:41

    located. Um and then another example

  57. 2:44

    here is katan. Um here another very

  58. 2:48

    simple question. How many rows does the

  59. 2:49

    blue player have? Um, these frontier

  60. 2:52

    models think extensively about this

  61. 2:54

    problem. Uh, one response I've seen is

  62. 2:56

    that, oh, the the guy has uh 10 blue

  63. 3:01

    rows off to the side of the board.

  64. 3:02

    Therefore, there must be five uh blue

  65. 3:05

    rows on the can board. Uh, but obviously

  66. 3:08

    that's not true. There's seven if you

  67. 3:10

    actually count. So these models um again

  68. 3:13

    are great at guessing uh great at

  69. 3:16

    pattern matching but they are not very

  70. 3:18

    spatially grounded and they just can't

  71. 3:20

    handle any kind of detailed questions.

  72. 3:24

    Um and then finally um we have this

  73. 3:26

    example where it actually um affects

  74. 3:30

    robots where here you have a robot arm

  75. 3:33

    uh manipulating this uh cup and um uh

  76. 3:38

    cooker basically and the

  77. 3:41

    state-of-the-art models today they miss

  78. 3:43

    the fact that the uh robot arm lifted

  79. 3:47

    the lid um and at the end they also

  80. 3:49

    missed the fact that the robot is

  81. 3:51

    turning on the stove like right now. So

  82. 3:53

    there's uh essentially context amnesia

  83. 3:56

    happening. Um and this is because these

  84. 4:00

    models can't maintain consistency um

  85. 4:03

    across long videos and they very easily

  86. 4:06

    lose track of what's happening. And a

  87. 4:09

    very common question I get is how do you

  88. 4:11

    define a visual reasoning problem versus

  89. 4:14

    a visual understanding problem? Um or

  90. 4:18

    you could say like visual thinking um

  91. 4:20

    compared to visual understanding. I

  92. 4:22

    think a very simple way to do it is just

  93. 4:25

    um ask yourself the same question. If

  94. 4:28

    you looked at an image or a video, how

  95. 4:31

    long would it take you to answer the

  96. 4:33

    question? So uh for example, in both of

  97. 4:36

    these cases, I doubt anyone in this room

  98. 4:39

    would be able to give an answer uh if

  99. 4:41

    they were only allowed one second to

  100. 4:42

    look at the image. So 1 second isn't

  101. 4:44

    enough to do these kind of like complex

  102. 4:47

    questions also called like system two um

  103. 4:50

    kind of thinking in Daniel Canon's book.

  104. 4:53

    But if I asked you what game is this uh

  105. 4:57

    or similarly what flower is this or if

  106. 5:00

    there are only three pieces on the

  107. 5:01

    chessboard if I asked you how many

  108. 5:02

    pieces are there those questions uh I'm

  109. 5:05

    sure all of you would be able to answer

  110. 5:07

    in less than a second and similarly all

  111. 5:09

    the frontier models would get that kind

  112. 5:10

    of question right. So that is the

  113. 5:12

    distinction um that we make between what

  114. 5:15

    is understanding uh what is like pattern

  115. 5:18

    recognition versus what is reasoning

  116. 5:20

    where you actually have to look in

  117. 5:22

    detail at the picture and um look at

  118. 5:25

    various things and this is exactly where

  119. 5:27

    frontier models uh fall apart today. So

  120. 5:31

    as you are designing your own systems uh

  121. 5:33

    that's something to keep in mind keep

  122. 5:35

    these visual tasks very simple otherwise

  123. 5:38

    you will have hallucinations a lot and a

  124. 5:40

    lot of hallucinations

  125. 5:44

    um so uh this leads into evals of course

  126. 5:48

    um frontier models there are already a

  127. 5:52

    bunch of multimodal reasoning evals or

  128. 5:54

    visual reasoning evals some that you

  129. 5:56

    might have heard of is arc agi this is

  130. 5:59

    uh quite often

  131. 6:00

    brought up to um people saying oh we the

  132. 6:04

    frontier models are 85% or 90% on RKGI

  133. 6:07

    therefore we are 90% of the way to a uh

  134. 6:10

    to AGI itself uh but I think these

  135. 6:13

    people they haven't really looked at any

  136. 6:15

    of the benchmark data because if you

  137. 6:17

    actually look at the data you will

  138. 6:19

    notice that the images are only 32x 32

  139. 6:22

    or 64x 64 pixels and I would challenge

  140. 6:26

    anyone uh to give me like a real world

  141. 6:30

    complex task that can be reduced to a

  142. 6:32

    32x 32 pixel problem. Um I think you'll

  143. 6:36

    very quickly realize almost no tasks

  144. 6:38

    almost no interesting tasks can be

  145. 6:40

    reduced to that kind of resolution.

  146. 6:42

    Another eval that people commonly uh

  147. 6:45

    bring up is MMU. Uh this is the massive

  148. 6:48

    multiddiscipline multimodal

  149. 6:50

    understanding. This is a step up from

  150. 6:51

    MMLU because it has um images rather

  151. 6:55

    than just pure text science questions.

  152. 6:57

    This is science questions based on

  153. 6:58

    images. But still images are a minor

  154. 7:02

    part of a lot of these questions. A lot

  155. 7:03

    of the questions you can just answer

  156. 7:05

    without looking at the image or just

  157. 7:07

    doing some pattern recognition just

  158. 7:08

    knowing roughly what the image is about.

  159. 7:11

    So what we really need is new visual

  160. 7:14

    reasoning benchmarks in the industry

  161. 7:16

    that really target the things that

  162. 7:18

    people care about like geometric align

  163. 7:21

    alignment, spatial intelligence, um

  164. 7:24

    object terminus and these are really

  165. 7:27

    critical for AI to be deployed in these

  166. 7:30

    visual use cases. And you might have

  167. 7:32

    noticed that still in a lot of

  168. 7:34

    industries that uh are primarily visual

  169. 7:38

    um which I will go into there isn't much

  170. 7:41

    uptake of AI right a lot of the AI

  171. 7:43

    uptake has been in the software

  172. 7:44

    engineering world and in the

  173. 7:46

    mathematician world um and in like

  174. 7:48

    documents um document handling etc. But

  175. 7:51

    this uh there is actually a huge gap

  176. 7:54

    huge opportunity that is just being

  177. 7:57

    looked over right now um based on the

  178. 8:00

    interest in coding.

  179. 8:03

    [clears throat] And so the missing

  180. 8:05

    paradigm in visual AI is thinking. So we

  181. 8:09

    have generation models very high quality

  182. 8:12

    generation models like bite dances

  183. 8:14

    seance model. Um, so we have these very

  184. 8:18

    high fidelity models and they look

  185. 8:20

    great, but they lack actual physical

  186. 8:22

    grounding um and causal logic. So you

  187. 8:24

    will you probably notice that if you ask

  188. 8:26

    these models to produce a a picture um a

  189. 8:29

    video of a some like uh something

  190. 8:32

    blowing up like um or a building falling

  191. 8:35

    down or these things they look very

  192. 8:37

    cartoonish they look Hollywood style

  193. 8:39

    kind of things and that's because they

  194. 8:41

    are just outputting what was in the

  195. 8:43

    training data and a lot of disaster

  196. 8:45

    videos um a lot of like action kind of

  197. 8:48

    videos on the internet are just going to

  198. 8:50

    be from Hollywood or game engines. So

  199. 8:52

    they're working to reproduce that and

  200. 8:54

    that's fundamentally a problem because

  201. 8:56

    it means they can be no better than

  202. 8:57

    those kind of uh videos. Um on

  203. 9:00

    understanding the what we are where we

  204. 9:03

    currently are is we have lot of tools

  205. 9:06

    that can map pixels to semantic labels

  206. 9:07

    like Google lens is obviously great to

  207. 9:10

    identify plants and flowers and I use

  208. 9:13

    that all the time. The SAM 3 for

  209. 9:15

    segmentation, YOLO for uh object

  210. 9:18

    recognition detection, mascaras CNN.

  211. 9:20

    These are of course highly robust and

  212. 9:22

    they're used everywhere in the industry,

  213. 9:24

    but they're fundamentally passive. So

  214. 9:25

    there's no reasoning capability to them.

  215. 9:27

    So they can't answer more complex

  216. 9:29

    questions. Um and really where the

  217. 9:31

    frontier is is uh with thinking visual

  218. 9:34

    thinking models. These models will have

  219. 9:36

    active spatial and temporal

  220. 9:38

    intelligence. They can extract actional

  221. 9:40

    logic for planning uh agentic workflows

  222. 9:44

    and physical execution.

  223. 9:48

    And so our approach uh is uh four stage.

  224. 9:52

    So we are collecting and generating our

  225. 9:55

    own uh multimodal data uh visual

  226. 9:58

    reasoning specific data. This this kind

  227. 10:00

    of data we found you just can't uh get

  228. 10:02

    online. Uh we have a synthetic data

  229. 10:05

    flywheel using evals agents SFT and RL

  230. 10:08

    to improve the model. We're making some

  231. 10:10

    uh we made some advances to the

  232. 10:12

    architecture um in terms of uh various

  233. 10:15

    different time um advance various

  234. 10:17

    different improvements on top of the

  235. 10:18

    transformer-based architecture and we're

  236. 10:21

    also enabling visual chain of thought

  237. 10:23

    reasoning and this is one of the key

  238. 10:25

    things that humans have that no frontier

  239. 10:27

    model has today since the frontier

  240. 10:29

    models are only textual uh chain of

  241. 10:31

    thought based

  242. 10:33

    um and this is one example of a visual

  243. 10:35

    chain of thought. So the question is

  244. 10:36

    like how many red hotels are built in

  245. 10:39

    this photo? Then the model realizes oh

  246. 10:43

    uh first we need to identify all the

  247. 10:45

    hotels. So it draws boxes around hotels

  248. 10:49

    um and other objects and then uh it

  249. 10:52

    reduces that to the red hotel. So it's

  250. 10:54

    this multi-step uh process happening in

  251. 10:57

    the visual space natively.

  252. 11:01

    So um about our company um I'm the

  253. 11:05

    co-founder and CEO. I spent the last 12

  254. 11:07

    years at Google Brain and Deep Mind. Um

  255. 11:10

    I developed a lot of the foundational

  256. 11:12

    techniques for the model for modern

  257. 11:13

    LLMs. 11 years ago I was the first

  258. 11:16

    author of the work that introduced

  259. 11:18

    pre-training and fine-tuning. That's the

  260. 11:20

    work when combined with the transformer

  261. 11:22

    paper in 2017 led to the GBT series of

  262. 11:25

    models. So all the GBT uh papers site

  263. 11:27

    our paper. Um I co-led the earlye models

  264. 11:31

    uh the first model that was

  265. 11:32

    state-of-the-art called glam and then um

  266. 11:35

    more recently I co-led the palm to 2

  267. 11:37

    pre-training architecture and I was

  268. 11:39

    co-lead for the gemini data area and my

  269. 11:42

    co-founder info

  270. 11:45

    and Google research he led research for

  271. 11:47

    Apple's first public multimodal model

  272. 11:49

    MM1 and he's has a a lot of experience

  273. 11:54

    in visual reasoning um across uh

  274. 11:57

    language as

  275. 11:59

    And this is our team. So we're roughly

  276. 12:02

    20 people now. Um we've also have a

  277. 12:06

    chief reasoning architect Dustin Tran.

  278. 12:07

    Previously he was lead of post training

  279. 12:09

    at XAI. Um and we've hired a world-class

  280. 12:14

    team um across uh many other uh

  281. 12:17

    companies like Apple uh XAI um deep mind

  282. 12:20

    Amazon and so on.

  283. 12:24

    Um and in terms of the uh use cases that

  284. 12:27

    I mentioned, robotics is one primary use

  285. 12:30

    case. So robots have uh really critical

  286. 12:33

    bottlenecks performing complex real-time

  287. 12:36

    physical actions uh in these kind of

  288. 12:38

    like dynamic environments. Uh but

  289. 12:40

    existing vision models uh you probably

  290. 12:43

    realize are trained from static images

  291. 12:45

    and very directed videos. They are not

  292. 12:48

    like act they don't have active physical

  293. 12:50

    interaction. So existing methods are

  294. 12:53

    overengineered and brittle. Um and uh we

  295. 12:57

    are planning to release a model API

  296. 12:59

    available uh by the end of this year. Um

  297. 13:02

    and at that point the API can be used to

  298. 13:06

    deliver action relevant uh scene

  299. 13:09

    understanding into existing um planning

  300. 13:13

    and control systems for these um robots.

  301. 13:16

    Another important use case for uh visual

  302. 13:20

    reasoning um is construction. So

  303. 13:23

    construction sites they have these very

  304. 13:26

    complex zone specific safety rules. Um

  305. 13:30

    and uh computer vision can't adapt fast

  306. 13:32

    enough to changing safety rules. They

  307. 13:35

    also can't interpret things like OSHA

  308. 13:38

    policy language and match the that

  309. 13:42

    language to what's actually going on at

  310. 13:44

    the site or understand the spatial

  311. 13:46

    relationships that are important there.

  312. 13:48

    For example, like how many of these

  313. 13:49

    workers are wearing helmets or like is

  314. 13:52

    the construction um happening according

  315. 13:56

    to the plans that uh were defined

  316. 13:58

    earlier.

  317. 14:00

    And um currently enforcing these rules

  318. 14:03

    require training separate models for

  319. 14:05

    different use cases uh because they're

  320. 14:07

    very these models as I said before are

  321. 14:09

    very brittle. So you constantly have to

  322. 14:11

    do uh retraining. Um and our approach uh

  323. 14:15

    with the video um understanding

  324. 14:17

    capabilities that we are building into

  325. 14:18

    our models is um allows you to um ground

  326. 14:23

    these video streams in the safety

  327. 14:26

    regulations. And of course the safety

  328. 14:27

    regulations are in text, they're in

  329. 14:29

    language. So you have to be um the model

  330. 14:32

    has to manipulate both language and

  331. 14:33

    vision very well.

  332. 14:35

    And um yeah uh this will allow these

  333. 14:38

    models to interpret uh site policies

  334. 14:41

    using the current camera infrastructure

  335. 14:44

    that they have.

  336. 14:46

    Um and then finally architecture and

  337. 14:49

    design we think is also a very uh

  338. 14:52

    promising use case here. Uh this is

  339. 14:55

    exactly the use case where you need to

  340. 14:57

    be very detail oriented. So back to the

  341. 14:59

    board game example around counting

  342. 15:02

    spatial relationships. This shows up a

  343. 15:04

    lot in architecture and design. Uh like

  344. 15:07

    if you design a if you design a house

  345. 15:10

    with with four bedrooms instead of

  346. 15:11

    three, that homeowner is going to be

  347. 15:13

    very angry, right? Um so obviously

  348. 15:16

    counting is actually important. Um and

  349. 15:20

    also just understanding these spatial

  350. 15:22

    constraints, real world constraints is

  351. 15:25

    uh is a very manual process uh these

  352. 15:28

    days. We spoke to a mechanical

  353. 15:31

    engineering company just a few weeks ago

  354. 15:33

    and they said to design one small part

  355. 15:36

    of a robot testing platform takes 100 to

  356. 15:40

    200 hours uh of the time to design the

  357. 15:43

    entire testing platform. Um, I believe

  358. 15:46

    it takes 2,000 to 3,000 hours of human

  359. 15:50

    uh time there. And they've uh a lot of

  360. 15:54

    these places they've tried frontier

  361. 15:56

    models, but they just don't work for

  362. 15:58

    these use cases. They really struggle to

  363. 16:00

    understand uh visual context across

  364. 16:03

    these like architecture blueprints, 3D

  365. 16:05

    CAD, CAM files. Um, and so there are

  366. 16:08

    lots of errors there. Um and similarly

  367. 16:12

    we believe that this can be useful

  368. 16:13

    useful for other kinds of design as well

  369. 16:15

    not just um architecture and engineering

  370. 16:18

    but maybe like designing

  371. 16:21

    um yeah for the web or fashion or other

  372. 16:23

    things and our approach is uh we're

  373. 16:26

    using multimodal reasoning to uh to

  374. 16:30

    extract um this uh geometric logic

  375. 16:33

    that's important. We're allowing

  376. 16:35

    programmatic validation or simulation

  377. 16:38

    validation. Just like in code, you can

  378. 16:40

    run code against unit tests. You can

  379. 16:43

    also run u mechanical devices through

  380. 16:46

    simulators that have been developed

  381. 16:47

    through seammens um and uh v various

  382. 16:50

    other companies to see if something will

  383. 16:52

    work in the real world. So there's a lot

  384. 16:54

    of parallels actually between uh this

  385. 16:57

    kind of like mechanical design and

  386. 16:58

    coding itself. But mechanical design is

  387. 17:01

    still relatively untouched by AI.

  388. 17:04

    Um and yeah, CAD CAM quality control is

  389. 17:07

    another potential use case and

  390. 17:09

    ultimately we believe that this is going

  391. 17:11

    to be a critical step to the future of

  392. 17:14

    mechanical design where the where AI can

  393. 17:18

    make faster cars, more efficient

  394. 17:20

    rockets, better batteries and all these

  395. 17:23

    things cannot be done just with code. Uh

  396. 17:26

    people are not coding up the next iPhone

  397. 17:27

    or coding up the next uh SpaceX rocket.

  398. 17:31

    It's all fundamentally very visual.

  399. 17:36

    So, um you can find out more about us

  400. 17:39

    through our website um lauren.ai, our

  401. 17:43

    Twitter page xx.comai

  402. 17:46

    or our LinkedIn uh page. And yeah, happy

  403. 17:50

    to take any questions. I'll be standing

  404. 17:53

    around here for for a little bit.

  405. 17:55

    Thanks.

  406. 17:58

    [applause]