|
| 1 | +# Regime Trend v1 — Intrabar Replay Errata 001 |
| 2 | + |
| 3 | +Status: **Accepted before corrected replay results are viewed** |
| 4 | + |
| 5 | +## Invalidated report |
| 6 | + |
| 7 | +The first `intrabar-replay-report.json` produced by the original 5-minute replay implementation is invalid and must not be used for research conclusions. |
| 8 | + |
| 9 | +The invalid output was identifiable because every target reported zero `STOP_FIRST` trades despite the baseline ledger containing initial-stop and trailing-stop exits. |
| 10 | + |
| 11 | +## Root cause |
| 12 | + |
| 13 | +The baseline 4-hour engine records a stop exit timestamp as the opening timestamp of the 4-hour candle whose open or low triggers the stop. |
| 14 | + |
| 15 | +The original replay iterated only while: |
| 16 | + |
| 17 | +`five_minute_timestamp < baseline_exit_timestamp` |
| 18 | + |
| 19 | +This excluded the entire 4-hour stop-exit candle, including the five-minute candle in which the stop actually occurred. |
| 20 | + |
| 21 | +The original replay also excluded a trailing-stop update whose activation timestamp equaled the baseline stop-exit candle open. Such an update is active for that candle and must be included. |
| 22 | + |
| 23 | +## Corrected replay horizon |
| 24 | + |
| 25 | +### Baseline trend exit |
| 26 | + |
| 27 | +A baseline `trend_exit` executes at the recorded 4-hour open. Replay remains strictly before the baseline exit timestamp: |
| 28 | + |
| 29 | +`[entry_timestamp, baseline_exit_timestamp)` |
| 30 | + |
| 31 | +The baseline trend exit has precedence at its recorded open. |
| 32 | + |
| 33 | +### Baseline initial or trailing stop exit |
| 34 | + |
| 35 | +A baseline `initial_stop` or `trailing_stop` timestamp identifies the opening of the 4-hour candle containing the stop event. Replay must include the full candle: |
| 36 | + |
| 37 | +`[entry_timestamp, baseline_exit_timestamp + 4 hours)` |
| 38 | + |
| 39 | +Within that final 4-hour candle, five-minute candles determine whether the frozen target or active stop occurs first. |
| 40 | + |
| 41 | +## Stop-update activation |
| 42 | + |
| 43 | +A stop update calculated at 4-hour timestamp `T` becomes active at `T + 4 hours`. |
| 44 | + |
| 45 | +An update with activation timestamp equal to the baseline stop-exit candle open must be included. |
| 46 | + |
| 47 | +## Consistency failure |
| 48 | + |
| 49 | +If a baseline stop-exit candle has complete five-minute coverage but replay finds neither the target nor active stop during that candle, classify the trade as `DATA_MISMATCH` rather than silently retaining `BASELINE_EXIT`. |
| 50 | + |
| 51 | +A missing five-minute candle before resolution remains `DATA_GAP`. |
| 52 | + |
| 53 | +## Research consequence |
| 54 | + |
| 55 | +All net-PnL, profit-factor and event-count results from the invalid first replay are discarded. Only the corrected report may be interpreted. |
| 56 | + |
| 57 | +The final holdout remains closed. |
0 commit comments