Skip to main content
The structures module (from pulse import structures) provides premade resolvers that turn one call into a bundle of ready-to-trade legs, so you skip resolving each expiry and strike by hand.

What a structure resolver returns

Each *_by_delta function takes the resolver, an underlying, a timestamp, the per-leg deltas and a min_dte, and returns a NamedTuple with one attribute per leg. You then place an order per leg:
The legs are addressed by name (legs.put, legs.call) or position. The resolver picks the strikes; the quantities and direction stay in your strategy - a structure resolver never decides how much to buy or sell, so the same strangle_by_delta serves both a long and a short strangle.
Strikes match the manual path exactlyA structure resolver is a thin wrapper over the strike and expiry resolvers: it resolves the expiry once, then each leg’s strike by delta (placing equidistant legs via the absolute resolver where the shape requires it). Resolving the legs yourself gives the same strikes.

The families

The named tuples are shared across families - butterfly_by_delta and its broken-wing variant both return a Butterfly; the condor shapes return a Condor; the iron variants return an IronCondor or IronButterfly.

Which structure when

Building structures

This page is the conceptual map. For copy-paste recipes - both the Manual path (resolve each leg yourself) and the Helper path (a structures resolver) - see the Structures section, which has runnable code per family. The full resolver list, including the exotic variants, is in the [structures API reference][pulse.structures]. Related: Resolvers · DataFeed and market data · Architecture and the pulse loop
Last modified on November 4, 2026