Iron condor builder API with leg-level discipline.

Condors fail as systems abstractions when one weak wing can hide inside a combined score. FerroSpread keeps construction and quality explicit.

Why this is an engine problem, not a UI filter

!

Iron condor builders need to reason about four legs, two wings, width symmetry, expiration, and liquidity at once.

!

A condor can look attractive while one leg is stale, thin, or mispriced.

!

The product surface needs to explain the range thesis and candidate quality, not just return a net credit.

How FerroSpread handles it

01

Construct the wings

The engine builds the put side and call side under explicit width, expiration, and availability constraints.

02

Evaluate quality

Candidate quality can reflect weak legs and structure-level tradeability instead of averaging problems away.

03

Explain the condor

The output is ready for a product surface to show payoff, breakevens, score drivers, and risk context.

What makes this FerroSpread-shaped

Condors are part of the standard supported strategy taxonomy.

Explanation payloads are part of the ranked candidate contract.

The engine sits beneath product workflows that keep risk beside opportunity.

Common concerns

Can FerroSpread construct more than iron condors?

Yes. Iron condors are one supported family among verticals, butterflies, calendars, diagonals, and custom spreads.

Does this replace trader review?

No. The engine constructs and explains candidates; review and trade decisions remain with the application and user.