Strategy Builder — Overview

The Strategy Builder turns a trading idea into an executable rule set. Instead of writing code, you assemble conditions — comparisons between indicator values, price fields and constants — and the platform evaluates them on every candle. It combines a form-based condition editor with a node-based visual flow canvas, so the same logic can be authored as a list of rules or as a wiring diagram.

Every strategy is backed by a DSL that serialises to JSON. That is what makes strategies portable — exportable for backup, shareable with other traders, and publishable to the marketplace.

Four layers, each with one job. The wizard collects configuration into a single store. The evaluator turns candles plus configuration into boolean signals. The backtest engine replays history through the evaluator and keeps the books. The execution layer does the same thing against a live broker instead of a recording.

┌──────────────────────────────────────────────────────────────────────┐
│                     WIZARD  (UI layer)                               │
│                                                                      │
│  Particulars → Settings → Tagging → Symbol → Quantity                │
│       └──────────→ Entry → Exit → Testing → Review                   │
│                              │                                       │
│                    ┌─────────▼─────────┐                             │
│                    │  Strategy store   │  all step, chart and        │
│                    │                   │  backtest state             │
│                    └─────────┬─────────┘                             │
├──────────────────────────────┼───────────────────────────────────────┤
│                     EVALUATION ENGINE                                │
│                              │                                       │
│   ┌───────────┐   ┌──────────▼───────┐   ┌───────────┐   ┌────────┐  │
│   │ Condition │──▶│    Evaluator     │──▶│ Variable  │──▶│Indicator│ │
│   │  builder  │   │                  │   │ resolver  │   │ library │ │
│   └───────────┘   └──────────┬───────┘   └───────────┘   └────────┘  │
├──────────────────────────────┼───────────────────────────────────────┤
│                     BACKTEST ENGINE                                  │
│                              │                                       │
│   ┌───────────┐   ┌──────────▼───────┐   ┌───────────┐   ┌────────┐  │
│   │ Position  │──▶│  Backtest runner │──▶│  Metrics  │──▶│ Charts │  │
│   │  manager  │   │                  │   │ calculator│   │        │  │
│   └───────────┘   └──────────────────┘   └───────────┘   └────────┘  │
├──────────────────────────────────────────────────────────────────────┤
│                     EXECUTION LAYER                                  │
│                                                                      │
│   ┌───────────┐   ┌──────────────────┐   ┌───────────┐   ┌────────┐  │
│   │   Paper   │   │  Live executor   │   │  Broker   │   │  Risk  │  │
│   │  trading  │   │                  │   │ adapters  │   │ limits │  │
│   └───────────┘   └──────────────────┘   └───────────┘   └────────┘  │
└──────────────────────────────────────────────────────────────────────┘

• UI layer — the wizard steps, backed by a single store that owns all step state, chart state and backtest state.
• Evaluation engine — resolves indicators, applies comparisons, and folds the results through the AND/OR tree. Shared by backtest and live execution, which is why a backtested rule behaves the same way in production.
• Backtest engine — drives the evaluator bar by bar, manages the position lifecycle, and computes the metric set.
• Execution layer — paper and live executors sharing one broker-adapter interface, with risk limits enforced above it.

The wizard is sequential — each step builds on the last — but navigation is free once a step is complete, so you can jump back to Symbol after seeing a backtest without losing anything.

1. 1
   Step 0 — Particulars

   Name, description, tags and visibility. An 8-digit Strategy ID is derived from the name and used for order tracking.
2. 2
   Step 1 — Settings

   Global behaviour: single or multiple entries and exits, the multi-entry strategy type, and level spacing.
3. 3
   Step 2 — Tagging

   Optional. Client order ID templates, signal tags and order linking — for live reconciliation, not for backtesting.
4. 4
   Step 3 — Symbol

   Broker, segment, instrument, timeframe and session mode. Decides what data is available and when the strategy is allowed to trade.
5. 5
   Step 4 — Quantity & Capital

   Position sizing mode, capital, leverage, position limits, and how capital is split across entry sets.
6. 6
   Step 5 — Entry

   The condition tree that triggers orders, the order type, and re-entry configuration for Grid, DCA and Pyramid.
7. 7
   Step 6 — Exit & Risk

   Exit conditions, stop loss, take profit, partial exits, and portfolio-level risk limits.
8. 8
   Step 7 — Testing

   Backtest, forward test, or switch to real-time paper and live execution. Where the strategy is judged.
9. 9
   Step 8 — Review & Deploy

   Every setting in one place, DSL export and import, and deployment to paper or live.