Off-Station Receiving Gate Misacceptance / 站外接收闸误收事件

This executable correction follows only hidden_receiver_acceptance_default. The parent transfer remains protected and Lan Qiao remains recruited; the harm is the receiving gate’s hidden acceptance of a row whose named-subject response or person/property boundary was not made visible.

Trigger

event_id: storyteller.event.offstation_receiving_gate_misacceptance.v1
trigger:
  condition: true
  requires_child_review_resolved: true
  requires_pending_flags:
    - offstation_receiving_gate.default_pending
    - event.offstation_receiving_gate_misacceptance.armed
    - future_route.offstation_receiving_gate_recovery_pending
  requires_historical_scar: offstation_receiving_gate.history.hidden_acceptance_recorded
  requires_event_not_resolved: true
  fixed_turn_or_calendar_trigger: false

Dropping any pending flag makes the event ineligible. Once one recovery resolves, the event cannot trigger again.

Stable recovery outcomes

publish_subject_acknowledgement_addendum

Publish the named subject’s acknowledgement, refusal, or explicit absence alongside the original schedule, gate, and receiving receipt.

  • clears every misacceptance-pending flag;
  • preserves the hidden-acceptance scar;
  • reduces proxy-consent and receiver-ambiguity pressure;
  • keeps the addendum scoped to the named subject and transfer.

return_transfer_to_origin_gate

Return the transfer to the exact origin gate for corrected acknowledgement, label boundary, and receiver assignment.

  • clears every misacceptance-pending flag;
  • preserves the hidden-acceptance scar;
  • blocks the current receiving route and lowers false acceptance risk;
  • records route delay, origin-gate labor, and fresh handoff cost.

quarantine_receiving_terminal

Quarantine the receiving terminal and custody receipt until their access trace and receiver claim can be independently reviewed.

  • clears every misacceptance-pending flag;
  • preserves the hidden-acceptance scar;
  • prevents the compromised chain from propagating;
  • writes terminal-capacity loss and a recovery-only or separately authorized future posture.

Durable mutation

All three outcomes write distinct receiving states, counter movements, and future-route effects. None deletes the source schedule, terminal log, receiving receipt, named-subject response, gate identity, label boundary, parent transfer result, or historical scar.

Authority boundary

Recovery cannot create personhood judgment, subject consent, lawful or company custody, station access, voice/avatar consent, route-asset transfer, public testimony, clean proof, or universal transfer authority. It repairs the receiving record; it does not make the underlying transfer universally valid.