new-strategy

To scaffold a trading strategy migration, create a Python module at src/alpacalyzer/strategies/{name}.py implementing your strategy class, then add corresponding tests in tests/test_{name}_strategy.py to ensure coverage.

StrategyConfig defines the configuration interface for a trading strategy, while BaseStrategy integration ensures consistent behavior across implementations by enforcing standardized entry and exit evaluation logic during the migration process.

Register a trading strategy by adding it to src/alpacalyzer/strategies/registry.py, which enables the Strategy Registry to recognize and route requests to your newly scaffolded Python strategy module during execution.

Yes, implementing risk management artifacts is required. Each trading strategy migration must define stop_loss and target parameters within the StrategyConfig to ensure proper risk controls are in place before registry integration.

Yes, Scope Constraint usage is enforced during the strategy migration process to constrain trading behavior. This ensures new implementations adhere to defined boundaries while integrating with the Strategy Abstraction layer.

The Phase 1 Strategy Abstraction migration targets only initial scaffolding and registry integration. It requires complete test coverage and risk management artifacts, limiting simultaneous migration of complex or legacy strategies outside this scope.