NexusTrade guide

Set options position size and exit rules

Translate a premium budget into whole contracts, inspect liquidity and buying-power bounds, and add complete trend and time exits to an options strategy.

As of 2026-10-10

Follow the example

Choose a step to follow the example. Opening a request lets you review it; it does not submit a job or change your account.

A premium budget is a cap, not a promised quantity: authored process map
Authored task map. It describes what to inspect; it is not an account screenshot or a measured result.
Step 1 of 3

A premium budget is a cap, not a promised quantity

The long call and bull call spread examples allocate $1,000 dollars per opening. The other algorithms request one strategy unit, subject to the recorded buying-power and liquidity bounds. The resolved debit and actual contract multiplier determine how many whole units can fit. Buying power and the liquidity model can reduce that quantity. A cheap-looking premium does not imply that the full budget will be deployed.

Trend exit
Condition: SPY price <= SMA(50, Day) · Close action: SPY, matching spread type, close scope spread, quantity all
Time exit
Condition: Always evaluated · Close action: Same matching spread filters, maxDte 14, quantity all
What you should see

A named field or event to inspect, rather than a generic options preset.

Inspect the size that was actually sent: authored process map
Authored task map. It describes what to inspect; it is not an account screenshot or a measured result.
Step 2 of 3

Inspect the size that was actually sent

The order decision record shows allocation inputs, requested quantity, chosen candidate and the sizing chain. Inspect allocationImplied, buyingPowerCap, volumeLimit and finalPriceRecap when present. A candidate may be kept, reduced, substituted or rejected; record what happened rather than assuming the preset's leg ratio is the final order quantity.

What you should see

An explained difference between intended selector, resolved contract, sent size and simulated fill.

Inspect or preview deliberately: authored process map
Authored task map. It describes what to inspect; it is not an account screenshot or a measured result.
Step 3 of 3

Inspect or preview deliberately

Open the contextual request with your actual returned backtest identifier when required. Review the request before sending; do not rerun simply because a result is disappointing.

What you should see

A bounded review of the requested task, without automatic deployment or broker orders.

A premium budget is a cap, not a promised quantity

The long call and bull call spread examples allocate $1,000 dollars per opening. The other algorithms request one strategy unit, subject to the recorded buying-power and liquidity bounds. The resolved debit and actual contract multiplier determine how many whole units can fit. Buying power and the liquidity model can reduce that quantity. A cheap-looking premium does not imply that the full budget will be deployed.

For an illustrative call premium of $8.50 and multiplier 100, one contract costs $850 before commissions and other execution costs; two cost $1,700. A $1,000 cap fits at most one under those assumptions. An illustrative two-leg debit of $3 and multiplier 100 costs $300 per spread before costs; three cost $900. Actual order sizing uses the resolved prices and its recorded constraints.

Inspect the size that was actually sent

The order decision record shows allocation inputs, requested quantity, chosen candidate and the sizing chain. Inspect allocationImplied, buyingPowerCap, volumeLimit and finalPriceRecap when present. A candidate may be kept, reduced, substituted or rejected; record what happened rather than assuming the preset's leg ratio is the final order quantity.

In the published first long-call opening, the allocation bound allowed one contract, while the liquidity bound allowed two. The sent quantity was one. Its candidate bid and ask explain indicative sizing; the Filled premium and commission explain the simulated execution.

Save both exits separately

The time exit checks positions at 14 or fewer DTE. The trend exit checks a separate market condition. Both target whole matching spreads. Keep unrelated matching positions in another portfolio if they need different exits. An opening preset does not add these close rules.

A condition firing does not guarantee an exit. Inspect close evaluations and Filled close orders, particularly when data is unavailable. If a position survives until expiration, inspect the run's recorded outcome and the broker's actual exercise and assignment procedures before using the same rules live.

Trend exitSPY price <= SMA(50, Day)SPY, matching spread type, close scope spread, quantity all
Time exitAlways evaluatedSame matching spread filters, maxDte 14, quantity all

Separate expiration payoff from closing P&L

A purchased call can lose its full premium. A debit call spread has limited expiration gain and loss under its matched-leg assumptions. The calculators use expiration intrinsic value, while these historical strategies attempt to close earlier. Volatility, time value, spreads and execution costs affect a close before expiration. Do not use expiration payoff as a substitute for the historical result.

Continue exploring

Aurora · AI research assistant

Try this in Aurora

Edit the request, then open it in Aurora. You choose when to send it.