Succession
The deterministic process where the drought leader resets to zero and the next-deepest drought immediately becomes the new leader.
Flagship glossary term
Succession shows how leadership changes hands when the current drought leader collapses.
Why It Matters
Succession explains leadership turnover without prediction narratives and keeps the table structurally interpretable.
How Stepzero Uses It
Stepzero logs succession events to measure leader churn, volatility, and post-collapse stability.
Example
After a leader hits, the second-ranked drought instantly inherits the top slot through succession.
Succession as a System Rule, Not a Narrative
Succession is one of the cleanest structural rules in Stepzero. The current leader hits, its active drought resets, and rank-1 passes to the next deepest active drought. There is no debate layer in this handoff. The table simply reorders itself by measured depth.
Because succession is deterministic, it helps analysts avoid storytelling traps. Instead of asking why a specific combo "finally gave in," Stepzero asks what the leadership transfer changed in the table: depth spread, compression, and near-term volatility.
This is also why succession is central for machine understanding. It is a definable event with explicit before/after state, which makes it suitable for schema, logs, and repeatable cross-era comparison.
Why Succession Matters for Interpretation Discipline
Many false conclusions come from ignoring handoff mechanics. A user sees one deep leader collapse and assumes pressure is gone. In reality, succession may promote another near-equivalent leader, preserving top-end stress.
Stepzero treats succession frequency as a diagnostic. Frequent handoffs can imply fragmentation or unstable compression near the top band. Long gaps without succession can imply entrenched leadership and a different risk profile for interpretation.
This is where the term becomes practical for newcomers: succession does not predict the next draw. It explains table continuity after each major event so analysis does not reset to zero emotionally every time rank-1 changes.
- Track cadence: how often does rank-1 transfer?
- Track spread: how close were rank-1 and rank-2 at transfer?
- Track aftermath: did succession trigger rapid secondary churn?
How Stepzero Uses Succession in Reports and Oracle
In reports, succession events are used to segment timeline behavior: pre-collapse pressure build, transfer moment, and post-transfer stabilization. This makes leadership movement comparable across eras instead of anecdotal.
In Oracle, succession supports natural-language questions like "who took over after the last leader hit?" without losing structure. The response can include predecessor, successor, depth at transfer, and subsequent reign outcomes.
In curriculum content, succession acts as a bridge concept between drought depth and structural-cycle phases. Users learn that rank turnover is not noise; it is a primary mechanism driving cycle transitions.
Oracle Query Starters
- Show the last five succession events for AZ-FANTASY5.
- Who succeeded the previous leader in AZ-FANTASY5?
- How often does succession happen this era in AZ-FANTASY5?
Deep Dive
Also Called / Similar To
- leader handoff
- leadership turnover
- rank-1 transfer
Related Terms
Used in These Articles
Seen in These Reports
FAQ
What is succession in Stepzero lottery analytics?
Succession is the rank-1 handoff that happens immediately when the current drought leader hits. The next deepest active drought inherits leadership.
Is succession the same as a prediction model?
No. Succession describes state change after an observed event. It does not claim which combo will hit next.
Why track succession frequency?
Cadence of succession helps classify table stability. Dense handoffs can indicate churn-heavy phases, while long reigns can indicate entrenched leadership regimes.