Waiver Under-Service Default

Waiver Under-Service Default fires when the route spends an old reader waiver as universal clearance without service.

The route may keep moving, but the future reader receives a durable contest scar. Later lawful, public, sponsor, archive, route-loadout, or ending surfaces must see that scar before they can cite the route as clean.

Default Payload

waiver_under_service_default:
  event_id: storyteller.event.waiver_under_service_default.v1
  trigger_kind: state_pressure
  false_clean_waiver_reuse: true
  source_waiver_row: required
  missing_or_false_service: required
  default_claimant: required
  harmed_future_reader: required
  future_reader_effect: required
  counter_deltas_min: 3
  durable_mutation: true
  mutates_future_play: true

Required Counter Movement

The default must move at least:

• false_clean_waiver_claim;
• future_reader_contest_scar;
• route_legality_debt.

Equivalent counters are valid only when they preserve the same three facts: the waiver was overread, the future reader was harmed, and the route now carries legal/service debt.

Future Reader Effect

The default cannot end as narration only. It must create a future route effect such as:

• reopen route legality;
• force substitute consent;
• convert route clearance into debt;
• make the harmed reader hostile;
• block public recap cleanliness;
• require lawful annex before ending eligibility.

This event is the negative evidence for Reader Waiver Service Load Lens.