Turn Your Trading Process Into a Measurable Edge

The EdgeFlow hierarchy

Every layer sits on top of the one before it. Skipping a layer means you cannot explain your results, only report them.

1. Technical confluences — the components of a setup.
2. Combinations — which confluences appear together and how they interact.
3. Market environment — the regime, session and timeframe context the trade lived in.
4. Execution — stop placement, entry timeframe, timing and rule adherence.
5. Trade management — break-even, trailing, take-profit style, early exits.
6. Expectancy — the average result per trade over a big enough sample to trust.

1. Technical confluences

Start by breaking a setup into its parts. A “break-and-retest” isn’t one thing; it is a structural pattern, a level, a trigger candle, a session, an HTF bias and probably a rejection quality. Each of those becomes a confluence with its own history. Required, supporting and disqualifying conditions can be distinguished so the plan is explicit.

2. Combinations

A confluence rarely earns its P&L alone. Fixing a set of confluences and splitting by another one reveals which combinations actually carry the edge. Combinations that only appear five times are flagged as too small to draw conclusions from.

3. Market environment

Higher-timeframe state, session and volatility regime are logged for every trade. The same setup can then be re-evaluated across environments so a strong-in-trend setup is not judged against ranging data, and vice versa.

4. Execution

Execution belongs in its own layer. Structure-based vs ATR-based stops, entry timeframe, timing quality and rule adherence are tracked as separate variables. Comparing planned R to realized R shows how much of the outcome came from strategy and how much from execution.

5. Trade management

Management is where positive-expectancy setups quietly turn break-even. Break-even timing, trailing style, partial exits and discretionary early exits are all tracked. MAE, MFE and capture percent make the cost of each management choice measurable.

6. Expectancy

Expectancy per cohort is the output of the layers above. It is computed against realistic sample sizes; below a small-sample threshold the result is flagged so it is not read as a proven edge. A meaningful expectancy number always travels with its sample size.

Where this happens in EdgeFlow

Trade Plans define the confluences, environment tags and management rules. Build Your Edge and Edge Discovery are the analytical views that surface which cohorts, combinations and environments are producing which expectancy numbers. Trades bring the raw data in; the layers do the rest.

Related reading

• What actually creates a trading edge
• Discover where your edge exists
• Trading expectancy
• Trading analytics that explain performance