Why seven tiers — the construction logic behind the ladder.

The problem with binary

On/off risk is a confession, not a system.

Most retail risk management reduces to two states: normal size and scared size. The trader runs full risk until something hurts, then halves everything until the fear fades. Neither transition is measured. Neither is logged. Both are driven by the most recent trade rather than by the state of the account or the quality of the evidence. The binary switch fails because deployment decisions carry more information than one bit — an account can be healthy but the week's evidence weak, or wounded but the structural diagnostics clean. A two-state model forces those very different situations into the same posture. The tier ladder exists to give each distinguishable situation its own deployment answer, so the response to pressure is graduated rather than panicked.

The three inputs

Conviction, evidence, and capital state each need room to move.

The ladder has to encode three independent dimensions. Capital state — the gate — sets the arena: how much drawdown the account is carrying determines which pool-budget row is even eligible. Evidence — daily all-blended EV and the weekly structural read — determines the tactical base tier inside that arena. And the structural overlay — Category 6 confirmation, calculated diagnostics, contradiction vetoes — modulates or suppresses from there. Three dimensions with a handful of meaningful values each cannot be represented by two or three tiers without destroying information. Seven rungs is where the ladder stops losing distinctions that matter and hasn't yet started inventing distinctions that don't.

• Fewer than five tiers: gate state and evidence state collide — a Growth account with weak evidence gets the same size as a Buffer account with strong evidence.
• More than eight: adjacent tiers differ by amounts smaller than normal week-to-week variance, so tier selection becomes noise.
• Seven: every rung corresponds to a posture an operator can name, defend, and log.

The rung anatomy

Each tier is a pool percent and a per-trade average, not a feeling.

A tier is not a label like 'aggressive' or 'cautious.' Inside the Pool Budget Panel, each tier resolves to two hard numbers for the active gate: the cycle pool percent — how much of the account the next 4-trade concurrent cycle may put at risk in total — and the per-trade average risk that pool implies. T7 in Growth deploys the widest pool the system ever permits; T1 anywhere is survival posture, the minimum deployment that keeps the operator in rhythm without meaningfully exposing the account. Because both numbers are printed in the workbook before any trade is taken, tier selection is auditable: the decision log shows which tier was authorized, what the pool was, and whether execution respected it.

Why the spacing is uneven

The ladder compresses where mistakes are fatal.

The distance between adjacent tiers is not constant, and that's deliberate. Near the bottom of the ladder, the difference between T1 and T2 is small in absolute pool percent because an account under pressure cannot afford large steps in either direction — a wounded account that doubles deployment on one good day is gambling on sequence luck. Near the top, the steps widen because a Growth-gate account with strong stacked evidence has earned meaningful expansion, and expansion that's too timid leaves the edge under-monetized. The ladder's shape encodes an asymmetry that discretionary sizing almost never respects: the cost of over-deploying while weak vastly exceeds the cost of under-deploying while strong.

The key idea

The tier ladder turns 'how much should I risk?' into a lookup, not a negotiation.

Every input that should influence position size — drawdown state, daily evidence, weekly structure, diagnostic overlays — flows into one resolved tier, and the tier resolves to printed numbers. The operator's judgment still matters enormously: in trade selection, in execution, in the honesty of the inputs. But the sizing question itself is settled by the machine, every cycle, the same way. That consistency is the entire point. An edge only compounds if the deployment engine underneath it behaves identically in week four and week forty.