Our Featured Setup Just Failed. Here's Exactly How, and the One Number That Never Moved.
Eight days ago, in Issue No. 15 of this newsletter, we published a specific number for Lam Research: entry zone 340-360, invalidated on a weekly close below 330. We wrote it before knowing which way the week would go, on purpose — a stop decided in advance is worth something precisely because it isn't negotiated after the fact.
Friday it closed at 13.30. The setup is dead. Here is the full week, no numbers skipped:
The Six Sessions, Plainly
Monday: 29.92 — already eight cents under the line, on the day of the Hormuz shock, but a Monday close doesn't count. Tuesday: bounced to 46.10, back inside the zone, looked like it had survived. Wednesday: 35.43. Thursday: 20.96, further under than Monday's scare had been. Friday: 13.30. Six sessions, one direction more often than not, and the level we drew never moved to meet it.
The Part That Actually Needs Explaining
Here is the detail that matters more than the loss itself: LRCX's score never left 98. Not once across the entire slide from 50 to 13. By the board's own math, this stock got a better entry every single day it fell — further below its 20-day average, scaled against its own volatility, exactly what the model is built to reward.
Both things are true at once, and reconciling them is the whole lesson. The score measures one question: is today's price statistically cheap relative to this stock's own recent trend? It does not know what price you or we entered at, and it has no opinion on a specific invalidation level drawn on a specific date. A stock can keep re-rating better by the model's logic while still blowing straight through a real trader's stop, because those are two different instruments doing two different jobs. The score finds the zone. The invalidation level, decided once and left alone, is what tells you when a specific trade is over.
What We Got Wrong, Specifically
Not the zone-finding — LRCX was a legitimately strong score, and still is. What we'd reconsider: featuring a single name as the setup of the week during a period when a live geopolitical shock (the Hormuz blockade, four days old at publication) was still resolving. The entry looked clean on Sunday because the shock's damage wasn't finished being priced in yet. That's a timing lesson about featuring setups mid-crisis, not a flaw in the scoring itself.
Why We're Writing This At All
Because the alternative is not writing it. A site that only publishes the calls that worked isn't giving you a track record — it's giving you a highlight reel. This one is public and dated: Issue 15, July 12, printed before Friday existed. If you'd sized it the way the newsletter suggested — half the position, tight leash — the loss was small and known in advance. If you went in bigger, this is your reminder why that sizing rule exists.
The setup outlives the news, we wrote a few issues back. Sometimes it doesn't. The discipline is what outlives either outcome.
Scores in this piece come from the ZonedInOut model. How the score works →
Get the Sunday Brief
One email a week, before the open: what the board did, which calls worked, which didn't, and what changed. Free. No spam, unsubscribe anytime.