Concession Raincheck Afteruse Receipt

Mechanically, the player must inspect a state-pressure docket before a future route uses the raincheck. The docket records source row, patron/absence, stall/date context, cited service scope, requested afteruse, harmed claimant, proof bridge, selected posture, after-state, future route effect, and counter deltas.

Branches must change counters and future route flags. Certification keeps service scope narrow; restriction names a reader; patron bridge adds proof; claimant reopening surfaces harm; split separates service apology from likeness custody; quarantine blocks afteruse; false-clean default creates durable recovery-only future play.