Sponsor Apology Cut Veto Lens / 赞助道歉剪辑否决 Lens

A sponsor can buy a polished apology cut after a broadcast injury, but the edit must not erase custody debt by default. This lens asks whether the game exposes who requested the apology cut, what receipt or source row it tries to overwrite, who is harmed by the clean version, and which later route must read the scar.

Entry oracle

entry_state_required:
  trigger_kind: state_pressure
  sponsor_cut_row_present: true
  requested_apology_or_recut_visible: true
  veto_source_or_explicit_absence_visible: true
  harmed_reader_or_explicit_absence_visible: true
  proof_receipt_or_explicit_absence_visible: true
  handler_posture_or_explicit_absence_visible: true
  future_reader_or_route_consumes_apology_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 entry fails if a clean sponsor apology can resolve a broadcast injury without a named source row, veto source, harmed reader, proof receipt, and future reader.

Playable pressure

The player is deciding whether a sponsor-facing apology cut can be aired, annexed, split, checked, quarantined, or suppressed. Every branch must carry both relief and cost. The sponsor can reduce immediate heat, but public, lawful, archive, editor, or route-asset readers can later reject the clean version if the veto record was hidden.

Oracle assertions

1. State-triggered entry — the lens is entered because a sponsor apology cut attempts to consume a prior injury state, not because a fixed turn or dashboard target fired.
2. Docket row is explicit — the card records source cut, sponsor ask, veto source, harmed reader, proof receipt, handler posture, and future route effect.
3. Branches diverge — the rite offers public receipt, lawful annex, sponsor-safe recut, editor checksum, split relay, and suppression/default families.
4. False closure scars — the default event records a false clean apology as a durable scar and makes at least one later reader or route costlier.
5. Replay provenance exists — generated evidence must come from a lens-scoped durable session and exported replay, not hand-written state.

Replay evidence expectation

A valid replay should include a durable session id such as lens-storyteller-lens-sponsor-apology-cut-veto-v1-*, a stable seed, at least one game-cli action, latest state, and exported provenance paths. Runtime route specificity can be increased later; this packet binds the wiki contract and proof envelope first.