Service Recipient Authority Docket / 送达受领权限案卷

Service Recipient Authority Docket records a service attempt when the chosen recipient is not automatically valid for the reader who will later consume the notice.

It is not a notice receipt by itself. 容量告知送达队列线 already proves that a claimant was served or omitted. 集体代表委任漂移线 already proves that old representative authority can drift. This card binds the seam: the player must show whether the person, desk, delegate, operator, witness, proxy, or carrier who received service had current authority for the intended reader.

Required payload

service_recipient_authority_docket_required:
  source_service_row:
    source_row_id: <stable service notice or remedy row id>
    source_surface: capacity_notice_service | reader_rebuttal_notice | access_caption_class | excluded_counterreceipt | remedy_reinstatement_bond | witness_carrier_discharge | substitute_carrier_requisition | equivalent
    service_purpose: capacity_notice | rebuttal_notice | callback | correction | counterreceipt | reinstatement | class_addendum | route_release | equivalent
    intended_reader: access_caption_reader | excluded_constituency | fan_public | lawful_reader | sponsor | archive | route_claimant | broadcast_reality | equivalent
    affected_cohorts: []
    future_reader_or_route: <reader route package proof window or broadcast reality surface>
  recipient_authority:
    selected_recipient: <actor desk carrier delegate proxy or explicit_absence>
    recipient_class: class_representative | fan_delegate | access_operator | witness_carrier | lawful_clerk | sponsor_desk | archive_desk | proxy_runner | explicit_absence | equivalent
    authority_source_row_or_absence: <representative mandate service receipt carrier discharge annex or explicit_absence>
    authority_scope: public_only | lawful_only | sponsor_only | archive_only | route_only | named_cohort_only | split_required | explicit_absence | equivalent
    authority_state_before: active | limited | withdrawn | discharged | substituted | captured | hostile | absent | quarantined | unknown | equivalent
    authority_state_at_service: current | stale | limited | refused | proxy_only | absent | disputed | equivalent
    proof_of_current_authority_or_absence: <receipt renewal notice mandate annex public addendum witness oath or explicit_absence>
  service_attempt:
    service_carrier_or_absence: <carrier actor surface or explicit_absence>
    delivery_surface: public_notice | lawful_annex | sponsor_notice | archive_stamp | fan_receipt | caption_addendum | runner_receipt | route_asset_packet | equivalent
    service_claim: recipient_can_accept_for_all | recipient_accepts_named_scope | proxy_accepts | absence_as_service | old_mandate_as_current | equivalent
    omitted_or_deferred_readers: []
    service_proof_or_absence: <proof or explicit_absence>
  state_after:
    selected_posture: verify_current_recipient | re-serve_named_reader | split_service | substitute_recipient | publicize_authority_gap | escrow_service | quarantine_service | default_recipient_service
    service_state_after: served_named_scope | reservice_required | split_required | public_only | lawful_only | sponsor_only | escrowed | quarantined | false_served | recovery_only | equivalent
    recipient_state_after: current_limited | substituted | protected_refusal | exposed | captured | hostile | absent | false_authority | equivalent
    future_reader_or_route_effect: callback_required | addendum_required | reservice_required | audit_required | route_delay | blocked | hostile | costlier | recovery_only | contradiction_pending | equivalent

The card fails if it only records notice sent, representative received, operator signed, sponsor acknowledged, lawful annex filed, or runner delivered without the recipient authority state and the future reader.

Player-facing use

Surface this as an operational docket on the production desk. The playable question is: did we serve the person who can actually accept for this reader now?

A constructive branch must always preserve the original service row, name the intended reader, name the recipient or explicit absence, and mutate a future route or reader. A default must leave a durable false-service scar instead of resolving as flavor.

Non-goals

• Not a generic legal-notice card.
• Not a replacement for capacity notice service.
• Not a new class certification card.
• Not valid unless a future reader or route will consume the service state.