Warrior_EA/Structures/README.md

# Structures Subsystem (Structures/)

## Overview
The Structures/ directory contains data structure definitions used throughout the Warrior EA for organizing and passing trading-related information. These structures are essential for maintaining clean, modular, and testable code, especially as the system evolves toward AI/ML-driven logic.

## Key Components

### signalInfoStructure.mqh
- **Struct:** `SignalInfo`
- **Purpose:** Encapsulates all relevant information about a generated trading signal.
- **Fields:**
  - `year`, `month`, `day`, `DOW`, `hour`, `minutes`: Timestamp of the signal.
  - `tableName`: Source or context table for the signal.
  - `pattern`: Name or type of the detected pattern.
  - `direction`: Trade direction (e.g., buy/sell).
  - `entryPrice`: Price at which the signal was generated.

### TradeRecordStructure.mqh
- **Struct:** `TradeRecord`
- **Purpose:** Stores all relevant information about a completed trade.
- **Fields:**
  - `year`, `month`, `day`, `day_of_week`, `hour`, `minutes`: Timestamp of the trade.
  - `pattern`: Pattern or strategy used for the trade.
  - `direction`: Trade direction (buy/sell).
  - `entryPrice`: Entry price for the trade.
  - `exitPrice`: Exit price for the trade.
  - `result`: Outcome/result of the trade (e.g., win/loss).

## Integration Notes
- These structures are used for logging, analytics, and passing data between subsystems (signals, database, AI/ML modules).
- Consistent use of well-defined structures improves maintainability and supports future AI/ML integration.

---
*Documented April 2026. For further details, see the main project documentation and AI_NETWORK.md.*
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			`# Structures Subsystem (Structures/)`

			`## Overview`
			`The Structures/ directory contains data structure definitions used throughout the Warrior EA for organizing and passing trading-related information. These structures are essential for maintaining clean, modular, and testable code, especially as the system evolves toward AI/ML-driven logic.`

			`## Key Components`

			`### signalInfoStructure.mqh`
			- Struct: `SignalInfo`
			`- Purpose: Encapsulates all relevant information about a generated trading signal.`
			`- Fields:`
			- `year`, `month`, `day`, `DOW`, `hour`, `minutes`: Timestamp of the signal.
			- `tableName`: Source or context table for the signal.
			- `pattern`: Name or type of the detected pattern.
			- `direction`: Trade direction (e.g., buy/sell).
			- `entryPrice`: Price at which the signal was generated.

			`### TradeRecordStructure.mqh`
			- Struct: `TradeRecord`
			`- Purpose: Stores all relevant information about a completed trade.`
			`- Fields:`
			- `year`, `month`, `day`, `day_of_week`, `hour`, `minutes`: Timestamp of the trade.
			- `pattern`: Pattern or strategy used for the trade.
			- `direction`: Trade direction (buy/sell).
			- `entryPrice`: Entry price for the trade.
			- `exitPrice`: Exit price for the trade.
			- `result`: Outcome/result of the trade (e.g., win/loss).

			`## Integration Notes`
			`- These structures are used for logging, analytics, and passing data between subsystems (signals, database, AI/ML modules).`
			`- Consistent use of well-defined structures improves maintainability and supports future AI/ML integration.`

			`---`
			`Documented April 2026. For further details, see the main project documentation and AI_NETWORK.md.`