Chapter 7's census named event cycles a survivor because they aren't mispricings to arbitrage away — they're the structural rhythm of when uncertainty resolves. This chapter is the engineering manual for that rhythm: the ramp, the peak, the crush, and the honest odds of each stance around it.
The cycle's anatomy. Ahead of a scheduled event — RBI policy, the budget, index-heavyweight results, major global prints — option premium accumulates an event reserve (Chapter 2, Lurch 3): IV in the affected expiries ramps as the date approaches, because the event is a scheduled dose of genuine uncertainty and the crowd (plus every model) prices protection for it. At the announcement, uncertainty resolves — whatever the outcome — and the reserve evaporates: the IV crush, often compressing days of accumulated fear into minutes. Crucial honesty from Chapter 5: machines don't erase this cycle; they are half of it — the ramp is correctly-priced fear of a real unknown, the crush its correct resolution. There is no free money anywhere in the cycle. There are, instead, three stances with three honest risk-shapes:
Stance 1 — Selling the peak (short the reserve, underwriting the event). The classic: sell elevated premium just before the event, collect the crush after. The honest accounting: you are being paid the event reserve because you are underwriting the event — the times it genuinely matters (the surprise hike, the shock result), realized movement blows through the reserve and the seller pays for every quiet event that preceded it. Engineering requirements if this stance is ever taken: defined risk only (the reserve-selling trade is precisely where Chapter 13's wings stop being optional — an unhedged short straddle into a binary event is the steamroller trade by definition), sizing at a fraction of normal mandate (the tail here is scheduled), and strike placement against the event-implied move (the straddle price into the event states the market's expected magnitude — your reference, not the week's habits). Your filter stack (Chapter 11) already handles the default case: for most retail engineers, most events, the pre-written output is stand-down or exit-before — Stance 1 is an earned exception, not a routine.
Stance 2 — Buying the ramp (long fear, early). The mirror trade: buy options before the ramp inflates — days out, when the event reserve is only beginning to build — and exit into the peak, selling fear to the late-arriving crowd without ever holding through the announcement. Honest constraints: the entry must genuinely precede the ramp (buying two days before RBI is buying the peak, not the ramp — the crowd's calendar is your competition), theta runs against you every quiet day (the position must be structured so the ramp you're forecasting outruns the rent you're paying — near-event expiries make this brutal; slightly farther ones soften it), and the trade's edge case is regime-dependent: it works best when Chapter 4's percentile says fear is cheap while the calendar says a scare is scheduled — the availability seesaw's underpriced end, with a date on it.
Stance 3 — Trading the resolution (the post-crush structural window). The least crowded stance and often the cleanest: do nothing through the ramp and the event, then trade the aftermath — where two engineered opportunities recur: (a) post-crush selling: after the evaporation, IV frequently overshoots downward or normalizes into a now-clarified regime — the strangle playbook (Module 3) often finds its best habitat in the sessions after a major event, with fresh premium, resolved structure, and your filter stack finally reading green (your RBI-week tracking from June was exactly this cycle's field notes); (b) post-event structure: the announcement frequently delivers the Market Structure school's cleanest verdicts — breakaway gaps, range resolutions, trend days with genuine fuel (that school's Chapter 17 fuel test, maximally satisfied) — and options express those verdicts with defined risk while the crushed IV makes the buying side briefly, honestly cheap. Stance 3's entire fee is patience: the willingness to watch the ramp's drama and the peak's temptation without a position, because your calendar says your trade begins after the noise ends.
The weekly ritual that runs this chapter: the event map (Chapter 11, Filter 2) gains a second column — beside each scheduled event, the pre-written stance: stand down / exit-before / Stance 1 with wings and fraction-size / Stance 2 if percentile-cheap / Stance 3 targets. Five minutes weekly; every event's emotional cycle met with a document instead of a feeling — which, by now, you'll recognize as this academy's entire philosophy wearing an options costume.
Key Takeaway
Every scheduled event runs a public, dated fear cycle: ramp, peak, crush, resolution — correctly priced end to end, with no free money and three honest stances. Selling the peak is underwriting the event (defined-risk, fraction-sized, earned not routine); buying the ramp requires beating the crowd's calendar and the rent; trading the resolution — post-crush premium and post-event structure — is the least crowded stance and costs only patience. Write the stance before the event, weekly, in the map.
Think About It
Your June RBI-week tracking mapped sector impacts in real time. Reread those notes through this chapter: where in the cycle were the best opportunities you saw — the ramp, the peak, or the resolution? Most traders' honest answer to that question relocates their entire event playbook to Stance 3.
Engineering Lab — One Full Cycle, Documented
Pick the next major scheduled event (RBI or a Nifty-heavyweight result). Without trading it: (1) log the affected expiry's ATM straddle price and IV daily from one week out (the ramp, measured); (2) log the final pre-event reading (the peak) and the reading one hour post-announcement (the crush, measured); (3) log the following two sessions' premium levels and structural verdicts (the resolution window). File the complete cycle in QbarTrade with one paragraph: which stance, at what size, would your rules have permitted — and what would it have returned? One documented cycle teaches this chapter permanently; three make the event map's stance column write itself.