Bet that a price stretched far from the day average comes back
- Written down on
- Not written down first. This one came before I started doing that.
- Result on
- 2026-07-02 · DR-21
- Pass mark
- Cost hurdle at target capital (4.2 to 22.8 bps depending on capital)
The signal I started with. Inside the range where I would actually have traded it, the edge was about 30 times smaller than my cheapest trading cost, and past five minutes it pointed the wrong way. I also ran it on a made-up price series that reverts perfectly by design, and it still lost money there. That told me the anchor was the problem. Killing this one is why I started writing tests down in advance instead of trying one idea at a time.
Bet that a stretched price keeps going instead of coming back
- Written down on
- 2026-07-06
- Result on
- 2026-07-14 · DR-24
- Pass mark
- ≥2× round-trip cost hurdle · ≥10 clean days · >1 regime family
The opposite of vwap_ext: instead of betting the price comes back, bet that it keeps going. The earlier study had hinted this direction was stronger. It was not. Nothing in the first batch came close to the pass mark.
Bet that heavy one-sided order flow keeps pushing the price
- Written down on
- 2026-07-06
- Result on
- 2026-07-14 · DR-24
- Pass mark
- ≥2× round-trip cost hurdle · ≥10 clean days · >1 regime family
When there is far more buying than selling sitting in the order book, does the price keep moving that way? No. Below the pass mark. Along with H7 this settles the question for me: the level of order flow does not tell you where the price goes next.
Stretched price and order flow both pointing the same way
- Written down on
- 2026-07-06
- Result on
- 2026-07-14 · DR-24
- Pass mark
- ≥2× round-trip cost hurdle · ≥10 clean days · >1 regime family
Price stretched a long way, with order flow pushing the same way. Best of the first batch at +2.23 bps over thirty minutes, and it only worked on 4 days out of 10. Short of the pass mark on both size and consistency.
Bet on a reversal when order flow pushes against a stretched price
- Written down on
- 2026-07-06
- Result on
- 2026-07-14 · DR-24
- Pass mark
- ≥2× round-trip cost hurdle · ≥10 clean days · >1 regime family
Price stretched one way while order flow pushed the other way, so bet on a reversal. In a five-day preview this looked good: it worked at every time horizon, on 4 of the 5 days, and best of all exactly where the signal was strongest. It reached 1.5 to 1.9 times my trading cost against a pass mark of 2 times. I had five more days of data saved up that I had not looked at. I could have peeked. I did not. When I ran all ten days, those five unseen days came in around minus 9 bps and flipped the whole result. The cases where the signal was strongest turned out to be the worst ones. Many small wins, and a few very large losses right where I was most confident.
Bet that a break out of the first-hour range keeps going
- Written down on
- 2026-07-06
- Result on
- 2026-07-14 · DR-24
- Pass mark
- ≥2× round-trip cost hurdle · ≥10 clean days · >1 regime family
Price breaks out of the first-hour range, so bet it keeps going. Below the pass mark, and I did not retry it. It taught me something separate: if you sample a condition every thirty seconds, one long stretch shows up as thousands of separate events. After this I stopped trusting raw event counts.
Bet that a trend continues when trading volume spikes
- Written down on
- 2026-07-06
- Result on
- 2026-07-07 · H5v2 precedent
- Pass mark
- ≥2× round-trip cost hurdle · voids below 500 events
Trend continues when trading volume spikes. It found zero events, but not because the market said no. The volume input was a placeholder that had never been wired up and always returned the same number. I recorded it as thrown out rather than failed, and made that a standing rule: if my instrument is broken, that is not an answer from the market. A broken test gets one retry.
The same idea, after I fixed the broken volume input
- Written down on
- 2026-07-07
- Result on
- 2026-07-14 · DR-24
- Pass mark
- ≥2× round-trip cost hurdle · ≥10 clean days · >1 regime family
The same idea, run again after I fixed the volume input. I kept the threshold exactly as it was, so I was testing the idea and not a new one. Below the pass mark.
Use the resting buy and sell orders in the book to predict direction
- Written down on
- 2026-07-10
- Result on
- 2026-07-15 · DR-30
- Pass mark
- ≥2× round-trip cost hurdle · ≥10 clean days · >1 regime family
Do the resting buy and sell orders sitting in the book predict the next few minutes? Yes. This is the most consistent thing I have found anywhere: it worked on all 10 days out of 10 at the short horizons, across 64,000 events, and the bigger the imbalance the better it did. Depending on account size it is somewhere between a twentieth and a third of what one round trip costs me. So it is a real effect that I cannot trade.
Use the change in order flow rather than its level
- Written down on
- 2026-07-10
- Result on
- 2026-07-15 · DR-30
- Pass mark
- ≥2× round-trip cost hurdle · voids below 500 events
Not the level of order flow but the change in it. Only 12 events turned up in 10 days. My threshold was set so high that it sat right at the extreme tail of the real distribution. The test threw itself out under its own minimum-events rule instead of giving me an answer based on noise.
The same idea, retried at a threshold measured from real data
- Written down on
- 2026-07-15
- Result on
- 2026-07-15 · DR-31
- Pass mark
- ≥2× round-trip cost hurdle · ≥10 clean days · >1 regime family
The one retry, spent on a threshold I calculated from the real distribution instead of guessing. That gave 1,860 events over 11 days, the most selective setting still allowed. The result was indistinguishable from noise, and the strongest cases were slightly negative. I am done with this family.
Same as H3, but measured against a rolling 30-minute average
- Written down on
- 2026-07-10
- Result on
- 2026-07-15 · DR-30
- Pass mark
- ≥2× round-trip cost hurdle · ≥10 clean days · >1 regime family
The same idea as H3, but measuring the stretch against a rolling 30-minute average instead of the whole day. This is the closest I have come. Changing the reference point flipped it from negative to positive and it worked on 8 days out of 10 at every horizon. It reached 0.97 times my single trading cost, which is about half of what it needed to pass.