Learn / Research process

Back to learn

Answer page / research process

Topic cluster / Regime detection and context

When should you remove a regime filter instead of keep tuning it?

Learn when a regime filter has become maintenance theater, and how to decide whether to retire, simplify, or replace it.

Reviewed by Alphora Research

Updated June 30, 2026

What to remember

  • Out-of-sample improvement vanished while in-sample tuning kept growing.
  • The filter now exists mainly to rescue one old historical period.
  • The operating burden is large enough that humans stop trusting the state changes.

Know the warning signs

A regime filter is on borrowed time when every new sample period demands a new threshold, every bad month gets a new exception, and the live team can no longer explain what the filter is supposed to protect against.

  • Out-of-sample improvement vanished while in-sample tuning kept growing.
  • The filter now exists mainly to rescue one old historical period.
  • The operating burden is large enough that humans stop trusting the state changes.

Run a clean removal test

Compare the current strategy against a simplified version with the filter removed or replaced by a much simpler rule. If the simplified version is nearly as good, easier to understand, and easier to operate, that is valuable information rather than a disappointment.

Simplify before you re-optimize

Sometimes the right answer is not deleting the context idea entirely, but shrinking it into one clear threshold or one cleaner size rule. That often preserves most of the benefit while eliminating the overfit scaffolding that accumulated around it.

How Alphora's workflow would frame it

In Alphora terms, a regime layer should justify itself the same way any other building block does: honest backtests, repeated out-of-sample evidence, and forward behavior that still looks coherent once the model is no longer being defended by the person who built it.