Ticket Stub Reissue Liability
A fan-facing route tries to spend an old ticket stub after the broadcast desk has reissued the same seat to a sponsor guest. The system must not treat the reissue as a clean replacement. It creates a liability row naming the original stub, old holder, new claimant, reissue authority or explicit absence, displaced reader, selected posture, and future route effect.
Entry
Open this storyline when a future reader or route attempts to consume a reissued seat/stub pair and these state surfaces are visible:
- source ticket stub row;
- old holder and new claimant;
- reissue authority or explicit absence;
- displaced reader;
- future reader or route that wants to use the stub;
- no clean universal replacement flag.
This is state pressure, not a fixed turn, raw ticket count, dashboard state, refund total, or lens-health trigger.
Playable Branches
Run Ticket Stub Reissue Review after Ticket Stub Reissue Docket is created.
certify_narrow_reissue: the sponsor copy can be used only inside a named scope while the old holder remains visible.compensate_displaced_holder: the reissue proceeds after the displaced holder receives costed relief.quarantine_double_claim: both copies are blocked until archive proof agrees.sponsor_public_copy: the sponsor/public copy leads, but the old holder becomes a future claimant.false_clean_reissue_default: the desk treats the reissue as clean and pushes the omitted holder into a future default.
Outcomes
Every branch must move at least three pressure surfaces such as public trust, sponsor pressure, claimant heat, route delay, archive heat, and receipt integrity. The selected posture must be visible to later route assets so future scenes cannot spend the reissued stub without carrying the liability scar.
Related
- Ticket Stub Reissue Liability defines the state-pressure contract.
- False Clean Ticket Reissue Default records the hidden-clean failure state.
- Fan Oxygen and Route Assets and Custody consume the later reader pressure.