Early in 2012, a portfolio in JPMorgan Chase’s Chief Investment Office was running over its risk limits. Then a new value-at-risk model arrived, and the problem seemed to vanish. The new model roughly halved the portfolio’s reported risk.

Months later, the trades that became known as the “London Whale” had produced losses exceeding $6 billion. An internal review by the bank later found that the new model relied on spreadsheets populated through manual copy-and-paste steps and contained calculation errors.

The trades were risky. More unsettling was the number that declared them safe.

That is the paradox at the heart of algorithmic trading risk management. Any risk system is, in the end, another model, built by people, implemented in code, and fully capable of being wrong. Surviving institutions have learned to pose a question most traders overlook. Who measures the measurer?

Why a Single Number Fails

Value at risk became popular because it compresses a portfolio’s danger into one figure. Its simplicity is also its flaw. VaR describes losses under ordinary conditions and says little about how bad the worst days can be.

Regulators learned this too. The Basel Committee’s revised market risk framework replaced VaR with expected shortfall in bank capital models. Expected shortfall asks a harder question: once you are in the tail, what does the average loss look like?

The principle reaches well beyond banks. Rigorous quantitative trading research doubts its risk metrics as much as it doubts its alpha signals. Each metric is tested against historical crises, its assumptions are documented, and any change to its methodology receives independent review. A risk model that cannot be challenged is merely an opinion with decimals.

Speed Is a Risk Too

On May 6, 2010, U.S. markets suffered the Flash Crash. A joint SEC and CFTC report pointed to a key trigger, a sell program of 75,000 E-mini S&P 500 futures contracts executed by an algorithm that targeted a share of trading volume without regard to price or time.

The position was ordinary. Its execution was not constrained.

Institutions now build execution limits directly into AI trading system development. Typical controls include price collars that block orders far from the prevailing market, participation caps, order-rate throttles, and checks that pause an algorithm when conditions shift faster than it was built to handle. Exposure limits govern the size of a loss. Execution limits govern its speed.

Stack the Controls

Mature risk architectures seldom depend on a single control. They stack several.

Before an order leaves the firm, pre-trade checks reject it if it violates size, price, or credit limits. During the day, real-time monitoring tracks positions and losses against hard limits that halt trading and soft limits that trigger escalation. Post-trade review then compares what happened with what was supposed to happen.

Every layer assumes the previous one may fail. That is not pessimism. It is engineering.

Treat Risk Code as Critical Code

The London Whale model failed partly through ordinary software problems: manual processes, insufficient testing, and weak change control. Institutional algorithmic trading software development now treats risk logic with the rigor usually reserved for trading engines. Changes require version control and peer review, and new models run in parallel with old ones before any switch.

Historical crises are replayed through the systems as well, to verify that the controls really trigger. This is often where AI trading infrastructure consulting proves most useful. Outside specialists, unattached to the current design, can test whether the safeguards survive conditions their builders never pictured.

Give Breaches Authority

The strength of a limit depends entirely on what happens once check here it is breached. At disciplined institutions, a breach is escalated to people independent of the trading desk, and the default response is to cut risk rather than revisit the limit.

The riskiest moment in any risk framework comes when someone explains a breach away.

The Four-Question Audit

Before you trust a risk framework, ask four questions:

Was the risk model validated by people independent of its owners?
What does the system do in the tail, not just on an average day?
Could an algorithm lose money faster than a human can step in?
When a limit is breached, which changes: the portfolio or the limit?
The Number That Feels Like Safety

Risk numbers hold an odd emotional power. They help people sleep and let committees approve. They make uncertainty look like knowledge.

Institutions surround these numbers with doubt for exactly that reason.

The London Whale trades did not hide. They sat in plain view and were measured every day. The danger was never invisible. It was recorded in a number everyone wanted to believe.