trading / confluences / SW-31-breakout-latency-window

SW-31 — breakout latency window DROPPED

Corpus lane — SW-31 · Killed before scoring, in the open, with a written reason.

BURNED DATA — 2019–2026 was selected on before this lab existedNOT TV-VERIFIEDSCREENING ≠ CERTIFICATIONOPTIMISTIC FILL MODEL — touch fills, zero slippageMES ONLY · P1 M2 managementSOLO LEDGER IS NOT A BOOK — never summed

What it asks

Only take the signal if it fires within some window after the opening range.

Drop record — verbatim

DROPPED: reduces to the FDR-dead `n4-earlySignal`. Both gate on how soon after the opening range the signal fires, so the mechanism is the same one the 2026-07-21 deep-dive already killed. Design §1 forbids re-running a candidate that reduces to a dead bit — it must be dropped with a note, not re-measured.

Status — DROPPED

DROPPED in the open: it reduces to the FDR-dead n4-earlySignal. Both gate on how soon after the opening range the signal fires, so the mechanism is the one the 2026-07-21 deep-dive already killed. Design §1 forbids re-running a candidate that reduces to a dead bit — it must be dropped with a note, not re-measured. 'Same mechanism, new packaging' counts as reduction.

Retest path

Forbidden while n4-earlySignal stands. Re-opening it means a new registration that cites n4, so the attempt count is visible.

Standing caveats

screen-2026-08-07stream conflab-pop-v1opportunity sha256 b62ca795de4a647b…harness ok · 0 real violations