Per-trade risk is the pool divided by four. It is never set independently.

The relationship

One number, two presentations, and no independent second setting.

Read the panel's rows and the pattern is exact rather than approximate. A growth row carrying a thirty-two percent pool carries an eight percent per-trade figure. Twenty-nine pairs with seven and a quarter. Twenty-six pairs with six and a half. Drop to the recovery rows and twenty-eight pairs with seven, twenty-one with five and a quarter. Down at the ground-floor row, twelve pairs with three. The relationship holds through every gate and every pool value in the table, which tells you something more useful than an arithmetic fact: nobody chose the per-trade values. They were derived, once, by a division, and what an operator is actually reading in that second family of columns is the same budget restated per slot.

Why it is built this way

Two independent dials would permit a budget to be honoured and exceeded at once.

Imagine the alternative, where pool and per-trade are separate settings. An operator could hold the pool at its authorised figure while raising the per-trade value, and the two numbers would each look compliant against their own row. Four trades at the inflated per-trade size would then exceed the pool, and there would be no single field where the breach appeared — it would exist only in a multiplication nobody performed. Deriving the per-trade figure removes the possibility rather than policing it. There is no cell in which an operator can honour the budget and oversize the trades, because the only per-trade number the panel offers is the one that multiplies back to the budget exactly.

What the divisor means

The four is the cycle, and it makes the whole ladder an even split.

The divisor is not a rounding convenience. The panel's own title describes a four-trade concurrent cycle, and the four in the arithmetic is that cycle appearing in the sizing. Every per-trade figure in the table therefore encodes an assumption: the pool is spent evenly across four concurrent positions. That assumption is what makes the pool a real constraint rather than an aspiration, because concurrency means the four exposures are live simultaneously and their sum is the account's actual risk at that moment. It also quietly forbids something an operator might otherwise consider reasonable — concentrating the budget into one high-conviction position at four times the per-trade size. That configuration honours the pool and is not available anywhere in the table.

The even-split rule

Conviction sizing is excluded by construction, not by discouragement.

This is worth stating directly because it cuts against a widespread instinct. Many risk frameworks scale position size with conviction, and the argument for it is genuinely appealing: if the evidence favours one setup more than another, why fund them identically? The system's answer is that conviction is not measured anywhere, and an unmeasured input granted control over size is the mechanism by which recent outcomes quietly reprice everything. The tier ladder is where evidence changes deployment, and it moves all four slots together on structural grounds rather than one slot on a feeling. The result is that the differences the system permits are the ones it can audit, and per-trade variation within a cycle is not among them.

The practical read

Read the pool for governance, the per-trade for execution, and never reconcile them.

In daily use the two columns serve different moments. The pool figure is what the smart-capacity chain reasons with, because it is the envelope that open exposure gets subtracted from. The per-trade figure is what a person needs when placing an order, because trades are sized individually. Neither is more authoritative than the other and there is never anything to reconcile between them, which is the practical benefit of the derivation. If a cycle's arithmetic ever appears to require choosing between honouring the pool and honouring the per-trade value, something upstream has gone wrong — most likely the mirrored pool figure in the console has gone stale relative to the throttle's authorisation.

• The per-trade column is the pool restated per slot, not a second setting.
• The divisor is the concurrent cycle, so the pool is a live simultaneous constraint.
• There is no legal way to fund one slot larger — conviction sizing has no cell.

The key idea

The safest constraint is one with no configuration to get wrong.

A rule stating that four trades must not exceed the pool would be correct and would require someone to check it. Deriving the per-trade figure from the pool means the rule cannot be broken through the panel at all, because the arithmetic that would break it has no input. That is the same construction the journal uses when it gives derived fields no input cells, and the same reasoning behind resolving tiers by minimums rather than by adjustment. Where a constraint can be built into the shape of the numbers rather than enforced on top of them, the system consistently chooses the shape.