Argix Labs
Documentation

Core Concepts

Bot Builder

The visual, tree-based strategy builder. Compose modular components into complete trading strategies without writing code.

Node types

Every bot is a tree of nodes. Each node has a type that determines its role in the trading strategy.

CategoryLogicComponentsPurpose
SignalOR (any can trigger)RSI, MACD, Bollinger, MA Crossover, Volume, StochasticWhen to consider entering
FilterAND (all must pass)Time, Volume, VolatilityGate conditions
EntrySingle selectionMarket, Limit, StopHow to enter
ExitOR (any can trigger)Take Profit, Stop Loss, Trailing StopWhen/how to exit
SizerSingle selectionFixed Percentage, Volatility-BasedPosition size calculation
RiskAND (all applied)Max Risk LimitsSafety limits (required)

Structural nodes

In addition to trading components, you can use structural nodes to organize complex strategies:

  • Weight: Allocate capital across sub-strategies
  • Group: Organize related components
  • If/Else: Conditional logic branches
  • Asset: Target specific instruments

How bots evaluate

On each evaluation cycle, your bot walks its tree top-down:

Evaluation cycle
For each evaluation cycle:
1. Traverse tree from the trading universe (top-level scope for symbols & branches)
2. Evaluate signal nodes (OR logic)
→ If ANY signal fires → proceed
3. Check filter nodes (AND logic)
→ If ALL filters pass → proceed
4. Calculate position size via sizer
5. Validate against risk limits
→ If ALL risk checks pass → proceed
6. Submit order via entry rule
7. Monitor exit conditions
→ If ANY exit triggers → close position

Strategy example

Here’s a simple mean-reversion strategy structure:

Example: RSI mean-reversion bot
1Trading universe
2├── Signal: RSI (period: 14, oversold: 30, overbought: 70)
3├── Filter: Volume (min: 1,000,000 daily avg)
4├── Filter: Time (market hours only)
5├── Entry: Market Order
6├── Exit: Take Profit (target: 2%)
7├── Exit: Stop Loss (limit: 1%)
8├── Sizer: Fixed Percentage (2% of portfolio)
9└── Risk: Max Risk Limits
10 ├── Max drawdown: 5%
11 ├── Max daily loss: 2%
12 └── Max position size: 5%

Incremental complexity

Constrain initial graphs to a minimal signal set and exit structure; expand branching only after paper-trading results confirm the baseline behavior matches the design intent.

Structural checklist

Validation executes prior to backtest and deployment; the following items mirror the constraints enforced by the engine. Missing dependencies—e.g. a data source where market input is required—produce blocking errors until the graph is completed.

  • At least one signal path to define entry triggers
  • Exactly one entry rule in the deployable configuration
  • One or more exit rules to define position closure
  • Exactly one position sizer for sizing logic
  • Risk management nodes as required by product policy
  • Data sources attached wherever upstream feeds are mandatory
  • Parameter completeness: required fields populated within documented bounds

Risk management is required

Every bot must include risk management. This is a safety requirement and cannot be bypassed. Bots without risk limits cannot be deployed.