Backchannel Applause Escrow / 后台掌声托管机制

Backchannel applause escrow turns invisible audience support into a named state object. A prior report may count applause internally, but routes that need public consent must still read who held it, who was omitted, and what was charged.

Required state row

backchannel_applause_escrow:
  trigger_kind: state_pressure
  counted_internally: true
  public_receipt_missing_or_redacted: true
  escrow_holder: sponsor_backchannel | management_backchannel | archive_proxy
  harmed_reader: fan_claimant_table | encore_route_reader | memorial_reader
  future_reader_present: true
  player_response_available: true
  no_fixed_turn_trigger: true

Resolution contract

Each branch must name relief, cost, and future reader effect. A clean internal applause number must never satisfy every reader by itself.

Branch	Relief	Cost	Future effect
release public receipt	public legitimacy	sponsor capture + inspection heat	accepted with cost
archive custody proof	archive legitimacy	delayed fan receipt	custody proof route
sponsor makegood conversion	sponsor pressure relief	fan refund debt + route narrowing	sponsor-contested access
default escrow	short management quiet	surcharge + narrowed route	public reader narrates first

Downstream afteruse

Backchannel Applause Afteruse Receipt starts only after this escrow state exists. It prevents a released, archived, sponsor-converted, or defaulted applause row from becoming clean universal stability for a later reader without source row, holder, proof bridge, harmed reader, selected posture, and future route effect.