The matrix is consulted before execution and again after it. It is never consulted instead of a plan.

The loop

Consult, execute, capture, review — and the capture step is what makes the loop a loop.

The workflow closes rather than terminating. Pre-execution, the matrix supplies the distance for a branch and posture that are already decided. Execution happens with that distance in place. Post-execution, the coefficient, the zone, the ratio and the resulting stop distance are written into the trade record. At review, those fields let the structural and execution labs ask whether the coefficient decisions have been helping or hurting trend-branch expectancy. Skip the capture step and the loop becomes a line: the matrix gives advice indefinitely and never learns whether the advice was good.

The first moment

Pre-execution, the question is narrow: what does each coefficient translate to here.

The value of consulting before execution is that it converts an abstract choice into a concrete distance. A coefficient is not intuitive — the difference between one band and the next is a number of pips that varies by instrument, session and current state, and an operator choosing a coefficient without seeing that translation is choosing between two abstractions. Seeing that one band puts the stop inside a structure that ordinary noise reaches twice a session, and the next band puts it outside, is what makes the choice a decision rather than a preference. That is the whole job of the pre-execution read.

The second moment

Post-execution, the question is only what was used — and it takes seconds.

The capture step has almost no analytical content, which is exactly why it gets skipped: it feels like data entry rather than thinking. Its value is entirely downstream. A trade record containing the coefficient, zone and ratio at entry can be grouped later by coefficient band and graded on stop-out rate, capture efficiency and giveback, which is the only route by which the calibration ever improves. A trade record without them contributes to the expectancy figures and contributes nothing to the volatility question, and the gap is invisible until a review needs to answer it and cannot.

• Capture is four fields and takes seconds; its value accrues months later.
• Trades missing these fields are usable for expectancy and useless for calibration.
• The capture happens at entry, not from memory at the weekend.

The moment it does not belong

Between structure and entry there is no volatility question, because the plan has already answered it.

The excluded moment is the one where an operator, having found a setup, opens the matrix to help decide whether to take it. Nothing the matrix produces addresses that question. It reports how far ordinary movement travels in this instrument right now — a fact about the environment, not about the setup's thesis, its structure or its position in the plan. Consulting it there does not add information; it adds a number to a decision that was supposed to be made on other grounds, and a number in a decision tends to dominate the qualitative considerations it sits beside.

The over-engineering clause

Normal trades do not get coefficient analysis unless the plan explicitly calls for it.

The doctrine carries an efficiency instruction that is easy to read as laziness and is not. A static branch runs a fixed break-even and a fixed target; running the full coefficient workflow on it produces a set of outputs that cannot change how the trade is managed. The cost is not just the time — it is that having done the analysis, the operator now holds a recommendation, and holding an unused recommendation on a trade is one of the reliable routes to using it. The instruction to skip the analysis where it cannot apply is a guard against inventing a use for the result.

The key idea

Defining when a tool is used is as important as defining what it does.

A translation engine with no stated moments will drift into the decisions adjacent to the ones it was built for, because its outputs are precise and precision is attractive wherever a judgement feels uncomfortable. Naming two moments — one before, one after — and naming the moment in between as excluded is what keeps the matrix credible in the role it is genuinely excellent at. The boundary is not a limitation on the tool. It is the reason the tool's outputs can be trusted when they do appear.