How Bridgewater Turned 100 Million Documents Into an Edge - Sam Green & Aaron Linsky, Bridgewater

AI Engineer · 16 min · 179 sentences · from YouTube's caption track

Each timecode opens YouTube at the start of that sentence. Line anchors (#s42) are the cue ids in the WebVTT, and every line carries its start and end seconds. All transcripts has every talk, and the whole corpus as one file.

  1. 00:01[music]
  2. 00:12Good morning everyone.
  3. 00:13I'm Sam Green, team lead for applied AI at Bridgewater Associates, and this is my colleague Erin Lensky.
  4. 00:20And today we're here to talk to you about the Vault, the data platform that we've built at Bridgewater to turn unstructured data into a first-class asset in our investment process.
  5. 00:31And as part of the talk this morning, we'd like to share three lessons that we've learned building the Vault.
  6. 00:37The first is that humans and agents have very different needs from a data platform.
  7. 00:43And so you have to build for those different needs separately.
  8. 00:46The second is that the greatest impact occurs when a single tool can meet both of these sets of needs at the same time.
  9. 00:53And the third is that the real prize is when you can build the foundations needed to make agents a proactive participant in your investment process or whatever you're doing with your with your your tools
  10. 01:06instead of a reactive reactive tool for your humans to use.
  11. 01:11Before I I dive deeper into talking about the Vault, I wanted to start with some some background about Bridgewater.
  12. 01:17Over the last 50 years, Bridgewater has been in the constant pursuit of the world's best understanding of how markets and economies work.
  13. 01:25And turning that into a systematic encoding that we can use to stress test our logic over time.
  14. 01:32And what originally began as a set of if-then rules on a yellow legal pad evolved into a continuous compounding process with humans at the center constantly looking for the next thing that's changing in markets.
  15. 01:44And more recently, we've been working on building AiA, the artificial investment associate, which puts a machine at the center of this continuous process.
  16. 01:53Across all these phases of evolution, we've had a constant philosophy in mind, which is that we want to be constantly looking at how the world is changing and what's going on in the world.
  17. 02:03Noticing what what dynamics are not yet encoded in our understanding and use that learning to improve and compound for the future.
  18. 02:14For most of Bridgewater's history, that meant building and overseeing time series models on structured data.
  19. 02:21And that structured data needed to be carefully built so that it could be safe for use in our research process and aligned to our internal ontology and world model so that we could get great leverage out of using the the data that we had built.
  20. 02:35With the emergence of language models, we had a huge new opportunity to engage with a with a much wider world of data.
  21. 02:42Um, you know, news and research, transcripts, policy documents, and all of the internal conversation that was previously just in the ether.
  22. 02:51So, the internal memos and meeting transcripts and debate happening inside the firm.
  23. 02:56We quickly realized that all of that data needed the exact same treatment to be fit for purpose.
  24. 03:01It needed to be carefully cleaned, governed, and made ready for use in both point-in-time research questions today and also our systematic study over time.
  25. 03:13And when we looked out at the landscape of data vendors and data platform providers, there was nothing that provided us with all of the control that we needed to build and maintain our data advantage.
  26. 03:25And so, we built the Vault, which is our repository of external and internal unstructured data.
  27. 03:33Um, and the platform that indexes, organizes, and makes all of it ready for use by our human investors and agents.
  28. 03:41Today, the Vault has more than 100 million documents in it with thousands more added every day, uh, minute by minute, from 135 external sources and again growing all the time,
  29. 03:52as well as all of the data from inside of Bridgewater.
  30. 03:55And crucially, all that data is not just dumped on our investors' desks.
  31. 03:59It is carefully aligned to our internal internal ontology with enrichments like the countries, concepts, markets, and most importantly, time period discussed in the document.
  32. 04:14To bring this to life, I want to start with a quick motivating example.
  33. 04:17So, what I did here is I asked a fairly basic representative investment question to an enterprise chat client.
  34. 04:25I asked, "How is AI infrastructure investment impacting the Korean won, and do market participants expect this to continue?"
  35. 04:33And as as you're all I'm sure familiar with, the agent goes to the web and looks for resources it can draw on because I've explicitly asked it to go find
  36. 04:44other people's perspectives on the question.
  37. 04:46And you can see it it zooms in and it finds 15 relevant-looking resources to draw on before it gives me back its answer.
  38. 04:56And when I when I zoomed in on the answer it gave back, a couple of things stood out to me.
  39. 04:59The first is that even though it found 15 relevant-looking sources, it only picked one or two to answer to answer my question.
  40. 05:08And the second is down at the end of this response where the agent itself acknowledges that it hasn't answered my question.
  41. 05:15It didn't find enough documents on the open web to establish a market consensus and meet the meet the parameters that I laid out.
  42. 05:24When I double-clicked even further, the problem got even worse.
  43. 05:28One of the notes that it primarily drew on to answer my question was published way back in July of 2026, even though I asked this question and captured this answer just at the end of last week in early October.
  44. 05:41In the age of AI and in investing, four three months is a massive amount of time.
  45. 05:47It's not even close to good enough to draw uh draw on this resource to answer my question.
  46. 05:54When I ask this exact same query attached to the vault, something totally different happens.
  47. 05:59The first is that the connection to the vault helps to prompt the agent that it should look for a specific period of time when answering my question.
  48. 06:06So, it zooms in on October 1st to October 8th.
  49. 06:09It finds a much wider array of resources, 52 candidate documents that are relevant to the query over this specific period of time because of the vault's much more significant
  50. 06:20corpus of content that's relevant to investing questions.
  51. 06:24And when it ultimately answers my question, it draws on seven instead of only one or two.
  52. 06:30And gives me back a rich answer that the agent is more confident is going to address my question.
  53. 06:37And so, for us, this is the the big lesson of from building the vault to kind of motivate the talk today, which is that it takes great data and the right connectors
  54. 06:45to make agents impactful.
  55. 06:47And I'm going to talk hand it over to Aaron now to talk about some of the product engineering takeaways from building the vault.
  56. 06:54Thanks, Sam.
  57. 06:55So, hi.
  58. 06:56I'm Aaron.
  59. 06:56I run product engineering at Bridgewater.
  60. 06:58I'm going to take us through a few of our learnings from building the vault over the past few years.
  61. 07:02I'm going to start with one that might seem obvious, but I still think it's worth saying, which is search is hard.
  62. 07:11But, it gets even harder if we're designing for two different consumers.
  63. 07:15And in this case, we're designing for humans and agents.
  64. 07:18I'm going to go over the difference here starting with us.
  65. 07:21So, humans need precision and a high signal-to-noise ratio because we can only read so much.
  66. 07:27Even a fast reader manages about 300 words a minute, and personally, I'm much slower.
  67. 07:33Agents are a different kind of reader.
  68. 07:36They're far less sensitive to precision.
  69. 07:38If the data is there, they'll find it.
  70. 07:40And basically, anything you hand to them will get attended to.
  71. 07:44They scale super quickly and they come and they consume about uh a hundred times faster, 30,000 words per minute.
  72. 07:53And so we need to build Vault for both of these.
  73. 07:56And when we're thinking about the dimensions that matter, there are these five on on the board.
  74. 08:02Recall, precision, filtering, entitlements, and scale.
  75. 08:07Some of them matter to people, some matter more to agents, many to both.
  76. 08:12I'm going to go deep on three of these.
  77. 08:13Precision for people, scale for agents, and then filtering for both.
  78. 08:19So, precision.
  79. 08:21Once we've filled the Vault, our which was a heroic effort by our data and legal teams, recall was no longer a pressing issue.
  80. 08:30However, the number one complaint was Vault search is bad.
  81. 08:35As a product owner, it's painful to hear that, but my response was let's benchmark it.
  82. 08:40And that's what we did.
  83. 08:42We collected questions and found the best documents by hand, including ones that looked helpful but weren't.
  84. 08:48In all In total it was about 200 examples and it took us less than a week.
  85. 08:52It was not fun or very glamorous, but it was very helpful.
  86. 08:57And after we ran it, it was very clear.
  87. 08:59Search was bad.
  88. 09:01The key metric we were looking at is precision at 10, which is of the top 10 results, how many are the right documents.
  89. 09:09And we were hitting about 60%.
  90. 09:12So, the people were right, it was bad.
  91. 09:15But now we had a way to measure all of the improvements.
  92. 09:18And here on the board are five of them.
  93. 09:21And by the time we got done with Agentic Search, we were up in the 90-95% uh recall at 10 or precision at 10.
  94. 09:31All right, so that was precision.
  95. 09:32Now on to filtering.
  96. 09:35Like anyone, we want the most relevant documents.
  97. 09:38But when we looked at the production traces, what we were seeing is that almost always there was some condition, either as of a certain date or from a certain source or about a specific asset.
  98. 09:50And all of that requires advanced filtering, and that's where we ran into our first major performance issue.
  99. 09:58So I'm going to quickly go through this of a little bit technical here of there's classically two ways to fill filter a vector database.
  100. 10:07Post filtering will use that vector index first and then filter the top results by metadata.
  101. 10:12It's fast, but recall could be pretty low because the globally relevant results might not match your filters.
  102. 10:20On the other side, we have pre-filtering where we'll filter first and then calculate distances for every one of those matches.
  103. 10:27The advantage there is that the recall is very good, but it can be very slow, and we needed something in between.
  104. 10:33So that's what led us to try and then ultimately switch to Turbo Puffer.
  105. 10:37Their approach, which they called native filtering, looks only in the nearest clusters that contain matches and then scores just those.
  106. 10:44What you end up getting is something that's fast like post filtering, but with close to the same recall as pre-filtering.
  107. 10:53And lastly, I'm going to talk about scale.
  108. 10:56Human scale for us is pretty pedestrian, 100 queries an hour.
  109. 11:00We have 300 users.
  110. 11:01They're going to search, you know, every so often.
  111. 11:04It takes our users minutes to read the docs that they're that they're receiving.
  112. 11:08Agents, on the other hand, are a few orders of magnitude beyond that.
  113. 11:13Easily 100 plus queries a second, and agent swarms can hit thousands easily.
  114. 11:18And they obviously, will read, as I said earlier, will read docs in seconds.
  115. 11:22So we needed something that could scale as well, and again, Turbo Puffer handled that easily, too.
  116. 11:28So we were covering all five dimensions.
  117. 11:30I didn't talk about entitlements, but I'll be talking about that later today.
  118. 11:34Um but we covered it all.
  119. 11:35It unlocked new workflows.
  120. 11:38But it didn't change how our researchers worked.
  121. 11:41They still weren't coming to Vault every morning.
  122. 11:44And that's my second lesson that I want to share here is that no matter how amazing the tools are, we can't just drop them on our investors' desks and expect them to be used.
  123. 11:53We need to migrate their old habits into an a new form.
  124. 11:58And so we looked at what they were already doing.
  125. 12:02Many of them were living in email.
  126. 12:04The research came straight from the brokers.
  127. 12:06They had subscribed lists.
  128. 12:08They had rules that filtered everything into folders.
  129. 12:11It worked.
  130. 12:11It was familiar.
  131. 12:13And they knew that they weren't missing anything.
  132. 12:16So we had to build all of these features into the Vault.
  133. 12:19That's exactly what we did.
  134. 12:20Everything's searchable.
  135. 12:21The subscribe lists became saved searches.
  136. 12:25And folders became saved collections.
  137. 12:27It's the same habits, just a new home.
  138. 12:30And once we had them there, we can open up new habits.
  139. 12:33So we can ask they can ask questions across all the data as Sam showed.
  140. 12:37They can follow dynamic feeds by topic.
  141. 12:39And they can hand those collections over to their agents to take further action.
  142. 12:43And that's when we clearly had product market fit.
  143. 12:47And once we had that fit, the users wanted it everywhere.
  144. 12:50So we put it in chat.
  145. 12:52We made a phone app.
  146. 12:53It's in Slack in their IDE.
  147. 12:54And of course, we availed all of that to the agents as well.
  148. 12:57Um including a a CLI because agents love CLIs.
  149. 13:02And so the main question here is okay, so what does this enable?
  150. 13:06Sam's going to talk about what we're building right now.
  151. 13:09But first and foremost, it's helping us to move around that research circle faster.
  152. 13:14With our pocket analyst, which is our first AI analyst, it can do it can do hours it can do hours of research in just a few minutes for a few dollars.
  153. 13:24And that's relying on the Vault.
  154. 13:26And then we're expanding now with the researcher, which is the next generation.
  155. 13:30It's the same idea stretched across days or weeks.
  156. 13:34We're also able to train custom models to more intelligently reason over the vault's data and use those together with other foundation models to feed systematic decision-making processes.
  157. 13:45The forecaster is our first one, which produces AI-generated macro-relevant predictions.
  158. 13:51And then, we also have a built investment signals from the vault, turning unstructured data into structured, tradable strategies.
  159. 14:00Now, I'll hand it to Sam to take us through Vault's latest capability.
  160. 14:05Thanks.
  161. 14:07So, like I alluded to at the beginning of the talk, the real prize is when you can take agents from a reactive resource that can be ready to answer a a human's question
  162. 14:18and instead make them proactive participants helping to steer your high-value professionals towards the most important areas for their attention.
  163. 14:27And the way that we're solving that problem is in an experience we're calling the investor workbench, where the agent is always on tracking what's important to that investor and presenting them with the areas that are most in need of their attention.
  164. 14:42It looks like an experience like this that relies on the vault, where a topic is proposed and several pieces of information are presented to the investor to decide whether they should dig deeper or ignore that topic entirely.
  165. 14:55You can see here the card that an investor sees in order to decide whether to dig in deeper into the same AI impact on currencies question that we looked at earlier in the talk.
  166. 15:05And the investor receives everything they need, an agentic summary if they want a quick scan across the agent's findings.
  167. 15:12They also get the exact evidence that the agent was drawing on, so they can assess for themselves what was leading to this recommendation.
  168. 15:21And if they choose to dig deeper, they have a direct connection to the research output from the analytical tools that Aaron was just describing.
  169. 15:29And when they dig deeper alongside the agent to look at the dynamics driving this question, the learnings are automatically captured, the results of their collaboration are automatically captured back in the vault.
  170. 15:44And so this for us is the key lesson.
  171. 15:45The vault enables compounding because it provides the right evidence, the right extra internal and external information at the fingertips of our investors and agents, and it automatically captures the synthesis that they generate and puts it back in the corpus for the next turn.
  172. 16:02And that makes us go around the circle faster and better.
  173. 16:06And so when we think back to our the the question we began with, what it takes to make an agent work is the right context and the right understanding of what's going on in your world.
  174. 16:16And so our question for you is, does your AI know what's going on in the world?
  175. 16:19And does it remember what your firm has learned about it?
  176. 16:22Because we are teaching ours too.
  177. 16:24And if these sounds like an sound like an exciting challenge, we'd love to talk.
  178. 16:28Thank you.
  179. 16:30[applause]