From 3ffd13ce6e2e7db1d8c0b0e95610a7726bba99af Mon Sep 17 00:00:00 2001 From: Dennis Thiessen Date: Mon, 13 Jul 2026 11:34:47 +0200 Subject: [PATCH] Record final gate-ladder parity pass --- docs/research/sr-levels-and-exits.md | 7 +++++++ reports/README.md | 7 ++++--- 2 files changed, 11 insertions(+), 3 deletions(-) diff --git a/docs/research/sr-levels-and-exits.md b/docs/research/sr-levels-and-exits.md index 3f8a2bf..b85727e 100644 --- a/docs/research/sr-levels-and-exits.md +++ b/docs/research/sr-levels-and-exits.md @@ -723,6 +723,13 @@ The `explicit_target_ladder` backtest arm calls the same pure helper as the live scanner, so the final full-period rerun is an implementation-parity check rather than another detector experiment. +Final implementation-parity result after commit `8161c35`: **pass**. The +regenerated full-period report differs from the pre-integration parity report +only in `generated_at`; all 202,765 candidates, 1,086 qualified setups, cohort +statistics, and portfolio results are unchanged. This closes the local +backtest gate for the dual-purpose implementation. It does not itself authorize +or perform a production deployment. + The post-2024 window has been opened and is now analysis data, not a valid final promotion holdout. These arms can isolate mechanism, but neither may ship without new future data or a separately pre-registered walk-forward protocol. diff --git a/reports/README.md b/reports/README.md index da2baca..03774e3 100644 --- a/reports/README.md +++ b/reports/README.md @@ -55,6 +55,7 @@ The explicit gate-ladder parity run writes: These establish the final architectural decision: the volume-free explicit ladder retains all 1,086 qualified setups and exactly reproduces the production -book (Sharpe 2.03, CAGR 50.0%, max drawdown 21.4%, 321 trades). A final rerun -after scanner integration verifies that the shared helper still preserves this -parity before anything is deployed. +book (Sharpe 2.03, CAGR 50.0%, max drawdown 21.4%, 321 trades). The final rerun +after scanner integration passed: the regenerated report changed only its +`generated_at` timestamp, confirming that the shared helper preserves exact +parity. Nothing in this research branch deploys the change to production.