Caption Translation Waiver Mismatch

A translated caption waiver becomes dangerous when production treats it as clean consent for every future reader. The source caption may be live, delayed, edited, or machine-translated; the reader may not share the translated language; the signer may only have waived delay for one cut, not route-asset reuse.

State-triggered entry

trigger_kind: state_pressure
source_caption_row_present: true
translated_caption_row_visible: true
waiver_scope_visible: true
reader_language_mismatch_visible: true
signer_or_delegate_visible_or_absent: true
proof_bridge_or_explicit_absence_visible: true
future_reader_consumes_waiver_state: true
no_fixed_turn_trigger: true
no_fixed_day_or_week_trigger: true
no_raw_count_trigger: true
no_dashboard_or_lens_health_trigger: true

The storyline opens when a future route, sponsor asset, editor cut, or public access reader tries to spend a translated waiver row as if it were universally legible consent.

Play pressure

The player must choose whether to certify a narrow translation, narrow the waiver, order retranslation, publish access notice, escrow lawful caption use, substitute a signer with a scar, quarantine unreadable caption use, or allow a false clean waiver default.

No route may treat the waiver as universally clean unless it preserves source/translated language, reader language, scope, signer/delegate, proof bridge, cost, and future reader effect.