Reader Waiver Service Load Mechanics

Reader Waiver Service Load opens from state pressure when a completed waiver is asked to do new route work.

The mechanic prevents old waiver rows from being used as generic permission. A waiver remains playable only if the source row, surface, reader boundary, service carrier, protected boundary, route use, selected posture, future effect, and costs stay observable.

Required State

reader_waiver_service_load:
  trigger_kind: state_pressure
  source_waiver_row_visible: true
  source_surface_visible: true
  original_waived_reader_or_explicit_absence_visible: true
  future_reader_or_route_visible: true
  requested_reuse_visible: true
  service_carrier_or_explicit_absence_visible: true
  protected_boundary_or_explicit_absence_visible: true
  selected_service_posture_visible: true
  future_route_effect_visible: true
  counter_deltas_after_service: min_3

Forbidden triggers: fixed turn, fixed day/week, raw waiver count, dashboard state, or lens-health state.

Service Postures

service_postures:
  certify_narrow_service:
    relief: served surface can proceed
    cost: universal clearance is narrowed
    future_route_effect: narrow scar visible
  serve_new_reader_notice:
    relief: future reader receives service
    cost: route is delayed
    future_route_effect: notice-pending route
  split_future_reader:
    relief: source waiver remains valid for source reader
    cost: future reader loses bundled clearance
    future_route_effect: split-reader route
  escrow_waiver_carrier:
    relief: carrier remains inspectable
    cost: route clearance is suspended
    future_route_effect: carrier-held route
  convert_to_waiver_debt:
    relief: route can proceed
    cost: future service remains due
    future_route_effect: debt-tagged route
  quarantine_reuse:
    relief: protected boundary survives
    cost: substitute consent required
    future_route_effect: blocked until substitute consent
  under_service_default:
    relief: route proceeds immediately
    cost: future reader contest scar hardens
    future_route_effect: false clean route clearance

Counter Contract

Every non-default branch must move at least three counters. Valid counter families include:

• waiver_scope_certified
• future_reader_notice_served
• clean_route_clearance_narrowed
• new_reader_notice_served
• route_use_delayed
• reader_split_recorded
• consent_gap_visible
• waiver_carrier_escrowed
• archive_review_heat
• waiver_debt
• future_service_due
• waiver_reuse_quarantined
• sponsor_route_delay
• voice_custody_protected

The under-service default moves false-clean waiver, future-reader contest, and route-legality debt counters.

Invalid Shortcuts

The mechanic fails if:

• the source waiver row is not visible;
• the original reader and future reader collapse into one anonymous consumer;
• the service carrier or explicit absence is missing;
• the protected boundary is hidden;
• a route can use the waiver as clean universal clearance without a future route effect;
• the branch moves fewer than three counters.