BlackRock’s Ex-Chief Published a 50-Agent Portfolio System. I Built a Smaller Version With Claude.

I Fed a Paper From BlackRock’s Former Chief Into Claude. It Described 50 AI Agents Running an Entire Portfolio.

Andrew Ang ran BlackRock’s factor investing division. He now co-authored a paper describing a 50-agent AI pipeline that produces capital market assumptions, constructs portfolios using 20 competing methods, has every agent critique two others, holds a vote, and then writes a board memo for non-technical stakeholders.

The entire process runs without a human making a single analytical decision.

I downloaded the paper. I fed it into Claude. Then I spent a weekend building a stripped-down version of the same architecture with three agents instead of fifty.

The first decision was what to cut. The paper runs 50 agents across five layers. I kept the three that contain the essential logic: the macro regime agent whose output governs everything downstream, the asset analyst agent that estimates returns using three competing methods, and the adversarial challenger whose job is to find everything wrong with what the first two produced. I cut the 20 competing portfolio construction methods and the peer review voting layer because those require infrastructure I did not have. What I kept was the specialisation, the adversarial checking, and the feedback loop.

The first full run produced something I did not expect.

Agent 1 output — Macro Regime

• Regime: Late-cycle with elevated stagflationary risk

• Confidence: 7/10

• Primary signal: yield curve re-inverted after a brief normalisation, high-yield spreads widening, core PCE reaccelerated for second consecutive month

• Implication: reduce equity duration exposure, favour short-duration credit over long bonds, hold elevated cash

Agent 2 output — US Equities

• Method 1 (10-year historical): 13.2% expected return

• Method 2 (Shiller PE valuation-implied): 4.8%

• Method 3 (regime-adjusted): 5.9%

• Composite: 5.6% (weighted 50% valuation-implied, 35% regime-adjusted, 15% historical)

• Flag: 760 basis point gap between historical and valuation-implied was the widest since 2007

Agent 3 output — The Attack

Agent 3 did not attack the return estimates. It attacked the regime classification itself.

It pointed out that yield curve inversion and credit spread widening both carry 6 to 18 month lead times before actual recession onset. Which meant Agent 2 had applied a recession-era return discount to assets still operating in a functioning late-cycle environment. The correlation assumptions were calibrated for a deterioration that had not yet arrived.

Then it named the scenario that breaks everything simultaneously:

A soft landing where PCE reaccelerates without recession. Fed on hold through Q3. Equity multiples expand on the expectation of eventual cuts. In that scenario the valuation-implied estimate is wrong because multiples expand anyway. The regime classification is wrong because the cycle extends. The portfolio ends up underweight equities during a melt-up driven by the exact conditions the agents had flagged as risks.

I had not thought about that scenario. I updated my equity positioning before the week ended.

What the Paper Actually Built

The researchers ran their full pipeline in March 2026 against a real institutional mandate: 18 liquid asset classes across 6 equity, 8 fixed income, and 4 alternatives categories. Target real return of CPI plus 3 to 4 percent. Volatility band of 8 to 12 percent. Maximum drawdown of negative 25 percent. Tracking error ceiling of 6 percent relative to a 60/40 benchmark.

The architecture is organised around the Investment Policy Statement, the same document that governs human portfolio managers. Every agent reads it. Every output must satisfy it. This is not a detail. The IPS as the governing constraint is what prevents the pipeline from optimising for something other than the mandate.

The pipeline runs across five distinct layers.

Layer 1: Macro AgentClassifies the current economic regime using macro data, market indicators, and live web searches. Its output flows downstream to every other agent. Nothing else runs until this completes.

**Layer 2: Asset Class Agents (×18, run in parallel)**One agent per asset class. Each estimates expected returns using six different methods, then blends them into a seventh composite. An LLM-as-judge step reads all seven alongside the current macro regime and valuations, and selects a final estimate with explicit weights and a written rationale.

**Layer 3: Portfolio Construction Agents (×20)**Each builds a portfolio using a different method, ranging from simple rules to sophisticated optimisation. A 21st researcher agent scans the academic literature and proposes methods not yet in the pipeline. A separate adversarial diversifier deliberately constructs the portfolio most different from the consensus of all the others.

Layer 4: Peer Review and VoteEach agent reviews two others simultaneously — one using a similar approach, one using a different one. All reviews are released at the same time. Agents then vote using Borda-count ranking. The final shortlist must include methods from at least three of four broad categories.

Layer 5: Meta-AgentAfter each rebalancing cycle, compares past forecasts against realised returns, identifies systematic weaknesses, and updates both the code and instructions governing the other agents. All changes are logged. The system rewrites itself.

What the Pipeline Actually Found

The results of the March 2026 run are worth understanding because they demonstrate what happens when you remove human bias from the analytical process.

The macro agent classified the current environment as late-cycle with stagflationary risk.

The valuation-adjusted forecasts showed a consistent pattern across asset classes:

• US Growth stocks: forecast cut 2.0 percentage points below the historical composite

• US Large Cap: cut 1.1 points below the composite

• Emerging Markets: barely adjusted

The agents were not pessimistic across the board. They were specifically skeptical of backward-looking estimates for the assets where current prices already implied low future returns. A human analyst anchored to historical averages would have produced a very different output.

The final portfolio allocation:

• Equities: 44.9% (vs 60% in standard 60/40)

• Bonds: 41.7% (roughly in line)

• Cash: 8.1%

Backtest results from 1996 to 2026:

• Return profile: nearly identical to 60/40

• Peak-to-trough drawdown: 25.6% vs 34.3% for 60/40

Same returns. Eight percentage points less drawdown. That is the entire argument for the architecture.

The researchers are honest that one run is a proof of concept, not a validated strategy. The paper is not claiming to have built a better hedge fund. It is claiming to have built a replicable process that removes the bandwidth bottleneck from institutional portfolio management.

Why This Architecture Is Accessible to Anyone With Claude

The insight I took from the paper is not that you need 50 agents. It is that the structure of the pipeline, specialised roles, peer review, adversarial checking, and a governing constraint document, can be rebuilt at any scale.

Three components from the paper are fully implementable in Claude Projects today:

Specialisation — Each agent has one job and one output format. It does not do general analysis. The regime agent does not comment on valuations. The asset agent does not comment on macro. That constraint forces depth over breadth on every output.

The adversarial diversifier — The agent specifically designed to disagree with consensus is the single most valuable element in the architecture. Most people building multi-agent systems make every agent try to find the right answer. This paper deliberately includes one whose job is to find the most different answer. That tension is where the risk management comes from.

The meta-agent feedback loop — After every cycle, performance is compared against forecasts and the underperforming agents get updated instructions. The system improves itself. This is what separates a multi-agent pipeline from a slightly more complex prompt.

The Three-Agent Version I Built

I am not running 50 agents. I built three that cover the essential logic of the pipeline without the institutional infrastructure.

Agent 1: The Macro Regime Agent

This agent runs first and its output governs everything that follows. It reads current macro data, recent Fed communications, and market indicators, then outputs a single regime classification with explicit reasoning.

Prompt

You are a macro regime analyst. Your only job is to classify the current economic environment.Search the web for current data on: GDP growth trajectory, inflation trend, employment data, yield curve shape, and credit spreads.Output exactly this structure: Regime: [Expansion / Late-Cycle / Recession / Recovery] Confidence: [1-10] Primary signal: [the single most important data point driving this classification] Risk: [the single biggest factor that could make this classification wrong] Implication for asset allocation: [one sentence on what this regime historically means for portfolio positioning]Do not produce a summary of economic conditions. Produce a regime classification with explicit reasoning. This output will govern two other agents that follow.

Agent 2: The Asset Analyst Agent

This agent runs once per asset class you want to analyse. It takes the regime classification from Agent 1 as a required input and adjusts its expected return estimates accordingly.

Prompt

You are an asset class analyst evaluating [ASSET CLASS].Current macro regime from the Macro Agent: [PASTE AGENT 1 OUTPUT]Estimate the expected return for this asset class over the next 12 months using three different methods: Method 1: Historical average return over the last 10 years Method 2: Current valuation-implied return (use Shiller PE for equities, yield-to-maturity for bonds) Method 3: Regime-adjusted return (adjust your estimate based on the macro regime provided)Then produce a composite estimate that explicitly weights each method. State the weight you assigned to each method and why.Flag if the current valuation suggests discounting historical returns. Flag any factor that could make all three estimates wrong simultaneously.Output format: three method estimates, composite, weights, and flags.

Agent 3: The Adversarial Challenger

This is the most important agent in the system. Its job is not to find the right answer. Its job is to find everything wrong with what Agents 1 and 2 produced.

Prompt

You are the adversarial agent in a portfolio construction pipeline. Your job is not to agree with the analysis that preceded you. Your job is to find everything that could be wrong with it.Here is the macro regime classification: [PASTE AGENT 1 OUTPUT] Here are the asset class return estimates: [PASTE AGENT 2 OUTPUTS]Attack this analysis on four dimensions:1. Regime misclassification: What evidence exists that the regime classification is wrong or about to change? Name the specific data points.2. Valuation blind spots: Which asset classes have their downside risk most understated by the current estimates? Why?3. Correlation assumptions: What happens to this portfolio if two assets that are historically uncorrelated move together? Which pair is most at risk?4. The scenario nobody modelled: Describe the specific macro scenario that would make the composite estimates wrong simultaneously across the most positions.Do not be polite. Do not balance criticism with positives. Your value is in finding what the other agents missed.

What This Setup Produces

Running these three agents in sequence produces something qualitatively different from asking Claude to analyse a portfolio in a single prompt.

The specialisation forces each agent to go deeper on one question rather than producing a broad overview. The regime agent does not comment on valuations. The asset agent does not comment on macro. Each output is narrower and more useful than what a general analysis prompt returns.

The adversarial agent is the step most people skip when they build their own multi-agent systems. It is also the step that produces the most useful output.

Most people building pipelines like this make every agent try to find the right answer. The paper deliberately includes one agent whose entire mandate is to find the most different answer. That tension is where the risk management comes from. An analysis that has not been attacked is not analysis. It is confirmation bias with extra steps.

The example above is what that looks like in practice. Agent 3 did not find a data error. It found a logical inconsistency between two agents that were both individually correct but collectively producing a flawed composite. The regime classification was accurate for the current moment. The valuation adjustment was accurate for the current moment. But applying a recession-era discount inside a functioning late-cycle environment is a category error, and no single-prompt analysis would have surfaced it because there is no mechanism to check one part of the analysis against another.

That is the structural value of the adversarial agent. It does not need to be smarter than the other agents. It just needs to be looking for what they missed rather than confirming what they found.

The Meta-Agent Layer You Can Add

The paper’s most differentiated feature is the meta-agent that rewrites agent code after comparing forecasts against realised returns. That requires running the system over multiple cycles and logging the outputs.

The lightweight version: after every cycle, run this prompt against your logged outputs.

Prompt

Here are the outputs from the last [N] cycles of this portfolio analysis pipeline: [PASTE LOGGED OUTPUTS]Here are the actual returns that followed each set of predictions: [PASTE REALISED RETURNS]Identify: 1. Which agent was systematically wrong? In what direction? 2. Which regime classifications had the worst predictive accuracy? 3. Which asset class estimates were most consistently off? Was the error directional? 4. What should change in the instructions for the agent with the worst track record?Output revised instructions for the underperforming agent. Explain specifically what in the original instructions produced the systematic error.

This is the feedback loop that makes the system improve over time rather than running the same analysis repeatedly and expecting different results.

The Honest Assessment

The full 50-agent pipeline requires:

• Engineering infrastructure

• API connections across 18 asset class data sources

• Automated scheduling across multiple rebalancing cycles

• A multi-month calibration period for the meta-agent

What I built is not that.

What I built is a Claude-native version of the three most important structural elements. It runs in a Claude Project in an afternoon. It does not produce institutional-grade portfolio allocation. It produces a structured analytical process that is significantly more rigorous than a single-prompt analysis because it forces explicit reasoning at each step and then attacks that reasoning before you act on it.

The paper’s core argument: agentic AI shifts the investor’s role from analytical execution to oversight. That shift does not require 50 agents to be real. Three agents running a structured process with adversarial checking changes the quality of the analysis you produce, whether the mandate is your own portfolio or an institutional one.

The paper is publicly available and free at arxiv.org/pdf/2604.02279. Download it, upload it to a Claude Project as context, and run the three prompts above in sequence. The architecture section starts at page 4. The agent role descriptions are specific enough to extend into additional agents once you have the three-agent version running.

The full pipeline code is being developed publicly. Watch the Altbridge team at altbridge.ai for updates as they build toward a production version of what the paper describes.

The gap between people who read papers like this and people who build from them is becoming one of the more visible divides in how serious investors actually work.

Follow @damidefi on X for daily Claude AI tools, crypto analysis, and the full journey to 100K. Bookmark this. Share it with one person still running single-prompt portfolio analysis.