ArdenAlgo · Concepts · Kill zones & sessions

Kill zones & sessions

Not in the engine · Time-of-day filters — deliberately absent from v1

Published 24 Jul 2026 · every rule box checked against mechanization v1 (frozen 16 Jul 2026) · parameter changes land in the changelog first

In three sentences
  • Kill zones are session windows (London, New York) that many ICT traders treat as the only valid hours.
  • This engine runs all 24 hours with no session filter of any kind.
  • Session conditioning is a recorded v2 idea, and it is exactly the sort of parameter that invites overfitting.
Not in mechanization v1 The engine applies no session or time-of-day filter. A setup at 03:00 UTC is treated exactly like one at 14:00 UTC.

What the concept says

Kill zones divide the day into windows — typically the London open and the New York open — and argue that moves inside them carry institutional intent while everything else is noise. In equity and FX markets this has an obvious structural basis: those are the hours when the venues that matter are open.

Why v1 skips it

Two reasons, one principled and one statistical. Crypto perpetuals never close, so the structural argument has to be imported rather than assumed. And a session filter is one of the cheapest ways to overfit a small sample: with a few dozen trades and a few candidate windows, some window will always look better in hindsight. Adding it before the engine has passed a basic null test would mean tuning a parameter on noise.

What we would need first

A pooled sample large enough that hour-of-day could be tested as a conditioning variable with a proper null benchmark and a split-half check — the same bar the gate ladder sets for every other conditioning claim. Until then, running around the clock is both the simpler and the more honest choice.

Common questions

Does the engine ignore time completely?

It uses time only for bar boundaries, higher-timeframe aggregation, a per-symbol cooldown and a 48-hour trade expiry. No hour of the day is privileged over another.

Crypto trades 24/7 — do sessions even apply?

That is the open question. Crypto has no closing bell, but it does inherit activity patterns from the markets its participants also trade. Whether those patterns carry information here is untested, and we would rather test it than assume it.

Why is a session filter risky to add?

Because there are only a handful of session definitions and a small sample of trades, so it is trivially easy to find an hour window that flatters past results. That is the textbook shape of an overfitted parameter.

No chart example — on purposeThere is no screenshot of this concept anywhere on this site, because the indicator never draws it. Publishing an illustration of something the engine does not compute is exactly the kind of decorative proof this project exists to avoid.

Related

Premium & discount · Liquidity map · Full methodology