Encore Applause Holdback Lens

This lens observes whether encore applause can become contested playable pressure when a sponsor-safe recap counts audience satisfaction before the fan-public receipt is served. It ties broadcast-reality management to fan oxygen, route assets, and proof custody.

Entry oracle

entry_state_required:
  trigger_kind: state_pressure
  source_applause_row_visible: true
  claimed_satisfaction_credit_visible: true
  holding_actor_visible: true
  proof_carrier_or_absence_visible: true
  omitted_fan_reader_visible: true
  future_reader_or_route_consumes_applause_state: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_dashboard_or_lens_health_trigger: true

The lens fails if the applause holdback opens from a fixed turn, raw applause count, dashboard state, or generic backlog instead of visible proof pressure.

Docket oracle

encore_applause_holdback_docket:
  source_applause_row: <row>
  claimed_satisfaction_credit: <credit>
  holding_actor: <actor>
  proof_carrier_or_absence: <proof or explicit_absence>
  omitted_fan_reader: <reader>
  accepted_cost_or_absence: <cost or explicit_absence>
  applause_state_after: <state>
  future_reader_or_route_effect: <effect>

Hearing oracle

Accepted branch families: publish_fan_receipt, escrow_archive_copy, split_sponsor_fan_credit, convert_to_route_debt, quarantine_recap_claim, accept_scoped_holdback, false_clean_applause_default, and future_effect_any. Every constructive branch includes relief, cost, and a future route effect.

Replay evidence

A durable lens-scoped replay must resolve storyteller.rite.encore_applause_holdback_hearing.v1 and export to lens/replays/encore-applause-holdback.replay.json with session id and seed provenance.

Progress metric

encoreApplauseHoldbackProgress = 0..6: source row, claimed credit, holding actor/proof/omitted reader, docket fields, branch spread, default mutation, durable replay.