Field Logistics Runner Custody Lens

ID

storyteller.turn55_field_logistics_runner_custody.v1

Design intent

This lens observes whether 交接链跑腿 makes physical chain-of-custody work playable. The player should not be able to solve receipt, archive, fan oxygen, sponsor, memorial, or voice custody disputes only by assigning high-rank actors. At least one low-rank carrier, witness, permit, receipt, or service-corridor asset must matter.

The lens is satisfied only when 林乔 or an equivalent field logistics surface becomes assignable, missable, recoverable, and costly. Success should reduce a custody problem while creating another visible pressure. Failure should remove or worsen future custody options.

Observed surfaces

• 交接链跑腿
• 交接链跑腿 Storyline
• Route Assets and Custody
• Receipt Packet Counterclaim
• Receipt Counterclaim Hearing
• Inspection Shadow Crew Permit
• Receipt Counterclaim False Owner Recovery Lens

State-triggered entry

The field logistics runner surface may be offered when all of the following are true:

1. at least one custody packet, receipt, docket copy, fan oxygen queue stub, black-box fragment, memorial air receipt, or voice custody proof is physically movable or has an uncertain handoff;
2. at least two factions can contest the handoff: archive authority, inspector authority, sponsor desk, fan public, editor claimant, memorial desk, voice claimant, or service corridor staff;
3. at least one handler can assign, protect, audit, publish, negotiate, or suppress the runner;
4. a relevant pressure counter is active or unresolved: custody_gap, archive_debt, inspection_heat, sponsor_stop_loss_pressure, fan_oxygen_resentment, runner_risk, payroll_leak, favor_debt, or false_custody_owner;
5. the runner is not already fully resolved as stable route asset, final missed state, or terminal hostile witness.

This entry is driven by state and contested custody, not by a fixed schedule count.

Required playable surface

Card or route asset

The implementation must expose 林乔 or an equivalent logistics runner with at least four states:

• available_runner
• recruited_runner
• runner_protected_under_oath
• route_asset.lin_qiao_custody_runner
• runner_missed
• runner_hostile_witness
• runner_unavailable

Assignable rites

At least two reusable rites or equivalent game actions must exist:

• rite.chain_receipt_recovery
• rite.fan_oxygen_side_queue_delivery
• rite.defend_chain_with_low_rank_runner
• rite.chain_safe_small_delivery
• rite.recover_runner_witness

Events

At least two events must be reachable or recorded:

• event.runner_seen_near_archive_door
• event.receipt_packet_counterclaim
• event.runner_protected_after_delivery
• event.runner_names_the_wrong_handoff
• event.false_owner_files_final_receipt

Counters

The replay must expose at least three counter/state deltas from this set:

• custody_gap
• archive_debt
• inspection_heat
• sponsor_stop_loss_pressure
• fan_oxygen_resentment
• payroll_leak
• favor_debt
• runner_risk
• receipt_legitimacy
• false_custody_owner

Oracle assertions

The executable sibling lens should fail unless all assertions below are true.

1. State reachability — The offer appears from contested custody state with movable or uncertain proof.
2. Assignable management action — At least one rite records assigned cards and includes the runner, a handler, a proof object, or an explicit unavailable-runner state.
3. Success branch — A success replay recruits, protects, or converts the runner into a route asset and changes at least two counters.
4. Cost is mandatory — Success must spend or risk money, favor debt, payroll leak, fan oxygen resentment, inspection heat, sponsor pressure, runner risk, or proof exhaustion.
5. Miss or hostile branch — Ignoring, underpaying, exposing, or suppressing the runner must produce runner_missed, runner_hostile_witness, runner_unavailable, or equivalent durable state.
6. No high-rank-only shortcut — Assigning a high-rank actor alone cannot satisfy the lens unless a carrier, permit, witness, receipt, or equivalent logistics surface is resolved.
7. False-owner interaction — If a receipt counterclaim has already produced wrong-owner pressure, runner state must change recovery options in Receipt Counterclaim False Owner Recovery.
8. Replay provenance — Evidence must include seed/session id, offered choices, assigned cards, outcomes, branch states, and counter deltas.

Branch model

Branch A — Recruit or protect runner

The player pays, protects, or legitimizes 林乔 and assigns a handler or proof object.

Expected outcomes:

• add recruited_runner, runner_protected_under_oath, or route_asset.lin_qiao_custody_runner;
• reduce custody_gap, improve receipt_legitimacy, or unlock rite.chain_safe_small_delivery;
• increase favor_debt, payroll_leak, runner_risk, inspection_heat, or sponsor pressure.

Branch B — Public delivery through fan queue

The player uses fan oxygen queue access or public witness pressure to move or prove the packet.

Expected outcomes:

• add fan_stub_witnesses_mobilized, receipt_publicly_split, or equivalent public route state;
• improve public receipt legitimacy;
• increase fan oxygen resentment, inspection heat, sponsor pressure, or runner risk.

Branch C — Suppress or bypass runner

The player relies on a high-rank actor, sponsor pressure, archive ambiguity, or silence instead of solving physical custody.

Expected outcomes:

• immediate pressure may fall;
• add runner_missed, runner_unavailable, sponsor_duplicate_receipt_deferred, or unresolved custody_gap;
• future counterclaim or false-owner recovery becomes more expensive.

Branch D — Runner turns witness against the chain

If the player exposes, underpays, or leaves 林乔 unprotected, she can become a hostile witness or unavailable carrier.

Expected outcomes:

• add runner_hostile_witness or runner_unavailable;
• increase inspection_heat, sponsor_stop_loss_pressure, custody_gap, or false_custody_owner;
• later recovery must use rite.recover_runner_witness or equivalent.

Replay evidence shape

lens_id: storyteller.turn55_field_logistics_runner_custody.v1
session_id: lens-storyteller-field-logistics-runner-custody-v1-<timestamp>
seed: <deterministic-seed>
replay_context:
  disputed_asset: receipt_packet | missing_stub | fan_queue_receipt | archive_docket_copy | black_box_fragment | memorial_air_receipt | voice_custody_receipt
  claimant_factions:
    - archive_or_sponsor_or_inspector_or_fan_public
    - second_claimant_or_equivalent
  runner_state_before: available | recruited | route_asset | missed | hostile | unavailable | explicit_absent
offered_choices:
  - rite.chain_receipt_recovery
  - rite.defend_chain_with_low_rank_runner
  - rite.fan_oxygen_side_queue_delivery
  - rite.recover_runner_witness
assigned_cards:
  success_branch:
    - card.lin_qiao_chain_runner_or_route_asset
    - handler_or_proof_object
  negative_branch:
    - none_or_suppressing_actor_or_insufficient_proof
branches:
  success:
    outcome: recruited_runner | runner_protected_under_oath | route_asset.lin_qiao_custody_runner
    costs:
      - favor_debt | payroll_leak | runner_risk | inspection_heat | sponsor_pressure | proof_exhaustion
    deltas:
      custody_gap: -1
      runner_risk: +1
  negative:
    outcome: runner_missed | runner_hostile_witness | runner_unavailable
    deltas:
      custody_gap: +1
      inspection_heat: +1
assertions:
  - offer is state-triggered
  - runner state changes branch availability or cost
  - success has nonzero cost
  - negative branch changes future availability or difficulty
  - high-rank assignment alone is insufficient

Progress metric

Progress is branch coverage and state distinction, not content count.

• 20%: runner source card/page exists with field logistics tags and states.
• 40%: contested custody state can offer a runner assignment or explicit unavailable-runner branch.
• 60%: success branch produces recruit/protect/route-asset outcome with costs and counter deltas.
• 80%: miss/unavailable/hostile branch produces a distinct penalty state and counter delta.
• 100%: success and negative branches are replay-proven with seed, session id, assignments, outcomes, and counter deltas.

Non-goals

• Not bulk filler.
• Not raw scale fulfillment.
• Not a mood note or chapter synopsis.
• Not a free universal fix for archive, memorial, voice, receipt, fan oxygen, sponsor, or inspector pressure.
• Not satisfied by prose alone; branch evidence must come from replay/session state.