Lin Qiao Chain-Safe Small Delivery / 林乔安全小件交接线

Bound character: 交接链跑腿.

The parent Lin Qiao Chain Runner Storyline can recruit and protect 林乔, convert her into route_asset.lin_qiao_custody_runner, and set rite.chain_safe_small_delivery.unlocked. This follow-on makes that unlock playable.

The central pressure is not whether 林乔 can carry another packet. It is whether production can keep a “small, safe delivery” from becoming permission to move every receipt invisibly through the same low-rank worker.

Entry state

This storyline opens only after protected recruitment and when a named packet needs a physical handoff.

entry_state:
  trigger_kind: state_pressure
  route_asset_lin_qiao_custody_runner: true
  chain_safe_small_delivery_unlocked: true
  named_delivery_packet_visible: true
  source_custodian_visible_or_explicit_absence: true
  destination_custodian_visible_or_explicit_absence: true
  future_reader_can_consume_delivery_state: true
  no_fixed_turn_trigger: true

If 林乔 is missed, hostile, unprotected, or only implied by a generic courier tag, the rite remains blocked.

Story beats

Beat 1 — The first packet after recruitment

A receipt packet, archive docket copy, memorial-air receipt, or voice-custody receipt needs to move. The producer creates Lin Qiao Chain-Safe Delivery Docket and names:

• the packet;
• source and destination custodians;
• 林乔’s protected route-asset state;
• payment or protection;
• receipt proof;
• delivery lane;
• future reader;
• selected posture and future effect.

Beat 2 — Safety becomes an assignment, not an adjective

Lin Qiao Chain-Safe Small Delivery requires the runner, docket, packet, source, destination, protection/payment, proof, and future reader in the same action.

A high-rank handler alone cannot satisfy the route. An archive seal without a physical carrier also cannot satisfy it.

Beat 3 — Choose how the packet travels

The player chooses one of five postures:

1. deliver through a named lawful chain;
2. publish a split counterreceipt;
3. hold the packet for runner protection;
4. route through the fan-oxygen queue;
5. overload 林乔 as an invisible universal courier.

Every successful posture preserves a cost. The safe route is safer than an improvised transfer, not free of payroll, favor, inspection, public, sponsor, or delay pressure.

Beat 4 — A future reader consumes the result

The delivery is not complete until a receipt counterclaim, archive route, memorial route, voice-custody route, sponsor route, or public table reads the resulting state.

delivery_states:
  delivered_with_named_chain:
    future_effect: named_receipt_required
  public_split_receipt:
    future_effect: public_counterreceipt_required
  held_for_protection:
    future_effect: delivery_deferred
  fan_queue_delivery:
    future_effect: fan_witness_required
  route_asset_overloaded:
    future_effect: recovery_only

Branch matrix

Branch	Relief	Cost	林乔 state	Future route effect
Lawful chain	custody gap falls; receipt legitimacy rises	favor debt and payroll leak rise	protected route asset remains named	named receipt required
Public split	public proof and custody clarity improve	inspection and sponsor pressure rise	visible public carrier	public counterreceipt required
Protection hold	runner risk falls	custody delay and favor debt rise	protected but delivery pending	delivery deferred
Fan queue	packet moves and gains witnesses	fan resentment and inspection heat rise	public-facing runner	fan witness required
Overload	apparent speed only	custody gap, runner risk, inspection heat, and false-owner pressure rise	hostile witness armed	recovery-only

Repeatability contract

The rite may repeat because each use is bound to a new docket row. Repeatability never means universal courier permission.

repeatable_use:
  new_delivery_packet_required: true
  new_source_and_destination_required: true
  payment_or_protection_required: true
  receipt_proof_required: true
  future_reader_required: true
  prior_delivery_does_not_clean_next_delivery: true
  universal_courier_permission: false

Default and aftershock

If the player chooses overload_route_asset, Chain-Safe Delivery Breach records that 林乔 was spent as invisible infrastructure. The event:

• makes her a hostile witness;
• suppresses the repeatable delivery route;
• widens the custody gap;
• increases runner risk, inspection heat, and false-owner pressure;
• makes the future reader recovery-only.

This is a character consequence, not only a packet failure.

Completion oracle

The storyline is complete when:

1. the protected recruitment replay proves the route asset and unlock flags;
2. a lens-scoped replay resolves rite.chain_safe_small_delivery with a named branch;
3. the docket, rite, and breach event preserve the route-asset, delivery, cost, and future-reader state;
4. at least one non-default branch and the overload/default branch remain observably non-equivalent.

Non-goals

• Not a generic courier action.
• Not a fixed-turn follow-up.
• Not a free benefit for recruiting 林乔.
• Not a replacement for Receipt Counterclaim Hearing.
• Not permission to erase payment, protection, custody, or future-reader obligations from later deliveries.