Off-Station Receiving Gate Counterreceipt / 站外接收闸反签回执线
The parent transfer review has already recruited and protected Lan Qiao, named the origin and receiving chain, and emitted named_origin_gate_receiver_required. This child storyline makes one concrete downstream consumer playable: the receiving gate must countersign, return, refuse, freeze, publish, or quarantine that already-protected transfer before a later reader may rely on it.
This is not another Lan Qiao recruitment. Lan Qiao does not occupy a child slot, and the receiving desk cannot reopen her person-state. The child consumes the protected transfer result and decides only what the receiving gate may certify about one named handoff.
Canonical parent gate
parent_contract:
parent_rite_id: storyteller.rite.lan_qiao_offstation_transfer_review.v1
required_parent_choice_index: 0
required_parent_choice_id: recruit_protected_transfer_list_witness
required_parent_completion: complete_storyteller.rite.lan_qiao_offstation_transfer_review.v1
required_parent_state: lan_qiao.state.recruited_protected_transfer_list_witness
required_parent_future_effect: lan_qiao.future.named_origin_gate_receiver_required
required_readiness_flag: offstation_receiving_gate.parent.protected_named_transfer_ready
other_parent_choices_open_child: false
parent_result_gains_exactly:
- storyteller.card.offstation_receiving_gate_counterreceipt.v1
- storyteller.card.offstation_named_subject_acknowledgement.v1
- storyteller.card.offstation_receiving_gate_d17.v1
- storyteller.card.offstation_person_property_label_boundary.v1
The four gained cards are non-starter child rows. The other four assignments are real transfer cards already present in the protected parent packet. No virtual slot, branch token, generic evidence card, or catalog-only card can replace them.
Storyline spine
Beat 1 - Protected transfer reaches the receiving boundary
Resolve storyteller.rite.lan_qiao_offstation_transfer_review.v1 with choice 0, recruit_protected_transfer_list_witness. The result keeps Lan Qiao recruited, writes the parent-ready flag, and materializes the four child cards. Choices 1-7 remain valid parent endings, but none opens this receiving-gate review.
Beat 2 - Eight exact rows form one receiving docket
The receiving review accepts these cards in this exact order:
storyteller.card.offstation_receiving_gate_counterreceipt.v1storyteller.card.lan_qiao_offstation_transfer_schedule.v1storyteller.card.lan_qiao_terminal_access_log.v1storyteller.card.lan_qiao_receiving_custody_receipt.v1storyteller.card.offstation_named_subject_acknowledgement.v1storyteller.card.offstation_receiving_gate_d17.v1storyteller.card.offstation_person_property_label_boundary.v1storyteller.card.lan_qiao_future_reader.v1
The selected receiving posture comes from the rite choice. There is no posture prop card and no second Lan Qiao card.
Beat 3 - The receiving gate chooses one bounded response
| Choice | Option ID | Receiving-gate result |
|---|---|---|
| 0 | countersign_named_receiver | Countersign only the named origin, receiver, gate, and custodian; the desk inherits audit liability. |
| 1 | return_for_subject_acknowledgement | Return the packet for missing, refused, or disputed subject acknowledgement; route delay and protection cost rise. |
| 2 | seal_person_first_exception | Seal a person-first exception without deciding personhood; independent review remains due. |
| 3 | publish_receiving_gate_addendum | Publish the gate discrepancy and receiving addendum; public accountability rises with exposure and correction cost. |
| 4 | freeze_company_receiver_claim | Freeze the company receiver’s attempt to convert receipt into custody; current transfer use stalls. |
| 5 | refuse_unlawful_handoff | Refuse a handoff whose origin, subject response, or receiver is not lawful enough to countersign. |
| 6 | quarantine_receiving_chain | Quarantine the terminal/receipt chain; propagation stops while recovery cost rises. |
| 7 | hidden_receiver_acceptance_default | Accept the transfer without exposing the named-subject or label boundary; arm the durable misacceptance recovery. |
Every option writes one exclusive receiving state, visible relief, visible cost, and a distinct future-reader effect. Countersigning records what one receiving gate accepted; it does not validate the transfer’s personhood, consent, custody, or universal route authority.
Beat 4 - Hidden acceptance receives a scarred correction
Only hidden_receiver_acceptance_default arms storyteller.event.offstation_receiving_gate_misacceptance.v1. The event offers exactly three recovery postures:
publish_subject_acknowledgement_addendum;return_transfer_to_origin_gate;quarantine_receiving_terminal.
Each recovery clears the pending incident, preserves offstation_receiving_gate.history.hidden_acceptance_recorded, and writes a distinct future route posture. Correction cannot retroactively turn hidden acceptance into lawful custody or subject consent.
Runtime-evidence expectation
The lens expects two real Storyteller Game CLI chains:
- parent choice 0 followed by child choice 0 with all eight exact in-hand assignments;
- parent choice 0 followed by child choice 7 and one executable recovery choice.
Wrong parent choices, missing or substituted cards, out-of-hand assignments, generic branch cards, omitted choices, repeat resolution, and cross-source objects must fail.
Non-duplication and authority boundary
- offstation-transfer-custody-readback owns the parent transfer result and eight emitted reader obligations. This child implements only the concrete branch-0 receiving consumer.
- lan-qiao-offstation-transfer-clerk owns Lan Qiao’s recruitment, refusal, capture, hostility, and missability. The receiving gate never recruits her again.
- lost-and-found-label-afteruse-receipt owns later reuse of an object label. This child checks a receiving gate before it countersigns the person/property transfer chain.
- The receiving desk does not decide personhood, author subject consent, grant lawful or company custody, open station access, transfer a route asset, create public testimony, or turn one receipt into clean universal transfer proof.
Only source: storyteller content may satisfy this storyline.