Execution Pipeline

Strategy Lifecycle

From quantitative intuition to exported, runnable code. The Algovex lifecycle covers static logic checks and reproducible backtest simulation.

01. Strategy Design

Authors define logic in the Visual Editor (a node graph) or the Simple Editor (when / and / then rules). This stage focuses on factor identification and initial signal chaining.

Concept & Factor Chaining

Visual & Rule-Based Editing

02. Verification

Algovex checks your strategy's structure and logic for errors, enforcing type-safe connections, sensible parameter ranges, and protection against look-ahead bias before anything runs.

Logic Verification

Logic & Type Checking

03. Backtest Validation

The strategy is run through the backtester on historical data, accounting for commission and slippage. The same compiled logic drives both the backtest and the exported code.

Reproducible Simulation

Commission & Slippage Modeling

04. Code Export

Verified strategies are exported to source code in four languages (Python, Pine Script v5, JavaScript and TypeScript), plus portable JSON, that you can run on your own platform.

Source Code Generation

Four Export Targets

Auditability & Governance

The same compiled logic drives both the backtester and the exported code, so a given input always produces the same signals. You can inspect and edit every node; there is no black box.

Deterministic

Behavioral Parity

Editable

No Black Box

4 Targets

Code Export

Execution: Deterministic & Reproducible

Output: Deterministic & Reproducible