#38 — FIFO-Live S5 exit monitoring redesign
Hypothesis — what it tests
Can a 5-second S5 trail-monitor thread in the live service close the fill gap (from 3-10p down to ~0.3p) and let the validated FIFO-Trends backtest edge be realized live?
Description
Engineering follow-through on Entry 37. The first fx-fifo-live deploy (GBP_JPY_ft on account 013) managed exits at M5 bar close and lost −96.5 pips over 9 trades in 3 days at 11% WR versus a 71% WR backtest — the 5-minute detection lag inflated every trail loss by 3-10 pips. Both the live and paper services were rewritten with a two-loop architecture: an M5 entry loop (unchanged P&F engine) plus a separate S5 exit loop polling 5-second candles and submitting a market order immediately on trail trigger. Relaunched 2026-05-21, a residual bug (`last_s5_ts` never initialized between trades) let stale pre-entry S5 bars fire immediate exits with 3.3-7.7 pip gaps — 5 trades, 0% WR, −39.0p — fixed 2026-05-24. Ultimately the strategy was stopped for good on 2026-05-26 (15 trades, −168.5p, 7% WR total): the 1-box 5-pip trail was structurally too tight for GBP_JPY's ~3-pip live spread even with correct S5 fills.
Key result
Indicators
Algorithms
Interactive version (search, filters, figures): the experiment explorer.