Strategies
BTC Weekly Directional Debit Spread on BINANCE_OPTIONS — Convexity-Wrapped Trend, Long Calls-Spread in Uptrend / Long Puts-Spread in Downtrend, Cheap-IV-Gated, Weekly Roll (Defined-Risk, Long-Premium, 3-Parameter)
Outcome: Abandoned
BtcWeeklyDirectionalDebitSpreadCheapIv
Outcome Summary
This strategy reached iteration 2, having already fixed a Layer-1.5 venue-consistency issue by re-routing its debit-spread mechanism onto the four declared BINANCE_OPTIONS BTC weekly legs. Its thesis was to buy cheap convexity in the direction of an ~8-week trend, using a short wing to finance the long leg and cap losses at the net debit. However, the pipeline never got to test it: backtest data for BTC-260116-120000-C.BINANCE_OPTIONS could not be collected after 5 retries, exceeding the 600s per-cycle budget. The run was abandoned for data_unavailable reasons — a data-layer blocker rather than a strategy flaw — with the note to re-evaluate the hypothesis once collection is fixed or the symbol is backfilled.
Hypothesis
data_unavailable: backtest data for BTC-260116-120000-C.BINANCE_OPTIONS could not be collected after 5 retries: data collection for BTC-260116-120000-C.BINANCE_OPTIONS exceeded the 600s per-cycle budget; resuming next cycle The data layer (not the strategy) is the blocker — re-evaluate this hypothesis once collection is fixed / the symbol is backfilled.
Implementation
Iteration History
Verification failed (Layer 1.5 — hypothesis/config consistency) [class=hypothesis_mismatch]: - config.instrument_id is BTC-PERPETUAL.DERIBIT but the hypothesis declares BTC-260116-120000-C.BINANCE_OPTIONS, BTC-260116-125000-C.BINANCE_OPTIONS, BTC-260116-100000-P.BINANCE_OPTIONS, BTC-260116-95000-P.BINANCE_OPTIONS — a different asset. Implement the hypothesis as written (or the Research Lead must revise it). Also note: - hypothesis states Weekly bars but config.bar_type is BTC-PERPETUAL.DERIBIT-4-HOUR-LAST-EXTERNAL (4-HOUR) — QA rejects a timeframe that contradicts the hypothesis; align bar_type or revise the text.
Outcome Summary
Before committing an options hypothesis to named BINANCE_OPTIONS contracts, confirm that the data layer can actually collect those specific legs within the per-cycle budget; a sound mechanism cannot be tested if the underlying market data is unavailable.
It was abandoned at the data-availability stage — backtest data for the declared contract BTC-260116-120000-C.BINANCE_OPTIONS could not be collected after 5 retries (collection exceeded the 600s per-cycle budget), so no backtest, backtest-review, optimization, or analyst stage was ever reached.
A defined-risk, long-premium directional options strategy on BINANCE_OPTIONS BTC weekly contracts that buys a call debit spread in an uptrend and a put debit spread in a downtrend, gated to enter only when short-dated IV is cheap, aiming for a positively-skewed payoff with capped losses.
No performance metrics exist: the backtest report is empty and no optimization report was produced, so the strategy was never actually evaluated for return, Sharpe, or trade count.
Backtest and paper results are hypothetical. Trading involves risk of loss.