AI Engineer World's Fair 2026

Modality Misalignment and Originality Attribution in Short-Form Video — Aditya Gautam, Meta

Read the talk

Modality Misalignment and Originality Attribution in Short-Form Video

Aditya Gautam of Meta explains how specialized vision-language models divide perception, retrieval, and review to catch brief content changes and investigate copied videos—and how training, evaluation, and selective processing make that architecture practical at scale.

From a talk by Aditya Gautam

At a glance

Ideas worth remembering

  • Time-linked clip evidence makes a brief topic change inspectable: the perceiver extracts it, and the reviewer compares it with surrounding content.

  • Offline indexing and clustering prepare the corpus for online retrieval; topics, embeddings, and entities supply different routes to similar clips and authors.

  • Production failures need trace diagnosis before correction: reasoning, tool calls, and retrieval can each cause a poor final result.

  • Choose specialized model sizes and reasoning budgets against domain quality, latency, and cost, while checking the LLM judge against fresh human labels.

  • Frame compression, cached decisions, and metadata pruning save work at different stages; ongoing evaluation and monitoring keep those optimizations useful as the data changes.

A brief change can alter what a video is doing

A video can begin with the subject a viewer expected, then slip in an advertisement or political message for a small part of its runtime. Finding that insertion requires understanding where the content changes, down to clips and frames. In this recording, Aditya Gautam of Meta pairs that problem with another: finding copied or transformed videos and identifying their source.

Source frame: A brief change can alter what a video is doing
Source frame: A brief change can alter what a video is doing

The operating conditions make both tasks difficult. The data spans 100 million plus videos, includes viral and adversarial content, and carries multilingual text inside images and video. Uploads change as new AI tools appear, so the distribution moves from month to month. There is also no clear ground truth for the problems being solved; the system must work with judgments whose meaning depends on the content and the task.

Comparing modalities is the simpler starting point: represent images, video, audio, or text with embeddings and compare their cosine similarity. The harder task here is detecting a change within a video over time. A representation of the whole video does not by itself locate the small interval where an unexpected message appears. That calls for granular visual understanding and temporal analysis.

Originality adds a different comparison: the uploaded video against other content in the corpus. AI tools make duplication and transformation easier, which complicates attribution and credit. Repeated copies also produce user fatigue. Detecting similarity is therefore useful both for investigating a video's source and for understanding why viewers keep encountering versions of the same content.

2:372:41
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

Separate seeing the video from judging its timeline

The architecture divides content understanding, retrieval, and reasoning because each needs specialized work. That division has a condition: if one agent or one language model can solve the problem, there is no need to add a multi-agent system. Here, a reviewer receives the video or clip ID and acts as the central orchestrator, asking a perceiver to gather the visual evidence.

Source frame: Separate seeing the video from judging its timeline
Source frame: Separate seeing the video from judging its timeline

The perceiver fetches the video from the database and divides it into smaller parts using semantic embeddings and temporal changes. It does not sample at a fixed frame rate. Instead, it finds changes and compresses similar frames into one or two representative frames. The segmentation algorithm is outside the recording's scope, but its purpose is clear: reduce repeated visual work while retaining the places where the video changes.

Each clip becomes structured evidence: embeddings, tags, OCR, a natural-language description, and timestamps or frame ranges. The perceiver passes that information to the reviewer as a JSON object. This separates the visual extraction task from the temporal judgment: the reviewer can compare what happened in successive intervals using descriptions and metadata tied to their locations.

The concrete example is a sports video through the first six seconds, followed by political content from six to 6.5 seconds. The observable change is only half a second long. Once the perceiver represents those intervals separately, the reviewer can compare their topics, locate the transition, and consider whether it is a misalignment or a larger issue. The topic change becomes evidence for a judgment rather than an automatic verdict.

How does a fleeting insertion become something the reviewer can inspect? The diagram follows the sports example from its two time intervals into clip metadata and then a temporal comparison. The important relationship is between content and location: retaining both lets the reviewer identify the half-second change instead of treating the video as one undifferentiated subject.

How it fits togetherPreserving the half-second change

The initial interval establishes the video's preceding topic.

Time-linked clip evidence lets the reviewer compare the political interval with the preceding sports content.

3:513:53
Suggest correction

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

3:49 · section reference included

Search the corpus through topics, embeddings, and entities

The reviewer then asks the retriever for similar clips, supplying the video and metadata it has already deduplicated and post-processed. Retrieval extends the investigation beyond the current timeline: the system can compare the upload with other clips, entities, topics, and authors in the corpus.

Source frame: Search the corpus through topics, embeddings, and entities
Source frame: Search the corpus through topics, embeddings, and entities

Different signals need different search structures:

  • Topics → inverted index. A topic points to the videos associated with it, giving retrieval a direct route from a named subject to matching content.
  • Embeddings → vector database. Clip and video representations support similarity search across the corpus.
  • Entities → graph database. Extracted entities provide another way to retrieve related content alongside topics and embeddings.

Using these stores together gives online inference several routes to relevant candidates and is intended to improve recall.

Much of this preparation happens offline. The perception machinery can run as a library in large-scale batch analysis; a Ray cluster is one example given. The resulting metadata is indexed, and periodic clustering assigns embedding and cluster IDs to clips and whole videos. Online retrieval then uses the query's clip ID and metadata to search those prepared stores, rather than rebuilding the corpus organization for every request.

Similarity produces candidates, which still need sorting. The retriever finds similar clips and authors, reranks them, and can use traditional classifier scores to identify spam or low-quality candidates. It returns the leading candidates to the reviewer. The reviewer combines them with the original content signals and can ask for more retrieval if the available evidence is insufficient. This supplies comparisons for the originality task; the recording does not specify a rule that conclusively selects the original creator from those matches.

6:306:33
Suggest correction

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

6:30 · section reference included

Add what viewers are experiencing now

The reviewer has two kinds of content evidence by this point: temporal signals from the video itself and comparisons with similar clips and authors. It also receives real-time interaction signals—reports, likes, dislikes, comments, and comment sentiment. Those signals capture responses that offline analysis and visual models can miss.

Source frame: Add what viewers are experiencing now
Source frame: Add what viewers are experiencing now

The reason to incorporate them is temporal as well as semantic. A change in sentiment or response may matter while the video is circulating, even though its pixels have not changed. Tools let the reviewer consider that evolving response alongside what the video contains. User interaction becomes an additional input to understanding the video.

9:509:51
Suggest correction

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

9:50 · section reference included

Train small VLMs for the data and the output

All three agents use specialized small vision-language models, or VLMs. The motivation is the amount of visual work: processing billions of frames needs compression and economical serving. Model preparation therefore includes pretraining, fine-tuning, distillation, and quantization, with each model aimed at its particular task.

Source frame: Train small VLMs for the data and the output
Source frame: Train small VLMs for the data and the output

Pretraining addresses a mismatch in the visual data. Gautam contrasts the clean web data used by available foundational models with messy, in-house, user-generated content created for this workflow. Training on those image tokens and language adapts the vision component to the actual input distribution. That work is expensive, so the decision depends on whether it produces a useful improvement over adapting an existing encoder.

Instruction fine-tuning teaches the task and the form of the answer. The training data includes policies, guidelines, content signals, and desired outputs in a JSON schema, including misalignment or duplication scores and reviewer reasoning. In the model architecture, a vision encoder processes the clip, a projector bridges its representation to the language model, and the language model produces the instructed output.

The context gives each model its role, policy, available tools, and relevant metadata in a brief form. In-house labels define the issues and the output a human reviewer should receive. These two training stages solve different problems: visual pretraining improves understanding of the input, while instruction tuning teaches how to use the supplied context and express the result in a form the pipeline can process.

7:517:53
Suggest correction

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

10:38 · section reference included

Trace production failures before retraining

The next stage is a DPO improvement loop built around production examples. A subsample of inference results passes through an in-house LLM judge trained on human-labeled data, followed by a human review queue. The recording uses 95% as an illustrative performance threshold; it does not report an achieved result or define a benchmark metric for that number.

Source frame: Trace production failures before retraining
Source frame: Trace production failures before retraining

A poor result must be traced through the system before it becomes a training target. Human reviewers inspect agent traces, model calls, and tool interactions to find whether the failure came from reasoning, a wrong tool call, or retrieval that did not work. The correction may belong in the model or in the surrounding harness. A final wrong answer alone does not identify which component needs changing.

Once the needed improvement is understood, positive and negative examples support retraining. Daily production sampling keeps the loop supplied with fresh data and helps reveal drift. It also checks how the LLM judge is doing. The evaluator is part of the system that must keep learning, rather than a permanently reliable reference outside it.

Where does an incorrect production result turn into an improvement? The loop below places trace diagnosis between evaluation and retraining. That step matters because it separates a model's mistaken judgment from a tool or retrieval failure, allowing the correction to reach the component that caused it.

How it fits togetherProduction examples feed targeted improvement

Subsample real results daily to track performance and drift.

Daily samples support evaluation, trace diagnosis, and new training examples; human review also checks the judge.

13:4013:44
Suggest correction

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

13:40 · section reference included

Choose model size against the whole system's cost

The model only needs to solve this internal domain problem. Gautam's useful test is blunt: “I really don't care if the model can solve a coding problem.” Frontier-sized VLMs carry inference cost and complexity that this workload cannot afford. Off-policy and on-policy knowledge distillation, followed by experiments with quantization, produce smaller candidates for deployment.

Source frame: Choose model size against the whole system's cost
Source frame: Choose model size against the whole system's cost

The decision comes from a table of model sizes and compression choices: which candidates preserve acceptable domain performance, and which save compute and inference cost? The recording does not provide the candidate sizes or measured savings. Its decision rule is to choose compression against task quality and production resources together, rather than assume that the smallest model is sufficient.

Evaluation begins with precision, recall, and F1 for task success, then opens up the pipeline:

  • Retrieval quality and latency. Check how well retrieval finds relevant content and how long it takes, rather than attributing every final error to the reviewer.
  • Reasoning quality and budget. Inspect whether the reviewer is overthinking. Reduce its budget when less work suffices; consider increasing planning or reasoning effort for more complex cases.
  • Failures by component. Track edge cases and error rates at the nodes and hooks where tool calls, retrieval, or model behavior fail.
  • System efficiency. Measure token cost and latency for each agent and for the combined system.

These measurements connect a final judgment to both its cause and its cost.

The judge needs its own evaluation against the human queue. User-generated content keeps drifting, so a judge that worked on an earlier distribution may need retraining on new labels. Otherwise, the improvement loop risks relying on an evaluator that has itself fallen behind the data.

16:0516:10
Suggest correction

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

16:05 · section reference included

Save work before invoking the full pipeline

The final optimizations reduce how much content needs expensive processing in the first place. They operate at different levels:

  • Similar frames. Spatial-temporal reduction compresses repeated frames, reducing visual work within a video.
  • Repeated content. Caching lets highly similar viral content reuse a decision and skip the multi-agent pipeline.
  • Candidate videos. Metadata pruning narrows the set sent for review. Topics and creator history can inform the choice, including authenticity scores, video quality, and engagement.

The first reduces the input, the second avoids repeated inference, and the third decides which videos enter the system.

Source frame: Save work before invoking the full pipeline
Source frame: Save work before invoking the full pipeline

Those shortcuts make selection consequential. The sports example requires retaining a brief change; caching requires deciding when similarity is high enough to reuse a judgment; metadata pruning uses a creator's record to skip processing. The recording describes these mechanisms without giving their decision thresholds or error tradeoffs, so they are design choices to evaluate alongside the pipeline they bypass.

The closing advice keeps decomposition conditional and evaluation central. Divide the problem when specialized work requires it, adapt optimization to cost feasibility, and keep production monitoring and qualitative improvement running. On changing, adversarial video data, maintaining the system means continuing to inspect what it misses, what its tools do, and how its judgments compare with human review.

19:3019:32
Suggest correction

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

19:30 · section reference included

Read the complete timestamped transcript
  1. 0:01

    [music]

  2. 0:12

    Hello everyone. Uh I am Adita and we

  3. 0:15

    will be talking about uh two main

  4. 0:17

    problems that happen on the short form

  5. 0:19

    surfaces. We are going to talk about how

  6. 0:21

    do we deal with these things at a scale.

  7. 0:23

    Uh

  8. 0:25

    so to get started first thing is we will

  9. 0:27

    understand what are the characteristics

  10. 0:28

    of the data that we are trying to deal

  11. 0:30

    with what are the two main problems that

  12. 0:32

    we are actually working on uh and what

  13. 0:35

    are the multi- aent systems to solve

  14. 0:37

    those problems at a scale what are the

  15. 0:40

    different specialized small scale WM

  16. 0:42

    that we can uh build uh to solve those

  17. 0:45

    individual agentic problem and how do we

  18. 0:48

    build those agents what are the

  19. 0:49

    different ways to actually optimize it

  20. 0:51

    like to make it like scalable at a very

  21. 0:53

    big scale and then we will be looking

  22. 0:56

    into the evaluation in a very holistic

  23. 0:58

    360 manner not just like a precision

  24. 1:00

    recall what is out there how do we

  25. 1:02

    understand the entire multi-agenting

  26. 1:04

    pipeline both from LLM level tools MCP

  27. 1:07

    and whatn not everything out there and

  28. 1:09

    then we will be getting into the

  29. 1:10

    optimization techniques which this which

  30. 1:12

    are very vision specific and metadata

  31. 1:15

    specific which will allow us and give us

  32. 1:17

    some intelligence to tell that we really

  33. 1:20

    don't need to do intell like this

  34. 1:21

    intelligent like workflow So for all the

  35. 1:23

    videos we can figure out what are the

  36. 1:25

    small set of videos which should be the

  37. 1:27

    candidate for doing these things and we

  38. 1:29

    will conclude with the takeaways.

  39. 1:32

    So the real life data is very messy. It

  40. 1:35

    is we are talking about at a scale of

  41. 1:37

    100 million plus and a lot more viral

  42. 1:39

    content. There's a lot of adversal

  43. 1:41

    content people are trying to gain the

  44. 1:43

    system. There are a lot of uh

  45. 1:44

    multilingual text on the screens and in

  46. 1:46

    their videos and images. And the uh data

  47. 1:50

    is very dynamic. it keeps on changing

  48. 1:52

    from like month to month different AI

  49. 1:53

    tools are coming everything out there so

  50. 1:55

    it's it's really really dynamic that

  51. 1:57

    means there is a lot of drift issues and

  52. 1:58

    other thing that comes with a video data

  53. 2:01

    and then we know that there is no clear

  54. 2:03

    ground truth for the problem that we're

  55. 2:05

    trying to solve so these are like

  56. 2:06

    existing problem which happens in a real

  57. 2:08

    world video data set we will be the

  58. 2:11

    first problem that we will be talking

  59. 2:13

    about is the modality misalignment where

  60. 2:15

    the first is intramodality which is a

  61. 2:18

    very solved problem you can have a clip

  62. 2:20

    model you can have a modality on uh uh

  63. 2:23

    images, videos, uh audio, text and

  64. 2:25

    figure out what exactly is the cosign

  65. 2:27

    similarity on those embedding and figure

  66. 2:28

    it out. So this is a much simpler

  67. 2:30

    problem. What we will be talking about

  68. 2:33

    how we are doing intraodality u issues.

  69. 2:37

    So this is consider that like a video we

  70. 2:39

    have a big video and then uh suddenly

  71. 2:41

    you are seeing something some ad agenda

  72. 2:43

    some political things or something out

  73. 2:45

    there which shouldn't be there in the

  74. 2:47

    video as when you clicked on it. So how

  75. 2:49

    do we actually look into the small

  76. 2:51

    segments of the uh video understand this

  77. 2:54

    problem and figure out where there is an

  78. 2:56

    anomaly or kind of like adversarial

  79. 2:58

    behavior out there which shouldn't be

  80. 2:59

    there in the first place. So this is the

  81. 3:01

    first problem which requires a lot of

  82. 3:03

    granular understanding vision

  83. 3:05

    understanding and a video understanding

  84. 3:06

    to see what is happening at a very clip

  85. 3:08

    and a very frame level. The second

  86. 3:10

    problem is uh to understand the

  87. 3:12

    unoriginal content. In today's economy

  88. 3:15

    with the AI tools available, it's really

  89. 3:17

    easy to actually duplicate the content.

  90. 3:19

    When someone uh upload a video or

  91. 3:22

    something, we see that okay, it is being

  92. 3:24

    copied, it is being transformed and with

  93. 3:26

    tools, it is getting much easier to

  94. 3:28

    transform these videos. U so how do we

  95. 3:30

    actually detect this kind of unoriginal

  96. 3:32

    content? How do we figure out the source

  97. 3:34

    of the video? And um this has actually

  98. 3:37

    caused a problem in attribution credit u

  99. 3:40

    ecosystem imbalance and lot of like user

  100. 3:42

    fatigue where we are seeing a lot of

  101. 3:44

    repetitive videos which shouldn't be

  102. 3:45

    there in the first place. So uh coming

  103. 3:49

    to the multi- aent system uh the first

  104. 3:51

    thing is that uh why we are going to

  105. 3:53

    multi-agent not a single agent or single

  106. 3:55

    lenm because the problem is really

  107. 3:56

    complex. It requires a really

  108. 3:58

    specialized uh nodes and uh kind of like

  109. 4:01

    an understanding at each part of

  110. 4:03

    retrieval content understanding and then

  111. 4:05

    reasoning and if you can solve a problem

  112. 4:08

    with one agent one LLM you we don't need

  113. 4:10

    to actually do it on multi- aent

  114. 4:13

    systems. So this is where the

  115. 4:16

    centralized brain how we are actually

  116. 4:18

    thinking kind of like how the uh

  117. 4:19

    decomposition happens of this problem.

  118. 4:22

    The first is basically you have a video

  119. 4:24

    and kind of like a clip video ID and

  120. 4:26

    everything given to a reviewer agent.

  121. 4:28

    This is a centralized agent. This is

  122. 4:30

    basically the orchestrator. Consider

  123. 4:31

    that as an API gateway of uh doing a

  124. 4:34

    sing signal decomposition and finding

  125. 4:36

    what is happening around in the image.

  126. 4:38

    So what this guy do is basically this

  127. 4:40

    guy takes ask the perceiver agent and

  128. 4:43

    perceiver agent is the one which is

  129. 4:45

    basically considered that a very

  130. 4:47

    sophisticated VLM expert with lot of

  131. 4:49

    image and the video tools at uh

  132. 4:52

    disposal. Uh perceiver agent will take

  133. 4:55

    the ID from the retriever reviewer agent

  134. 4:58

    and it fetches the video from the

  135. 5:01

    database. It decomposes into smaller

  136. 5:03

    parts using different tools, different

  137. 5:05

    like semantic embeddings and different

  138. 5:06

    kind of like temporal change that

  139. 5:08

    happens which is a little bit beyond our

  140. 5:11

    scope but of this talk but it's uh a

  141. 5:14

    technique which is making sure that we

  142. 5:15

    are not doing at a fixed frame rate but

  143. 5:18

    we are finding where the temporal change

  144. 5:19

    happen and compressing those similar

  145. 5:22

    frames into one or two frames and then

  146. 5:25

    the perceiver agent get all the data

  147. 5:26

    from a clip level. The video embedding

  148. 5:28

    level get all the information about a

  149. 5:31

    clip embedding tags OCR whatever is

  150. 5:33

    present out there what is the natural

  151. 5:35

    language description and what are the

  152. 5:36

    time stamp from which frame to which

  153. 5:38

    frame what are those this metadata looks

  154. 5:40

    like it gives that data to the reviewer

  155. 5:43

    reviewer will look into all the temporal

  156. 5:45

    this JSON object provided by the uh

  157. 5:47

    perceiver agent in a raw form along with

  158. 5:49

    embeddings along with semantic ids tags

  159. 5:52

    OCR and everything and it does a

  160. 5:54

    temporal analysis it looks into okay you

  161. 5:57

    know for from first frame to frame or

  162. 6:00

    frame number 360 or like till 6 second

  163. 6:02

    it was a video talking about a sports

  164. 6:05

    and suddenly we are seeing from 6 second

  165. 6:08

    to 6.5 second or frame number this to

  166. 6:10

    this we are seeing that like this is

  167. 6:11

    changing into some political thing. So

  168. 6:14

    just by looking into the metadata the

  169. 6:17

    reviewer agent is able to understand

  170. 6:19

    comprehend and figure out what exactly

  171. 6:20

    is the anomaly coming in the this

  172. 6:22

    temporal space and once it do that it

  173. 6:25

    figures out whether this is actually a

  174. 6:27

    modality misalignment or there is some

  175. 6:28

    bigger issue out there on there. So

  176. 6:30

    review agent will look and talk to the

  177. 6:33

    retriever agent and it tells that hey

  178. 6:35

    this is the video I'm looking into.

  179. 6:36

    These are the some of the metadata that

  180. 6:38

    I have already uh kind of like ddup and

  181. 6:40

    kind of like post-processed. Now give me

  182. 6:42

    some understanding of this similar clips

  183. 6:45

    which are available in the corpus. So

  184. 6:47

    retriever agent will look into all the

  185. 6:49

    signals provided by perceiver agent. All

  186. 6:51

    the metadata of a clip level and a whole

  187. 6:53

    video level and index it into different

  188. 6:56

    databases adaptively. For example the

  189. 6:58

    topics has to be maybe like a inverted

  190. 7:00

    index where we have topics and a lot of

  191. 7:02

    videos. For the embedding it will be a

  192. 7:04

    vector databases which is available out

  193. 7:06

    there. And for different kind of

  194. 7:08

    entities which I've extracted we have a

  195. 7:10

    graph databases kind of like where you

  196. 7:12

    review your agent will figure out okay

  197. 7:14

    these are the multiple databases these

  198. 7:15

    are the entities and these are the

  199. 7:16

    metadata let me index it so that in the

  200. 7:19

    online inference time I can figure out

  201. 7:21

    for a particular clip what are the

  202. 7:22

    similar clips what are the similar

  203. 7:24

    entities and topics which are available

  204. 7:26

    to fetch and improve the recall.

  205. 7:29

    So going into individual agent we talked

  206. 7:31

    about perceiver it looked into the

  207. 7:33

    entire video do a temporal decomposition

  208. 7:35

    into small clips based on the semantic

  209. 7:37

    embedding and couple of algorithms and

  210. 7:40

    it fine-tuned the VLM to actually emit

  211. 7:42

    all the real uh concrete and a very um

  212. 7:46

    granular information about like each

  213. 7:48

    clips and the entire video. Uh because

  214. 7:51

    we are dealing at a very big scale that

  215. 7:53

    means we cannot just go with the

  216. 7:55

    standard VLM which are out there. There

  217. 7:56

    has to be a compression. There has to be

  218. 7:58

    a cost effective way to actually serve

  219. 8:00

    this these models to do it at like

  220. 8:03

    billions of frames. That's where we are

  221. 8:06

    getting into the pre-training

  222. 8:07

    fine-tuning and knowledge distillation

  223. 8:09

    quantization to actually deploy and

  224. 8:11

    solve the very very specialized VLM

  225. 8:14

    based on this particular problem and we

  226. 8:16

    will be talking a little bit brief about

  227. 8:18

    that. U the retriever agent is the one

  228. 8:20

    which we talked at a very high level and

  229. 8:22

    then what it does in an offline

  230. 8:24

    processing is that all the signal which

  231. 8:26

    is decomposed by the perceiver agent in

  232. 8:28

    an offline fashion consider that rather

  233. 8:30

    an agent you are actually taking that

  234. 8:31

    library and doing an offline analysis on

  235. 8:33

    a big scale let's say ray cluster or

  236. 8:36

    something like that and then once you

  237. 8:38

    have all those metadata it is basically

  238. 8:40

    indexing it into different databases

  239. 8:43

    doing an uh periodic offline clustering

  240. 8:45

    and finding what are the similar content

  241. 8:47

    what should be the embedding ID what

  242. 8:48

    should be cluster ID for each clips and

  243. 8:50

    entire video. So that is a data which is

  244. 8:52

    basically used by online inference to

  245. 8:55

    find similar videos and in online manner

  246. 8:57

    it given a query a clip ID and every all

  247. 9:00

    the metadata details it's figured out

  248. 9:02

    what is out there in the corpus which

  249. 9:04

    this guy has is similar to what like

  250. 9:06

    what are the different things which has

  251. 9:08

    a high similarity. So what it does it

  252. 9:10

    looks into databases is it find similar

  253. 9:12

    clips and like similar authors and

  254. 9:14

    different other metadata information

  255. 9:16

    rerank those candidates find uh and use

  256. 9:19

    some of the tools about like for example

  257. 9:21

    the traditional model span score like a

  258. 9:23

    classifier score to see what are the

  259. 9:25

    different candidates which might be spam

  260. 9:27

    which might not be high quality and

  261. 9:28

    those things out there and once it has

  262. 9:30

    those top end candidates is give back it

  263. 9:33

    to the reviewer and reviewer is where it

  264. 9:35

    actually process this is my main content

  265. 9:37

    signals and clip embeddings These are a

  266. 9:40

    similar video which is given by

  267. 9:41

    retriever. Let me think over it and

  268. 9:43

    whether I need to retraate and get more

  269. 9:47

    data from retriever. So uh that's where

  270. 9:50

    reviewer have all the temporal signals

  271. 9:51

    from a single clip. It has all the

  272. 9:54

    information of similar clips

  273. 9:55

    understanding and what is similar

  274. 9:56

    authors and other thing. It also has a

  275. 9:59

    realtime information about how the users

  276. 10:01

    are actually interacting with this

  277. 10:02

    video. What are the different kind of

  278. 10:05

    like a reports or like likes, dislike,

  279. 10:07

    the comments? what is the u sentiment of

  280. 10:11

    those comments out there right so a lot

  281. 10:13

    of these signals which are actually

  282. 10:14

    missed by the offline uh signals and the

  283. 10:16

    VLMs and other kind of agents are

  284. 10:18

    actually also incorporated to see if

  285. 10:20

    there is a change happen in the

  286. 10:22

    sentiment what is the response I'm

  287. 10:24

    getting in the real time so there are

  288. 10:25

    different tools available for this to

  289. 10:28

    actually understand the video not just

  290. 10:30

    from the content and from the semantic

  291. 10:32

    perspective but understanding from the

  292. 10:34

    user interaction perspective those

  293. 10:36

    signals are really really important

  294. 10:38

    So once we have this judge and

  295. 10:40

    everything we build this uh agentic

  296. 10:43

    framework and each of these agentic

  297. 10:45

    frameworks uh all all these three agents

  298. 10:48

    are actually powered by specialized uh

  299. 10:50

    VLMs and small scale VLMs in a way. So

  300. 10:54

    we will be talking about uh pre-training

  301. 10:57

    first. Now uh in most of the cases you

  302. 11:00

    see that okay you have a pre-training

  303. 11:01

    you fine-tune your vision transform a

  304. 11:03

    little bit here and there and basically

  305. 11:04

    tune it for your specific purpose.

  306. 11:07

    Uh the thing is that these VLMs what we

  307. 11:10

    have outside and available the

  308. 11:12

    foundational model the front end models

  309. 11:14

    they are trained on a very clean very

  310. 11:16

    nice data set very web data which is

  311. 11:18

    very well tuned cleaned and everything

  312. 11:20

    but uh data inhouse for a specific

  313. 11:23

    purpose is not having the same data

  314. 11:25

    characteristics. It's it is messy. It is

  315. 11:27

    generated by users. It is for your

  316. 11:29

    specific workflow. That means you need

  317. 11:32

    to pre-train on those image tokens and

  318. 11:34

    language to fine-tune your vision

  319. 11:36

    transformer from scratch and see whether

  320. 11:38

    there is a delta in fine-tuning it and

  321. 11:40

    tuning it from the scratch. That's where

  322. 11:42

    the pre-training is helpful. It's little

  323. 11:44

    expensive but um it if if it can get a

  324. 11:47

    delta that that actually works really

  325. 11:49

    well. The second is instruction

  326. 11:51

    fine-tuning where we have the two

  327. 11:54

    problems. We have a certain policies and

  328. 11:56

    certain guidelines. We know the content

  329. 11:58

    out there, signal out there and it

  330. 12:00

    understand and tune it on that

  331. 12:03

    particular data set with it with a

  332. 12:04

    particular output which is schema like a

  333. 12:07

    JSON schema to understand what is the

  334. 12:09

    modality uh misalignment or duplication

  335. 12:11

    of scores and other chain of thought

  336. 12:14

    reasoning provided by reviewer agent. So

  337. 12:16

    here we have a video clip we have a

  338. 12:18

    vision encoder which we are already

  339. 12:20

    pre-trained a little bit like now we are

  340. 12:21

    doing a little bit more training on

  341. 12:23

    that. There's a projector which is

  342. 12:24

    sitting between the vision transformer

  343. 12:26

    and the L language models and it is

  344. 12:28

    actually basically a bridge between them

  345. 12:30

    and then we have our output depending on

  346. 12:32

    what is the instruction finetuning data

  347. 12:34

    we have on this side. So this is the

  348. 12:37

    critical part of actually making your uh

  349. 12:41

    model performance like go up for your

  350. 12:44

    domain specific. So uh the context is

  351. 12:47

    basically you have a role, you have a

  352. 12:48

    policy, what are the tools available to

  353. 12:50

    ground that into some of the metadata or

  354. 12:52

    and what are the other things available

  355. 12:54

    out there give it entire things into uh

  356. 12:57

    in in a very brief manner into the

  357. 12:59

    context and let it figure out like what

  358. 13:01

    the structured label you have for these

  359. 13:03

    labels are actually in-house label.

  360. 13:05

    These are the one where we have created

  361. 13:07

    like what exactly modality things are,

  362. 13:10

    what are the different uh issues we are

  363. 13:12

    seeing, what are the different chain of

  364. 13:13

    thought reasoning there should be there

  365. 13:15

    in the model and how does the output

  366. 13:17

    looks like for a human reviewer. So this

  367. 13:19

    is like a very high quality data data

  368. 13:21

    set that we are fine-tuning it on for

  369. 13:23

    different agents. Right? So once we have

  370. 13:27

    done with the pre-training just to

  371. 13:28

    understand the vision aspect of or the

  372. 13:30

    other modality aspects of the videos

  373. 13:33

    then we go into the finetuning to make

  374. 13:35

    it understand and provide the context

  375. 13:37

    and the output in the manner that we

  376. 13:39

    would want to actually process the data

  377. 13:40

    set on. So u the next phase is the DPO

  378. 13:44

    phase where uh which is basically this

  379. 13:47

    technique is used a lot in the uh post-

  380. 13:49

    training to actually fine-tune our

  381. 13:51

    models into a specific uh like realm

  382. 13:54

    domain policy understanding or

  383. 13:56

    something. But this can also be used a

  384. 13:59

    lot in the prediction for actually

  385. 14:00

    understanding what are the samples which

  386. 14:02

    are actually getting uh not so good by

  387. 14:05

    the by your multi-ent systems and by

  388. 14:07

    your u llms. So what uh can be done is

  389. 14:12

    that like uh you have this uh production

  390. 14:15

    data set which is coming out you have a

  391. 14:17

    lot of inference happening you take a

  392. 14:19

    subsample of these uh data which is from

  393. 14:22

    the production you pass it through LLM

  394. 14:24

    as a judge which is trained inhouse on

  395. 14:26

    the human label data set and then you

  396. 14:29

    have the human review Q to see what is

  397. 14:31

    the performance coming up on on the

  398. 14:33

    actual system. Once you have this thing

  399. 14:36

    if your performance is coming amazing

  400. 14:38

    and it is above like your whatever is

  401. 14:40

    the prediction threshold you have 95%

  402. 14:42

    for each of the problem it's great but

  403. 14:45

    if it is not that means there is a way

  404. 14:47

    there has to be a way to loan on these

  405. 14:49

    samples where the model did not do well

  406. 14:52

    that's where you have a human in the

  407. 14:53

    queue it understand those all the traces

  408. 14:56

    which is there from all the agents the

  409. 14:58

    LLM call MCP and it figured out where

  410. 15:00

    the problem happened is it like a chain

  411. 15:02

    of thought reasoning or is it like some

  412. 15:04

    of the wrong tool tools are called the

  413. 15:05

    retrieval did not work. So that entire

  414. 15:08

    validations and basically understanding

  415. 15:10

    of each and every hook and node both at

  416. 15:13

    a model intelligence level plus at a

  417. 15:16

    harness level is what you figure out and

  418. 15:19

    say that okay these are the improvement

  419. 15:20

    that we I need to do on these samples

  420. 15:23

    which was incorrectly um sampled by our

  421. 15:26

    um system. So once you have this thing

  422. 15:29

    you have a positive sample negative

  423. 15:31

    sample what needs to be updated and

  424. 15:33

    that's where you retrain your model to

  425. 15:36

    see what uh how can we improve it better

  426. 15:38

    and this is the continuous improvement

  427. 15:40

    where we are looking into these samples

  428. 15:42

    reiterating re um improving the models

  429. 15:45

    and having a new data set out there from

  430. 15:47

    the production u like samples and trying

  431. 15:50

    to understand whether the drift happen

  432. 15:52

    or what exactly the model is doing. So

  433. 15:54

    this human in the loop is like always a

  434. 15:56

    continuous thing where you have a daily

  435. 15:58

    sampling from the production and trying

  436. 16:00

    to understand like how the model and the

  437. 16:02

    L&M as a judge are doing.

  438. 16:05

    So uh because of the cost and ability to

  439. 16:10

    solve at this scale we cannot go with

  440. 16:12

    the standard like a like a VLM models

  441. 16:15

    from frontier sizes because it's not

  442. 16:17

    scalable. It requires a lot of

  443. 16:19

    inference. It's a lot of complexity and

  444. 16:20

    we are solving a very specific problem

  445. 16:23

    like I really don't care if the model

  446. 16:25

    can solve a coding problem. I only care

  447. 16:27

    about my domain specific problem. That

  448. 16:29

    is all I care. This is not exposed to

  449. 16:31

    the customer. This is an internal thing.

  450. 16:33

    So I would actually do a off policy and

  451. 16:35

    on policy knowledge distillation and do

  452. 16:37

    a little bit of quantizations depending

  453. 16:39

    on like some experimentation

  454. 16:40

    quantization to understand whether a

  455. 16:42

    forbit work braining float what actually

  456. 16:45

    work really well. Then I would have a

  457. 16:46

    table of different sizes of

  458. 16:48

    distillations and quantization and

  459. 16:50

    understand and see where exactly is my

  460. 16:53

    performance like up to the mark and

  461. 16:55

    where I'm gaining a lot of compute and

  462. 16:58

    the cost resources um savings from on

  463. 17:00

    inference production by doing these

  464. 17:02

    optimization. So this is really critical

  465. 17:05

    because as a problem what we have solved

  466. 17:08

    it's all good but in production it has

  467. 17:11

    to be scalable. It has to be cost

  468. 17:13

    effective. It cannot just be like

  469. 17:15

    something which is um out of the um

  470. 17:20

    which is just out in the market because

  471. 17:21

    we are solving a very specific problem

  472. 17:23

    out here. Coming back to the evaluation

  473. 17:26

    basically first is the task of success.

  474. 17:28

    Of course these are the binary things

  475. 17:30

    the modality happen it does not happen

  476. 17:32

    like there is alignment or disalignment.

  477. 17:34

    So precision, recall, F1 are obvious

  478. 17:36

    metrics to understand what the task is

  479. 17:39

    success is. But we want to look at a

  480. 17:41

    system in a very holistic manner. Not

  481. 17:43

    just like the end goal but what is

  482. 17:44

    happening at each nodes. How well like

  483. 17:47

    the retrieval system is working. What is

  484. 17:48

    the latency and recall of the system and

  485. 17:51

    how well we are able to reason it? What

  486. 17:53

    is the chain of thought reasoning coming

  487. 17:54

    from these models at each agentic level

  488. 17:57

    or wherever the its reasonings are

  489. 17:59

    applicable which is basically a reviewer

  490. 18:01

    agent in our case. And what is the

  491. 18:04

    quality of that? Is it like

  492. 18:05

    overthinking? Can we reduce a budget

  493. 18:06

    somewhere like to make sure that like

  494. 18:08

    the models is actually doing a good job

  495. 18:10

    with less uh budget or can we increase

  496. 18:13

    it the budget of the planning or the

  497. 18:15

    reasoning things to have it a higher

  498. 18:17

    budget and make sure that the complex

  499. 18:20

    problem that we are solving is maybe

  500. 18:22

    having a much higher performance and

  501. 18:24

    accuracy. So having an adaptive adaptive

  502. 18:26

    reasoning budgeting is also uh quite

  503. 18:29

    important. And then we have the

  504. 18:31

    robustness. what are the edge cases we

  505. 18:32

    are seeing? Uh what are the error rates

  506. 18:34

    we are having? What are the different

  507. 18:36

    nodes and hooks where they are

  508. 18:38

    happening? Is it like a tool call is not

  509. 18:39

    working really well? It's a retrieval

  510. 18:41

    part or LLM is not doing a good job

  511. 18:43

    where or those kind of thing. And then

  512. 18:46

    we have a system efficiency where we are

  513. 18:47

    not looking uh just at the performance

  514. 18:50

    of the output and everything but we are

  515. 18:52

    looking at each and every aspects of the

  516. 18:54

    token cost which LLM are calling can you

  517. 18:57

    optimize LLM little bit more to actually

  518. 18:58

    save the cost. What is the efficiency

  519. 19:00

    which is we are saying and the latency

  520. 19:02

    of each agents and the entire system

  521. 19:05

    combined together. Then we have a LLM as

  522. 19:07

    a judge where we see that like in any of

  523. 19:10

    the prediction system there is always a

  524. 19:12

    data drift happening especially when you

  525. 19:14

    have the user generated content. So how

  526. 19:17

    our LLM as a judge which is used for

  527. 19:19

    evaluation and everything is doing with

  528. 19:20

    respect to the human queue. Is there a

  529. 19:22

    drift happening? Do we need to retrain

  530. 19:24

    our LLM as a judge on new data set which

  531. 19:26

    is coming from labeling team or how do

  532. 19:28

    we actually do on those parts in

  533. 19:30

    optimization? We have the spatial

  534. 19:32

    temporal reduction optimization which

  535. 19:34

    actually look into the frame which are

  536. 19:35

    similar and just compress them into the

  537. 19:37

    one aspect. This reduces the total

  538. 19:41

    processing of the videos by a huge

  539. 19:43

    extent. The second one is basically you

  540. 19:46

    have a caching you have a viral content

  541. 19:48

    which is basically coming up and you do

  542. 19:49

    not want to have the same content out

  543. 19:52

    there which is doing going through the

  544. 19:54

    entire pipeline and that's where you

  545. 19:55

    have a high similarity score and just

  546. 19:57

    skip the multi- aent system and just

  547. 19:58

    make a call on that. The third one which

  548. 20:01

    is really important is the metadata

  549. 20:02

    pruning. This is where we actually

  550. 20:04

    shrink the space from lot of candidates

  551. 20:06

    based on some of the metadata. For

  552. 20:08

    example, some topics and some creator

  553. 20:10

    which already have a really good record.

  554. 20:12

    That means we really don't need to

  555. 20:13

    process these all these images all all

  556. 20:17

    the videos from the creator which has a

  557. 20:18

    really good high authenticity score

  558. 20:20

    which are really doing really well on

  559. 20:21

    this where the video quality is really

  560. 20:23

    high engagement is good those kind of

  561. 20:25

    things. A metadata is something which

  562. 20:27

    can be used to filter out the video

  563. 20:30

    which shouldn't even go to the systems.

  564. 20:32

    So some of these flags u would be

  565. 20:35

    helpful. Um so the last takeaway that u

  566. 20:39

    u we basically we can take out of this

  567. 20:42

    room is that like decomposition t is a

  568. 20:44

    key. Uh decompose uh a problem as and

  569. 20:47

    when necessary. Adaptive optimization is

  570. 20:50

    really important for uh ROI and cost

  571. 20:52

    feasibility. Good evaluation is

  572. 20:55

    paramount. Everything in and out depends

  573. 20:57

    on this. This is the foundation of your

  574. 20:58

    entire system and entire VLMs and

  575. 21:01

    production monitoring and qualitative

  576. 21:03

    improvement are really essential to make

  577. 21:05

    sure this is sustainable in long term.

  578. 21:08

    With that, I'll end it and thank you

  579. 21:10

    very much for listening. Thank

  580. 21:12

    [applause]