Chapter 1 · Theme 07 thesis
The core shift across 5 talks
In institutional investing and private markets, off-the-shelf web chatbots fail on stale or conflicting inputs; agents earn front-office trust only atop governed firm ontologies, validated golden sources, unified MCP connectors, and hybrid code-ML-LLM-human pipelines that write synthesis back into the vault.
Every institutional finance talk located competitive advantage in governed data infrastructure and workflow design rather than raw model selection. Bridgewater contrasted an open-web chatbot answering a Korean won query from a single three-month-old note with Vault—which aligns 100M+ documents to a bitemporal ontology, serves 1,000+ QPS agent storms via turbopuffer cluster-local native filtering, migrates researcher email habits into saved collections, and writes human-agent workbench synthesis back into the corpus so knowledge compounds. At Apollo's Redding Ridge credit platform, engineers sat daily with portfolio managers to codify golden-source precedence across 20 conflicting systems, turning multi-hour weekly loan reconciliations into one-minute automated QA reports and cutting 200–400-name CLO portfolio construction from days in Excel to minutes for the first 80–90%. Coatue modeled the hedge fund as a composite state-machine function `(external_context, internal_context) -> (stock, size, timing)`, insisting that every pixel a human sees must be API-accessible while assigning each step whichever runner—deterministic code, classical ML, LLM, or human—maximizes quality. Exa supplied the external temporal layer with 400 billion dated web snapshots built for dense exploratory agent queries, while Anthropic standardized multi-system enterprise access behind a single MCP connectivity layer.
Vocabulary in the rooms: hedge fund as a function · bitemporal firm ontology · golden data sources · compounding investor workbench · hybrid code-ML-LLM-human runners
“So at a high level, you can think about a hedge fund as a function that takes in two parameters — context external and context internal, and spits out one, two, volt selection size timing. What stock? How much? When?”Frank Long · A Hedge Fund as a Function · 00:00:00
Chapter 2 · Evidence across 2 talks
Bitemporal vaults and dated web snapshots over stale open-web chat
In Vault: Making Unstructured Data Work for Investing (00:00:00), Aaron Linsky, Sam Green argued that bridgewater ingests over 100 million documents from 135 external sources plus internal memos and debate transcripts into Vault, enriching each document with ontology tags for countries, concepts, markets, and discussed time periods. In Vault: Making Unstructured Data Work for Investing (00:02:20), Aaron Linsky, Sam Green argued that on a live Korean won query, an open-web chat agent relied on one stale three-month-old note out of 15 results, whereas connecting the same agent to Vault time-scoped the search, matched 52 candidates, and synthesized seven current sources.
In Vault: Making Unstructured Data Work for Investing (00:06:23), Aaron Linsky, Sam Green argued that because production queries nearly always filter by date, source, or asset and agent storms exceed 100 to 1,000+ queries per second versus 100 per hour for humans, Bridgewater switched to turbopuffer's cluster-local native filtering to pair post-filtering speed with near pre-filtering recall. In Vault: Making Unstructured Data Work for Investing (00:09:34), Aaron Linsky, Sam Green argued that winning daily investor adoption required replicating familiar broker-email workflows inside Vault — converting distribution lists into saved searches and inbox folders into saved collections — before introducing cross-dataset queries, dynamic topic feeds, and CLI/Slack agent access.
In Vault: Making Unstructured Data Work for Investing (00:12:12), Aaron Linsky, Sam Green argued that the proactive Investor Workbench pairs always-on topic cards and raw source evidence with deep-research agents like Pocket Analyst, automatically writing the resulting human-agent synthesis back into Vault so institutional knowledge compounds across research cycles. In Search the Web as It Was: An Introduction to Exa Snapshot (00:00:00), Ryan Ahern argued that unlike humans who enter brief keyword queries and stop early, AI agents issue high volumes of detailed, exploratory searches per task, requiring search infrastructure purpose-built for agentic retrieval.
In Search the Web as It Was: An Introduction to Exa Snapshot (00:06:29), Ryan Ahern argued that by archiving page states during continuous freshness crawls, Exa Snapshot exposes over 400 billion daily-indexed web snapshots for both point-in-time URL lookups and historical semantic search queries.
“It is carefully aligned to our internal ontology with enrichments like the countries, concepts, markets, and most importantly, time period discuss in the document.”Sam Green · Vault: Making Unstructured Data Work for Investing · 00:00:00
“And so for us, this is the big lesson for building vault to kind of motivate the talk, which is that it takes great data and the right connectors to make AI powerful.”Sam Green · Vault: Making Unstructured Data Work for Investing · 00:02:20
“Their approach, which they call native filtering, looks only in the nearest clusters if it can matches, and then scores just those.”Aaron Linsky · Vault: Making Unstructured Data Work for Investing · 00:06:23
- Aaron Linsky, Sam Green: Bridgewater ingests over 100 million documents from 135 external sources plus internal memos and debate transcripts into Vault, enriching each document with ontology tags for countries, concepts, markets, and discussed time periods.
- Aaron Linsky, Sam Green: On a live Korean won query, an open-web chat agent relied on one stale three-month-old note out of 15 results, whereas connecting the same agent to Vault time-scoped the search, matched 52 candidates, and synthesized seven current sources.
- Aaron Linsky, Sam Green: Because production queries nearly always filter by date, source, or asset and agent storms exceed 100 to 1,000+ queries per second versus 100 per hour for humans, Bridgewater switched to turbopuffer's cluster-local native filtering to pair post-filtering speed with near pre-filtering recall.
- Aaron Linsky, Sam Green: Winning daily investor adoption required replicating familiar broker-email workflows inside Vault — converting distribution lists into saved searches and inbox folders into saved collections — before introducing cross-dataset queries, dynamic topic feeds, and CLI/Slack agent access.
Chapter 3 · Evidence across 2 talks
Golden-source reconciliation and portfolio construction in private credit
In AI in Practice: An Inside Look at Apollo's Approach (00:00:00), Michael Manapat, Jack McDonald argued that rowspace deploys agents to perform continuous data engineering—reconciling fragmented records across disparate enterprise systems—so portfolio managers and traders act on unified data rather than querying isolated chatbots. In AI in Practice: An Inside Look at Apollo's Approach (00:03:24), Michael Manapat, Jack McDonald argued that weekly warehouse loan trade reconciliation—previously requiring two to three staff members hours of manual bank-statement checks—now runs automatically in a minute, shifting the team's role to daily QA.
In AI in Practice: An Inside Look at Apollo's Approach (00:03:24), Michael Manapat, Jack McDonald argued that combining indenture waterfall rules, compliance constraints, and real-time pricing cut 200-to-400-name mock CLO portfolio construction from two-to-three days in manual Excel to minutes for the first 80–90% of the build. In AI in Practice: An Inside Look at Apollo's Approach (00:06:32), Michael Manapat, Jack McDonald argued that because a single financial data point can appear across 20 conflicting systems with only one authoritative source, earning trading-desk trust required engineers sitting daily with PMs to encode golden-source precedence rules.
In AI in Practice: An Inside Look at Apollo's Approach (00:13:10), Michael Manapat, Jack McDonald argued that aI grounded in validated proprietary data creates a durable competitive advantage in private credit—rather than becoming a commodity like Excel—by giving managers real-time accuracy on available liquidity and pricing. In Anthropic: Accelerating frontier AI in Financial Services. (00:07:57), Belinda Neal, Keon Shahab argued that manually wiring individual agents to enterprise data systems creates a brittle integration matrix as use cases multiply, so organizations should standardize source-system access behind a single secure MCP connectivity layer.
“We essentially use agents to do the work of data engineering, right information or reconciled data from across a variety of systems to the portfolio managers, traders, and so forth can make decisions faster and more accurately.”Michael Manapat · AI in Practice: An Inside Look at Apollo's Approach · 00:00:00
“That report was then created and now repeatable in the span of a minute, and now all of that is automated.”Jack McDonald · AI in Practice: An Inside Look at Apollo's Approach · 00:03:24
“that allows these PMS to kind of build something to call it eighty, ninety percent completion, and then kind of use their judgment and their thought to further refine that portfolio, that last 10 percent, to make it theirs.”Jack McDonald · AI in Practice: An Inside Look at Apollo's Approach · 00:03:24
- Michael Manapat, Jack McDonald: Rowspace deploys agents to perform continuous data engineering—reconciling fragmented records across disparate enterprise systems—so portfolio managers and traders act on unified data rather than querying isolated chatbots.
- Michael Manapat, Jack McDonald: Weekly warehouse loan trade reconciliation—previously requiring two to three staff members hours of manual bank-statement checks—now runs automatically in a minute, shifting the team's role to daily QA.
- Michael Manapat, Jack McDonald: Combining indenture waterfall rules, compliance constraints, and real-time pricing cut 200-to-400-name mock CLO portfolio construction from two-to-three days in manual Excel to minutes for the first 80–90% of the build.
- Michael Manapat, Jack McDonald: Because a single financial data point can appear across 20 conflicting systems with only one authoritative source, earning trading-desk trust required engineers sitting daily with PMs to encode golden-source precedence rules.
Chapter 4 · Evidence across 1 talk
A hedge fund as a composite function across code, ML, LLMs, and humans
In A Hedge Fund as a Function (00:07:29), Frank Long argued that each sub-function should be assigned whichever runner—deterministic code, classical ML regressions, LLMs, or human judgment—maximizes absolute quality for that step rather than automating with LLMs by default. In A Hedge Fund as a Function (00:12:16), Frank Long argued that composing multi-step transformations across every firm data source with 10+ hyperparameters and 20+ values per node yields an effectively infinite graph whose core challenge is technical and organizational legibility.
In A Hedge Fund as a Function (00:01:25), Frank Long argued that agent capability is wasted unless every external market feed and internal firm record—positions, liquidity and risk constraints, and decades of trade decision notes—is exposed directly via API rather than UI copy-paste.
“There is no glory in automating things for the sake of automating things. The goal is not to take as many things and make them LLMs as possible.”Frank Long · A Hedge Fund as a Function · 00:07:29
“In each of those nodes, we just talked about, at least ten hyperparameters with at least 20 different valid values for them. So the search space is basically infinite.”Frank Long · A Hedge Fund as a Function · 00:12:16
“Every single thing that a human can see in pixels on the screen, an agent in your building should be able to see via API.”Frank Long · A Hedge Fund as a Function · 00:01:25
- Frank Long: Each sub-function should be assigned whichever runner—deterministic code, classical ML regressions, LLMs, or human judgment—maximizes absolute quality for that step rather than automating with LLMs by default.
- Frank Long: Composing multi-step transformations across every firm data source with 10+ hyperparameters and 20+ values per node yields an effectively infinite graph whose core challenge is technical and organizational legibility.
- Frank Long: Agent capability is wasted unless every external market feed and internal firm record—positions, liquidity and risk constraints, and decades of trade decision notes—is exposed directly via API rather than UI copy-paste.
Chapter 5 · Boundaries & debates
Where speakers pushed back and drew the boundary
Why this theme stood uncontested: No speaker argued that general-purpose models or ungrounded web search could support institutional capital allocation without proprietary governed data; Apollo, Bridgewater, and Coatue unanimously restricted ungrounded chat to low-stakes background research.