Usher Lantern Handoff Receipt Lens / 引座灯笼交接回执 Lens

Observable promise

A lantern handoff is not a generic kindness token. It is a custody object for who guided a displaced audience row through a blackout, whose safety claim later enters route accounting.

Entry oracle

entry_state:
  trigger_kind: state_pressure
  displaced_row_visible: true
  lantern_source_row_visible: true
  original_usher_or_explicit_absence_visible: true
  receiving_handler_visible: true
  requested_afteruse_visible: true
  future_reader_consumes_lantern_state: true
  safety_or_claimant_change_or_explicit_absence_visible: true
  proof_bridge_or_explicit_absence_visible: true
  harmed_audience_or_crew_visible_or_explicit_absence: true
  no_fixed_turn_trigger: true
  no_dashboard_or_lens_health_trigger: true

The lens fails if it opens from a fixed turn, dashboard score, raw lens count, or a vague “help the audience” task.

Must pass

The docket must keep the source row and attempted future use separate. The review must assign a carrier, handler, safety posture, receipt surface, relief, cost, and future route effect. The default event must leave a scar when the lantern is treated as false-clean evidence.

Branch assertions

Valid branch families include certify_handoff_scope, route_to_safety_reader, attach_usher_witness, split_light_from_custody, sponsor_guidance_package, quarantine_lantern_afteruse, false_lantern_default, and future_effect_any.