chore: consolidate post-stop research artifacts
Deploy / lint (push) Successful in 11s
Deploy / test (push) Successful in 1m18s
Deploy / deploy (push) Successful in 39s

This commit is contained in:
2026-07-17 20:46:21 +02:00
parent d13c54e3c7
commit c9c6967c9c
11 changed files with 46 additions and 36324 deletions
+20 -1
View File
@@ -29,7 +29,26 @@ cannot revive an older stop episode.
This replaces the previously proposed fixed five-session lockdown. The normal
reset counts an unqualified stop-day close when that close is observed after the
stop. The stricter experiment, which required a failed close on a later session,
was not promoted.
was not promoted as the research policy.
### Live scheduling boundary
The live daily pipeline runs the R:R scan **before** Outcome Eval. A trade that
is closed at its initial stop by that Outcome Eval—or by an intraday evaluation
after the full scan—was therefore still open when the day's gate observation
ran. Its stop-day state cannot establish the failure. The earliest possible
failure is the next successful full scan, and a fresh qualification requires a
subsequent full scan.
The study simulator closes positions before checking same-session re-entry
state, so its normal `gate_reset` arm can count the stop-day close. At this first
transition boundary, current live ordering is instead analogous to
`strict_gate_reset`. The distinction is material: the strict full-period row
recorded Sharpe 1.68, CAGR 44.8%, and 23.4% drawdown; its disjoint 2025+ row
recorded Sharpe 1.38, CAGR 32.9%, and 21.0% drawdown. The selected normal-reset
result (Sharpe 1.77) is therefore policy-study evidence, not exact live
scheduler-order parity. Changing that ordering would be a separate production
decision.
## Experiment design