Lan Qiao Off-Station Transfer Docket / 蓝桥站外换乘案卷

This evidence docket keeps one D-17 person-to-property transfer legible without turning the transfer list into personhood, consent, protocol, testimony, custody, or access authority.

Exact runtime fields

The runtime card storyteller.card.lan_qiao_offstation_transfer_docket.v1 requires these exact nineteen fields:

required_fields:
  - source_rite
  - source_branch
  - named_subject_or_explicit_absence
  - origin_gate
  - departure_gate
  - receiving_gate_or_explicit_absence
  - transfer_list_row
  - reclassification_label
  - terminal_access_log
  - handoff_receipt_or_explicit_absence
  - receiving_custodian_or_explicit_absence
  - subject_acknowledgement_or_refusal_or_explicit_absence
  - company_claim_or_explicit_absence
  - witness_or_explicit_absence
  - selected_posture
  - lan_qiao_state_after
  - transfer_state_after
  - future_reader_effect
  - counter_deltas

Explicit absence is evidence. Blank, omitted, inferred, borrowed, or generic values are not.

Supporting runtime cards

Runtime cardDocket roleAuthority limit
storyteller.card.lan_qiao_offstation_transfer_schedule.v1opening, departure window, receiving gateschedule is not consent or property status
storyteller.card.lan_qiao_terminal_access_log.v1badge/operator terminal touch and timelog grants neither K-404 protocol nor station access
storyteller.card.lan_qiao_receiving_custody_receipt.v1receiving desk, claimant, handoff gap, disputed labelreceipt does not create lawful custody
storyteller.card.lan_qiao_future_reader.v1named later consumer of the transfer rowreader must respect posture and future effect

When branch 0 opens the receiving-gate child review, that review reuses exactly these four supporting cards and combines them with four child-produced counterreceipt cards. It does not assign this parent docket or Lan Qiao as a child slot, and it cannot recruit her again.

Forbidden inferences

The runtime docket forbids these exact shortcuts:

forbidden_inferences:
  - transfer_list_equals_personhood_judgment
  - property_label_equals_voice_or_avatar_consent
  - lan_qiao_equals_subject_consent
  - terminal_log_equals_k404_protocol_authority
  - transfer_witness_equals_fan_testimony
  - company_claim_equals_custody_authority
  - route_asset_equals_station_access

These denials bind every branch, future reader, replay, and recovery attempt.

Refusal recording

Choice 4, honor_transfer_refusal_and_stop_handoff, writes the refusal result into subject_acknowledgement_or_refusal_or_explicit_absence and resolves:

refusal_result:
  lan_qiao_state_after: protected_refusal_handoff_stopped
  transfer_state_after: handoff_stopped_without_proxy_consent
  future_reader_effect: fresh_subject_acknowledgement_required
  separate_refusal_card: false
  proxy_consent: false

The replay must not assign or invent an additional refusal card.

Identity rule

The assigned transfer clerk and witness is Lan Qiao / 蓝桥, runtime card card-storyteller-lan-qiao. The named transfer subject remains a separate docket field; Lin Qiao / 林乔 is a different character and cannot satisfy the lan_qiao assignment.

Completeness rule

The docket is complete only when all nineteen fields, the selected branch’s exact three state strings, its six effect-backed counter deltas, and the actual runtime assignments are replay-visible. A catalog row or Wiki description alone is not evidence.