Reader Waiver Service Review

Reader Waiver Service Review asks the player to assign the waiver docket, source row, source surface, original reader, future reader, requested reuse, carrier/proof state, protected boundary, selected posture, and future route effect.

The rite is playable and repeatable, but it is not a calendar chore. It opens only when a prior waiver is being reused for new route work.

Required Assignments

slots:
  docket: storyteller.card.reader_waiver_service_docket.v1
  source_waiver_row: required
  source_surface: required
  original_reader_or_absence: required
  future_reader_or_route: required
  requested_reuse: required
  service_carrier_or_absence: required
  protected_boundary_or_absence: required
  selected_posture: required
  future_route_effect: required

Branch Families

branch_families:
  - certify_narrow_service
  - serve_new_reader_notice
  - split_future_reader
  - escrow_waiver_carrier
  - convert_to_waiver_debt
  - quarantine_reuse
  - under_service_default
  - future_effect_any

Every branch must preserve the source waiver row, name relief and cost, mutate at least three counters, and leave a visible future-route effect.

Branch Map

BranchPlayer decisionRequired counter movementFuture route effect
certify_narrow_serviceCertify only the served waiver surface and keep the scar on the route asset.waiver_scope_certified, future_reader_notice_served, clean_route_clearance_narrowednarrow scar visible
serve_new_reader_noticeServe a fresh notice to the future reader before reuse.new_reader_notice_served, route_use_delayed, notice_proof_creatednotice-pending route
split_future_readerSplit the future reader from the source waiver and require separate consent.reader_split_recorded, consent_gap_visible, route_asset_scope_reducedsplit-reader route
escrow_waiver_carrierEscrow the waiver carrier until archive can prove service.waiver_carrier_escrowed, archive_review_heat, route_clearance_suspendedcarrier-held route
convert_to_waiver_debtLet the route proceed as waiver debt instead of clean clearance.waiver_debt, scene_can_proceed, future_service_duedebt-tagged route
quarantine_reuseQuarantine the waiver reuse and require substitute consent.waiver_reuse_quarantined, sponsor_route_delay, voice_custody_protectedsubstitute consent required
under_service_defaultAllow the old waiver to pass as clean clearance and mark the future contest scar.false_clean_waiver_claim, future_reader_contest_scar, route_legality_debtfalse clean route clearance

Resolution Payload

reader_waiver_service_resolution:
  source_waiver_preserved: true
  relief: required
  cost: required
  future_route_effect: required
  counter_delta_count: min_3
  source_surface_remains_visible: true
  future_reader_or_route_remains_visible: true

The rite fails if it lets a route take the waiver without one of these records.