How to Read the Final Verdict
The [Final Verdict] answers the main question: launch the strategy now, wait, or drop it. It combines the [Robustness Score], deployment gates, and diagnostics into one screen with a clear verdict badge and recommended action.
1. Verdict badge
ROBUST – Strategy passes validation, risk, and execution checks; you can consider deploying within the stated constraints. CAUTION – Some checks failed or are borderline; improve before deployment or accept higher risk. DO NOT DEPLOY – One or more hard gates failed; do not deploy until blocking modules are fixed.
2. Kiploks Robustness Score and Bayesian pass probability
The [Robustness Score] (0–100) is built from Validation, Risk, Stability, and Execution. If any critical module fails, the score is 0. The Bayesian pass probability is the estimated probability that the strategy would pass validation if re-run; it uses the same metric as in Kill Switch and WFA Summary, and is not the same as the t-Stat and WFE composite below.
3. Deployment Gate
Validation Gates – Net edge, stability ([WFE]), [data quality guard]; each must pass its threshold. Statistical Confidence – t-Stat and OOS edge significance. Green (✔) means the check passed; red (✗) means it failed. If any hard gate fails, deployment is blocked and the verdict is DO NOT DEPLOY.
4. Critical Failures, Execution Note, Operational Insight
Critical Failures list which hard gate(s) blocked deployment. Execution Note appears when backtest execution settings were missing and a standard Safety Buffer was applied; set slippage and commission in your backtest for exact values. Operational Insight gives a short status (e.g. Edge Deficit, slippage headroom).
5. Executive Summary and Diagnostic Summary
Executive Summary – Short narrative: diagnostic verdict, operational and statistical summary, and recommendation. Diagnostic Summary (Symptom - Solution) – Table of modules with detected symptoms and technical action plans (e.g. change timeframe, add filters).
6. Recommended Action and What-If
Recommended Action – Clear next step: deploy, wait, or do not deploy and fix the listed gates. What-If Analysis – Table of scenarios (e.g. Ex-Outlier, Zero Slippage, Low Frequency) with robustness and verdict per scenario. What-If: Slippage Sensitivity – How the score and verdict change under different slippage assumptions.
One screen answers: launch now, wait, or drop. Fix blocking gates first; then use the What-If table to stress-test the strategy.
[Kiploks analysis methodology] – formulas, glossary, and FAQ.