MyAlgoGuru Help
Education Glossary Open the app
Help/Reference/Strategy

Strategy Management

Create, configure, version and organise your trading strategies. A strategy defines behaviour — it never executes on its own; that is the deployment engine’s job.

Where you will find this

Strategy Management, Strategy builder (rules/legs/parameters), Strategy detail / config, Versions, import & export.

Purpose

This is your strategy library. Each strategy has a status (Draft → Active → Inactive → Archived) and immutable versions, so you can evolve a strategy without losing its history. Configuration lives on the version; changing it creates a new version rather than mutating the old one.

Only Active strategies deploy

A strategy must be Active before it can be deployed. Draft strategies never execute. Historical versions are preserved permanently for audit and comparison.

The Strategy Management module enables users to create, configure, organise and maintain algorithmic trading strategies.

It provides the business framework for defining strategy behaviour independently of execution.

The module is responsible for the lifecycle of strategies from creation through retirement.

Objectives

The module will:

  • Provide central management of trading strategies.
  • Support creation and maintenance of multiple strategies.
  • Manage strategy configuration.
  • Organise strategies into logical groups.
  • Support versioning and lifecycle management.
  • Provide strategies to the Strategy Execution Engine.

Functional Scope

The module includes:

  1. Strategy Creation
  2. Strategy Configuration
  3. Strategy Organisation
  4. Strategy Versioning
  5. Strategy Lifecycle
  6. Strategy Duplication
  7. Strategy Import
  8. Strategy Export
  9. Strategy Validation
  10. Strategy Search

Strategy Model

A strategy represents a reusable trading methodology.

A strategy defines business behaviour but does not execute trades.

Execution responsibilities belong exclusively to the Strategy Execution Engine.

Strategy Creation

You can create one or more strategies.

Each strategy will maintain a unique identity.

Typical strategy information includes:

  • Strategy Name
  • Description
  • Asset Class
  • Trading Style
  • Version
  • Status

Strategy Configuration

You can configure strategy behaviour.

Configuration may include:

  • Trading Universe
  • Timeframes
  • Entry Rules
  • Exit Rules
  • Indicator Parameters
  • Risk Parameters
  • Position Sizing Parameters
  • Trading Sessions

Configuration remains independent of execution.

Strategy Status

Every strategy will maintain a lifecycle status.

Typical statuses include:

  • Draft
  • Active
  • Inactive
  • Archived

Only Active strategies is eligible for deployment.

Strategy Versioning

The platform will support multiple versions of a strategy.

Each version remains independently identifiable.

Historical versions is preserved.

Strategy Duplication

You can duplicate existing strategies.

Duplicated strategies will become independent business entities.

Subsequent changes does not affect the original strategy.

Strategy Organisation

Strategies may be organised using logical groupings.

Examples include:

  • Portfolio
  • Category
  • Asset Class
  • Trading Style
  • User-defined Groups

Strategy Validation

Strategies is validated before becoming eligible for deployment.

Validation will ensure required configuration is complete.

Invalid strategies does not be deployable.

Strategy Import

The platform will support importing strategies from external sources.

Imported strategies will undergo validation before becoming available.

Strategy Export

You can export strategies for backup, migration or sharing.

Export will preserve strategy configuration.

You can search and filter strategies.

Typical filters include:

  • Name
  • Category
  • Asset Class
  • Status
  • Version

Strategy Ownership

Every strategy will belong to one user within the current application deployment.

Ownership remains associated with the strategy throughout its lifecycle.

Strategy History

The platform will preserve historical information including:

  • Creation
  • Configuration Changes
  • Version Changes
  • Status Changes

Historical records remains available for audit purposes.

Business Rules

  • Every strategy will have a unique identity.
  • Every strategy will belong to one application deployment.
  • Every strategy will have one current active version.
  • Only Active strategies is eligible for deployment.
  • Draft strategies does not execute.
  • Archived strategies remains available for historical reference.
  • Strategy configuration remains independent of execution.
  • Historical strategy versions will never be deleted.

Audit Requirements

The platform will maintain an audit trail for strategy management activities.

Audit events includes:

  • Strategy Creation
  • Strategy Modification
  • Strategy Duplication
  • Strategy Import
  • Strategy Export
  • Status Changes
  • Version Creation
  • Version Activation

Audit records remains immutable.

Out of Scope

The following are outside the scope of this module:

  • Live Strategy Execution
  • Order Generation
  • Broker Connectivity
  • Risk Enforcement
  • Position Management
  • Portfolio Management

These are covered by their respective business modules.

Custom Strategies — authoring in Python

Custom Strategies is where indicators and strategies are written in Python, trial-run, and armed. One builder serves two kinds — an indicator and a strategy — and the kind decides what the output is allowed to do.

  • User code runs in a subprocess sandbox rather than inside the request.
  • The screen is readable by every role. Creating, saving, trial-running and arming are admin actions, and the server refuses them to anyone else — so a non-admin can read the page but cannot change anything on it.
  • A trial run measures the code. It is not a backtest, and it is not evidence of a tradable edge.
Arming is what trades

An armed basket places real orders. That is declared when you arm it rather than inferred from anything else, and it is always your own action.

Two different things are called a saved strategy

A saved scan and a strategy definition are separate records that both appear as something you saved. They are not interchangeable, and a reference to the wrong one fails quietly rather than loudly — so when a saved item does not behave as expected, which of the two it is, is the first thing worth establishing.