REGULATOR — Break & Retest Log

Every closed trade, one row each

Aggregates hide the shape. Five trades averaging a third of an R could be five small winners or four losses and a windfall, and only the second of those tells you anything about what to expect next.

⭐ Best and Worst are how far the trade ran in each direction before it closed, in R. A trade that reached +1.9R and closed at +0.3R gave something back; one that never left −0.3R was never right. ⚠ A positive Worst marked * means the EA restarted mid-trade and the excursion tracker was reseeded — it is not a real reading.

Every closed trade, drawn from the broker's own bars

The shaded band is the holding period, the gold dashes mark the entry and the white dashes the exit. Both take-profits are drawn: tp1 is where a third is banked at +1R, tp2 the target the remainder runs to — about 3R of the stop actually sent, because the target is priced off the untightened zone. Dots are the real fills, so a partial and a runner show as two. ⭐⭐ An amber ring marks a target we were NOT paid at, that price reached after we were out — a level the partial or the runner already filled is not a target we missed. On a scale-out strategy that is the single most informative mark here, and it is the whole reason these are drawn after the fact.

Each instrument, on its own

The four run the same logic with one thing changed per instrument — the spread cap, which is measured rather than carried across. ⛔ They also share a single Magic, which is what lets the account-wide risk cap see all of them at once: separate magics would make each instance blind to the others.

⚠ An instrument with decisions but zero taken and one dominant refusal code is usually a gate set wrong for that symbol, not a quiet market. The median spread column is there to make the commonest cause — a spread cap carried over from another instrument — visible at a glance.

Why setups did not become trades

⭐ This is the point of the journal. A strategy is defined as much by what it declines as by what it takes, and a gate nobody can see is a gate nobody can tune. Every code below was written by the EA at the moment of the decision, before any order existed.

Were we right to refuse?

Every declined setup is kept running on the same rule, through the same code, to find out what it would have done. Nothing here was traded — and a shadow long pays the spread, so it is not flattered against the trades that were.

⭐ A negative figure in the last column is the gate working: the trades it turned away lost money. A positive one means that gate cost us something. ⛔ Never add this column up across rows — the codes resolve at wildly different rates, so a pooled total says nothing.

Three recipes, one of them live

Every candidate records where all three stops would have sat. Only the zone-based one is ever sent to the broker. The other two cost nothing to record and are the only honest way to compare them later — on the same setups, not on a different backtest.

Does the zone score mean anything

Zones are scored 0–100 on touches, age, width and last reaction, and anything under MinScore is refused as WEAK. That threshold is a guess until this table disagrees with it.

Where the time goes

⛔ The bar is the latency. Confirming on a closed M15 bar means the entry can be up to fifteen minutes after the retest actually touched — a mean of about seven and a half. Nothing in this table comes close to that, and no amount of tuning here will. It exists so the claim can be checked rather than assumed. Working: docs/LATENCY.md.

Every decision

Straight from the EA's own journal. Nothing here is derived, reconstructed or inferred — the row was written at the moment the decision was made, on the closed bar that produced it.

Newest first. Showing the last 31 of 31 rows.

What this page cannot tell you