L2 — Player in Match-State

How a player performs by match state: first-innings (setting target), chase (batting second), or defend (bowling second). Surfaces the "how do they do in chases" question every fan asks.

Period: IPL 2026. Sample-size floor: ≥50 balls faced. Suppressed cells render the URI with the parent L1 link instead of metrics.

Conditioning dimensions

match_state — derived from the per-ball `scoreboard` ordinal (S1 = first innings, S2 = second innings). Rain-curtailed / D-L revised games surface as "unknown" — these games are NOT folded into the chase or defend buckets.

Sample-size floor + rationale

≥50 balls faced per cell.

3-bucket match-state collapses to fewer cells than UC1/UC4; a higher floor preserves citation credibility ("performs in chases" is a big claim).

Suppression rule

Standard L2 contract.

Update cadence

Standard.

Known limitations

D-L revised targets create ambiguous match states — those balls go to "unknown" rather than being silently classified.
Floor is higher than UC1/UC2 (50 balls vs 20-30) because the 3-bucket conditioning collapses to fewer cells; a higher floor preserves citation credibility.

Change log

2026-05-13 · Phase 1 launch. Floor: ≥50 balls faced.

Consumed by

UC3: /players/{slug}/in/{match-state}/