Read a verdict and export a strategy
Follow a completed run through the verdict screen and the strategy export dialog in app source version 0.1.0 at revision 6acbdc33ce0a0af2440a797bd0e726b13e879572, reviewed 5 October 2026. The recorded verdict and export dialogs come from screenshots committed on 21 September 2026 and hash-tracked on 22 September 2026. The result depends on your graph and data.
1. Wire a filtering validation gate
Prerequisite (app source v0.1.0, reviewed 5 October 2026). A runnable graph and imported bars, as in the first tutorial. Action. Connect a validation gate in filtering mode to the terminal Verdict, then run the backtest. Expected result. The completed run publishes the gate's reading and a terminal verdict, or a named refusal. Limit. An informational metric does not block a verdict; without a filtering gate the terminal does not claim GO.
2. Read the checks with their scope
Prerequisite (app source v0.1.0, reviewed 5 October 2026). A completed run with its output open. Action. Read the Verdict at a glance panel and the gate nodes on the graph. Expected result. The panel groups the checks this run published and shows the gate verdict beside its score. Limit. The GO verdict applies to the tested graph, data and wired gates. It is not a prediction of live returns.
3. Inspect export coverage before saving
Prerequisite (app source v0.1.0, reviewed 5 October 2026). A finished run selected for export. Action. Use File → Export strategy and select a target language. Read the dialog's exactness result or refusal. Expected result. An exact result opens the save path; a known or unverified gap names its cause and requires a separate Save anyway action; a blocking node blocks export. Limit. The trading file does not carry the GO/NO-GO verdict. A saved file with a declared gap must not be described as an exact replay.
Open the recorded export dialog.
See export targets and the fidelity protocol for the limits of each translation.