OpenClaw Tutorials4 min read

The Two Tickers Carrying My Curve

S

Suneet Malhotra

May 16, 2026

1 views
The Two Tickers Carrying My Curve - OpenClaw Tutorials blog post

The options engine has closed 25 trades on the paper account so far. I made the spreadsheet I should have made a month ago this morning, broke the 25 trades down by underlying, and the chart had one line on it that mattered.

Two tickers, NVDA and TSLA, fired four of the 25 trades and produced most of the engine's net positive P&L. The other six tickers, across 21 trades, netted close to zero R.

The breakdown

NVDA fired twice and TSLA fired twice. Three of those four trades were winners and the median R across the four was about 1.4. Across the full 25-trade book the median R was 0.34. The two-ticker subset has paid for nearly all of the upside the engine has produced since I started tracking expectation per ticker.

The remaining six underlyings, AAPL, MSFT, AMD, AMZN, META, and GOOGL, accounted for 21 of the 25 closures. Their combined net expectation rounds to negative zero point zero five R per trade. The win rate on that subset is 52 percent. The median R is 0.18. They make money on some days, lose it back on others, and over the sample they have not paid for the engine's existence.

If you handed me this dataset stripped of labels and asked which underlyings were generating the edge, I would point at the two without hesitation. The labels are real.

The chart

If I plot cumulative P&L by ticker, six lines hover near the zero axis and two lines step up and to the right. The shape is the punchline. There is no rotation between underlyings. The two carriers carry. The six riders ride.

The take

Twenty-five trades is not enough sample to claim NVDA and TSLA are the edge. It is enough sample to refuse to claim the other six are.

There are two readings of the chart and the engine's next two months depend on which reading is right.

The first reading is that the engine has a real edge on high-momentum names with above-average implied volatility, and the two carriers are the only underlyings in the universe that consistently match that texture. The other six get traded by the engine because the bias-score gate fires on them sometimes, but the underlying behavior is different, and the expectation is correspondingly different. Under this reading I should narrow the universe. Probably to four names. The original two plus the next two highest in momentum-times-IV rank.

The second reading is that the engine is general, the two carriers got lucky on the four trades I have so far, and a wider sample will revert. Under this reading I keep the universe as it is, log forty more closures, and rerun the audit at n=65.

The second reading is the responsible one given the sample. The first reading is the one I want to act on. That gap is the discipline test.

What I am doing

Nothing yet. The threshold I set for changing the universe in production is fifty closures per ticker. I am at two for each carrier and somewhere between three and four for each rider. The sample does not warrant a structural change.

What I did change is what I track. The daily Telegram now prints expectation-per-ticker as a tail line on the EOD summary. If six weeks from now NVDA and TSLA are still the only two contributing positive expectation, the next audit is not whether to narrow. It is how to narrow without overfitting.

The most expensive mistake a small-sample trader can make is acting on the n=25 chart. The second most expensive is pretending the chart is not there.

Share this post

You Might Also Like

Stay in the Loop

Get weekly insights on AI-driven QA, engineering leadership, and automation strategies.

No spam, ever. Unsubscribe anytime.