Cen Wei Temporary Chain Runner / 岑微临时交接跑腿线
Cen Wei Temporary Chain Runner is the character storyline for 岑微, the low-rank carrier who can move a contested proof object through the service corridors before a higher desk can turn it into doctrine.
The inspection-shadow mechanism already proves that fragile proof needs physical custody. This storyline adds the person-state: Cen Wei can become a protected chain witness, a neutral route asset, a public receipt carrier, a masked carrier, a captured courier, a hostile leak, or a missed absence. She is not a free delivery slot and not a fixed-turn reward.
The dramatic question is:
When a proof packet needs a human hand, do you protect the temporary runner who carries it, or let a faction convert her absence into the official chain?
Bound content pack
This storyline binds:
Why this fills a gap
Cen Wei already exists as a starter-visible temporary chain runner and can appear inside inspection-shadow and memorial-air chain pressure. Without a dedicated character storyline, implementation can still spend her as a generic carrier flag: a card is present, the proof moves, and nobody records whether the runner was protected, captured, bought, exposed, or missed.
This storyline makes the low-rank worker state durable:
- recruitable when she is authorized with proof, cover, handler, and future cost;
- missable when high-rank authority bypasses the carrier slot;
- hostile when she is blamed, unpaid, exposed, or used as a false chain;
- capturable when sponsor, archive, inspector, editor, pirate relay, or false owner controls the packet through her;
- route-bearing only when future rites read her state and the proof object’s state together.
Exact executable packet
The playable Storyteller implementation is intentionally narrower than the general design vocabulary. It starts with exactly these eight objects:
card-storyteller-cen-wei-temporary-chain-runner;card-storyteller-inspection-shadow-crew-permit;storyteller.card.cen_wei_contested_proof_packet.v1;storyteller.card.cen_wei_archive_claimant.v1;storyteller.card.cen_wei_public_claimant.v1;storyteller.card.cen_wei_chain_handler.v1;storyteller.card.cen_wei_custody_cover.v1;storyteller.card.cen_wei_future_chain_reader.v1.
They fill exactly runner, permit, proof_object, archive_claimant, rival_claimant, handler, cover, and future_reader. All eight are required in hand. Each slot accepts only its named starter object. Substitutions, virtual objects, explicit-absence placeholders, omitted slots, cards assigned to the wrong slot, and resolution without a selected choice all fail.
State-triggered entry
Open this storyline only when field custody pressure is already live.
entry_state_required:
trigger_kind: state_pressure
movable_or_uncertain_proof_present: true
proof_object_can_change_future_route_or_counter: true
claimant_factions_count_min: 2
cen_wei_state_or_explicit_absence_visible: true
carrier_slot_required_or_absence_recorded: true
permit_cover_or_explicit_absence_visible: true
handler_or_explicit_absence_visible: true
future_reader_or_route_consumes_chain_state: true
player_can_authorize_publicize_mask_bypass_sponsor_cover_sacrifice_or_record_absence: true
non_neutral_default_exists: true
no_fixed_turn_trigger: true
no_fixed_day_or_phase_trigger: true
no_raw_runner_count_trigger: true
no_dashboard_or_lens_health_trigger: trueValid proof objects include fan oxygen receipt, archive docket copy, black-box fragment, consent printout, witness stub, memorial air copy, voice custody receipt, route-asset packet, recovery counterstub, public receipt fragment, or equivalent.
Storyline spine
Beat 1 - A proof packet cannot move itself
A desk has a proof object that matters, but the object is physically uncertain. The issue is not whether Han Yanshuang can audit it, Yu Lan can publish it, Baiya can checksum it, or Shen Luo can negotiate over it. The issue is whether a low-rank carrier can cross the corridor with the packet and remain a valid witness after doing so.
Beat 2 - Cen Wei or her absence enters the chain
Inspection Shadow Crew Permit and the seven other exact starter objects must fill the executable transfer row before the rite resolves.
Required row shape:
cen_wei_chain_row:
runner: card-storyteller-cen-wei-temporary-chain-runner
permit: card-storyteller-inspection-shadow-crew-permit
proof_object: storyteller.card.cen_wei_contested_proof_packet.v1
archive_claimant: storyteller.card.cen_wei_archive_claimant.v1
rival_claimant: storyteller.card.cen_wei_public_claimant.v1
handler: storyteller.card.cen_wei_chain_handler.v1
cover: storyteller.card.cen_wei_custody_cover.v1
future_reader: storyteller.card.cen_wei_future_chain_reader.v1Beat 3 - The player chooses how she carries the packet
Run 影子证据转运 or an equivalent custody rite with Cen Wei as carrier, route asset, witness, protected worker, or explicit absence.
The player may:
- authorize a lawful chain;
- publicize the handoff through a receipt chain;
- mask the carrier through editor or black-box cover;
- keep her production-neutral;
- accept sponsor or management cover;
- bypass or suppress the carrier slot;
- sacrifice the permit or carrier;
- let leak, capture, or hostile default resolve the gap.
Beat 4 - Her state becomes route state
Every branch must change both the proof object and Cen Wei’s person-state.
cen_wei_route_states:
runner_authorized:
meaning: she can carry this packet but is not protected by default
lawful_chain_witness:
meaning: admissibility improves through oath or inspection cover
public_receipt_carrier:
meaning: private capture is harder because the public can see the handoff
editor_masked_carrier:
meaning: retaliation risk falls but source ambiguity and edit debt rise
neutral_route_asset:
meaning: she survives as a narrow future carrier with payroll or exposure cost
suppressed_carrier:
meaning: immediate pressure may fall but later transfer options become costlier
captured_carrier:
meaning: another faction controls her, the packet, or both
hostile_leak_source:
meaning: her testimony becomes hostile evidence against the producer
sacrificed_permit:
meaning: the temporary authority burns to preserve stronger proof
explicit_absence:
meaning: future readers know no valid carrier was presentBeat 5 - Future systems read the chain
Completion requires a later surface to consume Cen Wei’s state or explicit absence. Valid consumers include Memorial Air Chain Cross-Examination, Proof Burden Reassignment, Evidence Carryover Fork, Receipt Counterclaim False-Owner Recovery, Protected Witness Payroll, route-asset maintenance, or an equivalent proof reader.
Branch map
| Exact option | Cen Wei state | Relief | Cost/scar | Future route effect |
|---|---|---|---|---|
authorize_runner_lawful_custody | lawful_chain_witness plus route asset | custody integrity and proof legibility | inspection heat, exposure, sponsor retaliation | audit_required |
route_runner_to_public_receipt | public_receipt_carrier | public receipt legitimacy and proof legibility | fan liability, exposure, sponsor retaliation | public_only |
mask_runner_under_editor_checksum | editor_masked_carrier | continuity hazard falls | source ambiguity, edit debt, archive debt, runner risk | contradiction_pending |
retain_runner_as_production_neutral | neutral_route_asset | custody clarity | payroll leak, handler burden, exposure, recovery cost | reusable_once_with_cost |
accept_sponsor_cover_capture | captured_carrier | slot pressure falls | contract capture, public distrust, ownership debt, recovery cost | rescue_required |
suppress_runner_access | suppressed_carrier | immediate desk pressure falls | custody gap, proof burden, continuity hazard, recovery cost | recovery_only |
sacrifice_runner_permit | sacrificed_permit | proof legibility | witness debt, legitimacy debt, runner risk, recovery cost | leak_armed |
abandon_runner_to_pirate_loop | hostile_leak_source | public truth pressure | continuity hazard, exposure, receipt legitimacy loss, recovery cost | custody-leak default pending |
No branch may let a temporary runner become a clean universal proof courier for every archive, sponsor, public, editor, route-asset, lawful, and broadcast-reality reader.
Counter contract
Every constructive branch must mutate:
counter_deltas_required:
relief: at_least_one
cost: at_least_one
cen_wei_or_future_route_effect: at_least_oneAccepted surfaces include cen_wei_state, custody_clarity, custody_gap, proof_legibility, proof_burden, runner_risk, payroll_leak, inspection_heat, bureau_favor_debt, archive_debt, public_receipt_legitimacy, public_receipt_distrust, fan_oxygen_liability, sponsor_stop_loss_pressure, edit_debt, source_ambiguity, false_owner_pressure, future_recovery_cost, and route_asset_pressure.
Missability and recovery
The storyline is missed when the player moves contested proof through legal, sponsor, archive, editor, or public authority without recording a carrier, Cen Wei state, permit/cover, handler, or explicit absence.
Missed or defaulted states include:
explicit_absence;suppressed_carrier;captured_carrier;hostile_leak_source;sacrificed_permit;carrier_absent_false_chain;route_recovery_only;shadow_crew_custody_leak.
Recovery requires a visible cost: witness payroll, lawful oath, public receipt, edit mask, rescue or exchange, apology to the runner, proof-burden rehearing, route quarantine, or recovery-only transfer.
Replay evidence expectation
Durable evidence uses session ids beginning with lens-storyteller-lens-character-cen-wei-temporary-chain-runner-v1- and exactly these two replay artifacts:
lens/replays/cen-wei-temporary-chain-runner.recruit.replay.jsonresolvesauthorize_runner_lawful_custodyand proves the sole lawful route-asset result with visible costs.lens/replays/cen-wei-temporary-chain-runner.hostile-default.replay.jsonresolvesabandon_runner_to_pirate_loop, then resolves one of the four exact Shadow Crew Custody Leak terminal options without retaining a clean route asset.
storyline_id: storyteller.storyline.character.cen_wei_temporary_chain_runner.v1
session_id: lens-storyteller-lens-character-cen-wei-temporary-chain-runner-v1-<timestamp>
replay_paths:
- lens/replays/cen-wei-temporary-chain-runner.recruit.replay.json
- lens/replays/cen-wei-temporary-chain-runner.hostile-default.replay.json
seed: <deterministic-seed>
entry_state:
trigger_kind: state_pressure
movable_or_uncertain_proof_present: true
claimant_factions_count_min: 2
cen_wei_state_or_explicit_absence_visible: true
carrier_slot_required_or_absence_recorded: true
future_reader_or_route_consumes_chain_state: true
no_fixed_turn_trigger: true
offered:
npc: storyteller.npc.cen_wei_temporary_chain_runner.v2
card: storyteller.card.inspection_shadow_crew_permit.v2
rite: storyteller.rite.shadow_evidence_transfer.v2
branch_result:
selected_branch: lawful_chain | public_receipt_chain | editor_mask | production_neutral_route | sponsor_cover | managed_bypass_or_suppress | sacrifice_carrier_or_permit | leak_capture_or_hostile
cen_wei_state_after: lawful_chain_witness | public_receipt_carrier | editor_masked_carrier | neutral_route_asset | suppressed_carrier | captured_carrier | hostile_leak_source | sacrificed_permit | explicit_absence
proof_object_state_after: <state>
future_reader_effect: <effect>
counter_deltas:
relief: []
cost: []
future: []
default_branch:
event_seen_or_armed: storyteller.event.shadow_crew_custody_leak.v2 | explicit_absence
assertions:
- entry_is_state_triggered
- proof_object_claimants_carrier_cover_and_handler_are_visible
- cen_wei_state_or_explicit_absence_is_visible_before_resolution
- branch_outcomes_diverge_by_cen_wei_state
- every_success_has_relief_cost_and_future_effect
- bypass_suppression_capture_miss_and_hostile_leak_are_durable
- future_reader_consumes_cen_wei_state
- no_universal_clean_runner
- no_fixed_turn_day_phase_raw_count_dashboard_or_lens_health_triggerNon-goals
- Not a fixed-turn recruit.
- Not a generic courier system.
- Not a free proof transfer.
- Not a replacement for Inspection Shadow Crew Custody.
- Not valid if Cen Wei is only inventory, flavor dialogue, or a one-time modifier.
- Not valid if high-rank authority can erase physical custody.