The middle mode has its own failure, and nobody warns you about it.

What it preserves

Compress Risk holds the trade count fixed and lets size absorb the shortfall.

The three modes differ in which variable they hold constant when open exposure has eaten into the pool. Smart Capacity holds per-trade quality constant and lets the count fall — if remaining capacity cannot support four trades above the viability floor, it authorises fewer. Full Tier holds per-trade size constant and lets total exposure rise past the pool. Compress Risk holds the count constant at four and lets per-trade size fall to whatever the remaining pool divides into. Its stated priority is preserving the four-trade cadence while respecting remaining capacity, and it is recommended for when full rhythm matters and capacity still exists. That final clause is a condition, not a description, and it is the part most likely to be dropped when the mode is selected under pressure.

The failure

Below a certain size a trade stops being a position and becomes a gesture.

The default viability floor exists because a trade sized beneath it does not earn its place. Spread, commission and swap are largely fixed per position, so as size falls the proportion of the outcome consumed by friction rises, and a small enough trade is one whose expected contribution is mostly cost. It also consumes a slot in a four-position cycle, occupies attention, and generates a journal row that will be averaged into branch statistics alongside full-sized trades — which means it degrades the evidence as well as the account. Smart Capacity respects that floor by construction, reducing count rather than pushing size beneath it. Compress Risk does not: it divides whatever remains by four regardless of how little that is. In thin conditions the mode is faithfully executing an instruction to preserve cadence at a size where cadence has stopped meaning anything.

When it is right

The case for cadence is real, and it is about evidence rather than comfort.

This is not an argument that the mode is a mistake. There is a legitimate reason to hold trade count fixed, and it is not the urge to stay busy. The system's atomic unit of deployment is a four-trade concurrent cycle, and a great deal of downstream measurement is calibrated to it — cycle-level statistics, throughput comparisons, and the tier attribution that asks whether each rung converts. Cycles of varying width are harder to compare, so when capacity is adequate and the only reason Smart Capacity would reduce count is a marginal shortfall, preserving four trades at slightly compressed size keeps the measurement series clean at very little cost. That is the condition the manual names: full rhythm matters and capacity still exists. Both halves have to hold.

The temptation

It reads as the compliant choice, which is what makes it easy to over-select.

Compress Risk has a property neither of the other modes shares: it never exceeds the pool and it never reduces the trade count, so it produces no warning and no visible concession. Full Tier announces itself — it can breach the pool and must be logged with justification. Smart Capacity announces itself differently, by returning fewer trades than the operator expected, which is a small unwelcome message every time it happens. Compress Risk returns the expected number of trades, inside the authorised envelope, with nothing flagged. An operator who dislikes both of the other messages can select it permanently and remain technically compliant while systematically trading below the viability floor in every constrained cycle. The mode is not the exception layer, so nothing counts its use, which is precisely why its use is worth counting.

How to hold it

Treat the mode as a per-cycle decision with a stated condition.

The discipline is to select Compress Risk when its condition is met and to let the default handle the rest, which requires knowing the condition well enough to check it in a few seconds. Remaining capacity divided by four should still land above the viability floor — if it does not, the mode is producing sub-viable trades and Smart Capacity's smaller cycle is the better trade even though it feels like the lesser one. It is also worth reading mode usage the way override usage is read: a run of consecutive cycles in Compress Risk is a signature, and what it usually signifies is that open exposure has been persistently high rather than that rhythm has been persistently important. That is a finding about carryover behaviour, and it will not surface anywhere else.

• Smart flexes count; Compress flexes size; Full Tier flexes the pool itself.
• Compress below the viability floor produces trades that are mostly friction and still count as evidence.
• It generates no warning and no shortfall, so its usage has to be reviewed deliberately.

The key idea

A mode that never triggers a warning is not the same as a mode that is always safe.

Governance systems flag the paths that can breach a limit, and the flagging quietly trains an operator to read absence of warning as approval. Compress Risk is the case where that inference fails: it cannot breach the pool, so it never warns, and its actual failure is of a kind the pool constraint was never designed to catch — a cycle that fits perfectly inside its budget and is composed of positions too small to be worth taking. Recognising that some failures live inside the constraint rather than outside it is the difference between operating a governed system and operating the warnings it happens to emit.