Warrior_EA/Enumerations/README.md

# Enumerations Documentation

## GlobalEnums.mqh
Defines the `ENUM_SIGNAL` enumeration for trading signal states:
- `Buy`: Indicates a buy signal.
- `Sell`: Indicates a sell signal.
- `Neutral`: Indicates a neutral/no-action signal.
- `Undefine`: Indicates an undefined or uninitialized state.

## InputEnums.mqh
Defines a large set of enumerations for configuration and input parameters used throughout the EA. These include:
- Custom menu and property enums for UI/configuration.
- Period presets (e.g., 5, 10, 14, 20, 30, 50, 100, 200) for indicator calculations.
- Training years presets for ML/AI training window selection.
- ATR multipliers for volatility-based calculations.
- Threshold presets for signal/trigger sensitivity.
- Risk/reward ratio presets for money management.
- Bars expiration settings for trade/session logic.
- Entry multipliers for order sizing.
- Trailing strategy types (none, ATR-based, SAR, MA, etc.).
- Money management strategies (fixed risk, intelligent, fixed lot, etc.).
- Day-of-week and session enums for time-based logic.
- ITF (Intraday Time Filter) settings.
- Hourly session presets (H1-H23) for time filtering.

**Purpose:**
These enumerations provide a strongly-typed, maintainable way to configure and control the EA's behavior, supporting both traditional and AI/ML-driven logic. They enable dynamic feature selection, risk management, and strategy configuration, and are essential for modular, testable code.

**Modernization Note:**
- Enumerations should be referenced in configuration UIs and parameter files to enable dynamic, user-driven feature pipelines.
- Consider extending enums to support new AI/ML features and dynamic input selection as the EA evolves.

---
feat: Enhance README and documentation for Warrior_EA project - Updated README.md with project overview, key features, directory structure, getting started guide, and modernization roadmap. - Added AI_NETWORK.md detailing the neural network and AI/ML infrastructure, including architecture, components, usage patterns, and next steps. - Introduced DATABASE.md for the Database module, outlining key components, design highlights, usage patterns, and future enhancements. - Created README.md files for Enumerations, Expert, Money, Signals, Structures, System, Trailing, Variables directories, detailing their purpose, key components, and integration notes. - Documented the Signals subsystem, emphasizing modularity, extensibility, and AI/ML readiness. - Added comprehensive descriptions for individual signal modules in Signals/ directory. - Established clear integration notes and recommendations for future improvements across all modules. 2026-04-20 19:28:34 -04:00			`# Enumerations Documentation`

			`## GlobalEnums.mqh`
			Defines the `ENUM_SIGNAL` enumeration for trading signal states:
			- `Buy`: Indicates a buy signal.
			- `Sell`: Indicates a sell signal.
			- `Neutral`: Indicates a neutral/no-action signal.
			- `Undefine`: Indicates an undefined or uninitialized state.

			`## InputEnums.mqh`
			`Defines a large set of enumerations for configuration and input parameters used throughout the EA. These include:`
			`- Custom menu and property enums for UI/configuration.`
			`- Period presets (e.g., 5, 10, 14, 20, 30, 50, 100, 200) for indicator calculations.`
			`- Training years presets for ML/AI training window selection.`
			`- ATR multipliers for volatility-based calculations.`
			`- Threshold presets for signal/trigger sensitivity.`
			`- Risk/reward ratio presets for money management.`
			`- Bars expiration settings for trade/session logic.`
			`- Entry multipliers for order sizing.`
			`- Trailing strategy types (none, ATR-based, SAR, MA, etc.).`
			`- Money management strategies (fixed risk, intelligent, fixed lot, etc.).`
			`- Day-of-week and session enums for time-based logic.`
			`- ITF (Intraday Time Filter) settings.`
			`- Hourly session presets (H1-H23) for time filtering.`

			`Purpose:`
			`These enumerations provide a strongly-typed, maintainable way to configure and control the EA's behavior, supporting both traditional and AI/ML-driven logic. They enable dynamic feature selection, risk management, and strategy configuration, and are essential for modular, testable code.`

			`Modernization Note:`
			`- Enumerations should be referenced in configuration UIs and parameter files to enable dynamic, user-driven feature pipelines.`
			`- Consider extending enums to support new AI/ML features and dynamic input selection as the EA evolves.`

			`---`