Inputs must follow exactly the feature order defined in:
feature_order.json
Current live validation requires:
expected features = 830
present features = 830
missing features = 0
null after fill = 0
infinite after fill = 0
before inference.
Runtime flow
MT5 M5/M15/H1/H4 data
-> multi-timeframe feature engineering
-> structure / confluence / pattern features
-> 830-feature vector
-> V05H ONNX model
-> BUY probability
-> probability threshold
-> BUY signal or HOLD
Timestamp requirement
Live market timestamps must use consistent UTC semantics.
Broker/server time should not simply be labeled as UTC because session
and time-dependent features can otherwise shift.
Intended use
This model is designed to operate independently inside the
multi-strategy XAUUSD portfolio framework.
For example, an M15 SELL strategy and this M5 BUY strategy may both
generate their own independent positions on an MT5 hedging account.
Risk notice
This repository contains experimental trading research software.
Historical, validation, or backtest performance does not guarantee
future profitability. Leveraged trading can result in substantial
losses.
Use a demo or paper environment first and independently validate model
behavior, execution, spread, commission, slippage, and risk controls.