Discussing the article: "Building A Candlestick Trend Constraint Model (Part 11): Revealing Lower-Timeframe Triggers Within Higher-Timeframe Candle Relationships"

[MetaQuotes]

Check out the new article: Building A Candlestick Trend Constraint Model (Part 11): Revealing Lower-Timeframe Triggers Within Higher-Timeframe Candle Relationships.

This article develops an A-B-C-D candlestick constraint model for MetaTrader 5. Candles A and B establish a completed D1 relationship, Candle C supplies a historical M1 setup, and closed M1 candles inside the developing Candle D either confirm or invalidate the sequence. We implement the design as a visual Expert Advisor with optional trading disabled by default, sequence-specific chart objects, restart-safe history reconstruction, spread and position gates, normalized trade parameters, and a reproducible testing plan.

A higher-timeframe candle gives us a broad view of price direction, but its final shape hides the sequence of lower-timeframe events. I returned to our candlestick research to make that sequence explicit. In this article, we develop an A-B-C-D model in which completed A-B candles select the directional rules, C provides the first qualifying setup, and D supplies a closed-bar confirmation window for optional execution.

Our first article studied the internal development of a daily candle. In Part 10, we combined trend constraints with Golden and Death Cross logic. We now use the completed higher-timeframe relationship to select the lower-timeframe conditions we want to examine. A-B supplies our directional hypothesis, and the C-D sequence makes its event order explicit.

Candles A and B define the context. Candle C is accepted when its lower-timeframe bars meet the retest and displacement rules, and Candle D provides the execution window. We use accepted to mean a match to those rules. We assess the trading value of the resulting signals through separate experiments.

We want an Expert Advisor (EA) that distinguishes a completed context from a developing trigger. The state model answers four operational questions:

The defaults are D1 for Candles A-D and M1 for trigger bars. InpContextTimeframe and InpTriggerTimeframe select the periods independently of the host chart. Initialization requires positive period lengths and a trigger period shorter than the context period; it does not verify boundary alignment. We use D1/M1 as the worked configuration. Other combinations require separate synchronization checks. Trading is optional and disabled by default.

Author: Clemence Benjamin