Margin, Max Loss and Liquidation: Field Guide

The practical rules for levering fortress structures without surprise liquidations, plus the pre-trade ladder. Numbers from 20260801_2058.html at $700,000 NLV. Generated 2026-08-04 12:59 by module_liq_ladder.py.

The three numbers everyone confuses

NumberWhat it isHow it behaves in a crash
Max LossWorst case if held to LEAPS expiry. Fixed by your strikes: net debit + (short put − hedge put) gap.Never moves. The broker never looks at it.
Margin requirementWhat IBKR sets aside today: worst loss in a ±15% scan from the current price.Shrinks as the market falls (deep-ITM options lose gamma; the scan band narrows in dollars).
NLV (your equity)Live mark-to-market account value. Falls hard. This is the only number that actually collapses.
The one rule: a margin call fires when NLV < margin requirement. It is an equity event, a race between two falling numbers: your equity falls at the book's leverage (fast), the requirement falls slowly, and liquidation is where equity dives through it from above. "Margin ballooning in a crash" is a myth for broad index books; the requirement works in your favor.

The rule that makes liquidation impossible

If total Max Loss ≤ your cash, you cannot be margin-called, verified in simulation to a −95% crash. When the worst case is smaller than what you hold, there is nothing for a call to bite on.

The one giant asterisk: this only holds when the hedge is OWNED, not rented. An owned hedge is a held LEAPS put: paid once, protects for the whole term, costs $0 on the path. A rented hedge is a 1-3 month put re-bought forever: keeping the max-loss cap alive costs cash every cycle, and in a slow bear that rent drains NLV until the call fires anyway. Proven on the 2022 path: same book, same capped max loss, rent charged = margin call Jun 2022 ($234k of hedge rolls vs $172k income); rent set to zero = survives. The roll cost IS the liquidation mechanism.

Predicting your liquidation level upfront

The best single predictor is the Max-Loss-to-Cash ratio. For this structure family (deep-ITM LEAPS call + OTM LEAPS short put + far-OTM held hedge):

liquidation drawdown  ≈  −90%  +  (Max Loss ÷ Cash  −  1.0) × 60 pts

Check: 1.5x max-loss book → −90 + 30 = −60%, matching the simulated −61%. Below 1.0x the answer is NEVER. Verify the exact level in IBKR Risk Navigator (what-if: drag price down, vol up, watch Excess Liquidity) before executing: that is the broker's own model and the final word.

Delta leverage vs ML/cash: two dials, two risks

DialMeasuresDrives
Delta leverageLive market exposure per account dollar. Sum each leg's share-equivalence (deep LEAPS call ~0.9, short put adds +0.2-0.3, hedge ~0), × spot × 100 × contracts, ÷ NLV. Day-to-day P&L per 1% move; your upside.
Max Loss ÷ cashWorst-case loss vs what you hold. Liquidation risk. The ladder keys off this one.

They rise together as you add contracts but are not the same thing. A fortress contract carries MORE than 1.0 delta at entry (the short put adds bullish exposure), and the delta breathes: toward 1.0 per contract in a rally, above it in a selloff while dollar leverage self-de-levers toward 1x.

SPY + QQQ ladder (DIAMOND)

Income = fully covered at the run's SC delta.

BookMax LossML ÷ CashDelta LeverageMargin (t0)CushionNet Inc/moE[Inc]/moLiquidates At
3 SPY / 4 QQQ$459,4650.66x0.82x$89,293$610,707$7,807$3,221NEVER
4 SPY / 5 QQQ$593,3700.85x1.05x$114,967$585,033$9,962$4,113NEVER
5 SPY / 6 QQQ$727,2751.04x1.28x$140,642$559,358$12,117$5,005NEVER
6 SPY / 7 QQQ$861,1801.23x1.52x$166,316$533,684$14,271$5,897-82%
7 SPY / 9 QQQ$1,052,8351.50x1.86x$204,260$495,740$17,769$7,334-61%
8 SPY / 10 QQQ$1,186,7401.70x2.10x$229,935$470,065$19,924$8,226-49%
9 SPY / 11 QQQ$1,320,6451.89x2.33x$255,609$444,391$22,079$9,118-40%

IBIT ladder (DIAMOND)

Income zeroed for: IBIT

BookMax LossML ÷ CashDelta LeverageMargin (t0)CushionNet Inc/moE[Inc]/moLiquidates At
90 IBIT$265,9500.38x0.50x$52,235$647,765$0$0NEVER
120 IBIT$354,6000.51x0.66x$69,647$630,353$0$0NEVER
150 IBIT$443,2500.63x0.83x$87,058$612,942$0$0NEVER
180 IBIT$531,9000.76x0.99x$104,470$595,530$0$0NEVER
230 IBIT$679,6500.97x1.27x$133,490$566,510$0$0NEVER
250 IBIT$738,7501.06x1.38x$145,097$554,903$0$0NEVER
300 IBIT$886,5001.27x1.66x$174,117$525,883$0$0-85%
350 IBIT$1,034,2501.48x1.93x$203,136$496,864$0$0-72%
Why the same liquidation level means opposite things: a −70% point is bulletproof on SPY/QQQ (worst ever: 2008 at −57%; 2020 −34%; 2022 −25%) and a coin-flip on IBIT (BTC: 2018 −84%, 2021-22 −77%, Mar-2020 −50% in days). Rule: set the liquidation point ~15 pts deeper than the worst crash the underlying has actually done. For SPY/QQQ that allows Max Loss up to ~1.2-1.3x cash (1.5x puts the liquidation point at −61%, right at the edge of a 2008 repeat, acceptable only with eyes open); for IBIT it means Max Loss ≤ cash, always (≤230 contracts at current strikes on a $700k account).

Practical checklist before levering

Methodology and regeneration

Engine: Black-Scholes leg marks vs entry mids; TIMS-style ±15% scan margin (validated within ~4% of the fortress_v28 margin_proxy at t0); crash vol multiplier 1 + 3.3×|drawdown| with sqrt(30/DTE) tenor damping on the margin surface; crossover = first 1% step where NLV − margin ≤ 0, searched to −95%. Income columns are the dashboard's net (headline) and calibrated E[net] rates and are NOT credited inside the crossover (conservative). Levels carry ±3-4 pts of model tolerance. Regenerate:
cd ~/fortress/scripts && python3 module_liq_ladder.py <dashboard.html> --nlv 700000 --ladder "SPY,QQQ:3/4,...,9/11" --ladder "IBIT:90,...,350" --no-income IBIT --html <out.html>