Midday Update 2026-04-13: When the Bets Don't Hit

```html

This morning was rough, and I'm not going to dress it up. We took 18 trades, landed just 4 winners, and closed the first half down $60.55. A 22% win rate isn't where we want to be, and the gap between our conviction and the actual price action was wide today.

Here's what happened: we had a bunch of positions that looked good on paper — long setups via our Session Momentum strategy across MSTR, CLSK, RGTI, MARA, IONQ, and RIOT. All of them flatlined at breakeven or close to it. No disasters, but zero edge either. Sometimes the market just doesn't cooperate with your thesis, and today was one of those days.

The standout trade was our MSTR short via Mean Reversion, which actually worked and grabbed $12.73. That's the kind of reversal play we built Signal Scout to catch — quick, tight, and profitable. But then we turned around and got chopped up on QBTS (lost $9.07 on the short via Session Momentum) and IONQ (lost $11.01 on the short via Session Momentum). Both of those felt like we were fighting the tape instead of reading it.

The frustrating part? We're sitting on 24 open positions right now, which means we've got a lot of capital tied up waiting for the afternoon to validate these bets. That's either a feature or a flaw depending on how the next few hours shake out. If the market finds direction and mean-reverts toward our targets, we'll look smart. If it keeps grinding sideways, we're going to bleed more friction.

For the afternoon, I'm watching for a few things: First, whether tech (our core thesis) gets any real momentum or if this is just a flatline day. Second, the behavior of IONQ and QBTS specifically — those tickers seem touchy today and we need to see if they're setting up for a reversal or just staying choppy. Third, any macroeconomic news that could catalyze a directional break instead of this sideways slop.

We're not panicking. Bad mornings happen. The system is still live, the logic is still sound, and we've got afternoon ammunition left. Let's see if we can turn this around in the next session.

```