Off-Station Transfer Custody Readback / 站外换乘羁押回读线

Lan Qiao’s character storyline decides whether the transfer clerk is recruited, retained, captured, hostile, or missed. This system-facing storyline asks the next question: what may a later reader do with the transfer row after Lan Qiao’s disposition is already fixed?

The distinction matters because a company desk, inspector, public hearing, receiving station, named subject, or recovery route can otherwise read only transfer complete and silently erase the origin gate, reclassification label, receiving custodian, acknowledgement or refusal, and the cost attached to the selected branch.

Entry State

Open this storyline only when an identified later reader is about to consume the resolved off-station transfer state:

entry_state:
  trigger_kind: state_pressure
  source_rite_resolved: storyteller-rite-d17-lost-and-found-night
  transfer_review_resolved: storyteller.rite.lan_qiao_offstation_transfer_review.v1
  transfer_docket_present: true
  named_future_reader_present: true
  transfer_state_after_visible: true
  future_reader_effect_visible: true
  receiving_gate_or_explicit_absence_visible: true
  receiving_custodian_or_explicit_absence_visible: true
  acknowledgement_or_refusal_or_explicit_absence_visible: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

The storyline does not reopen from generic station pressure, a fixed episode beat, or the mere presence of a lost-property label. A concrete future reader must be trying to rely on the resolved row.

Bound Content Pack

• Property Transfer Custody defines the source row and eight stable transfer outcomes.
• Lan Qiao Off-Station Transfer Clerk owns Lan Qiao’s person-state, recruitment, hostility, and missability.
• Lan Qiao Off-Station Transfer Docket carries the source branch, gates, reclassification, handoff, receiving custodian, subject response, transfer state, and future-reader effect.
• storyteller.card.lan_qiao_future_reader.v1 makes the consuming reader a required runtime assignment rather than an implied audience.
• Lan Qiao Off-Station Transfer Review writes one of eight non-equivalent readback obligations.
• Lan Qiao Shift-End Default makes a scrubbed row recovery-only instead of silently clean.
• Off-Station Transfer Custody Readback Lens observes the system-facing contract.
• Off-Station Receiving-Gate Counterreceipt is the separate downstream consumer for branch 0 only; it verifies the named receiving gate without reopening Lan Qiao’s disposition.

Storyline Spine

Beat 1 - D-17 writes a source transfer row

storyteller-rite-d17-lost-and-found-night records whether the source encounter was person-first or company-cleanup. It also introduces the actual Lan Qiao card, transfer schedule, terminal access log, company claimant, and the trust/debt pressure that makes later review reachable.

The source rite is evidence of an encounter and transfer attempt. It is not a personhood ruling, consent record, protocol grant, lawful custody order, or station credential.

Beat 2 - The review writes a reader obligation

The eight-slot review requires the exact docket, Lan Qiao, terminal, company claimant, transfer schedule, access log, receiving-custody receipt, and named future reader. Its selected branch must write both transferStateAfter and futureReaderEffect.

The readback surface fails if a future reader receives only a generic success/failure flag or if the reader assignment can be omitted.

Beat 3 - The review emits a branch-specific limit before future use

Source branch result	What the later reader must preserve
protected_named_transfer_custody	named subject, origin, departure, receiving gate, and custodian
person_first_rows_preserved	an independent personhood reader; the transfer row cannot decide personhood
disputed_rows_escrowed	a lawful reclassification hearing before reuse
transfer_list_public	a public transfer receipt; publication is not consent
handoff_stopped_without_proxy_consent	fresh subject acknowledgement before a new handoff
company_captured_transfer_list	company-only evidence, not lawful custody
transfer_list_erased	hostile countertestimony and an explicit evidence gap
shift_log_scrubbed	recovery-only use; no silent restoration of recruitment or custody

These obligations are not interchangeable. A company reader cannot consume public disclosure as custody; a public reader cannot consume a transfer list as consent; a recovery reader cannot turn a scrubbed list into a clean route.

This parent wrapper’s runtime evidence still stops at the emission boundary across all eight branches: the selected option keeps transferStateAfter in exact option metadata and emits lan_qiao.future.<futureReaderEffect> while the named future-reader card is assigned. A separate receiving-gate counterreceipt review now consumes branch 0, recruit_protected_transfer_list_witness, as one concrete second hop with strict assignments, a focused runtime test, and two integrity-valid Game CLI replays for countersignature and hidden-acceptance recovery. That child does not prove second-hop consumers for branches 1 through 7, and neither wrapper claims a replay-populated nineteen-field parent docket instance.

Beat 4 - Character state and transfer state stay separate

Recruiting Lan Qiao grants the narrow route asset route_asset.lan_qiao_offstation_transfer_clerk, but the asset can attest only to one transfer-list author, source branch, gate chain, handoff receipt, and custodian row. It cannot author the subject’s response or promote the row into broader authority.

Refusal keeps Lan Qiao present without recruiting her. Company capture and scapegoating remove her for different reasons. Shift end removes her and then resolves the durable default. Later readers must preserve those differences.

Beat 5 - Four durable paths prove the reader obligation is emitted in play

The existing runtime evidence covers four materially different system outcomes:

• protected recruitment keeps the actual witness and grants only the narrow route asset;
• recorded refusal keeps the witness but requires fresh subject acknowledgement;
• scapegoating removes the witness and leaves hostile countertestimony;
• shift end removes the witness, resolves the default, and leaves recovery-only evidence.

Static branch metadata covers the other four reader obligations in the same stable order. The lens must fail if those metadata rows collapse to one universal transfer accepted result. Off-Station Receiving-Gate Counterreceipt is that separate implementation seam for protected branch 0; the other seven branches remain emitted obligations without a claimed downstream consumer in this packet.

Lost-Property Afteruse Boundary

Lost-and-Found Label Afteruse Receipt governs a later citation of an already-existing object label. This storyline governs consumption of the earlier person-to-property transfer chain itself: authoring branch, named subject or absence, origin and departure, receiving gate, terminal touch, handoff, custodian, and subject response.

Neither storyline can substitute for the other. A scoped object label cannot reconstruct a missing transfer chain, and a complete transfer row does not authorize later reuse of an object label.

Non-Goals

• Not a second Lan Qiao recruitment route.
• Not another generic afteruse-receipt packet.
• Not a decision about whether the named subject is a person or property.
• Not subject consent, terminal authority, lawful company custody, fan testimony, or station access.
• Not Lin Qiao’s chain-runner delivery authority.
• Not, by itself, proof that every emitted branch has a second-hop consumer; the child runtime test and durable replays exercise only branch 0, while this parent lens observes assignment, posture metadata, emitted reader flags, and durable default state across all eight branches.