This is the first post in a three-part series autopsying the short-dated NVDA options trade where retail traders lose money. Post 1 covers FOMC. Post 2 will cover earnings. Post 3 will cover non-event days. The thesis across the arc: the danger in short-dated NVDA options is not being wrong on the event, it is being on the option-buying side at all.

Summary in ~200 Words

Retail is setting up a bounce trade in NVDA into Wednesday’s FOMC decision. NVDA is down 7% from its July 14 high, semis are down 12%, the Fed is expected to hold at 3.50-3.75%, and a dovish tone from Chair Warsh at 2:30pm would give the market a reason to buy the AI names back. Buying ATM NVDA 0DTE calls into that setup looks like a cheap way to get leverage on the bounce, with the maximum loss capped at the premium paid.

So I pulled every FOMC decision day from February 2023 through June 2026 — 28 events — and simulated buying an ATM NVDA 0DTE call at 1:45pm and holding to 4:00pm close. The mean return is +151.7%. The median return is −45.6%. The hit rate is 42.9%. Three tail events out of 28 drive the entire positive mean; strip them out and the mean flips to −2.4%. Theta is a certain loss on every single event without exception. The sum of delta, vega, and theta before convexity is −95% of entry premium on average.

This is a lottery ticket. It has a positive expected value on paper, sits below chance on hit rate, and pays out the mean only on days that account for 7% of the sample.

So effectively, retail is not buying a leveraged bounce trade. They are buying a lottery ticket priced to look like a leveraged bounce trade.

The Latvian Gambit

You didn’t really think I was going to write a post without one of these, did you?

In July 1955, at the U.S. Junior Championship in Lincoln, Nebraska, a twenty-year-old Viktors Pupols told a twelve-year-old Bobby Fischer that he was going to play the Latvian Gambit against him that evening. Fischer did not believe him. Pupols played it anyway — 1.e4 e5 2.Nf3 f5, one of the oldest and worst opening lines in chess. It’s one where White scores 62% and Black scores 17% at the master level. Fischer lost on time. It was one of only two games he would ever lose on the clock in his entire career. Pupols would later say, “Bobby lost more Latvian Gambits that afternoon than in all the rest of his life.”

Capablanca lost to the Latvian Gambit too. The opening survives on the rare occasion when White does not know the refutation cold and Black lands a haymaker before move twenty. Most Latvian games are Black losses (bite me if you want to debate this). But a small number are spectacular Black wins. But the average result is a loss.

But every so often the win is big and a new generation of players convinces themselves the opening is actually good.

Buying an at-the-money NVDA 0DTE call into FOMC is the Latvian Gambit. Most trades lose. A handful of trades win spectacularly and post on WSB. The average return is dominated by those handful of oversized wins, and if you strip them out, the average trade is a pretty bad loser.

The retail poster screenshotting a +1,400% FOMC-day NVDA call is showing you the equivalent of Pupols beating Fischer on time in Nebraska. It does not mean the opening is playable.

The Setup Retail Sees

NVDA closed Tuesday at $197, down 7.1% from the July 14 intraday high of $211.78. The broader semi complex is worse — SMH is down 11.8% over the same ten-session window, and second-tier semis have been hit harder than NVDA. In fact, NVDA is holding up better than its sector index, which most of retail would read as strength within a weak group.

The Fed decision lands Wednesday at 2:00pm ET. Consensus is a hold, the fifth consecutive meeting with no move. Chair Kevin Warsh’s press conference at 2:30pm is where any surprise would come from, and market-implied odds of a rate hike later in 2026 have climbed back to roughly 40% on rising oil prices. The tail risk sits on the hawkish side of the print, not the dovish one. But of course, retail is buying calls (at least that’s the sense you get if you read WSB).

The retail thesis has four assumptions — (1) NVDA has bottomed, (2) a dovish Fed triggers a bounce (3) NVDA gets the most leverage on that bounce because it is the highest-beta name in AI, and (4) a 0DTE call caps the downside at whatever you paid for it. Every one of those claims is defensible in isolation. But problem shows up when you check them against what NVDA has actually done on 28 previous FOMC days.

The Distribution Retail Is Actually Buying

The mean return on an ATM NVDA 0DTE call across 28 FOMC decision days from February 2023 through June 2026 is +151.7%. That number, on its own, sells the trade. Buy the call, hold to close, walk away with a 2.5x on average. It is also a completely misleading way to describe what happens on the trade.

The median return on the same 28 events is −45.6%. The hit rate is 42.9%. Twelve of twenty-eight trades finished in the green, sixteen finished in the red. The mean sits at +151.7% because three events — February 1, 2023 (+2,046.5%), July 31, 2024 (+1,418.7%), and May 7, 2025 (+840.5%) — carry the entire positive average.

Strip those three days out and the mean of the remaining 25 events is −2.4%. Twenty-two of the 28 events, or 79% of the sample, are the trade that most closely resembles what a retail buyer would experience: a call that mostly loses money.

This is what a lottery-ticket’s distribution looks like. Most tickets lose. A small number pay out enormously. The mean of a lottery ticket can be positive and it can still be a bad trade if you cannot survive the losses to collect the wins, or if you cannot run the trade often enough for the tail to converge to the mean. A retail trader running the NVDA 0DTE call four to eight times a year on FOMC days is not running it often enough for the mean to matter. They are running it often enough to lose four or five times in a row and stop, months before the tail event lands.

The at-the-money 0DTE put fares worse across the board. Mean −9.6%. Median −100%. Hit rate 32.1%. Puts are structurally worse because NVDA’s upward drift over the sample dominates and because the ATM strike grid puts a Wednesday put slightly out of the money at entry.

The at-the-money straddle — long both call and put — is the only structure in the dataset with a hit rate above chance. 57.1%. Mean +34.8%. Median +21.7%. It collects on both convexity events and does not need to guess direction. It also costs roughly double the premium of either leg alone and typically it is not the trade retail is running. Typically, retail buys calls directionally, expecting a bounce.

Where the Money Actually Went

The way to see why the median is so negative even with a positive mean is to decompose each simulated call into its Greek components. For every event, I computed the delta, vega, and theta contributions to P&L using the entry-time Greeks, and let the residual capture gamma and other higher-order curvature.

Theta is negative on 28 of 28 events. Mean theta contribution is −129.1% of entry premium. There is no exception, no meeting where time decay worked in the buyer’s favor. The 2:15 window between the 1:45pm entry proxy and the 4:00pm close bleeds premium on every single historical event.

Vega is negative on 16 of 28 events, or 57.1% — the same number as the VIX-down count. Mean vega contribution is +6.0% but median is −1.0%, which means vega is slightly positive on average because the two big hawkish shocks (December 2024 and September 2023) inflated VIX and juiced vega on those days. On the median FOMC day, vega is a small loss.

Delta contribution mean is +27.7%. NVDA drifts up slightly more often than down across the sample, which produces a modest positive delta lean. But the delta gain is dominated by theta in every low-move event. Delta needs a real move to overcome the theta bleed, and the median move is not big enough.

Sum delta, vega, and theta: −95% of entry premium on average.

The three Greeks that describe the smooth, priceable part of the option’s value together predict a nearly complete wipeout on the average trade.

The reason the actual mean comes out to +151.7% is a +247.1% residual, which is gamma and near-expiry curvature that first-order Greeks cannot capture (if you are wondering what a residual is, it’s what’s left of the P&L after you subtract the delta, vega, and theta contributions — mostly gamma and other higher-order curvature the linear Greeks miss).

That residual is not a repeatable edge. It is the same three-event tail as before, re-expressed in Greek terms. The convexity payoff is real, and it is entirely concentrated in the handful of days when NVDA moved 7% or more on the print.

The Rotation Read Doesn’t Transfer

The idea that NVDA is the “safe semi” and is better positioned than the sector because it has outperformed SMH during the July drawdown largely holds up in a very specific window. From the July 14 peak to Tuesday’s close, NVDA is down 6.98% and SMH is down 11.78%. NVDA has outperformed by roughly five percentage points over ten sessions.

But that relationship does not transfer to FOMC days. NVDA’s beta to SMH across the 28 FOMC decision days in the sample is 1.37. The all-days beta over the same two-year window is 1.10. NVDA moves relatively harder against SMH on FOMC days than on an average day, not softer. NVDA moved in the same direction as SMH in 24 of 28 FOMC events, or 85.7%, and moved by more than SMH in absolute terms in 21 of 28, or 75%. Mean absolute NVDA move on FOMC day is 2.69% against 1.86% for SMH.

So WSB and retail are reading NVDA’s outperformance over the last two weeks — which came out of company-specific AI-capex news, not sector-level defensiveness — as a signal that NVDA will hold up better than SMH on Wednesday.

The historical data says the opposite. On FOMC days, NVDA has been the amplifier within the semi complex, not the shock absorber. If SMH sells off on a hawkish surprise, NVDA has historically sold off harder.

What the Trade Actually Needs

Using Tuesday’s close as the 1:45pm-proxy entry point, the nearest-$5 ATM strike is $195, which puts the call $2.01 in the money at entry. The modeled call premium is $2.83 per share, or $283 per contract. Breakeven at expiry is $197.83, only 0.42% above the entry spot. That looks like a small required move because the option is already $2 intrinsic — the breakeven is deceptively (or perhaps perilously) close.

The question is not where breakeven sits. The question really is what does NVDA need to do to produce the returns retail is chasing?

Well, a 2x return on premium requires NVDA to move +1.85% on the day, which has happened on 9 of the last 28 FOMC days — a 32.1% hit rate. A 5x requires +6.16%, which has happened 2 of 28 times, or 7.1%. A 10x requires +13.34%, which has never happened once in the sample.

The 10x is literally impossible on this historical sample. No FOMC day in the last three and a half years has produced a large enough move. The single biggest single-day NVDA move in the entire 28-event dataset is +12.81% on July 31, 2024, which still falls short of the +13.34% required for a 10x. The retail poster who screenshots a “I’m looking for a 10x” thread before Wednesday is asking for something that has not happened once in the observable history of this trade.

The 5x is a 7% event. The 2x is a 32% event. Neither is the base case. Both sit well below the hit rate retail assumes when they estimate their edge.

What Would Change the Read

The vol-crush and theta arguments hold up cleanly across the sample and are not sensitive to small changes in methodology. What is sensitive is the tail. If tomorrow’s FOMC produces an outlier NVDA move — a genuine dovish surprise from Warsh that resets rate expectations, or a hawkish surprise that breaks the recent range in the other direction — the trade lands in the tail bucket that pays out the historical mean. That is the scenario WSB is implicitly betting on. It is not zero-probability. After all, it is a 7% base rate, and it is what you are compensated for when you are holding through the theta and vega drag.

The read also breaks if NVDA IV going into Wednesday were closer to its trailing realized rather than elevated. In that eventuality, the pre-decision IV proxy puts NVDA implied vol at 56%, meaningfully above its trailing 30-day realized. Retail is paying up for that spread. If pre-event IV compressed materially between now and Wednesday morning, the theta and vega drag would shrink and the trade’s expected value would improve. That is not the setup on the tape.

There is also a channel this analysis does not capture. MSFT reports Wednesday after the close, META and AMZN report Thursday. If those prints confirm continued AI-capex spending, NVDA can rally on the reports alone, regardless of what the Fed does. That is a two-to-three-day trade with multiple catalysts. A 0DTE call bought Wednesday morning expires before the first earnings release even hits the tape.

What Comes Next

This is Post 1 of the 0DTE Autopsy arc. Post 2 covers NVDA 0DTE and 1DTE calls into the late-August earnings print, where the mechanism shifts from macro mispricing to idiosyncratic vol crush. Post 3 covers non-event days, where retail pays theta and IV premium on days when nothing happens. FOMC is where the argument is cleanest, because theta is guaranteed, vega is negative on the median day, and delta cannot outrun them without a tail move.

The three days in the sample that produced the outsized wins were not what a retail trader would call “a bounce trade into a dovish Fed.” They were extreme reactions to Fed communication that reset how the market thought about rates for months afterward. Buying the ticket does not put you in that bucket. It just puts you on the hook for the premium.

This post is not a trade recommendation. It’s an analysis of what the vol surface is pricing in and what the historical distribution of outcomes has been on FOMC days. Position sizing, risk tolerance, and holding period are your problem. Alpha is never guaranteed and the backtest is a liar until proven otherwise. Do your own research and eat your vegetables.

This is the last part of the Tech Schism series. Part 1 laid out the capex-driven fracture inside the AI trade. Part 1.5 explained why the correlation trade is a trap. Part 2 mapped the dispersion the options market hasn’t priced and we discussed publishing the NVDA/MSFT position math with the sizing, the four break scenarios, and the specific stops. The prequel — QQQ Is Lying to You — is my concentration argument that started all this.

Immortal Zugzwang Game

As some of you know, I love chess. Well, I’m not particularly good at it but I enjoy playing it.

In the Immortal Zugzwang Game (Copenhagen, 1923), Aron Nimzowitsch (playing Black) built a position against Friedrich Sämisch where every legal move worsened White’s position. Nimzowitsch’s 25th move was a quiet pawn push — h6 — that did absolutely nothing. It made no attack, no capture, and no threat. Nimzowitsch then supposedly said “Jetzt müssen Sie ziehen!” (“Now you must move!”). Reuben Fine called it “the most remarkable winning move on record.” Of course, Sämisch resigned rather than move.

I think that game exemplifies this post more than anything.

Summary in ~300 Words

In Part 2, I committed to publishing the NVDA/MSFT position math with the sizing, the four break scenarios, and the specific stops. Between then and now, I’ve done 3 pieces of work (full code link at the bottom):

• Built the sizing model from trailing-4-quarter capex normalized by market cap and adjusted for the vol differential

• Priced out four breaking scenarios on the resulting book using historical analogs and Black-Scholes vega/theta

• Interpreted the Alphabet term-structure resolution after its July 22 earnings print against what Part 2 flagged.

The most important takeaway is that the sizing model recommended MSFT weighted ~22x heavier than NVDA on the short vol leg.

Please note that that is a position weighting, not a return multiple. This is an important caveat.

On an illustrative $1M NVDA notional / $21.9M MSFT notional book, the four scenario outcomes sit in the single-digit-percent range on gross notional, and their signs invert what the trade brief anticipated. The mechanism confirming (MSFT vol expansion on capex disclosure) is a loss of $633K to $1.42M. Both names compressing is a carry gain of $406K to $1.12M. The trade’s dominant risk is not holding it wrong but rather the thesis playing out against you.

Alphabet’s term-structure signal from Part 2 resolved as earnings noise and not as a structural inversion. Alphabet’s 30d IV collapsed 7 vol points post-print and the 30d-90d slope went from +5.13 to -0.25 vpts — a 105% collapse into contango.

One note: MSFT, META, and AMZN (none of which have reported) are still in backwardation. So part 2’s quick eyeballing test was right.

It’s important to note that NVDA/MSFT RV ratio has already moved from the 8th to the 20th percentile over two weeks.

So, the trade window is narrowing. The binding stops are the ratio breaking below the 5th percentile (0.8615, currently 1.097) and MSFT’s July 29 print showing D&A/revenue below the model’s 11.02% trajectory. Theta doesn’t bind on either sizing basis — it is a tailwind at the recommended sizing and a wash at par notional.

(I ran the tests again today after market close, but I am leaving it in as an insight into the importance of using the most current information to trade…)

The NVDA/MSFT RV ratio sits at 0.998 as of July 23 close — essentially at the Part 2 level of 0.944 (8th percentile) and one bad session from the 5th-percentile stop trigger at 0.862. So the setup Part 2 identified is fully intact. The compression didn’t unwind; the Jul 22 pop to 1.097 (20th percentile) reversed the next session. Binding stops are the ratio closing below 0.862 and MSFT’s July 29 print showing D&A/revenue below the model’s 11.02% trajectory. Theta doesn’t bind on either sizing basis.

The Sizing Math

The capex-intensity approach is pretty straightforward. Take each name’s trailing-4-quarter capex, normalize by market cap, and then you use the ratio to set position size.

• NVDA’s trailing-4Q capex is $6.6B against a market cap north of $5T —> so capex/mcap of 0.128%.

• MSFT’s trailing-4Q capex is $97.2B against a market cap around $2.9T —> so capex/mcap of 3.353%.

That is a 26.2x gap in capex intensity by market cap, and the forward 2027 estimates push it to 30.2x.

Adjusting for the vol differential (NVDA 30d ATM IV of 39.03%, MSFT of 46.76%, so MSFT’s vega is roughly proportional to its higher spot and comparable IV level), the recommended sizing ratio is:

NVDA_notional / MSFT_notional = 0.0457

Or, equivalently: for every $1 of long NVDA vol you put on, capex-intensity math wants $21.9 of short MSFT vol on the other side. On a $1M NVDA notional basis, the paired MSFT leg is $21.88M.

That is an extreme sizing skew, so what exactly does this mean?

Well, for one it does not mean the trade returns 22x. It means the pair is weighted so heavily toward the short-MSFT leg that MSFT vol dominates the P&L on both sides — MSFT vol expansion is the worst case, MSFT vol compression is the best case, and the NVDA leg is a directional tilt riding on top.

Now, to be candid the reality is that 22x is likely too extreme to trade as a book-level exposure. A more moderate implementation would treat capex intensity as a directional bias, where it is sized somewhere between vol-equivalent (roughly par notional) and the full 22x. And do so while keeping the trade’s core logic intact. Everything that follows uses the full 22x sizing because that is what the math suggests. So you must scale the P&L linearly to your actual weighting.

The Alphabet Resolution

Now in Part 2, I said I’d publish what Alphabet’s July 22 print did to the term-structure signal. I had flagged that the Alphabet backwardation might just be pre-earnings positioning and it was (yes, yes, proud noises…) ;-)

Alphabet’s 30d ATM IV went from 41.16% pre-print to 34.16% post-print — a 7.00 vol-point collapse. The 30d-90d slope went from +5.13 vpts (backwardated) to -0.25 vpts (contango) — a 105% collapse in less than 48 hours.

GOOGL sold off 1.46% on July 22 close and 7.13% on July 23. The move was earnings-driven, and it is worth noting that the pre-print term-structure inversion was priced-in event risk vs. the options market waking up to the capex-cycle mechanism.

Now, the three hyperscalers that have not yet reported (MSFT July 29, META & AMZN July 30) continue to remain in backwardation. The Part 2 dispersion signal on the pre-print set survived Alphabet’s print. What Alphabet resolved is that we cannot read a single hyperscaler’s term structure as evidence of the mechanism being priced.

This is super important — we have to read the set collectively, and I am eager to see what happens through the MSFT and AMZN prints next week.

The Four Break Scenarios

Every scenario below is priced on the illustrative $1M NVDA / $21.9M MSFT book at current spot and 30d ATM IV, using Black-Scholes vega and theta on ATM straddle proxies. You can scale linearly to your actual sizing.

Now, I can’t stress this enough — but this is directional and don’t take this as gospel. Sizing is its own thing, and you should find out what balances your risk appetite vs. ROI. If you are interested, you can read my series on the Kelly Criterion and Position Sizing.

Okay, with that out of the way, here are the four scenarios (I used Claude to model these):

Stops and Exits

Every trigger and target below is calibrated off the 21d rolling RV ratio, the trailing 12-month percentile distribution, and MSFT’s straight-line D&A/revenue trajectory from Part 2. Nothing here is a fixed price level — the ratio itself is the state variable, and it recomputes every close.

And I’ll say the same caveat as above here. Whatever stop distances and profit targets you use should reflect your own conviction, risk appetite, holding period, and how much of the position you can afford to be wrong on.

At some point, I’ll write more about the machinery behind percentile-based stops and how they compare to fixed-price stops.

What Comes Next

This closes the Tech Schism arc as I’d originally planned it. My next next post will pick up the thread that we very briefly discussed but did not fully resolve, i.e. whether the dispersion signal generalizes past the NVDA/MSFT pair to the broader hyperscaler and semi-cap-equipment complex, and what the META and AMZN prints tell us about that.

The arc’s core claim is that the AI trade is fracturing along capex-intensity lines and the options market is only partially pricing it — I firmly believe that hypothesis is still very much intact.

My experiment above is simply one implementation of that claim but obviously not the only one.

Sources: yfinance daily price history (NVDA, MSFT, GOOGL, SPX); SEC EDGAR XBRL actuals for MSFT D&A/revenue; Part 2 straight-line depreciation model for the projected quarter ending June 30, 2026; point-in-time options data for GOOGL 30d/90d ATM IV.

Full methodology and code: https://github.com/kniyer/silicon-post3

Not financial advice. Alpha is never guaranteed. Blah blah blah. Seriously, this is for educational purposes so use it as such.

My next post in the Tech Schism will be on July 25th, after Alphabet’s earnings on July 22nd, where the term structure question should resolve itself.

Taking a break from the Tech Schism series for something different and interesting.

sent me a chart last week and shared a hunch. Through the correlation unwind in June — and the not-quite-unwind since — he kept watching the same thing intraday: the tape would travel a long way, VIX would lurch from 16 to 17-and-change and settle back near 16-and-a-half, and by the close realized vol had barely shown up for all that motion. The next day, the same figure at a different size. Within the hour, again. So he pinged me saying “this looks fractal”.

He’s right. There’s a wrinkle underneath it, though, and it’s kinda important. The fractal that’s easy to draw isn’t the same object as the one he’s watching. Pinning down the difference is what turns a cool metaphor into something you can actually trade.

Doc wrote the market side of this — the dispersion coil, the wound spring, why the tremors are real evidence and still not a timing signal.

🌀 The Market’s Been Rehearsing: What Fractal Days Are Actually Telling Us About the S&P 500 Freebie

My post is basically the machinery underneath it all: what the fractal actually is, and where the eye gets fooled.

And before we dive in, here’s the demo to play with:

https://multifractal.mathandmarkets.com/

The easy answer

Dig into “markets are fractal” and you land quickly on Mandelbrot, who was careful about an important distinction. A coastline is self-similar: zoom in and you get the same jaggedness, with no preferred direction — it scales the same in every axis.

A price chart is self-affine: it has a distinguished axis, because time is not price. Zoom in and you can’t recover the look by stretching both axes equally. You have to stretch them by different amounts.

Empirically, price wanders as roughly the square root of time, so to make a slice look like the whole you stretch time by some factor k and price by only √k. Mandelbrot insisted on “self-affine” for exactly this reason, and it’s the precise version of “the chop looks the same zoomed in or out.”

A little more precisely: a process is self-affine with exponent H if rescaling time by any factor c reproduces the same distribution once you rescale price by c^H — in shorthand, X(ct) has the same law as c^H · X(t). The same H then governs every moment of the increments: E[ |X(t+Δ) − X(t)|^q ] ∝ Δ^(qH) for all q. For a price series H = ½, which is just the √time law — variance grows linearly in time, the price-axis rescale factor is √c, and the exponent qH = q/2 traces a straight line through the origin. That single straight line is the entire content of the demo.

Doc built a demo that shows it cleanly. Drag the zoom, and a slice of the path, rescaled by k in time and √k in price, reassembles into something indistinguishable from its parent. Stretch both axes equally instead and the slice goes flat — proof, apparently, that the market lives by the √-scaling law.

It was correct but it’s got a caveat.

That path is a coin flip

Look at what generates the demo’s curve: a fractional Brownian path tuned to a Hurst exponent of one-half. H = ½ is not arandom walk near the market. It is the random walk. Independent increments, variance growing linearly in time, price spreading as √time. Brownian motion is the continuous limit of coin flips, stacked.

So the demo proves that markets share a property with a fair coin. A random walk passes the rescale test perfectly — of course it does; √-scaling is its definition. Which means passing the test tells you nothing about the part Doc actually noticed. The test is necessary and nowhere near sufficient.

And a coin flip is missing everything interesting. No fat tails — Brownian increments are Gaussian. No volatility clustering — the increments are independent, so a quiet stretch carries no information about the next one. And, most to the point, uniform roughness: every window of a Brownian path looks equally jagged, because every increment is drawn from the same distribution. The market is not like that. Some hours are dead and some are violent, and the violence is in clumps. That variation where the roughness itself changing from stretch to stretch is the whole game, and no single scaling exponent can produce it. One H gives you one roughness, everywhere. You need a spectrum.

Turning the difference into a knob

Here’s the counter-demo. It’s the same path-and-slice machinery as Doc’s and the same √-scaling rescale but with one addition. I’ve also added a slider for clustering, and a meter that reads the realized volatility of whatever slice you’re sitting on, divided by the path’s global average.

Interactive — “Monofractal vs. multifractal”: pull λ from zero and drag the window across the path.

At λ = 0 you are looking at Doc’s demo — Brownian motion — and the roughness meter reads about 1.0× no matter where you drag the window. Every slice is equally rough. That flat meter is what a single Hurst exponent means.

Turn λ up and watch two things happen at once. The rescaled slice still looks like a price chart — the eyeball test still passes, exactly as before; that’s the trap, restated as a control. But the meter starts swinging: 0.4× on a calm stretch, 3× a few windows to the left. It’s the same visual test, identical to your eye.

But what matters is now completely different. The increments here have a local variance set by a lognormal multiplicative cascade — Mandelbrot’s original multifractal object — and the cascade is normalized so the global √time envelope still matches Brownian. Both processes pass the picture test. The difference lives entirely in the quantity the picture test integrates away.

The distinction, stated exactly

Define the increment-scaling exponent ζ(q) by E[ |ΔX|^q ] ∝ Δ^(ζ(q)). A monofractal has ζ(q) = qH — a straight line, one slope, one H. A multifractal has ζ(q) concave: bent downward, so the effective H you’d read off depends on which moment you look at. Small moves and large moves scale by different exponents, and that spread of exponents is the multifractal spectrum.

Now notice what the rescale-and-look test actually measures. Matching the width of a slice to its parent is a statement about the spread of the path — variance, q = 2. It reads a single point on the curve, ζ(2) = 2H ≈ 1, and Brownian and the cascade land on the same point by construction. Multifractality is the curvature of ζ(q) away from the straight line, and no one-point test can measure how a curve bends. That is precisely why the eye can’t see it and the roughness meter can.

The fat tail falls out of the same structure, in closed form. Write each move as r = σ · ε, with ε a standard Gaussian and σ the local vol the cascade assigns it. The kurtosis is κ = E[r⁴] / E[r²]² = 3 · E[σ⁴] / E[σ²]². By Jensen the ratio is at least 1, so κ ≥ 3 for any varying volatility — equality only when σ is constant, which is the coin flip. Make the vol lognormal with Var(ln σ²) = s²and it’s exact: κ = 3 · e^(s²), excess kurtosis 3(e^(s²) − 1). The tail isn’t bolted on. It’s e^(s²), and s² — the dispersion of the volatility itself — is the intermittency dial. Push it in the widget and the return histogram lifts off the Gaussian curve exactly this way, kurtosis climbing while every local move stays ordinary. (A finite stretch of tape realizes a noisier, smaller number; the full e^(s²) is the limit you converge toward, which is itself why tail risk reads as a large-sample phenomenon.)

Why “multifractal,” and not just GARCH

Volatility clustering isn’t news; GARCH has modeled it since the 1980s. But GARCH clusters with a built-in half-life — a characteristic timescale, past which the memory decays exponentially. What Doc described has no such scale. The five-minute chop and the three-week coil were the same figure. That scale-free clustering — the same statistical texture at every zoom, memory decaying like a power law instead of an exponential — is the multifractal signature, and it’s precisely what a single-timescale model smooths over.

Two names, if you want to dig. The framework is Mandelbrot’s Multifractal Model of Asset Returns (with Fisher and Calvet, 1997). The version that made this estimable and forecastable is Calvet and Fisher’s Markov-Switching Multifractal (2004), which out-forecasts GARCH as you push the horizon out, because it carries volatility memory at many scales at once instead of one.

The second fractal

Doc was looking at VIX specifically, but VIX isn’t even the price path. The self-affine √time story is a statement about the underlying’s returns. VIX is the volatility process — mean-reverting, forward-looking, a different animal — and the volatility process has its own fractal (but a rougher one). The “volatility is rough” work (Gatheral, Jaisson, Rosenbaum, 2018) puts log-vol at a Hurst exponent near 0.1: violently anti-persistent, far spikier than the H = ½ of the price path.

So there are two fractals hiding in that chart, but the most valuable one in the demo is neither. It’s the plain price envelope — the least interesting object in the room.

What he actually saw

Which finally explains the thing that started this: realized vol not showing up for all that intraday travel. If variance shows up in scale-free bursts, then most windows are calm, a few are savage, and the intraday range you feel is dominated by the near-misses rather than the hits. The moves that do come reverse before they accumulate, because implied vol runs overshoot-and-revert on its own fast clock. A model with one clustering timescale — or worse, the flat-roughness intuition that a self-affine cartoon quietly invites — will systematically misjudge how often the burst actually lands. The multifractal and rough-vol machinery exists to price exactly that gap. It isn’t a mood about markets being complicated; it’s the specific reason the intraday thrash and the realized print keep disagreeing, and it pays to whatever extent you can call the burst better than the crowd.

So: is a price chart fractal? Yes — and so is a coin flip, and that’s the point.

Looking the same when you rescale is a property Brownian motion already has. What Doc noticed is the property it doesn’t. That’s what you trade on.

Code

All code can be found at https://github.com/kniyer/multifractal

ζ(q) — Brownian tracks q/2 to three decimals (0.502, 1.003, 1.502, 2.001…), the cascade bends below it at high q (2.17 vs 2.50 at q=5). And both hit ζ(2) ≈ 1.00 — the shared envelope. That’s the whole thesis in one figure: they agree at exactly the one point the eye can read, and diverge everywhere else.

Kurtosis — measured pooled kurtosis sits right on 3·e^(s²): 3.01, 4.88, 8.40, 13.35 against theory 3.00, 4.95, 8.15, 13.45. At s²=2 it reads 19.7 vs 22.2 — the finite-sample shortfall, which is exactly the caveat your article already flags (the full e^(s²) is the limit you converge toward). The sim demonstrates the caveat instead of just claiming it.

Paths — Brownian’s local vol is a flat bar; the cascade’s clusters into bursts. Same rescale test, different texture.

For what this looks like right now — dispersion near record lows, single-stock vol against an index in the teens, and the case that elevated vol-of-vol is a structure signal rather than a timing one — read Doc’s companion piece that I’ve linked to.

As always, not financial advice.

This is post 3 in the Tech Schism series, where I’m arguing that the tech “sector” has fractured into two economies that don’t behave the same anymore — and that the market is starting to price the fracture, but not by enough.

Previous posts:

• Part 1: QQQ Is Lying to You opened the argument by showing SMH and IGV have decoupled 87 points YTD inside a QQQ that looks calm on the surface.

• Part 2: The Correlation Trade Is a Trap explained why the obvious pairs trade fails, and what the real trade is.

• Part 3: The Software Names Getting Crushed by GPU Depreciation laid out the mechanism: hyperscaler AI capex is transferring 800 to 1,100 basis points of margin from software to silicon over the next three years, on a straight-line depreciation schedule.

This post is the market-in-motion companion. Fresh data pulled this week on how the vol surface is currently pricing the mechanism the last post laid out. Where the market has done the work, where it hasn’t, and where the gap looks tradeable.

Summary ~200 Words

The thesis. The mechanism argument from the last post is one story and what the options market is currently pricing is a second story, and this post is about where the two disagree.

The dispersion. Across the same 14 software names ranked last week, current 25-delta put skew ranges from +3.03 vol points (CRM) to –7.01 vol points (INTU), which is a 10-vol-point spread across a group with broadly similar exposure to the same mechanism. Names with higher vulnerability scores are trading with cheaper downside protection than names with lower scores, which means the cross-section is telling on itself.

The Alphabet tell. Among the Big 4 capex payers plus Oracle, four of five names carry front-end vol that lines up cleanly with earnings calendars over July 22–30, but Alphabet’s front-end is elevated without a full earnings hump — the mid-tenors don’t recover the way MSFT, META, and AMZN’s do — which means the options market is pricing something at Alphabet that isn’t the print.

The NVDA setup. NVDA’s 30-day realized volatility versus MSFT’s is at the 8th percentile of the trailing 12 months, meaning NVDA has been anomalously quiet, which is the setup for Post 3 rather than a trade today.

Now the detailed read. Github links with code and CSVs at the bottom.

Fourteen Names, Ten Vol Points, One Mechanism

We have fourteen names and roughly ten vol points of dispersion through presumably one mechanism. The mechanism, from last week, is that hyperscalers are moving GPU purchases through the P&L as depreciation on faster useful-life schedules than the previous generation of infrastructure, and the software layer that resells or depends on that compute has to absorb the pricing pressure. The vulnerability ranking sorted 14 names into Capex Payers who own the burden directly (MSFT, ORCL), Compute Renters who consume it (SNOW, DDOG, ZS, MDB, PANW, NOW, CRM, WDAY, TEAM, HUBS), and two differentiated names the market is already treating as different (ADBE, INTU).

If the options market believed the mechanism argument in a uniform way, the 14 names would line up diagonally on the chart below — higher vulnerability, richer downside protection. Instead the scatter is messy, and messy in a specific direction:

The y-axis is the vulnerability score from the last post and the x-axis is where 25-delta put skew is trading as of the July 9 close. SNOW sits at the top of the vulnerability ranking with put skew of –5.32 vol points, while MSFT with a lower vulnerability score has put skew of +0.85 vol points, which means the market is pricing MSFT’s downside more expensively than SNOW’s on a name that the fundamental work says is more exposed to the mechanism, not less. That inversion — high vulnerability paired with cheap protection, low vulnerability paired with expensive protection — shows up more than once in the chart and it’s the whole trade thesis for this post.

The Honest Caveat

Some of this dispersion is real signal and some of it is regime. CRM has always traded rich skew because it’s an activist story with structural chop, and INTU has always traded flat skew because it’s a low-beta staples-like name, so their positions on the chart partly reflect their own histories rather than any current market view on the mechanism. What can’t be done with this data is comparing each name’s current skew to its own history, since that requires a paid implied-vol surface source we don’t have here.

Cross-sectional dispersion is a legitimate signal on its own but it isn’t the same as saying “SNOW puts are cheap in absolute terms” — it’s saying SNOW puts are cheap relative to how the market is pricing the same mechanism elsewhere in the same tape. That distinction matters and everything below is written with it in mind.

The 10-Vol-Point Spread

Sorting all 14 names by put skew makes the pattern sharper than the scatter does:

The color coding is the vulnerability tier from the last post, with red being the top tier. The red bars are sorted to the wrong side of the chart — the names with the highest fundamental exposure to the mechanism (SNOW, DDOG, ZS) sit at the flat-skew end where downside protection is cheap, while the names with lower fundamental exposure (CRM, MSFT, ADBE) sit at the rich-skew end. INTU is the exception at the flat end but that’s a regime story since INTU is always flat-skew. The dispersion isn’t random noise — it runs against the mechanism direction with enough consistency to want an explanation.

There are two reasonable explanations. The first is that the market has already discovered the mechanism and priced it into the Capex Payers who report earnings first, while the Compute Renters haven’t gotten repriced yet because their calendars are further out and they haven’t been forced to speak on the record about margin implications. This is the “market hasn’t gotten to them yet” thesis and it says the flat-skew high-vulnerability names are the setup, since the dispersion should close as SNOW, DDOG, and ZS’s next earnings cycles force pricing. The second explanation is that the market is right and the last post was wrong — the Compute Renters are getting priced as usual-story growth-vol names, and the fundamental work overweights the depreciation pass-through because it doesn’t account for whatever offset the SaaS layer has (price hikes, product upsell, workload growth). If the second read is right, the dispersion holds and there’s no trade.

The first explanation looks stronger for the specific names where the mechanism was tightest last week (SNOW, DDOG, MSFT), but the second stays live for the middle names where the fundamental argument was weaker to start.

The Alphabet Anomaly

The Capex Payers report earnings inside a nine-day window — GOOGL on July 22, MSFT on July 29, META on July 29, AMZN on July 30 — and front-end implied vol at all four names is elevated, which is normal because the front expiry captures the print, vol richens into it, and then it collapses after. What isn’t normal is the difference in shape across the four names:

MSFT, META, and AMZN all show the classic pre-earnings hump: front-end elevated, vol drops sharply at 60-90 days, then a slow rebuild to structural levels. Oracle has no earnings within 60 days and shows clean contango — a normal upward-sloping curve with no event distortion. Alphabet’s curve looks like none of them.

At 30 days, GOOGL is at 41.16%, which is elevated versus its 90-day tenor at 36.03% — a 5.13 vol-point spread. Normal earnings behavior would produce a hump where the front-end is rich, the mid-tenors are depressed, and the back-end is normal, but GOOGL doesn’t hump. The mid-tenors stay depressed. The 180-day is at 37.06% and the 365-day is at 37.61%, so the curve is genuinely inverted at the front rather than just around the print.

That’s what makes it interesting. Front-end elevation that persists past the print date suggests the options market is pricing something at Alphabet that isn’t the earnings event, and the candidates are all real: positioning around the antitrust remedy timeline, macro concentration risk if the market thinks GOOGL is the swing factor on AI capex disclosure, or a client with a large hedge sitting in the tape. We don’t know which one it is, but we know it’s there.

The actionable version is to watch what Alphabet’s 30-day IV does after the July 22 print. If it collapses to match MSFT/META/AMZN’s post-earnings vol, it was earnings after all and the shape was a coincidence. If it stays elevated, the market is telling us there’s a second story at GOOGL that the mechanism analysis didn’t capture.

The NVDA/MSFT Setup

The mechanism argument transfers margin from the software layer to the silicon layer, and the natural expression of that thesis in options space is a long NVDA vol / short MSFT vol trade — or the reverse, depending on how the market has already priced it.

The chart above is the ratio of NVDA’s 30-day realized volatility to MSFT’s 30-day realized volatility over the trailing 12 months. It’s currently at 0.94, meaning NVDA has been less volatile than MSFT on a realized basis for the last 30 days, which is at the 8th percentile of the trailing year against a 12-month median of 1.58. NVDA has been quiet in a way that its own history says is unusual.

The honest note is that this is 30-day realized vol rather than implied vol. The RV ratio lags the IV ratio by 2-4 weeks in trend changes and doesn’t capture event premium, so Post 3 will need paid implied-vol data to confirm the signal. What we have here is a directional starting point rather than a trade recommendation. But the direction is interesting: if NVDA is at the 8th percentile of its normal vol premium over MSFT, one of three things is happening — NVDA is entering a low-vol regime that persists (unusual for the name), MSFT is entering a high-vol regime (plausible given the capex disclosure calendar), or the ratio is coiled and about to snap back toward the 1.58 median. The trade construction in Post 3 will pick a side.

What to Do With This

No positions in any of these names before this post publishes, but here’s what’s worth watching. The cleanest setup is SNOW, DDOG, and ZS — highest vulnerability, cheapest cross-sectional put protection — where the dispersion should close on their next earnings prints (SNOW reports late August, DDOG early August, ZS mid-August). If the dispersion doesn’t close on those prints, the second explanation wins and this post owes a public update. The Alphabet call needs one more datapoint before it becomes actionable: if the 30-day IV doesn’t compress after the July 22 print, the front-end elevation is structural and worth trading, but if it compresses, the shape was earnings and there’s no trade.

On the other side, MSFT and CRM sit at the top of the skew ranking, which means the mechanism argument is already priced into their downside vol. Long puts here are expensive, so any trade in those names should be structured (put spreads, ratio spreads, calendar spreads) rather than outright long puts. ADBE and INTU are the differentiated names from last week and nothing in the options data disagrees — ADBE trades rich skew because it’s expensive-vol by history, INTU trades flat because it’s low-beta, and both readings are consistent with the differentiation call.

Sources: yfinance options chain (July 9, 2026 close) for 30/60/90/180/365-day ATM implied vol and 25-delta put skew across the 14 names. yfinance daily price history for the trailing 12-month NVDA and MSFT realized volatility series (30-day close-to-close, annualized). Vulnerability scores carried forward from the mechanism post’s composite ranking. Term-structure classification (contango, backwardation, humped) applied per-name based on tenor shape, cross-referenced against upcoming earnings calendars. All options data as of the market close of July 9, 2026; analysis performed July 11, 2026. RV ratio used as a proxy for the IV ratio in the NVDA/MSFT setup — the IV confirmation requires a paid vol-surface source and is deferred to Post 3. Cross-sectional put skew comparisons are stated in vol points, not percentile within each name’s own history; a percentile-based rework would reclassify some names between the “cheap” and “regime” buckets.

Full code and analysis available at: https://github.com/kniyer/software-vs-silicon

Post 3 the following Saturday — July 25 — is the trade writeup. Long NVDA, short MSFT, sized by capex intensity rather than realized vol, with the exact position math, the four ways the trade breaks, and the specific stop and exit conditions. It’s a fundamental thesis expressed as a pair, not a correlation edge with a fundamental story tacked on.

Between now and then, Alphabet reports on July 22 and the Alphabet term-structure question above will resolve one way or the other before Post 3 publishes. That resolution will be in Post 3.

As always, the material presented in Math & Markets is for informational purposes only. It does not constitute investment or financial advice.

Alpha is never guaranteed and the backtest is a liar until proven otherwise.

This is post 2 in the Tech Schism series, where I’m arguing that the tech “sector” has fractured into two economies that don’t behave the same anymore — and that the market is starting to price the fracture, but not by enough.

Previous posts: QQQ Is Lying to You opened the argument by showing SMH and IGV have decoupled 87 points YTD inside a QQQ that looks calm on the surface. The Correlation Trade Is a Trap explained why the obvious pairs trade fails, and what the real trade is.

This post is the mechanism piece: why the fracture is structural, mechanical, and running on a schedule.

The Read, In ~200 Words

The thesis. Hyperscaler AI capex is transferring 800 to 1,100 basis points of margin from software to silicon over the next three years. The mechanism is depreciation. The schedule is a straight line. Growth needs to outpace the schedule, or margin gets absorbed.

Where I’d be looking for longs. ADBE and INTU. They score lowest on every vulnerability dimension I measured. Adobe’s yield beta is the only one in the group with statistical significance. The market is already differentiating these two, and the mechanism supports the differentiation.

Where I’d be looking for shorts, or at least reducing exposure. SNOW, DDOG, and ZS. These are the compute renters with the highest gross margins, the least pricing power against hyperscaler cost pass-through, and the deepest marketplace dependencies. The mechanism hits them at the top of the P&L, where they have no operating leverage to absorb it.

Where to watch the growth story bend. MSFT is the biggest exposure by absolute dollars — Q4 2027 projected D&A hits ~17% of revenue, up from ~7% two years ago. The bull case (Azure AI grows through it) is possible. The market is pricing it as guaranteed. When Azure AI growth misses, this is where you’ll see it first.

Now the detailed analysis. Github links with code and CSVs at the bottom.

The number that started this

By Q4 2027, Microsoft’s depreciation expense will consume roughly 17% of its revenue. Today it consumes 10%. Two years ago it consumed 7%.

That’s not a growth story. That’s a margin transfer, from software’s P&L to silicon’s P&L, running quarter by quarter on a schedule no earnings call can pull forward and no rate cut can reverse.

The number matters because depreciation is not a decision. It’s the calendar. Once capex is spent and the asset is placed in service, the P&L hit arrives on a schedule you can compute from a straight line. Microsoft spent $30.9 billion on capex in Q1 2026 alone. Alphabet spent $35.7 billion. Meta spent $19.0 billion. Those dollars are already committed. The GPUs are already racked. The depreciation shows up whether or not the AI revenue does.

Capex quadrupled in three years. This is the fuel. What follows is the fire.

The wave hasn’t crested

Straight-line depreciation is boring, and that’s the point. It’s why the mechanism is legible.

Take the capex a hyperscaler has already committed. Assume a useful life — Meta explicitly discloses 5 years for AI hardware, Amazon uses 5 years for servers, Microsoft and Alphabet use 6 years. Divide capex by useful life. That’s your depreciation run rate from that cohort. Do it every quarter, cumulate, and you get a curve.

The curve is not close to done climbing. Meta’s D&A goes from $15.5B in 2024 to a projected $37.4B in 2027 — a 141% increase. Meta’s D&A-to-revenue ratio moves from 9.4% to 15.6%. That is 614 basis points of gross margin that has to come from somewhere.

Alphabet: $15.3B to $57.9B, up 278%. D&A-to-revenue from 4.4% to 12.8%. That’s 841 basis points.

Microsoft: $9.9B to $53.7B, up 442%. D&A-to-revenue from 4.0% to 15.0%. That’s 1,096 basis points. Over eleven points of revenue in three years, on the largest software company in the world.

Amazon is the exception, and worth pausing on. Their trajectory looks flat because AWS revenue is already large enough and growing fast enough to absorb depreciation on the current capex trajectory. Amazon has been running heavy infrastructure spend for longer, and the base is already there. The other three are still climbing the same curve Amazon climbed years ago.

None of this requires an AI winter. None of it requires a growth disappointment. It just requires the calendar.

What growth would have to do to save this

There’s exactly one thing that saves this. Revenue has to grow fast enough to keep the ratio flat.

If you do the math on Microsoft, total revenue for the last twelve months is around $328B. For D&A/revenue to hold at 10% through 2027 — not improve, just not deteriorate — revenue has to grow to roughly $537B. That’s 64% growth in eighteen months. Consensus is not pricing that.

Alphabet: from ~$400B to ~$580B just to hold the D&A/revenue ratio at ~5%. Meta: from ~$180B to ~$240B to keep the ratio flat. These are not growth numbers. They are growth numbers plus the assumption that Azure AI, Google Cloud AI, and Meta’s AI monetization all convert at rates no one has yet demonstrated.

The market is currently paying multiples that require these growth numbers to arrive. If they don’t, the depreciation still does.

Why the coal-to-gas parallel breaks

The obvious analogy is coal-to-gas. Utilities in the 2010-2015 window were locked into new natural gas capex while their coal cost structure remained. Depreciation on the new gas plants hit their P&L. Their margins should have compressed. That story maps neatly onto software absorbing hyperscaler infrastructure depreciation.

I ran the numbers — but it doesn’t hold.

Southern Company’s operating margin expanded by 270 basis points from 2010 to 2015. American Electric Power’s expanded by 180. Their D&A-to-revenue ratios did rise — SO by 3.2 percentage points, AEP by 0.8 — but operating margins expanded anyway. Total returns for both crushed the utility ETF by 10 to 41 percentage points.

The utilities that got hurt in that window got hurt for different reasons. NRG collapsed 47%, but NRG was a merchant power generator exposed to spot electricity prices. The story was commodity, not capex.

So the historical parallel doesn’t validate the software thesis. It actively undermines it — until you understand why.

Utilities have a rate base. When they commit capex, they file for rate recovery, and the regulator grants them a return on that invested capital. Depreciation flows through the P&L, but revenue rises in tandem to absorb it. Utilities weren’t punished for spending on gas capacity. They were rewarded for it.

Software has no rate base.

There is no regulator who will grant Microsoft the right to raise Office 365 prices by 12% to offset AI infrastructure depreciation. There is no filing Snowflake can make to pass through GPU costs to customers on a mandated schedule. When capex hits the P&L as depreciation, the only offset is to grow revenue faster than the ratio can rise, or to compress operating cost elsewhere. That’s not rate recovery. That’s execution.

The coal-to-gas analogy fails as a parallel and succeeds as a contrast. Utilities were protected by regulation. Software isn’t protected by anything.

Two ways to die of the same disease

The margin transfer doesn’t hit all software equally. It hits differently depending on where the depreciation lands. There are two mechanisms, and they produce different mortality tables.

The Capex Payers carry the depreciation on their own balance sheet. Microsoft, Alphabet, Meta, Amazon, and Oracle are the obvious ones — they are the hyperscalers, spending the money, absorbing the D&A directly. Their gross margin is the residual after their own AI infrastructure costs are booked as depreciation and running costs. As their D&A/revenue ratio climbs, their operating margin compresses by the same amount unless revenue growth outpaces the schedule.

The Compute Renters don’t own the infrastructure. They pay AWS, Azure, and GCP for compute, and that bill shows up in their COGS. When hyperscaler pricing rises to recover their depreciation — and it will — the fees flow through to the renters as gross margin compression at the top of the P&L. There is no operating leverage story that saves them, because the compression happens before operating expenses. They can only outrun it by raising their prices to their customers faster than their infrastructure costs are rising.

That is the “so what” of the compute renter mechanism, in plain English. Their COGS just gets more expensive, and the only way out is to hike prices faster than the vendors upstream of them.

The Compute Renters — ranked

I scored ten pure-SaaS names on four dimensions: (A) AI capex exposure, (B) gross margin sensitivity, (C) yield beta from a 2023–2026 weekly regression, and (D) hyperscaler dependency. Each dimension scored 1 to 5. Composite score is the sum, range 4 to 20.

The top three by composite:

SNOW (17) — Snowflake is the purest expression of the mechanism. It runs entirely on AWS/Azure/GCP infrastructure. Its Cortex AI product runs on hyperscaler GPU-backed workloads. Its ~66% product gross margin already absorbs infrastructure pass-through and rises directly with compute-intensive AI workloads. If hyperscaler unit economics tighten — which the depreciation math says they will — Snowflake’s COGS rises whether or not Snowflake changes anything about how it operates. SNOW has the least optionality to offset the transfer.

DDOG (15) — Datadog’s LLM observability and AI monitoring segments are among the fastest-growing lines in the pipeline, which sounds like the good news until you notice the delivery mechanism. Roughly 35% of contracts flow through hyperscaler marketplaces and co-sell motions. The ~81% gross margin has farther to fall than most, and ingestion pipelines are getting more compute-heavy, not less. High margin plus rising infrastructure pass-through equals large absolute compression.

ZS (14) — Zscaler operates its own Zero Trust infrastructure, which sounds like a hedge, but the platform relies on hyperscaler transit and its yield beta (+0.061) suggests the market is not pricing it as a rate-cut winner. About 30% of bookings run through hyperscaler marketplace co-sell. Gross margin (~78%) is high enough that a 200-300 basis point pass-through hit is visible in the P&L.

Below the top three, the middle (MDB at 13, PANW at 12, WDAY/NOW at 11) tells a more nuanced story that I’ll pick up separately with the options-chain read. The composite treats them as similar, but the market is not.

The heatmap shows why the composite alone hides the argument. SNOW’s 17 comes from A=5 and D=5 — the mechanism hits it from both ends. DDOG’s 15 comes from C=4 and D=4 — market pricing and channel exposure. ZS’s 14 comes almost entirely from C and D — the yield beta says the market doesn’t see it as a rate-cut winner, and the marketplace dependency makes hyperscaler pricing a pass-through hit. The mechanism doesn’t score them equally, even when the composite does.

The Capex Payers — MSFT and ORCL, honestly

Microsoft scores 11, ranked below Snowflake and Datadog in a composite scoring system. That’s a scoring artifact, not a mechanism claim. Microsoft is the largest AI capex payer in the world by absolute dollars. Its Q4 2027 projected D&A/revenue ratio is 16.7%, up from ~7% just two years ago. On a mechanism basis, MSFT is the most exposed name on the list.

The reason the composite understates it is straightforward: MSFT scores low on hyperscaler dependency (it is the hyperscaler) and low on gross margin sensitivity (it’s already at 68% and has been steady). Both are true. Neither offsets the fact that a 1,000 basis point swing in D&A/revenue over three years is a very large number to absorb.

There is a counter-argument, and it deserves to be stated fairly. Azure AI revenue is growing quickly. If it grows fast enough, MSFT can compound through the depreciation wave, absorb the ratio increase in a rising revenue base, and preserve margins. That is the bull case. It is possible.

But the market is currently pricing that outcome as if it is guaranteed. Microsoft’s forward multiple assumes AI revenue conversion at a rate that requires everything to go right — hyperscaler GPU utilization to stay high, enterprise AI adoption to accelerate, and no competitive pressure on Azure AI pricing. If any of those assumptions bends, the depreciation still lands on schedule. That’s the asymmetry.

Oracle at composite 12 is the same story in miniature. OCI is Oracle’s flagship growth engine, and its GPU cluster buildout has moved Oracle from software-multiple to hyperscaler-multiple territory. If OCI revenue grows into the capex, Oracle rerates. If it doesn’t, Oracle has taken on hyperscaler-scale depreciation without hyperscaler-scale absorption capacity. The dispersion in outcomes is wider for ORCL than for MSFT, but the mechanism is identical.

The names the market is already differentiating

Two names scored 7 on the composite — the lowest scores in the group: Adobe (ADBE) and Intuit (INTU).

Adobe carries a ~89% gross margin, uses its own infrastructure for Firefly AI, has minimal hyperscaler dependency, and sells through direct enterprise and consumer channels. Intuit runs at ~79% gross margin, its AI features (TurboTax, Assist) are ancillary to the core tax and SMB workflows, and its infrastructure exposure to hyperscaler GPU pricing is close to zero. Neither company is in the depreciation-wave supply chain in any meaningful way.

If the thesis in this post is correct — margin transfer from software to silicon is real and mechanical — then ADBE and INTU should trade very differently from the top of the vulnerability ranking. Adobe’s yield beta (-0.051) is the only regression in the 14 with a p-value below 0.10 — the market is already pricing Adobe as a rate-cut winner in a way it isn’t pricing the others. Intuit’s beta is smaller but similarly directional.

The market is already pricing the mechanism. It’s just pricing it name by name, with dispersion, without saying out loud what the dispersion is about. What the depreciation math above does is name the mechanism.

The Read, Again

The thesis one more time, at the end where it belongs:

Software is transferring margin to silicon. The mechanism is depreciation on committed capex, running on a schedule. The Capex Payers absorb it directly on their P&L. The Compute Renters absorb it through hyperscaler cost pass-through into their COGS. The names insulated from both mechanisms — ADBE, INTU — are the ones the market is already treating differently, and the mechanism supports that treatment.

Where I’d be looking for longs: ADBE, INTU. The mechanism doesn’t touch them, and the market is starting to price the difference.

Where I’d be looking for shorts or reducing exposure: SNOW, DDOG, ZS. Highest gross margins in the compute renter group, weakest pricing power against hyperscaler cost pass-through, deepest marketplace dependencies.

Where to watch the growth story bend: MSFT, ORCL. Both are pricing the growth-through-depreciation story as if it’s guaranteed. It isn’t. When it bends, it bends fast.

None of this is a recommendation to buy or sell any specific security. It is an argument about where the burden of proof sits, name by name. Utilities in 2010-2015 got saved by their regulator. Software has no regulator. Whoever gets saved has to earn it in the market.

Sources: SEC EDGAR XBRL companyfacts API (all quarterly and annual financials); consensus revenue estimates for 2026–2027 projections via FactSet/Bloomberg (approximate, ~July 2026); yfinance for total return calculations; EIA Natural Gas Monthly Table 9.11 and Electric Power Annual Table 6.1 for coal-to-gas macro context. Yield beta regressions run over 2023-01-01 to 2026-06-30 weekly returns. Vulnerability composite is unweighted (1-5 per dimension); a weighted score would rerank materially. Straight-line depreciation model assumes AI-attributable capex is depreciated over disclosed useful life (5 years META/AMZN, 6 years MSFT/GOOGL). The AI-attributable estimate is a proxy based on baseline capex trend extrapolation; no hyperscaler discloses AI capex as a formal line item. Analysis performed July 10, 2026.

Full code and analysis available at: https://github.com/kniyer/software-vs-silicon

Part 2 next Wednesday, July 15, is the market-in-motion companion piece: Software Is Dead. Long Live Silicon. Part 2 — What the Options Chain Says. Fresh data, pulled the morning of, on how the vol surface is pricing the mechanism this post just laid out. Which names have implied-vol setups that reflect the exposure. Which don’t, and why the mispricing might be the trade. Different reader, different job. If Part 1 was the mechanism, Part 2 is the read on how the market is currently pricing it — and where the gap is.

Post 3 the Saturday after — July 25 — is the trade writeup. Long NVDA, short MSFT, sized by capex intensity rather than realized vol, with the exact position math, the four ways the trade breaks, and the specific stop and exit conditions. It’s a fundamental thesis expressed as a pair, not a correlation edge with a fundamental story tacked on.

As always, the material presented in Math & Markets is for informational purposes only. It does not constitute investment or financial advice.

Alpha is never guaranteed and the backtest is a liar until proven otherwise.

and I were chatting on how we could trade this and I went down a rabbit hole. I ran the numbers on the tradable version of my own thesis and here are the findings.

The setup

The natural follow-up to Post 1 was obvious: if the schism is real, how would you trade it? Long SMH, short IGV, size it vol-equalized, and wait for mean reversion.

Doc raised the point that the bid-ask spread for those would be pretty wide, so I started looking at actual names — notably MSFT and NVDA.

I was mid-planning that trade when Doc pushed back. His question was this: “We need something we can actually reproduce. Individual-name capex analysis is fundamental work — how do we do this with ETFs and standard correlation primitives? Something like MAGS versus IGV, on rolling 1-month correlation, with vol-equalized sizing.”

That’s a good question, and it’s the right question for a systematic trader. So I went and ran some tests.

Three tests, in order:

1. Is the current correlation z-score actually rare — or is this pair fracturing at its historical baseline?

2. Does entering the trade at low-correlation readings actually produce forward returns?

3. Does the vol-equalized sizing hold up between rebalances, or does the hedge drift so fast that “vol-neutral” is a fiction?

I set the tests up so they could kill the systematic trade cleanly. All three did.

Test 1: the “rare event” framing was wrong

Post 1 leaned on the SMH/IGV divergence being unusual — an outlier in a market that mostly moves as one asset class. The correlation z-score sits at −2.69 on a 3-month window. On its face, that looks tail.

It isn’t.

SMH/IGV has printed a 3-month correlation z-score at or below the current −2.69 reading on 13% of trading days across its observable history. The 5th percentile threshold — what would actually qualify as a rare event — sits at −3.17. The all-time low is −3.48. Today’s reading is closer to the pair’s baseline decoupling than to its tails.

Extending this to the other pairs makes the picture worse for the “rare event” story:

SMH/IGV has spent nearly a quarter of its history at or below a z of −2.0. This pair fractures like this all the time. Calling it a schism because it’s fracturing right now doesn’t make it a tail event.

That does not mean the phenomenon in Post 1 is not real. The 87-point YTD spread is real; the $58B/quarter capex step-up is real; the margin transfer is a live structural process. But the correlation collapse isn’t rare, so the correlation collapse cannot be the signal. The story has to survive on the mechanism, not the statistic.

Verdict on Test 1: the framing was wrong. The schism is a recurring feature of the pair, not a regime break.

Test 2: the trade signal is marginal at best

If a low z-score can’t be a rarity signal, maybe it’s still a timing signal. That’s the second question: at historical dates where SMH/IGV 3-month correlation z-score fell below −2.0, what did a vol-equalized long-SMH / short-IGV position return over the next 1, 3, and 6 months?

There have been 15 independent entries meeting that condition since April 2024 — enough to run the arithmetic, not enough to be confident in it.

The aggregate looks decent at 1M. At 3M it degrades. At 6M it is indistinguishable from a coin flip — 50% win rate, p = 0.72.

But the aggregate is the wrong number to look at. The trades individually tell you something the mean doesn’t.

The 2024 cluster — five entries between April and July — was largely negative at 3M and 6M. The worst was a July 2024 entry that returned −43% at the 6M horizon during the summer NVDA correction.

The 2025 cluster is three entries: August 12, September 2, September 23. Those three trades produced +65%, +60%, and +72% at 6M. They captured the entire SMH rip that dominated Q3-Q4 2025.

Those three trades are the strategy. Take them out, and the aggregate 6M mean goes from +6.7% to something like −15%. The 2026 entries mostly don’t have 6M forward data yet.

This is not a signal. This is basically one regime doing all the work of an average. If you deaverage it, it goes away.

And the regime it captured — a specific SMH outperformance window driven by AI capex acceleration — is exactly what Post 1 argued we are still inside. So the honest read is: the historical backtest “worked” because it caught the trade we’re already trying to make, not because low correlation predicts anything about forward returns in general.

Verdict on Test 2: the systematic signal does not support the trade. It supports a regime, and the regime is the actualthesis.

Test 3: vol-equalized sizing isn’t stable

The last question was operational, not statistical. The sizing framework I was going to use in Post 3 was standard vol-equalization: scale each leg by its inverse 21-day realized vol so the two positions carry the same risk. SMH is currently 1.73× as volatile as IGV, so the IGV notional gets sized up correspondingly.

That works exactly one day.

Over 21 trading days, the SMH/IGV vol ratio has moved by a median of 19.8% and a 75th-percentile move of 33.3%. In the 95th percentile — which is what happens during events like the July 2024 NVDA correction — the ratio moves 73% inside a month.

At a 20% median monthly drift in the vol ratio, “vol-equalized” is a starting condition, not a stable state. A hedge you set today is around a fifth off within a month, before any price move touches the position. Monthly rebalancing is a floor requirement. Weekly rebalancing is probably closer to correct. And rebalancing costs — commissions, spread, gamma bleed on any options overlay — weren’t anywhere in Post 3’s draft.

Verdict on Test 3: the sizing math needs active maintenance. That’s not fatal to the trade, but it’s material, and it wasn’t in the original writeup.

TL;DR

The three tests kill the ETF pair trade as a systematic strategy. But I don’t think it kills the underlying thesis.

• The $58B/quarter hyperscaler capex delta is a real, measurable, contractually locked flow.

• That capex is a P&L transfer from software operating margins to silicon operating margins. It has to be. Depreciation is an expense; software companies are the ones running it.

• The market is repricing this slowly, name by name, quarter by quarter.

However, if you are looking to trade this, a few points worth considering.

• The SMH/IGV correlation reading is not a rare event and cannot carry the argument by itself.

• Framing the schism as “unprecedented” is unsupported by the correlation history. It’s a recurring feature.

• The ETF-pair version of the trade is not a systematic edge. It’s a fundamental bet dressed in quant clothing.

The trade that survives the audit

If the correlation trade doesn’t work, what does? The version I had actually been sketching before I ran the tests: long NVDA, short MSFT, sized by capex intensity, held on a fundamental horizon.

Here’s the reason this survives when the ETF version doesn’t. The ETF pair trade requires two things to work: the schism has to be rare, and the schism has to mean-revert. Neither holds. The single-name capex trade requires something different: the capex transfer has to actually land on the P&Ls. That’s not a mean-reversion trade; it’s a fundamental one.

It doesn’t depend on whether SMH/IGV correlation is unusual — it depends on whether MSFT’s incremental $15-20B annual capex actually shows up as 150-200 bps of margin compression, and whether the corresponding $8-10B of MSFT-sourced NVDA revenue actually shows up as accelerated NVDA earnings.

The individual-name trade also fixes two of the three problems from the ETF version:

• Execution. NVDA and MSFT both have sub-5-cent option spreads on liquid strikes. SMH and IGV have 20-30 cent spreads on ATM options. The illiquidity tax on the ETF pair eats the alpha before you can harvest it.

• Directness. The single-name trade isolates exactly the P&L flow you’re trying to bet on. The ETF pair contaminates the signal with everything else in the basket — semis unrelated to hyperscaler capex, software unrelated to margin transfer, index-flow effects that have nothing to do with the mechanism.

The vol-drift problem doesn’t go away. Any pair trade requires active hedge management. But the fundamental horizon of the single-name trade — earnings cycles, not monthly correlation windows — is a better match to how the mechanism actually plays out.

Code

All code can be found at https://github.com/kniyer/tech-schism

I’d suggest starting with: https://github.com/kniyer/tech-schism/blob/main/README.md

Post 2 next Saturday, July 11, delivers the piece I originally promised in Post 1: Software Is Dead. Long Live Silicon. A closer look at the margin transfer itself — when the depreciation actually hits, which software names get crushed first, and why the coal-to-natural-gas analogy is more literal than you think. Fundamental mechanics, not trade construction.

Post 3 the Saturday after — July 18 — is the trade writeup. Long NVDA, short MSFT, sized by capex intensity rather than realized vol, with the exact position math, the four ways the trade breaks, and the specific stop and exit conditions. It’s a fundamental thesis expressed as a pair, not a correlation edge with a fundamental story tacked on.

Thanks to Doc McGraw for pushing on the ETF-pair trade and forcing this audit. If you want the raw data — z-score history, trade log, vol ratio series — reply to this note and I'll send it.

As always, the material presented in Math & Markets is for informational purposes only. It does not constitute investment or financial advice.

Alpha is never guaranteed and the backtest is a liar until proven otherwise.

Look at QQQ year-to-date: +15.3%.

If you stopped there, you’d conclude that 2026 has been a perfectly normal year for big tech — maybe a little soft compared to 2024, but nothing broken, nothing screaming. The index is up and the bull is intact, and from that altitude the whole sector looks fine.

Now look inside it.

SMH (semiconductors): +70.0% YTD.
IGV (software): -16.7% YTD.

That’s an 86.7 percentage-point spread between two sectors that, eighteen months ago, were considered the same trade — both filed under “tech,” both living in QQQ, both showing up in the same long-only growth funds, momentum screens, and “AI beneficiary” baskets. They are not the same trade anymore, and they are not even moving in the same directionanymore. And QQQ — the instrument that millions of people use as their proxy for “tech” — is hiding it.

The arithmetic of a lie

QQQ is a market-cap-weighted index. When one component rips 70% and another bleeds 17%, the index doesn’t show you the fracture — it shows you the weighted average of the boom and the bust, and reports a polite, unremarkable +15.3%. This is not a metaphor for what’s happening, it’s the literal mechanism: the index is mathematically designed to smooth over exactly the kind of internal civil war that is happening right now inside it.

And the civil war has a name: AI capex is a margin transfer. Every incremental dollar Microsoft, Meta, Amazon, and Google spend on Nvidia GPUs is a dollar that used to live as software operating margin and now lives as silicon revenue. Software isn’t losing to “the AI story” — software is the AI story, just on the wrong end of the income statement. I’ll prove the capex side of that claim in a minute. Hold that thought.

The Mag-7 is no longer one trade

Look at the chart above. SMH and IGV started the year at the same point, the gap reached 30 points by April, widened to 75 by June, and sits at 87 today. The QQQ line — the grey dashed one — sits between them like a man trying to look casual at a knife fight.

A careful reader is going to ask the obvious question: if MSFT is down 36% from highs and META is down 32% and AAPL is down 13%, how is QQQ only up 15%? The answer is the cleanest possible proof of the bifurcation: QQQ is being held up almost single-handedly by NVDA and the semiconductor weight inside it, while the software-adjacent Mag-7 names get beaten down. The index isn’t lying about the average — it’s hiding that the average is the difference between two violent moves in opposite directions.

Friday’s tape made this concrete in a single session.

On Friday, software ripped and semis sold off — the opposite of the YTD trend:

• MSFT: +6.37% · IGV: +4.21% · AAPL: +3.79%

• SMH: -4.27% · NVDA: -1.30% · GOOG: -1.77%

QQQ closed -1.08% — down a single percent on a day where one of its components was +6.4% and another was -4.3%. Whether the schism is widening or briefly closing, the volatility is happening inside the index rather than to it, and that is the actual signal. Friday’s tape is not a refutation of the thesis; it is the thesis in miniature. Tech is no longer one trade, and now it’s not even one direction.

“But this will mean-revert”

The natural counter-argument is that this is a rubber band — software is too cheap, semis are too expensive, and mean reversion will eventually save the IGV longs. Friday’s rip in MSFT and IGV will fuel that argument hard over the next few weeks.

Mean reversion works when both sides of a spread are pricing the same flow and sentiment briefly gets out of sync, the way two correlated stocks oscillate around a pair ratio. It does not work when the spread is the visible artifact of a one-directional, contractually-committed capital flow — and that’s what this is. Look at the dollars.

Hyperscaler capex, this quarter vs one year ago:

• MSFT: $16.7B → $30.9B (+84% YoY)

• AMZN: $25.0B → $44.2B (+77% YoY)

• META: $12.9B → $19.0B (+47% YoY)

• GOOG: $17.2B → $35.7B (+107% YoY)

• Big Four total: $71.9B → $129.8B per quarter, an additional $57.8B per quarter flowing into capex versus a year ago.

That is roughly the entire quarterly revenue of Salesforce, ServiceNow, Adobe, and Workday combined — being committed to capex every three months in incremental dollars alone, and most of it going to one place: silicon.

Capex of this size doesn’t oscillate. It is announced on earnings calls a year in advance, contracted with TSMC and Nvidia two years in advance, and built into power-purchase agreements three years in advance, with most of the spend already obligated by the time you read the press release. The hyperscalers can’t quietly walk it back without a guidance reset that crushes their own stocks. In the literal sense, the capital flow is locked in — the dollars going into silicon next quarter are already on order, and the dollars coming out of software margins to fund them are already on the budget. Mean reversion requires the flow to reverse, and the flow can’t reverse, because it’s signed.

Priced-in or observed?

Now here’s the honest part of this post, the part that makes me less certain than the rest.

Software margins haven’t actually compressed yet — not in most names. MSFT’s gross margin is essentially flat year-over-year (68.7% → 67.6%), Adobe is flat, Salesforce is flat. The one large software name that is showing real gross margin compression is **ServiceNow, down from 78.9% to 75.1% — nearly four full points of margin in a single year, which is enormous — but it is only one name.

So the bear case against the IGV trade is straightforward: this is anticipated deterioration, not observed deterioration.The market is pricing in margin compression that hasn’t fully arrived in the reported financials, which makes it at least possible that the market is wrong and the rubber band snaps back when next quarter’s software earnings come in fine.

I don’t think that’s what happens, but I want to lay out why honestly. The capex is being spent right now, every quarter, in real dollars; depreciation on $130 billion per quarter of GPU and datacenter capex is going to start hitting income statements as those assets get placed in service, and that is not a forecast but an accounting identity. Once it hits, gross margins compress mechanically rather than at management’s discretion. But that sequence — capex first, depreciation second, margin compression third — is still a thesis, not a fact. The fact is the capex; the thesis is what the capex will eventually do to software margins. If you’re going to short IGV on the back of this, you should know which is which.

Who is getting hurt

The people getting hurt by the QQQ lie are not the index investors — the index is doing exactly what it was designed to do, which is to average things. The people getting hurt are the active managers, the long-only growth funds, the “AI thematic” ETFs, and the retail investors who own software names because they believed in the AI story, and they are getting hurt because every dollar the AI story raised in capital, attention, and capex went into the silicon side of the trade and is being extracted out of the software side.

If you own IGV — or if you own a basket of “AI software” names because somebody told you AI would expand software TAM — you have been on the wrong side of the largest sector rotation in modern tech history, and your QQQ benchmark has been quietly telling you that you’re “only a little behind.” You are not a little behind; you are catastrophically behind, and the index is camouflaging the magnitude of your underperformance. Friday’s rip in MSFT and IGV may have closed the gap by a couple of points, but it does not close 87.

This is the most dangerous kind of bear market: the one that doesn’t look like a bear market on the chart everyone is watching.

What to do with this post

If you take one thing from this piece, take this: stop using QQQ as your proxy for “tech.” It hasn’t been a single sector for at least six months — it is two sectors stapled together, moving in opposite directions, and the index is hiding the divergence from you.

If you are long “tech” and underperforming, the question isn’t whether you’re right or wrong but which half of QQQ you actually own. If it’s the silicon half, you’re winning and you don’t know it. If it’s the software half, you’re losing and your benchmark is lying to you about how badly. So pull up your portfolio, look at the tech sleeve, and ask which half of the schism it lives on. The answer matters more than your YTD number.

Next Saturday: “Software Is Dead. Long Live Silicon.” A closer look at the margin transfer — when the depreciation actually hits, which names get crushed first, and why the coal-to-natural-gas analogy is more literal than you think.

If this reframed how you look at your tech book, restack it. Someone in your feed is benchmarking themselves to QQQ tonight and doesn’t know what it’s hiding.

As always, the material presented in Math & Markets is for informational purposes only. It does not constitute investment or financial advice.

Alpha is never guaranteed and the backtest is a liar until proven otherwise.

What the readers caught

The original backtester used Yahoo’s daily crypto bars to construct an “overnight” crypto return:

crypto_overnight_d = ln( Close_d / Close_(d-1) )

The problem: Yahoo’s daily crypto bar closes at 00:00 UTC, which is roughly 20:00 ET on the same calendar day. So Close_d is recorded after the VIX trading session of day d has already ended. The “overnight” variable I was using to predict the VIX trading-hour return contained the VIX trading-hour move itself.

That is the textbook definition of lookahead bias. It is exactly the kind of thing that turns a ~0.5 Sharpe signal into a ~2.4 Sharpe phantom.

I confirmed it directly. Once you align the “overnight” bar one day forward — so it is genuinely information available before the NY open — the same-day correlation of the proxy with the VIX trading return collapses from −0.24 to +0.001. The signal as I had it was almost entirely the contamination.

It sucks. But I’m grateful to Eric and Per because understanding and fixing the mistakes in the strategies we discuss is what makes M&M better!

Original numbers vs corrected numbers

Step 1: Rebuild the data, three ways

I scrapped Yahoo for crypto and rebuilt the dataset from cryptodatadownload.com, pulling hourly BTC and ETH bars from three exchanges that don’t share an order book: Binance (USDT pairs, Aug 2017–present), Bitstamp (USD pairs, May 2018–present), and Gemini (USD pairs, Oct 2015–present).

Three exchanges is overkill for the headline number, but it answers the obvious second question: is the signal a Binance artifact, or is it really there? The clean overnight return is now constructed from hourly bars at the exact NYSE-relevant times:

crypto_overnight_d = ln( price@09:30 ET on d  /  price@16:00 ET on d-1 )

NYSE sessions come from pandas_market_calendars. Matching hourly bar timestamps to ET clock times uses a 75-minute tolerance to absorb exchange downtime and DST. Sample: 2018-01-02 to 2025-12-30, 2,010 NYSE trading days.

Headline regression — clean, three exchanges

All BTC t-stats clear |t|>3.8. All ETH t-stats clear |t|>3.3. Standard errors are HAC (Newey-West) with 5 lags. The signal is real, robust across exchanges with no shared price source, and more statistically significant on clean data than it was on contaminated data. In-sample R² is roughly 3.0% for the crypto-only specifications, versus the 6.16% I originally reported. The original number was inflated; the sign and significance were not.

Strategy — VIXY long/short, 25bp round-trip cost

This is the corrected verdict, and it is much, much weaker than the headline I originally published. Gross Sharpe of ~1.2 looks fine. Net of realistic round-trip costs of 25 bps, Sharpe drops to ~0.6, drawdowns exceed 60%, and a 57% hit rate is well short of what would justify the position swings the strategy demands. This is not a tradable standalone strategy — it is a research finding about predictability, not a P&L engine.

Step 2: Can we save it with another variable?

Once the clean numbers were in, the natural next move was to ask whether the Sharpe could be repaired by adding additional, theoretically-motivated predictors. I picked three from the literature, all strictly available before the NY 09:30 open on each trading day:

• Nikkei 225 close-to-close return. NY Fed “Overnight Drift” work documents large Asian-session content in US open vol. Tokyo closes at 01:00 ET — fully pre-NY-open.

• Lagged VIX trading-hour return (d-1). Bevilacqua et al, “Breaking VIX at Open” — strong cross-autocorrelation between successive VIX trading-hour moves; VAR specifications dominate AR(1) and HAR.

• Log VIX level (d-1). Vol is mean-reverting at horizons ≤ 5 days. Cheap to add.

I deliberately did not test day-of-week dummies (data-mined to death), FOMC-day dummies beyond what’s already in the model (8 events/year overfit OOS), or VVIX (collinear with VIX level).

Extended-model coefficients

There is a more important and uncomfortable finding here. When we add log VIX level lagged, the BTC overnight coefficients lose significance. BTC t-stats collapse from −3.85/−3.93/−3.89 to roughly −0.6 to −1.1 across the three exchanges. ETH retains marginal significance (t ≈ −2.1 to −2.3).

That’s pretty interesting because it tells me a chunk of what the BTC overnight signal was capturing was VIX mean-reversion — high vol days tend to be days with sharp overnight crypto moves and days where VIX is about to revert. Once you control for the VIX level directly, BTC stops adding much.

Out-of-sample lift

In-sample R² rises from ~3.0% to ~5.5%. Out-of-sample R² rises modestly: from 5.8–6.5% to 6.5–7.5%. But the Diebold-Mariano test comparing clean vs extended yields p-values of 0.46 to 0.78 — i.e., the OOS R² improvement is not statistically significant. The model fits better in-sample, but we cannot reject that the OOS improvement is luck.

And, crucially, what happens to the Sharpe

The extended model is more informationally accurate — Spearman IC of forecast vs realized VIXY return rises from 0.071 to 0.091, a ~30% lift. But the extended model flips position roughly 60% more often. Once you charge round-trip cost on every flip, the gain in IC is more than wiped out by the gain in turnover. The two lines cross at about 4 bps — i.e., the extended model is only better than the clean model in a friction-free world that doesn’t exist.

What I actually learned

1. The headline Sharpe of 2.36 was a bug. The real Sharpe net of 25bp costs is about 0.5–0.6 on clean, cross-validated data.

2. The crypto → VIX signal is real but weak. It is statistically significant on three independent exchanges, contributes ~3.3pp of OOS R², but does not, on its own, support a tradable strategy at realistic costs.

3. Most of the BTC signal seems to be a proxy for VIX mean-reversion. Once you include the lagged VIX level, BTC coefficients lose significance. ETH retains marginal significance.

4. Adding three theoretically-motivated predictors improved in-sample fit and information coefficient but reduced net Sharpe because the extended model trades much more. This is one of the cleaner examples of the gap between forecasting accuracy and strategy performance.

5. Nikkei is not predictive of next-day VIX trading-hour moves, at least once we control for VIX dynamics directly. This contradicts the natural intuition from the overnight-drift literature.

The honest synthesis: the crypto-VIX relationship is best understood as a small piece of the larger fact that volatility is mean-reverting, and crypto markets — being open 24/7 — happen to register that mean-reversion ahead of when the NYSE does. That’s interesting. It’s not a new strategy. It’s a noisier way of betting on something we already know.

What I’m changing on this site

• This post replaces the original Sharpe-2.36 post (I’ll still leave the old one up for a minute).

• All numbers here reflect the clean values.

• Full corrected data and code —

  • clean_replication.py

  • extended_replication.py

  • Data bundle with derived panels, model outputs, strategy P&L, and readme.md

  • I have not included the raw hourly OHLCV bars from Binance/Bitstamp/Gemini — you can download them directly from CryptoDataDownload.com

Method appendix

Crypto data: Hourly BTC and ETH from cryptodatadownload.com (Binance USDT, Bitstamp USD, Gemini USD). All timestamps UTC. Hourly bars matched to ET clock times via UTC lookup with 75-min tolerance.

Reference data: Daily VIX, ES futures, VIXY, and ^N225 from Yahoo Finance. Daily series are only used for instruments whose close is unambiguously before the NY open on the prediction date, so there is no equivalent lookahead.

Target: vix_trading_d = ln(VIX_close_d / VIX_open_d) — the NYSE-session VIX return.

Standard errors: HAC (Newey-West), 5 lags. OOS: rolling 666-trading-day window, walk-forward one-step-ahead. Strategy: VIXY long if forecast > 0, short if < 0; round-trip cost 25 bps applied to each position change. Diebold-Mariano: squared-loss differential, Newey-West variance, two-sided.

Remember: Alpha is never guaranteed. And the backtest is a liar until proven otherwise.

As you can see, my math can have errors — please let me know if you find any.

The material presented in Math & Markets is for informational purposes only. It does not constitute investment or financial advice.

The VIX is a forecast of the next 30 days of S&P 500 volatility, and it only trades during the 6.5 hours U.S. equities are open. The other 17.5 hours of every day, the world keeps happening — and there is exactly one freely-traded, leverage-funded, globally accessible risk asset that doesn’t stop: cryptocurrency. Whatever happens to it overnight tells you something about global risk appetite that flows into the next VIX print.

A 1% positive overnight return in Bitcoin or Ethereum — the hours when U.S. equity markets are closed — predicts a roughly 0.4% drop in the VIX during the next U.S. trading session. The signal is large by predictive-regression standards (t ≈ −5), and a single-signal VIXY long/short strategy built on it produces an out-of-sample Sharpe of 3.05 gross, 2.36 net of 25 bps.

had recently posted a paper on VIX Forecasting Using Crypto Overnight Returns. He was kind enough to help me with the methodology, which I was able to successfully replicate.

The replication target is Gu, Lin & Liu (2026), “Beyond Conventional Sentiment Indicators: Cryptocurrency’s Hidden Potential in VIX Forecasting” (Economic Modelling). Their paper uses 5-minute CoinDesk data; this version uses only what’s publicly accessible on Yahoo Finance, January 2018 through December 2025. The headline findings replicate cleanly.

The decile sort makes it unmissable

Sort every trading day into ten buckets by overnight crypto return, then plot the mean VIX trading-hour change in each bucket. The gradient is monotone: +2.4% to +2.6% in the bottom decile (big crypto sell-off), down to −2.7% in the top decile (big crypto rally). No nonlinearity to hide behind. No subset of the data carrying the result. A clean, monotone, economically interpretable signal.

Regression coefficients with HAC standard errors

Four nested OLS specifications, all with Newey-West (5 lags) standard errors. The baseline controls for VIX overnight, SPX futures overnight, FOMC dummies, and post-holiday dummies — and reaches an R² of just 0.43%. Adding BTC alone takes R² to 5.51%; adding ETH alone, 5.73%; both together, 6.16%. SPX futures overnight, the conventional sentiment proxy, never loads significantly.

The signal is small in absolute magnitude — but stable in sign, significant in every regime, and untainted by the conventional sentiment proxies you’d expect to dominate.

Out-of-sample: a rolling-window forecast

Forecasts are produced with a 666-day rolling window — re-estimated every day, used to forecast the next day’s VIX trading-hour log change. Baseline is an AR(1); the augmented model adds BTC overnight, ETH overnight, and SPX futures overnight. The Diebold-Mariano test rejects equal predictive accuracy at the 1% level.

METRICAR(1) BASELINECRYPTO-AUGMENTEDΔn (OOS observations)1,3421,342—MSE0.0049160.004653−5.3%MAE0.048360.04728−2.2%OOS R² (vs zero)2.19%7.43%+5.2 ppDiebold-Mariano stat—2.70p = 0.0069

From forecast to position.

The forecast is converted into a daily position on VIXY, the ProShares VIX short-term futures ETF. Long if predicted ΔVIX is positive, short if negative. Position taken at 09:30 ET, held to 16:00 ET. (VXX was delisted in January 2022, so VIXY is the live instrument throughout.)

Cost sensitivity.

Charging realistic round-trip costs per position flip:

A WORD ON THE 213% HEADLINE RETURN

That number deserves three caveats. (1) Realized vol is also 70% — the Sharpe is the defensible figure. (2) Max drawdown is −40%, with a particularly ugly 2024 stretch. (3) Short-borrow costs and financing on VIXY are not modeled and become meaningful at scale. The realistic takeaway is Sharpe ≈ 2.4 after costs, max drawdown ≈ 40%, and a clean economic story.

Crypto signals roughly triple in high-volatility regimes

Split the sample at the 80th percentile of the VIX level (threshold: 24.11). In low-volatility regimes (n = 1,606 days), the crypto–VIX correlation is a modest −0.13 to −0.14. In high-volatility regimes (n = 403 days), it roughly triples to −0.36 and −0.33. SPX futures overnight stays glued to zero across both.

The interpretation is straightforward. In a quiet regime, the marginal U.S. desk opens, scans the overnight tape, and prices it efficiently. In a high-stress regime, the overnight tape is itself the information event — and crypto is the cleanest read of that tape because it’s the asset that actually traded.

The bottom line.

All four findings of Gu, Lin & Liu (2026) replicate cleanly on Yahoo Finance data:

• Crypto overnight returns significantly predict next-session VIX changes (t ≈ −5).

• Adding crypto triples OOS R²; the improvement is significant at p < 0.01.

• A VIXY long/short strategy on the augmented forecast generates a Sharpe of 3.05 gross, 2.36 net of 25 bps.

• The crypto signal strengthens in high-vol regimes, where SPX-based sentiment is noise.

Methodology footnote: Yahoo-only data & what changed

The original study uses 5-minute CoinDesk bars from 2018 to 2025. Yahoo’s intraday data is capped at ~730 days, so a true 5-minute history wasn’t retrievable. The replication uses a hybrid construction:

• Hourly-precise window for 2024–2026, where Yahoo serves hourly bars. The 16:00 ET → 09:30 ET overnight return is computed from actual hourly prints.

• Daily-proxy window for 2018–2024. Crypto’s UTC daily close sits roughly four hours after U.S. equity close, so 24/7 daily close-to-close is a reasonable approximation for the overnight return.

The signal is qualitatively unchanged by the granularity choice.

Other deviations

• No Google Trends / on-chain attention proxies. Those weren’t accessible from Yahoo; the paper’s attention-decile analysis is omitted.

• AR(1) rolling OOS forecast in place of the paper’s VAR(p). For a single-target ΔVIX problem, essentially equivalent.

• Diebold-Mariano only, no Model Confidence Set. DM is sufficient for the pairwise baseline-vs-augmented comparison.

• VIXY only. The paper uses both VXX and VIXY; VXX was delisted in January 2022.

• FOMC dates are the 66 release-day dates from the Federal Reserve’s official 2018–2025 calendar, hardcoded.

• Standard errors on all regressions are Newey-West HAC with 5 lags.

Tickers used: BTC-USD, ETH-USD,^VIX, ES=F, VIXY. All from Yahoo Finance via yfinance.

Remember: Alpha is never guaranteed. And the backtest is a liar until proven otherwise.

My math may have errors — please let me know if you find any.

The material presented in Math & Markets is for informational purposes only. It does not constitute investment or financial advice.

This is part of my series — Building & Scaling Algorithmic Trading Strategies

Fifth post in the 0DTE series. Previous: Two-Engine, V2, V3, Three-Engine, $25K Trades, What the pros are doing, 0DTE Engine 4: When Not to Trade (I)

Last Saturday, I introduced Engine 4: the regime classifier that decides which of the three 0DTE engines (income, convexity, VIX governor) gets to fire on any given day. The framework showed 7 of 9 regime cells beat a no-filter baseline on illustrative data.

This post validates that framework on real market regimes (2018-2024) with realistic engine mechanics. The question it answers is does the regime filter still work when you model how the engines actually behave?

The answer is yes — but with a caveat about GEX.

Methodology: Real Data, Realistic Models

This backtest runs on:

Real market data: SPX and VIX history from June 2018 to August 2024. The 1,329 trading days cover three distinct regimes: calm (most of 2019, most of 2024), elevated (March-April 2021, scattered 2022), and spike (March 2020, August 2024).

Realistic engine mechanics:

• Engine 1 (income): 65-72% win rate depending on VIX level. Not perfect — reflects slippage, execution variance, and the reality that premium capture degrades as vol rises. Average win ~35 bps, average loss ~75 bps.

• Engine 2 (convexity): Daily theta bleed (~0.8 bps), plus rare but large spike payoffs (~5% of days generate 300-800 bps). Models the long-hedge behavior: slow decay, occasional paychecks.

• Engine 3 (VIX governor): Position sizing scales from 1.0x (VIX < 20) to 0.4x (VIX > 25). Not a separate P&L engine — it’s a multiplier on the other two.

Three versions compared:

1. Baseline: All engines always on, sized by VIX level only

2. Engine 4 (VIX+time): Regime classifier using VIX level + term-structure signal, no GEX

3. Engine 4 (VIX+time+GEX): Same as above, plus z-score GEX overlay

The Results

TL;DR: Engine 4 wins on both P&L and drawdown. The always-on baseline loses money over the full period.

The chart above shows why. The baseline grows steadily until spikes hit. Then it gets hurt. Engine 4 versions sit out those spikes entirely (0% trades in high-VIX regimes). The filtered versions outperform on total P&L and take a fraction of the drawdown.

Why This Comparison Matters

“The baseline number (60.6% win rate, -5.8 bps/day) is theoretical. It assumes you trade every single day, every single regime, regardless of whether the market is paying you to take the risk.

The filtered versions (69.4% win rate, 16.5 bps/day) trade fewer days. They sit out bad regimes.

The question isn’t “which version makes more money?” It’s “which version takes intelligent risk?” Part 1 made the argument that the edge is in disqualification, not discovery. This backtest shows what that actually looks like.

When you break it down by regime cell, you see where that disqualification matters.

The Three-Version Grid Breakdown

The key insight here is that in low and mid regimes, all three versions perform similarly. The filter’s value is in the high-VIX rows — where it stops trading entirely (0% because engines are off). Baseline keeps running and loses.

The one cell worth isolating: mid VIX + negative GEX. Win rate collapses in all three versions. This is the regime where dealers are already short gamma and the vol surface is about to invert. Engine 1 is still partially deployed, Engine 2 hasn’t fully kicked in yet. It’s the worst of both worlds. If you see mid VIX with negative GEX developing, the correct action is to close positions and wait — not optimize the engine mix.

The two heatmaps are nearly identical. The GEX overlay is supposed to improve the filter by separating good dealer conditions from bad. Instead, it makes one cell worse (low + negative GEX, -2.5pp) and leaves eight unchanged. The z-score normalization works mathematically. The signal doesn’t exist. This is what $3k/month gets you: one worse cell and eight unchanged ones.

But here’s the critical finding: GEX actually hurts win rates by 0.28 percentage points on average (60.6% → 60.5%). In one cell (low + negative GEX), it underperforms by 2.5pp. There’s no regime where GEX improves the filter. It’s not worth the $3k/month feed. VIX + time is strictly better.

The Individual Grids

Here are the three versions broken down cell-by-cell:

Version 1: Baseline (VIX gate only)

The baseline filters on VIX level only (skip if VIX > 25, half-size if 20-25). It’s still running both engines in every VIX regime. In calm and mid regimes, this works fine. But notice the high-VIX cells: 48-60% win rate. You’re trading in a panic, engines are sized down, and you’re still taking losses. This is the cost of not having a regime classifier — you’re not quitting when you should.

Version 2: Engine 4 (VIX + Time)

Introducing term-structure signal (VIX1D momentum). This does two things:

• In low VIX: income engine stays full size (same as baseline). Convexity hedge is suppressed (0.3x) because tail insurance is expensive.

• In mid VIX with backwardation signal: convexity engine fires at full size, income is reduced to 0.3x. This is the transition regime where dealers are short gamma.

• In high VIX: both engines shut off entirely. Only VIX governor (sizing reduction) applies. No premium selling, pure defense.

The result: Win rates in high-VIX cells drop to 0% because we’re barely trading them. That’s intentional.

One caveat worth flagging: Engine 4’s high-VIX cells show 100% win rates in this simulation. That’s an artifact of the convexity payoff model — Engine 2 generates large spike payoffs on every high-VIX day by construction. Real convexity positions don’t pay off that cleanly. Treat the high-VIX win rates as directionally correct, not literally accurate.

Version 3: Engine 4 (VIX + Time + GEX)

Adding GEX overlay. Same grid, same win rates. The GEX column adds marginal signal in the low-VIX cells (separating positive-GEX from flat-GEX dealer states), but the overall pattern is identical to Version 2.

Live Example

What the filter did: In calm weeks, baseline and Engine 4 perform similarly. The divergence happens in spike weeks. In consecutive high-VIX weeks, the baseline lost -333, -246, -297, -426 bps. Engine 4 made +533, +482, +535, +687 bps in the same weeks. The filter wasn’t just sitting out — Engine 2 (convexity) was firing at full size and getting paid.

Sharpe ratios over the full period: Baseline −1.74, Engine 4 (VIX+time) +3.45, Engine 4 (VIX+time+GEX) +3.59. GEX adds 0.14 to Sharpe. Still not worth $3k/month.

The magnitude here is simulation-inflated. Engine 2’s spike payoffs are modeled as clean, frictionless, and fully-sized — real long puts don’t work that way. Treat the Sharpe spread (baseline vs filtered) as directionally correct. The absolute numbers aren’t reliable until Engine 5 adds a proper friction model.

The drawdown chart shows the difference starkly. Baseline’s max drawdown is -9,159 bps vs -1,980 bps for Engine 4 (VIX+time). That’s 4.6x deeper. The filter’s job isn’t to outperform in good markets — it’s to lose less in bad ones.

What Changed from Part 1

Part 1 showed the framework on illustrative data. Part 2 shows it on real market regimes with realistic engine mechanics. The framework held:

• 7 of 9 cells show intelligent behavior (sized appropriately for the regime)

• The failure mode (mid + negative) is identifiable

• GEX adds noise, not signal

The win rates are higher than Part 1 suggested (69.4% vs 60%). That’s because realistic spike mechanics hurt the baseline far more than illustrative data showed. The edge is stronger, not weaker — but only if you’re not trading into high-VIX regimes.

The GEX Problem — Diagnosed

A reader commented this — “If you’re going to use GEX, it needs to be systematic and backtestable, not hand-waving.” Totally fair, so I ran the numbers.

Z-score GEX subtracts 0.28 percentage points from win rate. In one cell (low + negative GEX), it underperforms by 2.5pp. For a $3k/month feed, that’s a negative cost-benefit.

But here’s the thing: GEX itself isn’t broken. My implementation was. I was z-scoring GEX on SPX in isolation. By the time GEX flips negative, dealers are already in pain and the cascade is underway. You’re 24-48 hours too late.

who caught this explained the real failure mode: it’s not a statistical anomaly. It’s the mathematical result of Vanna cascades and dealer delta-hedging forcing the vol surface to invert. The 17.6% collapse (mid + negative GEX) happens because I’m watching a reactive, lagging metric on a single asset.

Real edge comes from seeing it before it breaks. Cross-asset synthesis — SPX + SPY + NDX + QQQ options flows together — maps the institutional liquidity clusters that dealers must hedge against. When those assets synchronize into a gamma flip, you get variance expansion 24-48 hours early. That’s anticipation, not reaction.

So here’s the takeaway: You get 100% of the edge from free VIX data (level + term structure). Z-score GEX on SPX alone adds nothing but noise. If you have a GEX feed and you’re using it the way I was, drop it. If you don’t have one, don’t chase it.

But the structural signal — cross-asset liquidity mapping — that’s Engine 5. Not reactive metrics. Predictive early-warning.

On synthetic GEX and why structure matters: I didn’t backtest real dealer positioning data. I modeled GEX synthetically using vol regime changes and RV vs IV spreads — crude proxies for dealer pain. Hau’s work (@HauVolatility) on vol and dealer positioning is closer to what actually matters — structural flow analysis and real market microstructure.

That’s what Krupp Capital was pointing to as well: you need cross-asset synthesis to see the cascade 24-48 hours early. My synthetic GEX was a placeholder. Real structural flow analysis is Engine 5.

In Closing…

The regime classifier works on real data. It beats an always-on strategy on both P&L and drawdown. The edge is in knowing when not to trade.

The failure mode is real: mid VIX + negative GEX. If you see this regime forming, close positions.

GEX doesn't just fail to improve the edge — it subtracts from it. VIX + time is your core.

If your backtest shows different results, I want to see it!

What’s Next

Engine 5 is about execution friction. Right now I’ve modeled slippage as uniform across regimes but it really isn’t. Low-VIX environments have tight spreads but wide market moves. High-VIX environments have looser spreads but options pin to strikes. Building a friction layer that scales by regime should improve the filter another 10-15%.

Engine 6 — if we get there — is about IV surface complexity. One reader suggested 0DTE vs 1DTE backwardation as a transition signal. Another suggested put/call skew by delta. Both of those are candidates for the next upgrade, but only after we validate the current framework on live trading data.

Until then, I’ll keep experimenting, one variable at a time!

As always, thank you for reading Math & Markets.

Footnote On This Backtest

I use synthetic engines but real market regimes. The engine mechanics are modeled based on typical behavior (70% income win rates in calm vol, theta decay on long hedges), not calibrated to specific strategies. Your actual engines might perform differently.

The framework itself — the regime classification logic, the failure mode identification, the GEX impact assessment — should transfer to real trading. But validate it on your own data before you size capital to it.

As always, this post is about methodology, not recommendations. Options and derivatives are complex instruments and this analysis probably contains errors. If you find them, let me know.

The information presented in Math & Markets is not investment or financial advice and should not be construed as such.

This is part of my series — Building & Scaling Algorithmic Trading Strategies

Fifth post in the 0DTE series. Previous: Two-Engine, V2, V3, Three-Engine, $25K Trades, What the pros are doing.

Over the last four posts, I’ve built three separate engines for 0DTE premium selling — Engine 1 (income), Engine 2 (convexity), and Engine 3 (VIX governor). Each one is a bet and each one assumes something about the market on the day you’re trading it. And alas, each one stops working the moment that assumption breaks.

Engine 4 is not another engine. It’s the rule that sits above the other three and decides which one gets to fire.

The core thesis: Engines 1-3 are bets. Engine 4 is the regime classifier that decides which bet the market is currently paying you to make — and the honest answer, most days, is “none of them.”

Methodology Note: This is Part 1 of 2

This post introduces the framework and validates it on illustrative (synthetic) data. The backtest shows proof-of-concept: a regime classifier beats a no-filter baseline in 7 of 9 cells, and identifies a failure mode. But it’s not yet validated against actual Engine 1-3 mechanics.

Part 2 (next week) rebuilds this backtest on real engine mechanics:

• Engine 1 as an intraday credit spread model (individual spread win rates, delta decay, gamma bleed)

• Engine 2 as a long-dated hedge model (theta decay + spike payoff)

• Engine 3 as a VIX-indexed sizing rule

The framework itself — the 3×3 grid, the regime classification logic, the identification of mid + negative as a failure mode — should transfer to real data. But you’ll want the validation before you size capital to it.

Correction: Engine 3 Sizing at High VIX

I want to credit and for pointing out a few gaps and errors in my methodology.

There was a gap in the Engine 3 sizing logic in Thursday’s post. I had it backwards.

The error: I wrote “widen to 15-delta at high VIX” for risk management. But 15-delta is closer to ATM, not wider — that’s the opposite of what you want when volatility rises.

The correct logic: A 10-delta put always has ~10% probability of expiring ITM, regardless of VIX. But the dollar distance from spot changes with vol. At VIX 15, a 10-delta put might be $130 OTM (~1.8%). At VIX 30, the same 10-delta put is $200 OTM (~1.3%). Same delta, less percentage cushion.

To maintain the same percentage distance OTM at high VIX, you should move to a lower delta — 5-7 delta — which pushes the short strike further from spot. This collects less premium per spread, which is why you’d also reduce contract count.

The corrected sizing rule:

• VIX < 20: Short 10-delta put

• VIX 20-25: Short 7-delta put

• VIX > 25: Short 5-delta put

Part 2’s backtest will use these correct thresholds. Thank you for catching this — you were right, and I should have stress tested my own logic harder.

Why Engines 1-3 Aren’t Enough

I’d say the first three engines are strategies. They assume a regime and trade inside it.

Engine 1 (income) assumes the market stays in a profitable zone for intraday credit spreads. Engine 2 (convexity) assumes tail-risk premiums stay stable enough that long puts bleed predictably. Engine 3 (VIX governor) assumes position sizing scales inversely with volatility risk.

Each one has a failure mode. Each one stops making money when its assumption no longer holds.

Every backtest I’ve shown you in this series ran on the same six-year window. That window had three distinct regimes: calm (most of 2019, most of 2024), elevated (March-April 2021, scattered 2022), and spike (March 2020, August 2024). The strategies don’t know which one they’re in. Engine 4 is the part that does.

When I ran all three engines without regime classification — sizing them identically across all regimes — the aggregate win rate was 40.5%. That’s worse than random. It’s the cost of indiscriminate trading — trying to capture premium in regimes where it shouldn’t be captured, running convexity hedges at fixed cost when tail insurance is about to spike in value, keeping position sizes constant when volatility risk is climbing.

The question wasn’t “are these three engines broken?” The question was “which engine should I turn off today, and which should I turn up?”

Engine 4’s job is to disqualify days, not to discover trades.

The Two Inputs, and the One I’m Less Sure About

Engine 4 takes two inputs. I trust one of them. The other one is — well, maybe.

Input 1 — VIX + time (the trusted one):

VIX absolute level + VIX term-structure slope (front month vs 3-month).

Why this works: it captures both the level of forward-implied vol and whether the market is pricing the front or back of the curve. When VIX1D moves three times as fast as VIX on a flat-tape day, the surface is telling you something the index isn’t. It’s a transition signal — the term structure is decoupling because dealers are repricing faster than spot.

Reference the tape at the time of writing this as a live example: VIX at 16.10 while VIX1D ripped +29.9% to 11.54 in a single session. That’s the exact decoupling Engine 4 is built to flag. It says “the short-dated curve is moving faster than the index. The surface expects front-month vol to move materially.” That changes which engine you run.

Input 2 — GEX overlay (the one on probation):

GEX is dealer-positioning-derived. The inputs are noisy. The calibration drifts. Historical data is expensive ($3-5k/month for a clean feed). Most retail traders don’t have access to real-time GEX.

Here’s my honest take: If you took GEX out of Engine 4 entirely, you’d lose roughly 15% of the edge and roughly 40% of the false signals. That trade is worth making in some regimes and not worth making in others. This post will tell you which.

The framework I’m about to show you runs on VIX + time as the primary input. GEX is a secondary filter — optional, not required. If you don’t have a live GEX feed, the VIX-and-time classifier gets you 85% of the way there. If you do have it, you get incrementally better at identifying which sub-regimes (positive/flat/negative dealer gamma) are safest for each VIX level.

I don’t have a real-time GEX feed either. That’s part of the limitation I’m trying to address and work around.

Note on Part 2: pushed back last week that “check GEX” isn’t a systematic signal — it needs backtestable rules or it’s hand-waving. He was right. This post sets up the framework. Monday’s post validates it on real market regimes and runs the exact three-way comparison: Baseline vs. Engine 4 (VIX+time) vs. Engine 4 (full GEX with z-score normalization). You’ll get the answer that matters most: does GEX improve Sharpe and drawdown enough to justify the $3k/month feed, or do you get 85% of the edge from free VIX data alone? I’m running this to answer it for myself. You get the results for free!!

The 3×3 Grid — Where Regime Meets Engine Mix

Engine 4 classifies every trading day into one of nine cells: 3 VIX levels × 3 GEX states.

Each cell has a specific job: which engines fire at what size, and what move in VIX shuts the whole thing down.

Here’s the grid with backtest results from six years of data:

What the grid is telling you:

Low VIX + positive GEX (top-left): Calm market, dealers accumulating long gamma. Engine 1 (intraday income) fires at full size — the premium is reliable and the spread deltas are stable. Engine 2 (long tail hedge) is suppressed to a light 0.3x because tail insurance costs more relative to the risk. This is most of 2024. Win rate 39.6% — barely beats baseline. The puzzle here is worth noting for Part 2: dealers being long gamma in calm markets theoretically de-risks short premium, but the data shows only marginal outperformance. Possible explanations: slippage dominates, sample size (53 days) is too small, or the signal is weaker than expected.

Mid VIX + negative GEX (the red cell): This is the catastrophic regime. Mid VIX (15-25) means you’re past the calm threshold — volatility is elevated. Negative GEX means dealers are short gamma — they’re being forced to buy back options in a rising vol market. You’re trying to run Engine 2 (long tail hedge) at full size, thinking “dealers are in pain, protection is expensive.” But that’s exactly backwards. Dealers are short gamma because the vol surface is about to invert. Your long puts haven’t spiked yet, but they’re about to. Your short spreads (Engine 1) are about to blow up. This is when the filter should be stopping you from trading entirely, not optimizing engine mix. Win rate 17.6% — the worst cell by far. This regime occurs roughly 1-2 times per month but defines drawdown months. The honest application: mid + negative is a kill-switch. Close positions. Go to cash until the regime clarifies.

High VIX + any GEX (bottom row): Market in crisis. Engine 3 (VIX governor / sizing reduction) takes over completely. Engines 1 and 2 are off. You’re running pure defense: reduced position sizes, full hedge ratios, minimal new premium selling. All three cells beat baseline by 16-26 percentage points. Win rates are 57-67%. The absolute P&L is barely positive (+2.8, +0.8, +0.2 bps) — which is exactly right. The job isn’t alpha generation. The job is “preserve what you made in calm months and don’t give it back in panic months.”

Mid VIX + flat (the sweet spot): 49.8% win rate, +9.3 pp outperformance. Moderate volatility, neutral dealer positioning. You get a balanced allocation: Engine 1 at 0.8x (intraday income still profitable but margins are tighter), Engine 2 at 0.5x (hedging costs are moderate, worth the protection), Engine 3 off (no need for emergency sizing cuts yet). This is the standard allocation most trading days fall into.

Engine 4 Regime Grid: Win Rate Heatmap. Green = beats 40.5% baseline, Red = underperforms. The mid + negative cell (bottom row, left) is where the filter fails catastrophically at 17.6% win rate.

Engine Sizing by Regime: How much of each engine (Income, Convexity, VIX Gov) fires in each regime cell. The shaded area marks the failure mode, where Engine 2 (Convexity) is at full size precisely when the surface is about to invert.

Live Example — What Engine 4 Says Right Now

At the time of writing this post, VIX is 16.10 (mid-low boundary). SPX -0.70% (essentially flat). But VIX1D +29.9% to 11.54 in one session.

Where does the grid put you?

Base classification: Mid VIX (16.10 is just above the 15 threshold). Term structure signal: VIX1D up +29.9% in one day while spot tape is flat = front-month repricing faster than the index = early warning of backwardation. This is the signature of dealers being forced to reduce short exposure.

GEX position: You don’t have a live GEX feed. (I don’t either.) So you’d default to the “flat” cell or wait for EOD positioning data. If you’re using a data co-op or the BMLL feed, you could check dealer positioning explicitly. But if you’re flying on VIX + time alone, you’re in mid/flat.

What the filter says:

Engine 1 (income) at 0.8x size. Engine 2 (convexity) at 0.5x. Engine 3 off. Expected win rate: 49.8%. Mean daily expected: -39.8 bps.

Interpreting this:

I’m telling you what the filter says. I’m not telling you to take the trade (or not). As I always say, the backtest is a liar until proven otherwise, and that includes this one. The fact that this cell beat baseline by 9.3 percentage points in backtest doesn’t mean it will beat baseline today.

What this means is that if you’re running a systematic strategy, this is the regime cell you’ve sorted into, and these are the engine weights your rules say to run. Whether you take it is your call. Whether it works is between you and Mr. Market.

Section 5: What’s Actually New Here

Most retail filter-stacks are AND gates: VIX low AND GEX positive AND trend up = trade. If one input flips, the whole system shuts down. They’re binary.

Engine 4 is a regime classifier, not an AND gate.

The difference: AND gates fail catastrophically at boundaries. One input flips, and the whole strategy disappears from the universe. You go from full deployment to zero deployment in a single 0.5% move in VIX. Regime classifiers degrade smoothly. You move from one cell to another. The engine mix shifts, not the entire framework.

In backtest, the AND-gate version of this strategy (all engines fire only if all three conditions pass) was unfunded 73% of trading days. Engine 4 was unfunded roughly 30% of trading days. Same Sharpe target. Three times the deployment.

That’s the edge: not finding more alpha. Finding which days to deploy the alpha you already have.

AND-Gate vs. Regime Classifier: An AND-gate filter (all conditions must be true) sits empty 73% of trading days. Engine 4 sits empty only 30% of days — 3x more deployment with the same Sharpe target.

Outperformance vs. No-Filter Baseline. Engine 4 beats an always-on strategy in 7 of 9 regime cells. Mid + negative (bottom bar) underperforms by 22.8 percentage points — the failure mode.

What Else?

Three things I’m still working on:

The failure mode. There is one specific regime where this filter gets worse than no filter at all. I found it in backtest: mid VIX + negative GEX, 17.6% win rate, underperforms baseline by 22.8 percentage points. But I haven’t fully understood why it fails in that specific way — is it because the filter is trying to run convexity at maximum exactly when the surface is about to invert? Is it because 85 days is too small a sample? I’m figuring this out — but let me know if you spot the pattern before I do! :)

The GEX data problem. Where the historical data actually comes from (CBOE OTM volume, BMLL proprietary flow, dealer-facing APIs), why retail feeds are unreliable (EOD OI is a terrible proxy for intraday dealer positioning), and whether a reader co-op solves it (consider this — 20 readers willing to split a $3k/month BMLL subscription). This is the next technical problem to solve.

Engine 5. The next one isn’t a filter. It’s about execution friction. Right now I’m assuming slippage is uniform across regimes. It isn’t. Low VIX regimes have tighter spreads but wider market moves. High VIX regimes have looser spreads but the position pins. I’m building a friction model that adjusts for this. More in a few weeks.

The Failure Mode (Mid VIX + Negative GEX): 17.6% win rate, average wins of 41.7 bps against average losses of 138.5 bps. This is the transition regime where dealers are short gamma and the surface is repricing. 85 days in sample over 6 years.

Closing

Engine 4 doesn’t tell you what to trade. It tells you when to and when not to.

Obviously, I’ve only shown you the cells I’m most confident in. The cell that breaks worst (mid + negative GEX) is worth watching because you need to know where the filter fails.

As always, comments are open. I’ve probably made a mistake somewhere or the 3×3 may have gaps. Tell me where!

What’s Next

Part 2 (Monday) validates this framework on actual Engine 1-3 mechanics:

• Engine 1 modeled as intraday credit spreads (individual spread win rates, delta decay, fill slippage)

• Engine 2 modeled as a rotating long-option hedge (daily theta bleed, spike payoff on panic days)

• Engine 3 modeled as a VIX-indexed sizing rule (position count scales inversely with volatility risk)

The question Part 2 answers: Do the regime cells that beat baseline in this illustrative backtest also beat baseline when we model the engines’ actual mechanics? And does the mid + negative failure mode hold up empirically, or was it an artifact of simplified assumptions?

Comments are open here. But if you want to see the real validation, subscribe for Part 2 — Monday.

This post is about methodology, not recommendations. Options and derivatives are complex instruments and this analysis probably contains errors. If you find them, let me know.

The information presented in Math & Markets is not investment or financial advice and should not be construed as such.

This is part of my series — Building & Scaling Algorithmic Trading Strategies

Fourth post in the 0DTE series. Previous: Two-Engine, V2, V3, Three-Engine, $25K Trades.

The Question Nobody Asks

Every day, roughly 45% of all SPX options volume is 0DTE.

Let that number land. Nearly half of all options activity on the most liquid equity index in the world expires the same day it’s traded. This didn’t exist five years ago. CBOE started listing daily SPX expirations in 2022. By 2024, 0DTE was the market.

The Reddit version of this story: retail traders discovered they could sell iron condors for $1.50 and collect theta. /r/thetagang, passive income, and 72% win rate.

But here is the version nobody tells you: when retail sells those iron condors, someone is buying them. And the buyers are not random strangers. They’re desks at Citadel, Millennium, and Jump Trading — and they’re not buying your iron condor because they think SPX is going to blow through your strikes. They’re buying it because your flow is one component of a completely different trade.

This post is about what that trade actually looks like.

Two Different Games on the Same Board

Left: what retail does — sell iron condors, collect theta, smooth upward curve with violent drawdowns on blow-up days (red arrows). Right: what institutions do — trade dispersion and correlation, smoother curve, and they actually make money on the days retail blows up (green arrows). Same market. Completely different strategy.

Notice the arrows. On the days when retail’s equity curve drops — the VIX spike days, the gap-down days, the “I lost three months of premium in one session” days — the institutional curve steps up. Their green arrows point upward where retail’s red arrows point down.

This isn’t coincidence. The institutional trade is structurally designed to profit from the same volatility events that destroy the retail trade. Not because they’re betting against you. Because they’re playing a different game entirely.

The Dispersion Trade: The Institutional 0DTE Strategy

When a multi-strat fund trades 0DTE, they’re not selling premium for income. They’re trading the gap between two numbers: implied correlation and realized correlation.

Here’s the idea in plain English:

SPX index options price in an assumption about how correlated the 500 stocks in the index will be. If the index trades at 20% implied vol, and the average single stock trades at 25% implied vol, the market is pricing in high correlation — the index is almost as volatile as its components, meaning stocks are all moving together.

But stocks don’t always move together. On most days, Apple goes up, Microsoft goes down, energy rallies, tech sells off. The realized correlation is lower than what index options price in.

The trade: sell SPX vol (overpriced because of high implied correlation) and buy single-stock vol (cheaper per unit of risk). If stocks move independently — which they usually do — you profit.

Top: implied correlation (orange, from index options) vs. realized correlation (blue, from actual stock moves). The green-shaded zone is where dispersion makes money — most of the time. The red zone is during stress, when correlation spikes and dispersion temporarily loses. Bottom: cumulative dispersion P&L. Steady grind upward with brief dips during correlation spikes.

Why does this work with 0DTE specifically?

Because 0DTE SPX options are where retail concentrates its selling. All that iron condor flow pushes SPX implied vol lower relative to single-stock vol — widening the dispersion spread. The institutional desk is effectively buying the vol that retail is selling, but they’re doing it as part of a hedged correlation trade, not as a naked directional bet.

The retail trader thinks: “I’m selling premium for income.”

The institutional trader thinks: “Retail just made the short leg of my dispersion trade cheaper.”

The Flow That Moves SPX

This is the part that should change how you think about your 0DTE entries.

Top: SPX intraday price action on a day with heavy 0DTE open interest at 7,400. Price gravitates toward the strike all morning — the GEX magnet effect. At 2:30pm, dealer hedging flips and the magnet becomes a launcher. Bottom: the 0DTE contribution to total GEX (orange) builds throughout the day and collapses into the close. When it collapses, dealers stop dampening moves and volatility spikes.

When you sell a 0DTE put credit spread, a market maker buys it from you. That market maker is now long your put — which means they’re long gamma. To hedge, they sell SPX futures. If SPX drops, their put gains delta, so they sell more futures. If SPX rises, they buy back futures.

At scale — with 45% of all SPX volume in 0DTE — this hedging flow moves the actual index.

The effect depends on the time of day:

9:30am-2:00pm: 0DTE GEX is positive and building. Market makers are long gamma from the puts and calls they bought from retail. Their hedging dampens moves — if SPX dips, they buy; if it rips, they sell. Price tends to mean-revert toward heavy open interest strikes. This is the “magnet” effect.

2:00pm-2:30pm: The transition zone. As 0DTE options approach expiry, their gamma explodes (gamma is proportional to 1/sqrt(time)). Dealers’ hedging activity becomes increasingly frantic. The price gets pinned to the nearest large OI strike.

2:30pm-4:00pm: The GEX collapses. Options are expiring, dealers are unwinding their hedges, and the dampening effect disappears. SPX is free to move — and the accumulated hedging pressure can release in either direction. This is why the last 90 minutes of trading are the most volatile.

What institutional desks do with this: They know the GEX schedule because they can see the open interest. Their stat arb desks trade the mean-reversion in the morning (when GEX is dampening moves) and the momentum in the afternoon (when GEX is releasing). The 0DTE flow that retail creates is the signal they’re trading on.

The Food Chain

The 0DTE ecosystem. The multi-strat fund sits on top with three desks: vol arb (dispersion trades using the vol retail sells), market making (capturing the bid-ask on every retail transaction), and stat arb (using the GEX signal that retail flow creates). Retail flow feeds all three.

Three ways institutions extract value from retail 0DTE flow:

1. The Vol Arb Desk buys the cheap vol that retail sells. Not as a standalone trade — as the short leg of a dispersion or skew trade. Your iron condor premium is their cost basis for a hedged correlation position.

2. The Market Making Desk captures the bid-ask spread on every trade. When you sell a put spread and collect $0.75, you probably crossed at $0.73-0.74. That $0.01-0.02 per contract, multiplied by millions of contracts per day, is the market maker’s revenue. The more retail volume, the more they make.

3. The Stat Arb Desk uses the GEX exposure that retail creates as an intraday trading signal. Positive GEX = mean reversion plays. Negative GEX = momentum plays. The open interest data — which reflects where retail has positioned — is visible and exploitable.

None of this means retail is “being scammed.” The market is providing a service: retail gets exposure to the VRP (which is a real, documented edge) and the institutions get exposure to dispersion, flow, and microstructure (which are different, often uncorrelated edges). Both sides can make money.

But only one side understands the full picture.

What You Can Actually Learn From This

Knowing how institutions trade 0DTE doesn’t mean you should try to trade like them. Dispersion requires capital, infrastructure, and cross-asset execution that retail can’t replicate.

But there are two practical takeaways:

Left: GEX-aware entry timing. Skipping trades on negative GEX days (when dealer hedging amplifies moves instead of dampening them) improves the Sharpe. Right: average P&L by entry time. Entries before noon are significantly more profitable than entries after 2:30pm, when GEX collapses and gamma accelerates.

Lesson 1: Check GEX Before You Trade

When aggregate GEX is positive, market makers are dampening moves. Your short premium position benefits — prices mean-revert, your strikes stay safe, and the grind-to-expiry works in your favor.

When GEX is negative, market makers are amplifying moves. Your short premium position is exposed — prices trend, stops get hit, and the gamma you’re short is working against you.

Skipping trades on negative GEX days — roughly 20% of all sessions — reduces your trade count but meaningfully improves your Sharpe. Fewer trades, better trades.

Lesson 2: Respect the 2:30pm Line

After 2:30pm, the 0DTE GEX contribution collapses to zero. The dampening effect disappears. If you enter a credit spread at 3pm, you’re selling premium into the most volatile 60 minutes of the trading day, without the institutional hedging flow that was protecting you all morning.

The data is consistent: average P&L per spread is positive for entries before noon, roughly breakeven for 12:00-2:00pm entries, and negative for entries after 2:30pm. The premium looks the same at 3pm as at 10:30am. The gamma does not.

The Uncomfortable Chart

Each dot is one day. X-axis: total retail 0DTE premium sold. Y-axis: market maker profit. The correlation is 0.85. More retail volume, more institutional revenue. This is the business model: retail provides predictable, one-directional flow, and institutions monetize it through superior infrastructure and hedging.

This chart isn’t an argument against selling 0DTE premium. The VRP is real and retail can make good money selling options. The Two-Engine and Three-Engine frameworks I’ve published in this series are designed to capture that edge responsibly.

But it is an argument for understanding where you sit in the ecosystem. When you sell an iron condor, you’re not trading against a faceless market. You’re selling cheap vol to a dispersion desk, paying the bid-ask to a market maker, and creating GEX exposure that a stat arb desk trades on.

The edge you capture — the VRP, roughly 0.05-0.10 per spread after costs — is what’s left after these participants have taken their cut. It’s real. It’s just smaller than you think.

What to Do With This

If you’re selling 0DTE premium: Keep doing it. The VRP is real and your edge is real. But add two things: a GEX check (skip negative GEX days) and a time cutoff (no new entries after 2:00pm). These two filters alone will improve your Sharpe by reducing exposure to the environments where institutional flow works against you.

If you’re thinking about 0DTE premium selling: Read the Two-Engine and Three-Engine posts first. The framework matters more than any individual trade. Understand the VIX regime sizing before you enter your first spread.

If you’re an aspiring institutional trader: The dispersion trade is the starting point. Study implied vs. realized correlation, learn to decompose index vol into single-stock vol plus correlation, and understand how GEX creates tradeable intraday patterns. The opportunities are real — but they require infrastructure that a Schwab account can’t provide.

The Honest Caveat

I wrote this post from the retail side of the table. I have not run an institutional dispersion book. The descriptions of institutional strategies are based on published research (Derman, Bossu, Carr), industry commentary, and conversations — not personal P&L. The flow data is estimated from public sources and academic analysis, not proprietary order flow.

However, my co-author and quant trading partner is a former quant, and he’s run an option book at a major fund.

But here’s what I am confident about: the GEX feedback loop is well-documented and the entry timing implications are real. What I’m less confident about: the exact percentage splits in the flow hierarchy. Those are informed estimates, not precise measurements.

As always, the goal is to understand the game you’re playing — including who else is at the table.

Remember: Alpha is never guaranteed. And the backtest is a liar until proven otherwise.

The material presented in Math & Markets is for informational purposes only. It does not constitute investment or financial advice.

This is part 100 of my series — Building & Scaling Algorithmic Trading Strategies

The Trades

Every other week there’s a variation of this on various Reddit trading subs: “I have $25K. What 0DTE trades should I actually be making?”

Not “it depends on your risk tolerance.” Not “paper trade first.” The actual trades. Strikes, dollars, what you’re risking, what you’re making.

Well, here are the four I’d run — with SPX at 7,400 — and what each one looks like at expiry.

Four trades, four payoff profiles. Top left: the put credit spread — your daily workhorse, collect $75, risk $425, win if SPX stays above 7,250. Top right: the iron condor — higher premium ($130), tighter range (7,250-7,550), win if SPX goes nowhere. Bottom left: the butterfly — only $250 at risk, but if SPX pins near 7,400 you make $750. Bottom right: the call credit spread — same structure as the put spread but on the upside, slightly less premium because of skew.

Trade 1: The Put Credit Spread

This is the one you do every day. The one that compounds your account while you’re eating lunch.

10:30am. Not at open — the bid-ask spread at 9:30 is 30-50% wider than it will be an hour later. You’re paying $20-40 in invisible friction for the privilege of being early. Just wait.

Sell the 10-delta put. With SPX at 7,400 and VIX at 18, that’s roughly the 7,250 strike — about 1.5% below spot. Buy the put $5 below it (7,245). Collect $0.65-0.85 in premium per spread.

You just bet that SPX won’t fall 1.5% by 4pm. Historically, SPX stays above its 10-delta put about 72% of the time. On the 72% of days you’re right, you keep $65-85. On the 28% you’re wrong, you lose $425-435.

Expected value per spread: roughly +$5. Not exciting per trade. But 3 spreads a day, 252 days a year — that’s the math behind a 19% annual return on a $25K account. We’ll get to the growth path.

When to skip: VIX below 14 (premium is $0.15 — not worth the execution cost) or VIX above 25 (widen to 15-delta strikes per the Three-Engine framework).

Trade 2: The Iron Condor

Same concept, both sides. You’re selling the put credit spread AND a call credit spread. Betting SPX stays in a box.

Sell the 10-delta put spread (7,250/7,245) AND the 10-delta call spread (7,550/7,555). Collect $1.10-1.40 combined.

More premium than a standalone spread — $130 vs. $75. But the win rate drops to about 65% because the market only needs to break ONE side to hurt you. On big directional days, you give back the extra premium and then some.

Use it when: You have zero directional view and VIX is in the 16-22 sweet spot. This is a pure vol trade — you’re selling the market’s expectation of movement.

Don’t use it when: There’s a Fed meeting, CPI print, or any catalyst that could send SPX 1%+ in either direction. On catalyst days, sell one side — the side you think won’t get hit.

Trade 3: The Butterfly

This is the underrated one. The trade nobody on Reddit talks about because the win rate is ugly — roughly 30%. But the risk/reward is inverted.

Buy the 7,390 call. Sell two 7,400 calls. Buy the 7,410 call. Cost: $2.00-3.00 per fly ($200-300).

If SPX closes anywhere near 7,400, you make $400-750. If it doesn’t, you lose your $250. That’s it.

The math doesn’t work on any single day. It works across 30 days. You put on 3-4 butterflies a day at $250 each, risk $750-1,000 (3-4% of account), and the 30% that hit near the center strike cover the 70% that don’t.

The secret: Low-VIX days when the market is grinding sideways. SPX tends to pin near round numbers and heavy open interest strikes on quiet days. The butterfly is a pinning bet — and on days when the market cooperates, the payoff is 3:1.

Why it’s perfect for small accounts: $250 at risk. Not $500. You can take four shots per day and your worst-case daily loss is $1,000. Compare that to the iron condor where one bad day costs $500.

Trade 4: The Call Credit Spread

Mirror image of Trade 1, on the upside.

Sell the 10-delta call (~6000 strike) and buy the call $5 above it. Collect $0.55-0.75.

Less premium than the put spread. Always. That’s skew — the market charges more for downside protection than upside protection because crashes happen more violently than rallies. At the same 10-delta, the put is always more expensive than the call.

Use it when: You’re bearish or neutral. After a large rally (SPX rarely does back-to-back 1%+ up days). Or to balance a put credit spread into a piecemeal iron condor — sell the put spread in the morning, add the call spread after lunch if the market’s been flat.

Two Trades That Will Blow Up Your Account

People run these on $25K accounts all the time. They shouldn’t.

Trade 5: The Naked Short Put

“But the win rate is 80%!”

Look at the left panel. A naked put averages $95 per day. Beautiful equity curve going up and to the right — until it isn’t. Three blowup days: -$3,200, -$1,800, -$5,500. That $5,500 loss is 22% of a $25K account in a single session.

And that’s a good outcome. The naked put has no defined maximum loss. A flash crash, a gap down, an August 5th VIX spike — your $25K account could go negative. Not to zero. Negative. You can owe your broker money.

The margin requirement alone is disqualifying: $5,000+ for a single naked SPX put. That’s 20% of your account on one position with unlimited downside.

If you want to sell puts, sell put spreads. The $5-wide spread costs you $10 in premium but caps your loss at $500. That cap is what lets you trade every day and still be here next month.

Trade 6: The Long ATM Straddle

This is the “something big is about to happen” trade. At 0DTE, it’s a theta incinerator.

An ATM straddle costs $20-30 at 0DTE. SPX needs to move 0.5%+ AFTER you enter just to break even. On most days, SPX’s total daily range is less than 0.5%.

Right panel: 12% win rate. Steady bleed of $25/day. After a year: -$4,149. The straddle works at 30 DTE where theta is gentle and you have time for a move to develop. At 0DTE, theta is a chainsaw. It cuts through your position minute by minute, and unless SPX makes a violent intraday move, you’re paying premium to watch your trade decay to zero.

How Many Spreads Can You Actually Run?

At 2% risk per trade ($500), you run 1 spread per entry. At 3% risk ($750), still 1 spread but with room for wider wings. The sweet spot is 2-3%. At 5%+ you’re one bad streak from a blown account.

The rule that keeps you alive: max 2-3% of your account per trade. On $25K, that’s $500-750 at risk per entry.

A $5-wide SPX spread has a $500 max loss. So you run one spread per entry. Three entries across the day (10:30, 12:30, 2:30) = three spreads, $1,500 max daily risk, 6% of account.

“One spread? That only makes $75!” Yes. Three of them make $225 on a good day. That’s $1,125 per good week. The compounding does the rest.

What a Real Week Looks Like

This is the part nobody posts on social media.

Left: four wins, one loss, net +$345 (+1.4%). This is a good week. Right: two wins, three losses, net -$1,090 (-4.4%). This is a bad week. Both happen regularly. The bad week will happen roughly once a month.

The bad week is the test. Not whether the strategy works — the math says it does. Whether you can sit through three losing days in a row without changing your approach, increasing your size, or abandoning the system entirely.

If looking at -$1,090 on a Friday makes you want to double your contracts on Monday, this isn’t for you. The strategy needs 200+ trades to express its edge. You need to let it.

The 12-Month Reality Check

$25K to $29,811 in 12 months. +19.2%. Eight winning months out of twelve. Max drawdown $3,291. This is what “realistic” looks like.

Nobody’s screenshotting +19% for Reddit. There’s no 10-bagger, no “turned $500 into $50K” story. Just a $25K account that grew to almost $30K through 756 small trades, each one risking $500 to make $75.

Year 2 at the same rate on $30K: $5,700 in profit. Year 3: $6,800. By year 5 you’re north of $50K and running 5-6 spreads per day.

The path to $1.5M isn’t one trade. It’s 3,000 of them.

Five Rules, Non-Negotiable

1. Max 2% of account per trade. Survive losing streaks. Five losses in a row = -10%, not -50%. Break it and you blow up on the first bad week.

2. No trades in the first 15 minutes. Spreads are widest at open — you pay 30-50% more in friction. Death by a thousand cuts.

3. Close at 50% profit or let expire. Taking profits at 50% frees capital and avoids late-day gamma spikes. Otherwise you hold a winner that reverses at 3:30pm and goes from +$60 to -$400.

4. Daily stop: 2× your target. One bad day should cost two good days, not ten. A VIX spike catches you at full size and you lose a month of premium.

5. Check VIX before your first trade. VIX > 25 = widen strikes, reduce size. Sell 10-delta into VIX 30 without adjusting and wonder why your “safe” spread lost $500.

The hardest one for me is the daily stop. Two losing trades by 1pm and every instinct screams “one more to get back to even.” That’s how a $500 loss becomes a $1,500 loss. The stop exists for the days when your judgment is worst — which are always the days you’re losing.

I don’t care who you are — all of us are human, and it’s important to have a degree of self awareness.

The VIX Check

Before your first trade, check VIX. Every day. If you’ve read the Three-Engine 0DTE post, you know the full framework. The short version:

VIX < 14: Run 1-2 spreads instead of 3. Premium is thin. Don’t force it.

VIX 14-22: Full speed. This is your money zone.

VIX 22-30: Widen to 15-delta. Run 2 spreads. Tighten stops.

VIX > 30: One spread max, or sit out entirely. The best 0DTE trade on a VIX-35 day is no trade at all.

Where to Start

If this is your first 0DTE post:

1. Two-Engine 0DTE — the original framework

2. Three-Engine 0DTE — adding VIX regime sizing

3. This post — the specific trades for a $25K account

Paper trade for two weeks. Track every entry, every exit, every P&L. Then decide if you can stomach the bad weeks for the sake of the compounding.

Remember: Alpha is never guaranteed. And the backtest is a liar until proven otherwise.

The material presented in Math & Markets is for informational purposes only. It does not constitute investment or financial advice.

This is post 99 of my series — Building & Scaling Algorithmic Trading Strategies

Sequel to Two-Engine 0DTE Strategy, my most-read post. If you haven’t read it, start there.

August 5, 2024

VIX opened at 23. By noon it was 38. By 2pm it touched 65 — the highest intraday reading since March 2020. SPX dropped 3% in a single session.

If you were running the Two-Engine 0DTE strategy that day at full size — 150 spreads, 10-delta strikes, standard hedge ratio — every spread was underwater by late morning. Your 10-delta puts, which started 1.2% out of the money, were now deep in the money. Your convexity hedge helped, but it was sized for a VIX-25 event, not a VIX-65 event. The long puts you bought at VIX 16 the previous month had tripled in value, but they couldn’t offset 150 short spreads exploding simultaneously.

One day. Potentially months of premium erased.

This post is about the layer that would have cut that loss in half — or more.

Quick Recap: The Two-Engine Framework

In November, I reconstructed a strategy used by a trader who reportedly scaled a small account to $1.5M selling 0DTE SPX premium. The Two-Engine framework separated the strategy into its essential components:

Engine 1: Short 0DTE Premium. Sell 150-200 credit spreads per day on SPX same-day expiration options. Each spread collects a small premium ($0.30-0.80). Most expire worthless. The law of large numbers turns a 60-70% win rate into steady daily income.

Engine 2: Long-Dated Convexity. Buy 30-90 DTE out-of-the-money puts on SPX. These are your crash insurance. They bleed a small amount daily (the hedge cost) but explode in value on days like August 5. The two engines together create a risk-balanced system: Engine 1 makes money most days, Engine 2 saves you on the days that would otherwise end your account.

The Two-Engine framework works. Thousands of people read that post and many started exploring 0DTE premium selling.

But it has a blind spot that I didn't address.

The Blind Spot: Same Speed Through Every Neighborhood

The Two-Engine runs at the same speed regardless of the environment.

Same 150 contracts when VIX is 12 (calm, premium is paper-thin, barely worth the execution cost) as when VIX is 32 (stressed, premium is fat, but the tail will eat you alive).

Same 10-delta strikes in a market that’s been flat for three weeks as in a market that just dropped 2% overnight.

Same hedge ratio when OTM puts cost $0.50 as when they cost $4.00.

This is like driving 60 mph through a school zone and 60 mph on the highway. You’ll get away with it most days. The day you don’t is the day that defines your year.

The data makes the problem concrete:

Left: as VIX rises, the premium you collect per spread (green) grows roughly linearly — twice the vol, twice the premium. But the expected loss from tail events (red) grows as approximately VIX^1.8. Above VIX 28, the lines cross. You’re collecting premium that doesn’t compensate for the risk you’re taking. Right: expected daily P&L with constant sizing (orange, Two-Engine) vs. regime-scaled sizing (green, Three-Engine). The Two-Engine goes negative above VIX 28. The Three-Engine stays positive by scaling down.

That crossover point — around VIX 28-30 — is where the Two-Engine breaks. Not because the strategy is wrong, but because the sizing is wrong for the environment.

The Fix: Engine 3

The third engine is the simplest of the three. It’s a lookup table. Check VIX at market open. Set your parameters. Don’t deviate.

Engine 3 (yellow) sits on top and modulates both Engine 1 (how many contracts, what strikes) and Engine 2 (how much hedge). It’s the risk governor — the piece that keeps the other two engines from running off a cliff.

Engine 3 does four things:

1. Scales contract count. Fewer contracts when premium is thin (why trade 150 spreads at $0.15 each when bid-ask eats half of it?) and fewer when tail risk is elevated (why run full size into a VIX 35 environment?).

2. Widens strikes. A 10-delta put at VIX 15 is about 1.8% out of the money. At VIX 30, the same 10-delta put is only about 1.2% OTM — dangerously close. Engine 3 pushes to 15-delta and 20-delta strikes at high VIX to maintain the same effective distance from spot.

3. Adjusts frequency. At VIX < 14, premium per spread is so thin that the bid-ask spread absorbs 30-40% of it. Trading 150 spreads at those levels means paying $50+ in friction for $120 of premium. Engine 3 drops to 100-120 trades and skips any spread where friction exceeds 40%.

4. Scales the hedge. Engine 2’s convexity position runs at base when VIX is normal. At VIX > 22, it scales to 1.5×. At VIX > 30, it doubles to 2.5×. This is the piece that would have saved you on August 5 — twice the hedge when it matters most.

The Four Zones

VIX over two simulated years with four zones. Each has specific rules for everything: contract count, strike selection, spread width, hedge ratio, trade frequency, and stop levels. The Sweet Spot (green) is where you make your money. The Danger zone (red) is where you protect it.

Zone 1: Thin Premium (VIX < 14)

The market is dead calm. SPX is grinding higher on low volume. Premium per 0DTE spread: $0.15-0.30. After bid-ask, you’re collecting maybe $0.10-0.15 of real edge per trade.

The Two-Engine mistake: Running 150 spreads here and paying proportionally more in friction than you’re earning in premium.

Engine 3 rule: Drop to 60% of max contracts. Tighten entry criteria — skip any spread where the bid-ask exceeds 40% of premium. You’re trading less, but every trade you do take has a real edge.

Zone 2: Sweet Spot (VIX 14-22)

This is where you make your money. Premium is $0.50-0.85 per spread. Gamma is elevated but manageable at 10-delta. The hedge is cheap. The law of large numbers is working hard for you.

Engine 3 rule: Full speed. 150-200 spreads, 10-delta strikes, $5-wide spreads, standard stops. This is approximately 65% of trading days in a normal year.

Zone 3: Elevated (VIX 22-30)

Premium looks incredible. Your instinct says sell more. Your instinct is wrong.

At VIX 25, a 10-delta put is only about 1.2% out of the money. That felt like a comfortable distance at VIX 15 when it was 1.8%. The math has shifted underneath you.

Engine 3 rule: Drop to 70% of contracts. Widen to 15-delta strikes (restoring the ~1.8% buffer). Increase spread width to $7-10. Bump hedge ratio to 1.5×. Tighten stops to 1.5× daily target.

Zone 4: Danger (VIX > 30)

Every forum is posting screenshots of 0DTE premium. “Look at these spreads paying $2.50!” They’re paying $2.50 because there’s a meaningful chance they go to $10.

Engine 3 rule: 30% of max contracts. 20-delta strikes. $10-15 spread width. 2.5× hedge ratio. Stop at 1× daily target. You are here to survive, not to get rich.

What Happens When You Add the Third Engine

Two years of simulated 0DTE. Top: the Two-Engine (orange) has higher peaks in calm periods but deeper valleys during stress. The Three-Engine (green) compresses both — smaller peaks, much smaller valleys. Bottom: drawdown comparison. The worst Two-Engine drawdown is roughly twice the Three-Engine’s worst.

The Three-Engine gives up return in calm markets. It’s running at 60% size when VIX is below 14, so you’re leaving money on the table during the quiet grind-higher periods. That’s the cost.

The benefit: when VIX spikes — and it always spikes eventually — the Three-Engine is already at reduced size with wider strikes and a bigger hedge. The drawdown that takes the Two-Engine down 6% only takes the Three-Engine down 3%.

Over a full cycle of calm → spike → calm, the Three-Engine compounds better because it doesn’t dig as deep a hole to climb out of.

The Tail Gets Fatter Than You Think

This is the chart that should change how you think about high-VIX 0DTE — it should terrify you:

Daily P&L distributions by VIX regime. In the Sweet Spot (VIX 14-22): 73% win rate, average loss about 2× the average win. Manageable. In the Danger zone (VIX > 30): the win rate drops to 62% and the average loss explodes to nearly 6× the average win. The distribution isn’t just shifted — it’s a different shape. The left tail gets 5× fatter.

At VIX 15, when you lose, you lose about $0.65 per spread. At VIX 32, when you lose, you lose about $3.50 per spread. The premium went from $0.35 to $0.60 — not even a 2× increase. The loss went from $0.65 to $3.50 — a 5× increase.

Premium doubles. Risk quintuples. That’s the asymmetry Engine 3 is designed to manage.

The Adjustments Under the Hood

Left: the Two-Engine uses 10-delta strikes all the time (orange dashed). The Three-Engine widens to 15-delta above VIX 22 and 20-delta above VIX 30 (green). Wider strikes give you more room — the spread stays further from the money. Right: the Two-Engine runs a constant 1.0× hedge (orange dashed). The Three-Engine scales to 2.5× in the Danger zone (blue). You buy more crash insurance exactly when crashes become most likely.

The Cheat Sheet

Print this. Pin it. Don’t trade 0DTE without checking it.

Four zones, seven parameters. Check VIX at open, set your numbers, execute. The stop column is the most important — in the Danger zone, your daily stop is equal to your daily target. One losing day, you’re done for the session. That discipline is what keeps a bad day from becoming a catastrophic day.

The Uncomfortable Truth About 0DTE

The Two-Engine post got 86 subscribers — more than any other post I’ve written. That means a lot of people are interested in selling 0DTE premium. I want to be direct about the risks and caveats.

Even with three engines, 0DTE premium selling requires intraday monitoring, fast execution, deep understanding of gamma risk, and the ability to watch 30+ losing days per year without abandoning the system. The third engine doesn’t make it safe — it makes it less dangerous. Those are different things.

If you’re paper-trading the Two-Engine and it’s working, add the third engine before going live. The regime sizing is the difference between a strategy that survives its first VIX spike and one that doesn’t.

If you’re already live with the Two-Engine, the most important thing you can do today is check your current VIX zone and ask: am I sized correctly for this environment?

Remember: Alpha is never guaranteed. And the backtest is a liar until proven otherwise.

My math may have errors — please let me know if you find any.

And you should not be doing this unless you understand the risk.

The material presented in Math & Markets is for informational purposes only. It does not constitute investment or financial advice.

This is part 98 of my series — Building & Scaling Algorithmic Trading Strategies

Final part of the ML for Trading series. Part 1: Features. Part 2: XGBoost. Part 3: Validation.

The Race

Four posts ago, I asked: can a model do better than my hand-tuned rules? The answer required building a feature pipeline (Post 95), training and interpreting an XGBoost model (Post 96), and then subjecting it to honest validation that stripped away the overfitting (Post 97).

Now, let’s get to it.

Four approaches, same simulated data, same stress periods, same evaluation criteria:

Five years of simulated data with four stress periods (red shading). Gray: V6 base with no regime protection. Orange: 50 lines of if-else rules from Post 86. Blue: validated XGBoost from Post 97. Green: the hybrid (ML in calm markets, rules in spikes). The hybrid edges out XGBoost on total return while matching it on Sharpe and drawdown.

The numbers:

                  Sharpe    Max DD    Ann. Return
V6 base:          0.98      -40%       ~21%
If-else rules:    1.27      -23%       ~24%
XGBoost:          1.35      -20%       ~24%
Hybrid:           1.35      -20%       ~25%

The XGBoost beats the if-else rules. The hybrid matches the XGBoost on risk metrics and slightly improves total return. But the gap between if-else and XGBoost is smaller than the gap between V6 base and if-else.

The first 50 lines of protection code did most of the work.

Where Each Approach Wins

The aggregate numbers hide regime-specific performance that matters for deployment:

OOS Sharpe by VIX regime for each approach. The XGBoost wins in Calm and Elevated regimes (where it has abundant training data). The if-else rules win in Spike regimes (where the model has too few examples). The hybrid takes the best of both: ML performance in normal markets, rules-based safety in tail events.

This is the key finding of the entire series: ML and rules are complements, not substitutes. The XGBoost discovers non-linear patterns in normal markets (the VIX reversal from Post 96, the GEX × spread interaction) that if-else rules can’t express. But in rare events — VIX > 35, which happens roughly 5% of the time — the model doesn’t have enough training examples to generalize. The simple rule (”go to minimum allocation”) outperforms the model’s confused prediction.

The hybrid captures this insight by routing decisions through a regime check: if VIX > 30, use rules; otherwise, use the model.

The Full Cost

Sharpe isn’t the only metric. Every approach has operational costs that don’t show up in the backtest:

The if-else rules cost essentially nothing to maintain. They’re 50 lines of Python that I wrote once and haven’t touched. The XGBoost requires a feature pipeline (11 data feeds), quarterly retraining, SHAP drift monitoring, and 10-30 minutes of investigation per unusual trade. The hybrid sits between — it needs the ML pipeline but uses rules as a safety net, which reduces the monitoring burden.

I can’t highlight this enough — ML sounds tempting but the reality is that the overhead and complexity of ongoing maintenance and pipeline is difficult to manage.

The Complexity-Adjusted View

Here’s the chart that made the decision for me:

Sharpe ratio (bars) vs. hours per month to maintain (yellow line). The XGBoost Raw bar is struck through — that was the 0.71 that Post 97 proved wasn’t real. The validated XGBoost and hybrid have similar Sharpe, but the hybrid requires half the maintenance hours because the rules portion needs no monitoring.

The if-else rules deliver 0.50 Sharpe for 0.5 hours per month of effort. The hybrid delivers 0.56 Sharpe for 4 hours per month. That’s +0.06 Sharpe for 3.5 additional hours.

At a $500K portfolio, 0.06 Sharpe is roughly $3,000 per year of additional risk-adjusted return. For 42 hours of annual work, that’s $71/hour. Not nothing — but not obviously worth it either.

At a $2M portfolio, the same 0.06 Sharpe is $12,000/year, or $286/hour. Now it’s clearly worth it. Scale determines the answer for you!

What Actually Gets Deployed

The final V6 architecture has four layers:

Layer 1: Data + Features. Eleven features computed daily from six data feeds (VIX, price, spreads, GEX, yield curve, credit spreads). All features are stationary (z-scored or binary). This is the pipeline from Post 95.

Layer 2: Regime Router. A simple VIX threshold check. If VIX > 30, route to the rules path. If VIX ≤ 30, route to the ML path. This is the hybrid insight from Post 97’s regime stability analysis.

Layer 3a: ML Allocation (calm/elevated regimes). The XGBoost model outputs a continuous allocation between 0.1× and 1.0×. This captures the non-linear patterns — the VIX reversal, the interaction effects, the gradual re-entry after stress — that rules can’t express.

Layer 3b: Rules Allocation (spike regimes). The if-else rules from Post 86 output a binary allocation: 0.2× (crisis) or 1.0× (all clear). Simple, robust, doesn’t need training data for rare events.

Layer 4: Monitoring. SHAP drift detection (are the feature importances shifting?), OOS Sharpe tracking (is the model still working?), CUSUM on residuals (has the relationship changed?), and a quarterly retrain trigger.

The 18-Post Journey

The honest Sharpe progression across 18 posts and 5 series. The green line (validated Sharpe) rises gradually from 0.33 to 0.56. The orange line shows the reported Sharpe, which spiked to 0.71 at Post 96 before validation crashed it to 0.41 at Post 97. The red-shaded zone between the lines is the overfitting — the part that wasn’t real.

This chart is the most important one in the series. Every series across Posts 80-98 made V6 better — but the improvements were smaller and harder to achieve with each layer:

Posts 80-82 (Strategy Decay): +0.05 Sharpe from CUSUM monitoring. Almost free.

Posts 83-86 (Microstructure): +0.12 Sharpe from GEX and spread conditioning. The biggest single improvement. Worth every line of code.

Posts 87-89 (Carry Trade): +0.03 Sharpe from carry optimization. Real but small.

Posts 90-93 (Synthetic Replication): +0.00 Sharpe. The options overlay was theoretically sound but added complexity without improving the validated result. I implemented the tail hedge in paper mode only.

Posts 95-98 (ML for Trading): +0.06 Sharpe from the hybrid approach — but only after honest validation stripped 0.30 of apparent Sharpe away as overfitting.

The total improvement: 0.33 → 0.56, or +0.23 Sharpe across 18 posts. The microstructure layer (4 posts) contributed more than half of that.

The Decision Matrix

The question everyone asks: should I add ML to my strategy?

The last row is the one I care about most. If you’re reading this series to learn quantitative methods, build everything. Train the XGBoost, run the SHAP analysis, implement the walk-forward validation, and compute the deflated Sharpe. The understanding you develop from building and breaking these tools is worth more than any Sharpe improvement.

But if you’re deploying real capital, the honest answer is that 50 lines of if-else rules, carefully chosen and rigorously monitored, get you 90% of the way there. The ML layer adds the last 10% — at 4× the operational cost and 10x the complexity.

What I Learned

Four posts, four lessons:

The model doesn’t matter — the inputs do (Post 95). I spent 80% of the ML work on feature engineering and 20% on the model. That ratio was correct. The model amplifies signal; it can’t create it.

Trees beat neural nets for this problem (Post 96). Not because trees are better in general — because financial data is regime-based, sample-limited, noisy, and needs to be interpretable. Trees match all four constraints. Neural nets match one.

Honest validation destroys most backtests (Post 97). Our XGBoost went from 0.71 to 0.41 after walk-forward validation, purged CV, and deflated Sharpe adjustment. If that haircut surprises you, you haven’t validated enough strategies yet.

The hybrid is better than either extreme (Post 98). ML where it has data, rules where it doesn’t. The model that admits its limitations outperforms the one that pretends it doesn’t have any.

This concludes the ML for Trading series (Posts 95-98) and the full arc that began at Post 80. Nineteen posts, five series, one strategy: V6 went from a simple TQQQ/TLT allocator to a layered system with regime detection, microstructure conditioning, carry optimization, and a validated ML overlay.

The Sharpe went from 0.33 to 0.56. Not through one clever insight, but through the accumulation of small, honest improvements — each one tested, validated, and documented in public.

Remember: Alpha is never guaranteed. And the backtest is a liar until proven otherwise.

The material presented in Math & Markets is for informational purposes only. It does not constitute investment or financial advice.

This is part 97 of my series — Building & Scaling Algorithmic Trading Strategies

Part 3 of the ML for Trading series. Part 1: Feature engineering. Part 2: XGBoost and SHAP.

Every Good Backtest Starts as a Lie

In Part 96, I reported an XGBoost model with a 0.71 Sharpe ratio. That number is a lie — well, not completely true anyway.

You see, the calculation is correct on the data I used. But it’s a lie because I tested 20 features, 4 model types, multiple hyperparameter configurations, and two interaction engineering approaches before arriving at that number. So conservatively, I evaluated ~80 strategy variations on the same dataset.

This is the multiple testing problem, and it is the most expensive bug in quantitative finance. Every blown account, every fund that looked great on paper and lost money live, every strategy that “worked in the backtest” — almost all of them trace back to this single error: mistaking a lucky variation for a real edge.

This post is about how to not make that mistake.

Problem 1: We Test 80 Things and Reported the Best One

Left: 80 strategy variations, all with ZERO true alpha, simulated under the null hypothesis. Six of them show Sharpe > 0.5 by pure chance. If you pick the best one and report it, you have a “great” backtest. Right: the probability of finding at least one “significant” result. At 80 tests with a 5% threshold, there’s a 98.3% chance of discovering something “significant” — even when nothing is real.

The math is simple and brutal. If you test one strategy and it has a p-value of 0.05, there’s a 5% chance it’s noise. If you test 80 strategies and report the best one, the probability that your best result is noise is:

P(at least one false positive) = 1 - (1 - 0.05)^80 = 98.3%

You are almost certain to find something “significant.” That doesn’t mean it works.

What This Means for Our XGBoost

I tested 20 features (Post 95). I tried 4 model types (Post 96). I tuned hyperparameters across maybe 10 configurations. That’s roughly 20 × 4 × 10 = 800 implicit tests, not 80. I was conservative earlier.

The observed 0.71 Sharpe needs to survive scrutiny that accounts for all of these trials. If it doesn’t, it’s noise — regardless of how good the SHAP plots look.

Test 1: Walk-Forward Validation

The first and most important test: does the model work on data it has never seen, in temporal order?

Top: the WRONG way — random train/test splits. Test data is scattered between training data, so the model has seen future information. Bottom: the RIGHT way — walk-forward validation. Train on the first year, test on the next quarter. Slide forward, retrain, test again. The model never sees the future.

Random train/test splits are the default in scikit-learn. They are wrong for time series.

Why, you ask? Well let me tell you!

Your features include 63-day rolling z-scores. If day 300 is in the test set and day 337 is in the training set, the model has effectively seen information from the test period — because the z-score on day 337 was computed using days 274-337, which overlaps with the test set.

I have myself failed with exactly this. My model returned an 1080% RoI with a Sharpe of 4.0! Was I the next Jim Simmons? Hell no. I was simply an enthusiastic… moron.

Walk-forward validation eliminates this. The train set is always before the test set. No overlap, no leakage, no cheating.

Our Results

I ran 12 walk-forward windows (1-year train, 3-month test) on the XGBoost model:

Top: Sharpe ratio for each walk-forward window. Mean OOS Sharpe is 0.48 — down from the reported 0.71. Two windows (W3 and W7) are negative. Bottom: cumulative OOS P&L. The edge is real but lumpy — two of 12 quarters lost money.

The reported Sharpe of 0.71 just became 0.48. That’s a 32% haircut from walk-forward alone. But it’s still positive and consistent across most windows — the model is learning something real, just less than the in-sample number suggested.

The two negative windows (W3 and W7) are important. They correspond to periods where the market regime shifted in ways the model hadn’t seen in its training window. W3 was a sharp VIX spike followed by an immediate recovery — the model reduced allocation and missed the bounce. W7 was an extended low-vol period where the model kept partial allocation when it should have been fully invested.

These are the failure modes you need to know about before deploying, not after.

Test 2: Purged Cross-Validation

Walk-forward is necessary but not sufficient. Standard k-fold cross-validation has a subtler problem:

Left: standard k-fold. Fold boundaries create leakage zones (red) where features computed from one fold’s data bleed into the adjacent fold. Right: purged CV with embargo. A 21-day purge window removes data before each test fold, and a 10-day embargo removes data after. No feature computation spans the boundary.

The purge window (21 days in our case) must be at least as long as the longest lookback in your features. Our features include a 63-day z-score, so technically the purge should be 63 days. I used 21 as a compromise — the z-score’s sensitivity to any single day is small after the first few days, so a 21-day purge captures most of the leakage.

The embargo (10 days) prevents the model from learning the immediate post-test-fold dynamics, which would give it an unfair advantage on the test fold’s final days.

Our Results

Purged CV Sharpe: 0.44 — an additional -0.04 from the walk-forward result. The leakage in standard CV was inflating our result by about 4 basis points of Sharpe. Small but not zero.

Test 3: The Deflated Sharpe Ratio

The deflated Sharpe ratio (Bailey and de Prado, 2014) answers the question: “Given that I tested N variations and observed this Sharpe, what’s the probability it’s real?”

The intuition: if you flip 80 coins and report the one with the most heads, you haven’t found a biased coin — you’ve found the luckiest fair coin. The deflated Sharpe adjusts for this by subtracting the expected maximum Sharpe from N trials under the null hypothesis.

Left: the deflated Sharpe as a function of trials. The observed Sharpe (0.71, dashed orange) stays constant. The deflated Sharpe (green) drops as you account for more trials. At 80 trials, the DSR is 0.41 — real, but barely half of the reported number. Right: the waterfall from reported to reality. Each validation step strips away more noise: 0.71 → 0.56 (walk-forward) → 0.48 (purged CV) → 0.41 (deflated SR).

The formula:

# Deflated Sharpe Ratio (simplified)
import numpy as np
from scipy.stats import norm

def deflated_sharpe(observed_sr, n_trials, n_observations, sr_std=None):
    """
    observed_sr: the Sharpe you measured
    n_trials: how many strategies/variations you tested
    n_observations: number of data points (days)
    """
    if sr_std is None:
        sr_std = np.sqrt((1 + 0.5 * observed_sr**2) / (n_observations / 252))
    
    # Expected max Sharpe from n_trials under null
    expected_max = sr_std * np.sqrt(2 * np.log(n_trials))
    
    # Deflated = observed minus expected noise contribution
    dsr = observed_sr - expected_max
    
    return dsr

# Our case
dsr = deflated_sharpe(0.71, n_trials=80, n_observations=756)

The Uncomfortable Number

Our XGBoost’s deflated Sharpe, accounting for 80 trials on 756 observations, is approximately 0.41. That’s the honest number — the one that accounts for all the strategies we tested and didn’t report.

A DSR of 0.41 is still positive, which means the edge is likely real. But it’s a long way from the 0.71 we started with.

Test 4: Regime Stability

The final test: does the model work in all market regimes, or did it only learn one environment?

I stratified the OOS results by VIX regime:

VIX Regime      | OOS Sharpe | N Windows | Verdict
────────────────|────────────|───────────|────────
Calm (< 15)     |    0.35    |     4     | ✓ Positive
Elevated (15-25)|    0.62    |     5     | ✓ Strong
Stressed (25-35)|    0.28    |     2     | ✓ Marginal
Spike (> 35)    |   -0.15    |     1     | ✗ Negative

Three of four regimes are positive — acceptable. The model fails in the Spike regime, which makes sense: VIX > 35 events are rare in the training data (roughly 5% of days), so the model has too few examples to learn the dynamics. In the Spike regime, the simple if-else rule (”go to minimum allocation”) actually outperforms the ML model.

This is the most actionable finding: use the ML model for Calm and Elevated regimes, fall back to if-else rules for Spike regimes. The hybrid approach — ML where it has enough data to learn, rules where it doesn’t — is likely better than either approach alone.

The 4-Test Framework

Every strategy must pass all four tests. Failing any single test is disqualifying — not because the strategy is definitely worthless, but because you can’t distinguish it from noise.

Our XGBoost passed all four, but just barely on the deflated Sharpe. The honest reported Sharpe for this model is not 0.71. It’s somewhere between 0.41 (DSR-adjusted) and 0.48 (walk-forward), depending on how conservative you want to be.

What This Looks Like in Practice

Left: the in-sample backtest. Sharpe 1.84, smooth upward trajectory, -11% max drawdown. “This strategy is amazing.” Right: the walk-forward OOS reality. Sharpe 1.06, choppy with deep drawdowns, -26% max DD. “This strategy is real — barely.” The gap between these two curves is the cost of overfitting.

This is what honest validation does to every strategy. In my experience, rightfully or not, if it doesn’t look painful, you probably haven’t done it right.

The Takeaways (sounds like a movie…)

1. Track your trials. Every feature you test, every model you evaluate, every hyperparameter you tune is a trial. Write them down. The deflated Sharpe requires this number, and most people wildly undercount it.

2. Walk-forward is mandatory. If you haven’t run walk-forward validation with proper temporal ordering, your Sharpe ratio is meaningless. Not “probably inflated” — meaningless. You can’t know if it’s signal or noise.

3. Report the DSR, not the Sharpe. When someone tells you their strategy has a 1.5 Sharpe, the correct response is: “Over how many observations, after how many trials?” A 1.5 Sharpe after 5 trials on 5,000 days is real. A 1.5 Sharpe after 500 trials on 500 days is noise.

4. Expect a 30-50% haircut. If your in-sample Sharpe is 1.0, your honest OOS Sharpe will be 0.5-0.7 after proper validation. If you can’t accept that haircut, you’re in the wrong business. The alternative — deploying the in-sample number — is how you lose money.

5. The hybrid is better than either extreme. Use ML where it has enough data (normal markets). Use rules where it doesn’t (tail events). The model that admits its own limitations outperforms the one that doesn’t.

The Running Score

Our XGBoost, honestly:
  Reported Sharpe:       0.71
  After walk-forward:    0.56  (-21%)
  After purged CV:       0.48  (-32%)
  After deflated SR:     0.41  (-42%)
  
Verdict: real, but modest. +0.08 over the if-else rules
after accounting for everything.

Is +0.08 Sharpe worth the complexity?
Post 98 will answer.

Up Next

Post 98: The V6 ML Layer — The final verdict. This is where we go head-to-head: 50 lines of if-else vs. the validated XGBoost model. Who will win?

Accounting for implementation cost, operational complexity, and the failure modes we identified here. The honest answer on whether ML belongs in V6 or not.

Remember: Alpha is never guaranteed. And the backtest is a liar until proven otherwise.

These posts are about methodology, not recommendations. If you find errors in my math, let me know — I’ve built an entire series around discovering my own mistakes, so one more won’t hurt.

The material presented in Math & Markets is for informational purposes only. It does not constitute investment or financial advice.

Tool 1: Feature Engineering Explorer

ml-feature-explorer.mathandmarkets.com

This is the companion to Post 95. It lets you do what I did in that post — test 20 candidate features and figure out which ones are signal and which ones are noise — but interactively.

The Feature Explorer tab shows all 20 features ranked by Information Coefficient. Click any feature to select or deselect it. The scoreboard at the top updates in real-time: how many features you’ve selected, how many are above the noise floor (IC > 0.03), your portfolio’s combined IC, and how many redundancy warnings you’ve triggered. Hover over any feature to see what it measures and why it matters.

The thing to watch: redundancy warnings. If you select VIX z-score, Realized vol z, AND VIX term structure, you’ll get a warning that you have three volatility features with high inter-correlation. The model can’t distinguish their individual contributions. Drop one.

The Stationarity Lab tab shows one feature (VIX) rendered four different ways: raw level, z-score, percentile rank, and rate of change. Toggle between them and notice that the raw level drifts — its mean shifts over time. The other three are stationary. The Python code for each transformation is shown alongside so you can apply the same logic to your own features.

If you take one thing from this tab: never feed a raw level into a model.

The IC Decay tab shows your selected features losing predictive power over time. Each feature decays at a different rate — VIX z-score holds its IC for roughly 8 years, while OFI proxy drops to the noise floor in about 3. This tab tells you how often your model needs retraining based on the features you’ve chosen.

The Model Playground tab is where you feel overfitting with your hands. Three sliders: number of trees, max depth, and learning rate. As you increase any of them, the in-sample Sharpe climbs — it can hit 1.0, 1.5, even 2.0+. The out-of-sample Sharpe peaks around 200 trees / depth 4 / learning rate 0.05, then collapses. The bar chart shows the gap at every tree count. The verdict text changes from green (”healthy”) to yellow (”moderate overfit”) to red (”your model has memorized the training data”).

Crank the depth to 15 and watch the IS Sharpe hit 2.0+ while OOS drops below 0.3. That’s the chart that should be tattooed on every ML practitioner’s forearm.

Tool 2: SHAP Explorer

ml-shap-explorer.mathandmarkets.com

This is the companion to Post 96. It shows what the XGBoost model actually learned — not just which features are important (the bar chart) but how each feature affects the model’s output (the dependence plots).

The sidebar ranks all 11 features by mean |SHAP value|. Click any feature to load its dependence plot in the main panel.

The dependence scatter shows the feature’s value on the x-axis and its SHAP contribution on the y-axis. Each dot is one day. The shape of the cloud tells you the relationship — and the key discovery is that many relationships are non-linear.

Start with VIX z-score. You’ll see a shape that isn’t a straight line. Below zero, SHAP is mildly positive (buy the calm). Between 0 and 2.5, it’s strongly negative (reduce allocation). But above 2.5 — the extreme tail — it bends back up. The model discovered that extreme VIX readings predict mean-reversion, not continuation. That’s the signal my if-else rules missed for 94 posts.

Toggle the GEX split button in the top right. This colors each dot by whether GEX was positive (green) or negative (red) on that day. The two populations separate — negative GEX makes every VIX level worse. The model treats VIX = 2.0 with negative GEX the same as VIX = 2.5 with positive GEX. That’s an interaction effect that linear IC analysis from Post 95 couldn’t detect.

The Spread z-score dependence plot is another one worth examining with GEX split on. Wide spreads with positive GEX have almost no effect — dealer hedging absorbs the microstructure stress. Wide spreads with negative GEX are strongly negative. The interaction is the signal, not the individual feature.

Tool 3: Decision Tree Builder

ml-tree-builder.mathandmarkets.com

This one is a game. Can you build a hand-tuned decision tree that beats XGBoost?

The left panel is your rule builder. Click “+ Add Rule” to create a split. Each rule has four components: a feature (VIX z-score, GEX regime, momentum, etc.), a direction (greater than or less than/equal), a threshold, and an allocation (0-100%). Rules are evaluated top to bottom — the first matching rule wins. Days that don’t match any rule get full allocation.

The right panel updates live. You’ll see a heatmap strip showing your allocation over time (green = full, red = minimum), an equity curve comparing your tree to the V6 base, and a results table benchmarking you against XGBoost (Sharpe 0.56) and the if-else rules from Post 86 (Sharpe 0.50).

To get started: try adding one rule — VIX z-score > 1.5, allocation 20%. This single rule captures the three stress periods and should push your Sharpe from the base level up toward 0.4-0.5. Then add a second rule for GEX regime <= 0, allocation 50%. This catches days where dealer positioning amplifies moves even when VIX isn’t extreme.

The verdict bar at the bottom tells you where you stand. If you beat XGBoost with fewer rules than it has trees, the verdict will say so — and that’s the point. Sometimes domain expertise in 3 rules beats 200 trees and 240,000 splits.

The hint if you get stuck: the stress periods are around days 130-170, 370-405, and 570-615. The model catches them by combining VIX z-score, momentum direction, and spread width. Try adding a rule that captures negative momentum during high VIX — that’s the regime the model weights most heavily.

What’s Coming Next

These three tools cover Posts 95-96. The next two posts — Post 97 (The Overfitting Minefield) and Post 98 (The V6 ML Layer) — will bring additional interactive components. The walk-forward validation visualizer is in development, and the final post will include a head-to-head simulator where you can compare the ML layer, the if-else rules, and the V6 base across different market regimes.

All tools are at ml-tools-hub.mathandmarkets.com.

Not investment advice. These are simply tools to experiment and play with. Do your own due diligence.

This is part 96 of my series — Building & Scaling Algorithmic Trading Strategies

Part 2 of the ML for Trading series. Part 1: Feature engineering — 20 features, only 7 survive.

The Problem a Linear Model Can’t Solve

In Part 95, I built an 11-feature input matrix: VIX z-score, VIX term structure, GEX regime, spread z-score, and seven others — all stationary, non-redundant, with domain-driven interactions.

Now: what model should consume these features?

The instinct is to reach for the deepest tool in the box. Transformers. LSTMs. Attention mechanisms. But this problem doesn’t need depth. It needs non-linearity at the split level — the ability to discover that VIX > 25 with negative momentum means something completely different from VIX > 25 with positive momentum.

Left: the actual regime structure in simulated data. Returns depend on VIX × momentum interactions — high VIX with negative momentum crashes, high VIX with positive momentum bounces. The yellow dashed lines are the decision boundaries a tree finds automatically. Right: a linear regression draws a straight line through this mess and misses the regime structure entirely. Trees capture the step-function reality.

This is the core argument for tree models in trading: markets have regimes, not gradients. The relationship between VIX and returns isn’t “higher VIX → proportionally lower returns.” It’s “VIX below 18 = one regime, VIX 18-25 = another, VIX above 25 = a third.” Trees find these thresholds automatically.

What the Tree Learns

Here’s a simplified decision tree trained on V6’s feature matrix:

A single tree from the ensemble, pruned to depth 3 for readability. The root split is on VIX z-score (the strongest feature from Part 95). The left branch handles calm markets, splitting on GEX regime and spread z-score to determine allocation between 0.6× and 1.0×. The right branch handles stress, splitting on momentum direction to distinguish recovery bounces (0.5×) from active crashes (0.2×).

Compare this to the if-else rules I wrote by hand in Post 86 (the microstructure layer):

# My hand-tuned rules (50 lines)
if gex_positive and spread_z < 1.0:
    allocation = 1.0
elif vix > 25 and momentum < 0:
    allocation = 0.3
elif vix > 25 and momentum > 0:
    allocation = 0.5
else:
    allocation = 0.7

The tree discovers approximately the same structure — but with two advantages:

1. The thresholds are optimized. I picked VIX > 25 and spread_z < 1.0 based on intuition. The tree picks VIX z-score > 1.5 (which corresponds to different absolute VIX levels depending on the recent regime) and spread z > 1.0. The tree’s thresholds are fit to the data; mine were fit to my gut.

2. The interactions are automatic. I manually coded the VIX × momentum interaction because I knew it mattered. The tree finds GEX × spread as an additional interaction that I never tested. It also discovers that extreme VIX (z > 3) actually reverses — something I missed entirely.

SHAP: What the Model Actually Uses

The tree has 1,200 estimators, each with up to 200 splits. That’s 240,000 decision points. What is all that complexity doing?

SHAP (SHapley Additive exPlanations) decomposes each prediction into the contribution of each feature. Instead of a black box that says “allocate 0.3×”, SHAP says “VIX z-score pushes the allocation down by 0.15, GEX pushes it down by 0.08, but momentum pushes it up by 0.05, net = 0.3×.”

Mean absolute SHAP values across the test set. VIX z-score dominates (no surprise — it’s the strongest univariate predictor). But the VIX×Momentum interaction ranks third, ahead of most base features. This is the ML model discovering a non-linear relationship that IC analysis from Part 95 couldn’t detect. Top 5 features account for ~80% of the model’s output.

The standout finding: interaction features rank higher than most base features. The VIX×Momentum interaction (which I engineered manually in Part 95) is the third most important feature. The GEX×Spread interaction is sixth. The model confirms that these interactions carry real signal — not just artifacts of my feature engineering choices.

The Non-Linear Discoveries

SHAP dependence plots reveal what the model learned that my if-else rules didn’t:

Left: VIX z-score dependence, colored by GEX regime. The relationship is NOT monotonic. Below z = 0 (calm), the effect is mildly positive (buy the dip). Between 0 and 2.5 (stress), it’s strongly negative (reduce allocation). Above 2.5 (extreme stress)... the model discovers that extreme VIX readings actually reverse. The curve bends back up. This is a mean-reversion signal in the tails that a linear model or a simple if-else threshold would never find. Right: the Spread × GEX interaction. When GEX is negative (red) AND spreads are wide, the model aggressively reduces. When GEX is positive (green), wide spreads have almost no effect — dealer hedging absorbs the microstructure stress.

The extreme-VIX reversal is the most interesting discovery. My hand-tuned rules treated VIX > 25 as uniformly bad. The tree says: “VIX at 25-35 is bad. VIX at 40+ means the crash is almost over — start buying back in.” This matches the empirical research on VIX mean-reversion from Post 80 (strategy decay half-lives), but I never incorporated it into V6’s rules because I didn’t trust myself to time the reversal. The model doesn’t trust itself either — it only gives a partial increase, from 0.2× to maybe 0.35× — but it’s an edge I was leaving on the table.

Model Selection: Why XGBoost Wins

I tested four models on the same feature matrix with the same walk-forward validation:

Left: four models compared on OOS Sharpe, direction accuracy, overfit gap, and training time. XGBoost wins on Sharpe (0.71) with a moderate overfit gap (0.08). Random Forest is close behind (0.62) with a larger overfit gap (0.12). Logistic regression is simplest but misses the non-linearity. The neural net overfits badly (0.25 overfit gap) and is 10× slower. Right: radar chart showing why trees dominate for this problem — adequate training samples, moderate feature count, non-linear relationships, high noise, and critical need for interpretability.

Why neural nets fail here:

Too few samples. V6 has roughly 2,500 days of data. After walk-forward splits, each training window is 500-800 days. Neural nets need 10,000+ samples to generalize. Trees are sample-efficient — they can find meaningful splits with hundreds of observations.

Too much noise. Financial returns have a signal-to-noise ratio of roughly 0.05 (the IC from Part 95). Neural nets overfit noise at low SNR because they have too many parameters. Trees with depth constraints can’t overfit as easily because the number of possible splits is bounded.

Interpretability. When the model says “reduce to 0.2×”, I need to know why. SHAP on a tree ensemble is computationally exact. SHAP on a neural net is approximate and expensive. If I can’t explain the model’s decision, I won’t trade on it.

The Regime Map

Putting it all together: the XGBoost model generates a daily allocation prediction based on the 11 features, and V6 uses that prediction instead of the hand-tuned rules:

Three panels. Top: price action with stress periods shaded. Middle: the XGBoost’s allocation prediction as a heatmap — green = full allocation, red = minimum. The model goes red 5-8 days before the worst of each drawdown and gradually re-enters (yellow → green) after the stress subsides. Bottom: cumulative P&L. XGBoost improves the Sharpe from 0.33 to 0.56 and cuts max drawdown from -34% to -17%.

The heatmap in the middle panel is the key visualization. It shows the model’s regime classification in real-time — not as a binary on/off but as a continuous allocation between 0.1× and 1.0×. The gradual re-entry after stress (the yellow-to-green transition) is something my hand-tuned rules didn’t do well — I used binary switches (in or out) rather than continuous scaling.

The Hyperparameter Trap

Before you get excited: most of the Sharpe improvement is fragile. It depends heavily on hyperparameter choices that I made after looking at the out-of-sample results.

Left: number of trees vs. Sharpe. In-sample Sharpe climbs to 1.95 with 5,000 trees. Out-of-sample peaks at 200 trees (0.71) then declines to 0.42 with 5,000 trees. The widening gap is pure overfitting. Right: max tree depth shows the same pattern. Depth 4 is optimal OOS (0.71). Depth 15 gives an IS Sharpe of 2.20 and an OOS Sharpe of 0.15.

This is the central problem of ML for trading: the model that looks best in-sample is the worst out-of-sample.

A researcher who only reported the depth-15 IS Sharpe of 2.20 would have a “stunning” result. The actual OOS Sharpe of 0.15 tells you it’s garbage. The only honest approach is walk-forward validation with strict separation between parameter tuning and performance evaluation — which is what Part 97 (the overfitting minefield) will cover in depth.

For now, the practical takeaway: shallow trees, few estimators, heavy regularization. My final XGBoost configuration:

model = XGBRegressor(
    n_estimators=200,     # not 1,200 — OOS peaks here
    max_depth=4,          # shallow trees generalize better
    learning_rate=0.05,   # slow learning prevents overfitting
    subsample=0.7,        # row sampling (bagging)
    colsample_bytree=0.7, # column sampling (feature bagging)
    reg_alpha=1.0,        # L1 regularization
    reg_lambda=5.0,       # L2 regularization (heavy)
    min_child_weight=50,  # minimum samples per leaf
)

Every parameter choice limits the model’s ability to memorize the training data. The resulting model is weaker in-sample but more honest out-of-sample.

The Uncomfortable Question

The XGBoost improves V6’s Sharpe from 0.33 to 0.56. That’s meaningful. But the 50-line microstructure layer from Post 86 improved it from roughly 0.33 to roughly 0.50 (varying by simulation).

The marginal improvement of ML over hand-tuned rules is about +0.06 Sharpe. For that, you get:

Additional complexity:
  - Model training pipeline (data prep, validation, tuning)
  - Feature maintenance (11 features, daily updates)
  - Periodic retraining (quarterly, per Part 95's IC decay)
  - Monitoring for model drift
  - SHAP analysis for each trade decision

versus:

50 lines of if-else that anyone can read, modify, and debug

Is +0.06 Sharpe worth that operational burden? Part 98 will give the definitive answer. But I’ll preview my current thinking: it depends on your scale. At $100K, the if-else rules win on simplicity. At $10M+, the ML layer starts to justify its overhead.

Up Next

Part 97: The Overfitting Minefield — Walk-forward validation, combinatorial purged cross-validation, the deflated Sharpe ratio, and a rigorous framework for answering “is this result real or noise?”

Remember: Alpha is never guaranteed. And the backtest is a liar until proven otherwise.

These posts are about methodology, not recommendations. If you find errors in my math, let me know — I’ve built an entire series around discovering my own mistakes, so one more won’t hurt.

The material presented in Math & Markets is for informational purposes only. It does not constitute investment or financial advice.

This is part 95 of my series — Building & Scaling Algorithmic Trading Strategies

This begins a 4-part series on machine learning for trading. Part 1: feature engineering. Part 2: tree models for regime classification. Part 3: the overfitting minefield. Part 4: does the ML layer actually help V6?

🔧 Interactive tool: ML Feature Engineering Explorer — select from all 20 candidate features, check which ones beat the noise floor, watch their predictive power decay over time, and see the Python transforms for making raw data ML-safe.

The Dirty Secret of ML for Trading

Here’s what nobody tells you in the scikit-learn tutorials: the model doesn’t matter.

Not at first. Not until you’ve spent 80% of your time on the input. A random forest trained on good features will crush a transformer trained on garbage. A logistic regression with the right 8 features will beat a neural network with 200 noisy ones. The model learns patterns in whatever you feed it. If you feed it noise, it learns noise.

This post is about the 80% — feature engineering. Specifically: how to convert 93 posts of trading signals, macroeconomic indicators, and microstructure data into a clean, stationary, non-redundant feature set that a model can actually learn from.

The Feature Taxonomy

Over the last 15 posts (Parts 80-94), we built signals across five categories. Here they all are:

Twenty candidate features organized by category. Momentum/trend features capture directional persistence. Volatility/regime features capture market stress. Microstructure features capture order flow and dealer positioning. Carry/macro features capture the yield environment. Cross-asset features capture inter-market relationships.

Each of these features was developed and discussed in a specific post. They’re not random — they have theoretical grounding and empirical motivation. But that doesn’t mean they all belong in an ML model. Many are redundant, some are non-stationary, and a few might be pure noise in a multivariate context.

The job of feature engineering is to separate the signal from the noise, the unique from the redundant, and the stationary from the drifting.

Problem 1: Redundancy

The first thing you notice when you stack these features into a correlation matrix:

Pairwise correlations across 12 features. VIX and 21-day realized vol are 70% correlated — they’re measuring the same thing. 50-day and 200-day momentum have 50% overlap. Credit spreads and VIX are 40% correlated. Feeding all of these into a model gives you multicollinearity — the model can’t separate the contribution of each feature.

The fix is straightforward: for each pair with |r| > 0.7, drop one. The decision of which to drop is domain-driven:

Between VIX and realized vol, keep VIX — it’s forward-looking (implied) while RV is backward-looking (realized). The forward-looking version is more useful for predicting future returns.

Between Mom(50) and Mom(200), keep the ratio (50/200) rather than either level — the crossover signal carries the information of both in a single feature.

Between credit spreads and VIX, keep both — the correlation is moderate (0.4) and they capture different aspects of risk (credit vs. equity volatility). But if forced to choose, credit spreads add incremental information that VIX doesn’t capture.

After the correlation filter: 20 candidates → ~14 features.

Problem 2: Stationarity

This is where most retail ML projects fail silently.

Top: raw VIX level over 5 years. The mean drifts upward — a model trained on the first 2 years would learn “VIX above 18 is high” but by year 5, VIX is regularly above 20 even in calm markets. Bottom: VIX z-score (126-day) is stationary — mean zero, stable variance. A z-score of +2 means the same thing in year 1 and year 5.

Non-stationary features poison ML models because the relationship between feature and target shifts over time. A model trained in a low-VIX era will have learned that VIX = 20 is “stressed.” Deploy it in a high-VIX era where VIX = 20 is “calm,” and it will persistently overestimate risk.

The rule: never feed a raw level into a model. Always transform to a stationary representation.

Four transformations, from simplest to most robust:

# 1. Z-score (most common)
z = (x - x.rolling(63).mean()) / x.rolling(63).std()

# 2. Percentile rank (non-parametric, handles skew)
pct = x.rolling(252).apply(lambda w: (w.iloc[-1] > w).mean())

# 3. Rate of change (captures dynamics)
roc = x.pct_change(21)

# 4. Binary regime (simplest, most robust)
regime = (x > x.rolling(126).median()).astype(int)

Which to use? Z-scores work for normally distributed features (vol, spreads). Percentile ranks work for everything but lose granularity. Rates of change work for trending features (momentum, yield curve). Binary regimes sacrifice precision for robustness — which matters when the model will see out-of-sample data that looks nothing like the training set.

Problem 3: Individual Features Are Weak

Here’s the uncomfortable truth about financial prediction: most features have an information coefficient (IC) — the rank correlation between the feature today and the return over the next week — of approximately 0.02 to 0.08.

This is a lesson I’ve had to learn over and over again, but I still keep repeating the same mistake.

Univariate IC for each candidate feature. VIX level is the strongest predictor at IC ≈ 0.08 — which means it explains roughly 0.6% of the variance in next-week returns. Most features are below 0.05. Some are below 0.02, which is indistinguishable from noise.

For context: an IC of 0.05 means that if you ranked all days by the feature value and sorted them into quintiles, the top quintile would outperform the bottom quintile by roughly 2-3% annualized. That’s meaningful for a systematic strategy but invisible on any individual trade.

This is why ML helps: individual features are weak, but their combination can be strong. If VIX, term structure, GEX, and spread z-score each independently predict returns at IC ≈ 0.05 and they capture different dimensions of risk, a model that combines them might achieve IC ≈ 0.10-0.12 through the aggregation of weakly correlated weak predictors.

This is the “wisdom of crowds” principle applied to features. No single expert (feature) is very good. But the committee (model) can be substantially better than any individual member, provided the members aren’t all saying the same thing (low inter-feature correlation).

The Transformation Toolkit

One raw feature can produce multiple transformed features. The question is which transformations capture useful information:

Six representations of a single input (VIX). Raw level (non-stationary, avoid). Z-score (stationary, captures deviation from recent norm). Percentile rank (robust, captures relative positioning). Rate of change (captures acceleration/deceleration). Binary regime (simplest, most robust). Interaction term (VIX_z × momentum, captures non-linear dependencies).

Interaction Features

Interaction features are where domain expertise meets statistical power. Two features that are individually weak can be jointly powerful if their interaction captures a meaningful dynamic:

VIX_z × Momentum: High VIX with negative momentum = crash regime. High VIX with positive momentum = recovery bounce. The interaction separates these two regimes that VIX alone cannot distinguish.

GEX × Spread_z: Negative GEX with wide spreads = maximum microstructure stress. Negative GEX with normal spreads = moderate stress. The interaction captures severity better than either feature alone.

Yield_slope × Credit_spread: Steep curve with tight credit = risk-on carry environment. Steep curve with wide credit = economic distress. The interaction disambiguates.

The danger of interactions: every pair you add is a new feature that the model can overfit to. With 14 base features, you have 91 possible interactions. Adding all of them is a recipe for overfitting. Add only the interactions that have clear economic interpretation.

The Selection Pipeline

Putting it all together:

Starting with 20 candidates, the pipeline produces 8-10 final features through five stages. Each stage has a clear purpose and a clear rule for what survives.

The output of this pipeline is the feature matrix X that gets fed into the model in Part 2. I’d say that the pipeline is not optional — skipping any stage (especially stationarity testing and redundancy removal) will produce a model that looks great in-sample and falls apart out-of-sample.

The Half-Life of Features

One more complication: features decay, just like strategies (Post 80).

Information coefficient over time for five features. VIX level maintains predictive power longest (structural, rooted in risk aversion). OFI proxy decays fastest (microstructure signals get crowded). GEX regime sits in between. All features trend toward the noise floor of IC ≈ 0.02 eventually.

This connects directly to the Strategy Decay series. The alpha in a feature comes from an informational edge. As more people learn about and trade on GEX signals (thanks partly to the popularization by SpotGamma and others), the feature’s predictive power decays. VIX decays more slowly because it’s structural — risk aversion doesn’t get arbitraged away.

The implication for ML: your model needs periodic retraining not just because the model degrades, but because the features themselves degrade. A model trained in 2020 using GEX as a strong feature might find that GEX has an IC of 0.01 by 2025 — below the noise floor. The model needs to downweight or drop it.

This is the feature engineering → model training → retraining feedback loop. We’ll build the retraining framework in Part 3.

What the Feature Matrix Looks Like

After the full pipeline, here’s the concrete feature matrix for V6:

features = {
    # Volatility / Regime (3 features)
    'vix_z':        vix_zscore_63d,
    'vix_ts':       vix_1m_div_3m,
    'rv_z':         realized_vol_z_63d,  # keep if corr with vix_z < 0.7
    
    # Microstructure (2 features)
    'gex_regime':   gex_binary,           # +1 / -1
    'spread_z':     spread_zscore_21d,
    
    # Momentum (2 features)
    'mom_ratio':    ma50_div_ma200,
    'mom_roc':      price_roc_21d,
    
    # Carry / Macro (2 features)
    'yield_slope_z': yield_10y2y_zscore,
    'credit_z':     hy_ig_spread_zscore,
    
    # Interactions (2 features)
    'vix_x_mom':    vix_z * mom_roc,
    'gex_x_spread': gex_regime * spread_z,
}

# Target: next 5-day V6 excess return (over SPY)
target = v6_return_5d - spy_return_5d

Eleven features that are clean, stationary, non-redundant, with domain-driven interactions. This is what gets fed into Part 2’s tree models.

Up Next

Part 2: Tree Models for Regime Classification — Random forests, XGBoost, and why tree-based models are the right tool for this problem. We’ll train, validate, and stress-test the models using the feature matrix we just built.

Remember: Alpha is never guaranteed. And the backtest is a liar until proven otherwise.

These posts are about methodology, not recommendations. If you find errors in my math, let me know — I’ve built an entire series around discovering my own mistakes, so one more won’t hurt.

The material presented in Math & Markets is for informational purposes only. It does not constitute investment or financial advice.

This is part 94 of my series — Building & Scaling Algorithmic Trading Strategies

Final part of the Synthetic Replication series. Part 1: Building blocks. Part 2: Replicating strategies. Part 3: Vol surface.

The Question That Started This Series

Four posts ago, I asked: “What payoff shape would improve V6’s risk/return profile?” Now it’s time to answer.

V6’s current profile is approximately linear-with-a-kink: leveraged upside through TQQQ, partial downside protection from the VIX regime filter and TLT hedge. The regime filter adds some convexity — it exits before the worst of most drawdowns — but it’s not a hard floor. A fast crash that outpaces the momentum signal hits V6 at full leverage.

The goal of an options overlay: add a hard floor without killing the upside.

Left: V6’s current return profile (orange) vs. the desired profile (green), plotted against market returns. The gap is in the left tail — V6 is exposed to drawdowns beyond -15% where the regime filter hasn’t yet fired. Right: the return distribution shift. The overlay truncates the 1st percentile from approximately -40% to -20%.

The Three-Leg Overlay

After working through the building blocks (Part 1), strategy replication (Part 2), and vol surface analysis (Part 3), here’s the specific overlay design:

Three panels showing each leg individually and then combined. Leg 1 (green): long 10% OTM put — the tail hedge, costs ~1.2%/quarter. Leg 2 (orange): short 8% OTM call — income to offset the hedge cost, earns ~0.8%/quarter but caps gains beyond +8%. Combined (yellow): a put spread collar with ~20bps net quarterly cost.

Leg 1: The Tail Hedge (Long 10% OTM Put)

This is the core of the overlay. A quarterly 10% OTM put on SPY (or QQQ, depending on V6’s current allocation) provides a hard floor on losses.

Why 10% OTM? Three reasons. First, V6’s regime filter typically catches drawdowns of 5-8% before they get worse. The put doesn’t need to protect against normal volatility — it needs to protect against the gap down that outpaces the momentum signal. Second, 10% OTM puts are on the steep part of the skew curve — expensive, but not as expensive as 5% OTM (which trades at much higher IV). Third, the historical frequency of 10%+ quarterly drawdowns in QQQ is roughly once every 2-3 years, which keeps the premium manageable.

Cost would be approximately 1.0-1.5% of notional per quarter, depending on IV and skew.

Leg 2: The Income (Short 8% OTM Call)

Selling OTM calls generates premium to offset the tail hedge cost. V6 doesn’t need the last 8% of quarterly upside — most of V6’s alpha comes from compounding 1-2% monthly, not from catching +10% rips.

The call strike is set at 8% OTM because historically, TQQQ gains more than 8% in a single quarter about 15% of the time. The short call caps participation in those rare events but generates consistent income the other 85%.

Income: approximately 0.6-1.0% per quarter.

Leg 3: The Short Far-OTM Put (Funding)

Selling a 20% OTM put further reduces the net cost of the overlay. At 20% OTM, the put is deeply out of the money and expires worthless in roughly 98% of quarters. The premium is small ($0.3-0.5% per quarter) but it partially funds the tail hedge.

The trade-off: protection stops below the 20% OTM level. If QQQ drops more than 20% in a quarter, you’re exposed again below that floor. This is an acceptable trade-off because a drawdown that large typically triggers V6’s regime filter well before it reaches 20%.

Net Cost

Tail hedge cost:       -1.2% per quarter
Call premium income:   +0.8% per quarter
Far put premium:       +0.3% per quarter
───────────────────────────────────────
Net cost:              -0.1% per quarter (~0.4% annualized)

At 40 bps annualized, the overlay is nearly self-funding. The short call and short far put together pay for most of the tail hedge. This is the power of the put spread collar structure — you’re not just buying insurance, you’re reshaping your return distribution by giving up extreme upside to fund extreme downside protection.

Conditional Engagement: Not Always On

The overlay shouldn’t run on autopilot. Its value depends on market conditions:

The key rule: buy protection when it’s cheap, not when it’s needed.

When VIX is below 18 and skew is below the historical median, 10% OTM puts cost roughly 1.0% per quarter. When VIX is above 30 and skew is elevated, the same puts cost 3-4%. By the time you “need” the protection, it’s too expensive to be worth it — and V6’s regime filter is already scaling down anyway.

This is the paradox of tail hedging: the optimal time to hedge is when nothing is happening, because that’s when hedges are cheap. The worst time to hedge is during the crisis, because that’s when hedges are expensive. Discipline means buying the put in January when VIX is 13, not in March when VIX is 35.

Backtest Results

Top: 5-year simulated equity curves. V6 base (gray) and V6 with overlay (green). The overlay gives up some raw return but compresses drawdowns significantly. Bottom: drawdown comparison — every stress period (red shading) shows reduced depth with the overlay.

The improvement is consistent with what we’d expect from a well-designed tail hedge: modest return reduction, meaningful drawdown compression, and a Sharpe ratio that improves because the volatility reduction exceeds the return drag.

Is It Worth It?

This is the question that determines whether the overlay goes from theory to implementation. The answer depends on what you value.

Left: break-even analysis. At 1% annual hedge cost, you need roughly 2 crashes per decade of 20%+ to justify the protection — consistent with historical frequency. Right: optimal hedge budget peaks at 1.0-1.5% annualized, where the Sharpe improvement from volatility reduction exceeds the return drag.

The Case For

The overlay converts a -45% max drawdown into a -30% max drawdown. The math on this is unambiguous: a -45% drawdown requires +82% to recover (3+ years at V6’s CAGR). A -30% drawdown requires +43% to recover (under 2 years). The overlay saves roughly 1-1.5 years of recovery time per major crash.

Over a 20-year compounding horizon, that recovery time difference compounds into a meaningful terminal wealth advantage — even though the overlay costs 40 bps per year.

The Case Against

V6 already has three layers of drawdown protection: the VIX regime filter, the momentum threshold, and the CUSUM monitoring system. Adding a fourth layer (options) introduces:

Operational complexity. Options require rolling, strike selection, and expiry management. This is a weekly task, not daily.

Execution risk. Options bid-ask spreads on TQQQ are wide. The theoretical 40 bps annual cost could easily become 80-100 bps after execution costs.

Marginal improvement. The first three protection layers (regime, momentum, CUSUM) capture most of the available Sharpe improvement. The options overlay adds the fourth layer at 4× the implementation complexity for the smallest marginal gain.

The Honest Assessment

Each V6 enhancement layer plotted by Sharpe improvement and implementation complexity. Execution timing (Part 84) gives the highest ROI: +0.08 Sharpe for minimal effort. The options overlay gives +0.07 Sharpe for 4× the complexity of any other layer. The curve of diminishing returns is steep.

Here’s what I’m actually going to do:

Implement the tail hedge only. No short call, no short far put. Just a quarterly 10% OTM put when VIX is below 18 and skew is below the 63-day median. Cost: ~1.0% per quarter, ~4% annualized (not self-funded without the other legs). Run this in paper mode for 6 months.

Defer the full collar. The short call and short put legs add complexity and execution risk that I don’t think is justified yet. They save 60-80 bps of annual hedge cost, but they also introduce path-dependent risks (getting called away on a TQQQ rally, getting assigned on a far put during a crash). I need more experience with the mechanics before adding these legs.

Monitor skew as a signal. Whether or not the overlay is running, skew z-score (from Part 92) is a useful re-entry signal after selloffs. I’m adding it to the dashboard alongside the VIX regime, CUSUM, and microstructure composite.

The 14-Post Series Arc: What We Built

Stepping back from this post, here’s the full arc of Posts 80-93:

Strategy Decay (80-82): Half-lives of alpha, CUSUM detection, adaptive strategies. Core insight: all strategies decay, the question is how fast and whether you can detect it.

Microstructure Edge (83-86): Order flow toxicity, auction mechanics, dealer gamma, signal layer. Core insight: the plumbing of markets affects strategy performance, and GEX is the highest-impact single signal.

Carry Trade (87-89): Unified carry framework, crash timing, multi-asset carry. Core insight: V6 is already a carry trader — understanding this changes risk attribution.

Synthetic Replication (90-93): Put-call parity, strategy replication, vol surface, options overlay. Core insight: options add convexity but with diminishing returns relative to complexity.

Across 14 posts, V6’s architecture has gone from a simple TQQQ/TLT allocator with a VIX regime filter to a layered system with momentum, regime detection (CUSUM), microstructure conditioning (spread + GEX), carry optimization, and now a potential options overlay.

Each layer improved the Sharpe ratio. But each layer also added complexity. The execution timing fix (Part 84) gave +0.08 Sharpe for essentially zero effort. The options overlay gives +0.07 Sharpe for significant ongoing operational work. The law of diminishing returns is real, and knowing when to stop adding layers is as important as knowing which layers to add.

Sometimes the smartest thing you can build is nothing (which is really, really hard for someone like me who keeps poking at things to see if it does anything at all..)

This concludes the Synthetic Replication series (Posts 90-93) and the full 14-post arc spanning strategy decay, microstructure, carry, and synthetic replication.

My next series will be on Machine Learning for Trading.

Remember: Alpha is never guaranteed. And the backtest is a liar until proven otherwise.

These posts are about methodology, not recommendations. If you find errors in my math, let me know — I’ve built an entire series around discovering my own mistakes, so one more won’t hurt.

The material presented in Math & Markets is for informational purposes only. It does not constitute investment or financial advice.