strategy-builder

To manage a crypto trading strategy, you define its logic, risk parameters, and market conditions in a structured YAML format. The system persists this as a STRATEGY.md file, tracking the strategy through draft, active, paused, and retired states across its full lifecycle.

Yes, backtesting trading strategies is integrated directly into the validation process. You can specify backtest parameters within the structured strategy definition, allowing you to validate logic across various trading symbols and timeframes before activation.

Defining risk management and entry logic requires a structured YAML format. This format encapsulates strategy rules, risk parameters, and backtest settings, which are then persisted as a STRATEGY.md file for lifecycle management.

Transitioning a trading strategy from draft to active involves defining the strategy and validating it through backtesting. Once validated, you manage its status, moving it through active, paused, or retired states by updating the persisted STRATEGY.md file.

Yes, strategy lifecycle management supports pausing and retiring automated trading rules. You can update the status of a strategy within its STRATEGY.md file to pause trading operations or permanently retire it from your active portfolio.

Persisting trading strategies as STRATEGY.md files separates strategy logic, risk, and backtest parameters from execution code. This structured YAML approach streamlines creation, validation, and lifecycle management, turning trading ideas into persistent, actionable definitions.