Session allowlist in code: Asia off, London on

[LondonScalper]

Session allowlist in code sounds cold; it saved me from overnight improvisation.

I keep a simple gate: Asia mostly off for my discretionary FX book, London on, overlap on with tighter filters, late NY reduced. The code — or even a rigid spreadsheet flag — removes the debate at 03:00 when a candle looks "too good."

Why allowlist beats willpower

• Off means off: platform alerts do not become entries
• On still requires spread and news checks — allowlist is necessary, not sufficient
• Changes to the list happen on Sunday review, not mid-trade

Automation here is about forbidding sessions, not finding magical entries.

If you use an allowlist (code or paper), which session did you turn off first, and did expectancy improve after costs?

When I temporarily enable Asia for a research block, it gets an end date in the same config. Open-ended exceptions are how allowlists die. Research that never expires becomes the new default book.

Code does not remove judgment inside allowed sessions — it only stops me inventing a new session policy at three in the morning.