裴栈 / 首接保全员 Storyline

Bound character: 首接保全员.

裴栈 is the floor bailiff who makes first custody playable. When a false-service claimant row reaches the live floor, public queue, lawful archive, sponsor counterdesk, artist boundary, floor carrier, pirate relay, and management report may all try to become the first accepted reader. 裴栈’s route asks whether the producer can keep the first receipt scoped before one reader turns it into a false universal key.

Gap this storyline fills

The current corpus already covers adjacent surfaces:

• 误服裁定认领升级线 creates a concrete row from claimant-facing false service.
• 认领人现场接待线 receives a row through a gate and floor lane.
• 裁定读者冲突线 handles incompatible later readers.
• 认领告知顺序线 handles advance notice before a pending action.

The missing playable slice is the custody seam after the false-service row exists but before future readers cite it. Who got the first receipt? If that is not explicit, a sponsor metric, public queue, pirate relay, lawful seal, or management report can retroactively become the first reader for free.

Primary playable question

When a false-service claimant row is live and multiple readers want first custody, can the producer protect a scoped first receipt through 裴栈 — and what public, lawful, sponsor, boundary, floor, or route cost does that create?

No answer may turn first custody into clean universal acceptance.

Entry state

This storyline opens from state pressure, not a fixed turn count.

entry_state:
  trigger_kind: state_pressure
  false_service_claimant_row_present: true
  source_ruling_or_row_preserved: true
  candidate_first_readers_min: 2
  first_custody_can_change_future_route: true
  pei_zhan_state_before: unseen_chain_bailiff | offered_first_custody_bailiff | equivalent
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true

Valid candidate first readers include fan/public queue, Yu Lan, pirate relay, lawful archive, Han Yanshuang, sponsor counterdesk, Shen Luo, artist or witness boundary, floor carrier, edit checksum, management metric, route asset, or explicit absence.

Story beats

Beat 1 — The false-service row reaches a first-custody seam

A 误服裁定认领行 exists. It names source ruling, missing load, demanded control, gate or absence, and future route effect. Now the row needs first custody before later readers can cite it.

Create or refresh 首接保全回执.

Beat 2 — 裴栈 is offered for the character route

The character route opens only while 裴栈 can serve as the exact handler:

pei_zhan_offer_state:
  pei_zhan_state_before: <state>
  handler_slot: character.pei_zhan_first_custody_bailiff
  proof_or_absence: <proof object or explicit_absence>
  intake_gate_or_absence: <gate/lane or explicit_absence>
  candidate_first_readers: []
  excluded_or_scoped_readers: []

If he is absent or already captured, this character rite does not substitute another object into his slot. Control passes to the system-level rite.storyteller.first_custody_handler_absence_recovery.v1, which records that no active handler remains and retains a recovery scar.

Beat 3 — The producer assigns first custody

The player opens 首接保全裁断.

The character rite consumes an exact thirteen-object packet:

1. card.storyteller.false_service_claimant_row.v1
2. card.storyteller.first_custody_slip.v1
3. card.storyteller.first_custody_source_ruling.v1
4. card.storyteller.first_custody_candidate_readers.v1
5. card.storyteller.first_custody_selected_reader.v1
6. card.storyteller.first_custody_excluded_readers.v1
7. card.storyteller.first_custody_proof_bundle.v1
8. card.storyteller.first_custody_intake_gate.v1
9. character.pei_zhan_first_custody_bailiff
10. card.storyteller.first_custody_support_witness.v1
11. card.storyteller.first_custody_posture_register.v1
12. card.storyteller.first_custody_cost_ledger.v1
13. card.storyteller.false_service_future_reader.v1

All thirteen must be in hand and assigned to their exact slots. The eight stable choices are 0 public_first, 1 lawful_first, 2 sponsor_first, 3 boundary_first, 4 floor_carrier_first, 5 split_custody, 6 quarantine_or_refuse, and 7 default_capture.

Beat 4 — 裴栈 mutates into route state

A valid branch changes 裴栈’s state and future use.

pei_zhan_route_states:
  offered_first_custody_bailiff:
    slip_seen: true
  protected_public_witness:
    public_copy_scoped: true
    cost: sponsor_pressure_or_witness_exposure
  lawful_chain_witness:
    proof_chain_scoped: true
    cost: public_delay_or_bureau_debt
  split_custody_bailiff:
    two_scoped_slips_exist: true
    cost: source_ambiguity_or_archive_debt
  boundary_quarantine_guard:
    breach_prevented: true
    cost: route_delay_or_recovery_only
  route_asset_first_custody_witness:
    route_asset_unlocked: route_asset.pei_zhan_first_custody_witness
    recruited_only_by_choice: 4
    cost: floor_lane_load_and_handler_burden
  default_pending:
    rite_choice: 7
    event_armed: event.storyteller.first_custody_default.v1
  sponsor_captured_signature:
    immediate_pressure_relief: true
    cost: contract_capture_or_public_distrust
  pirate_overrun_witness:
    public_memory_first: true
    cost: pirate_relay_heat_or_inspection_heat
  management_absent_signer:
    clean_metric_claimed: true
    cost: false_first_custody
  hostile_chain_bailiff:
    future_testimony_against_player: true
  missed_first_custody_route:
    future_route_effect: recovery_only

Beat 5 — The future reader is bound to the scar

The exact packet names card.storyteller.false_service_future_reader.v1, and every branch writes a durable future_route.* state. The focused Pei Zhan replays prove that binding and terminal route state; an adjacent downstream storyline may consume it later rather than inside the same session.

Valid readers include:

• 裁定读者冲突线 consuming scoped first custody as its source row;
• 认领人现场接待线 consuming gate or floor-lane scar;
• 经营压缩台 being blocked from clean false-service reporting;
• 认领撞锁 treating the slip as a route asset, false owner, or split copy;
• 误服裁定认领升级线 reopening the row with first-custody state visible.

Branch matrix

Branch	裴栈 state	Relief	Cost	Future route effect
0 public_first	protected_public_witness	public legitimacy +3, false service exposed +2	witness exposure +2, distrust +1, handler burden +1	public_table_required
1 lawful_first	lawful_chain_witness	proof-chain integrity +3, custody clarity +2	inspection +1, archive debt +2, bureau debt +1	lawful_only
2 sponsor_first	sponsor_captured_signature; card lost	stop-loss -2, immediate burden -1	capture +4, distrust +2, future cost +2	sponsor_only
3 boundary_first	boundary_quarantine_guard	refusal respected +3, harm prevented +2	inspection +1, ambiguity +2, recovery cost +2	boundary_gated
4 floor_carrier_first	route_asset_first_custody_witness; recruited	proof credibility +3, route integrity +2	floor load +3, handler burden +2, refusal risk +1	floor_gate_required
5 split_custody	split_custody_bailiff	capture resistance +3, custody clarity +1	ambiguity +3, archive debt +2, correction cost +2	contradiction_pending
6 quarantine_or_refuse	hostile_chain_bailiff	false-owner risk -3, breach risk -2	recovery cost +4, hostility +3, refusal risk +2	recovery_only
7 default_capture	default_pending	immediate burden -2	false-first +4, blocked +3, recovery +3, capture +2	first_custody_default_pending

Choice 4 is the only full recruitment route and must set pei_zhan.recruited plus route_asset.pei_zhan_first_custody_witness. Choice 7 is not terminal: it arms the priority default event.

Beat 4A — The choice-7 default resolves

The proven captured path selects 首接保全默认 option 0, sponsor_capture. That option clears the three trigger flags plus pei_zhan.state.default_pending and slip.state.default_pending_first_custody, sets sponsor as the default reader and private_countercopy as the failed input, marks 裴栈 captured and missed, changes him to sponsor_captured_signature, removes his character card, and grants card.storyteller.first_custody_scar_counterreceipt.v1.

The terminal slip is default_captured_first_custody; the future route is sponsor_only. The scar counterreceipt proves capture for later recovery review but grants no universal first-custody authority.

Counter contract

Every meaningful branch changes at least three counters or durable states:

• first_custody_legitimacy
• first_custody_slips_open
• false_service_exposed
• proof_chain_integrity
• custody_clarity
• public_receipt_legitimacy
• public_receipt_distrust
• inspection_heat
• bureau_favor_debt
• sponsor_stop_loss_pressure
• contract_capture
• archive_debt
• fan_oxygen_resentment
• artist_refusal_respected
• witness_exposure
• floor_lane_load
• crew_refusal_risk
• handler_burden
• reader_collision
• false_first_claimant
• future_route_acceptance
• route_recovery_cost

Missability and recovery

裴栈 is missed when the false-service row enters later systems without a first custody slip or when sponsor, law, public, pirate, or management surfaces become first reader without excluded-reader state.

Missed states:

• first_custody_slip_absent
• management_absent_signer
• sponsor_captured_signature
• pirate_overrun_witness
• false_first_custody_hardened
• missed_first_custody_route
• recovery_only_custody

Recovery is allowed only with a visible scar:

• late first-custody arbitration;
• public number plus sponsor/inspection cost;
• lawful monitor plus public delay;
• split custody and accept source ambiguity;
• boundary quarantine and accept route narrowing;
• floor lane repair and accept crew burden;
• accept public-only, lawful-only, sponsor-only, boundary-gated, hostile, or recovery-only route use.

The executable choice-7 miss preserves the original slip, removes only character.pei_zhan_first_custody_bailiff, and adds card.storyteller.first_custody_scar_counterreceipt.v1 as recovery evidence.

Replay/session evidence shape

• lens/replays/pei-zhan-first-custody-bailiff.recruit.replay.json
  • session: lens-storyteller-lens-pei-zhan-first-custody-bailiff-v1-20260716t1503z-recruit
  • assigns all thirteen exact objects
  • selects rite choice 4
  • proves pei_zhan.recruited, route_asset.pei_zhan_first_custody_witness, floor_carrier_first_receipt, and floor_gate_required
• lens/replays/pei-zhan-first-custody-bailiff.default-capture.replay.json
  • session: lens-storyteller-lens-pei-zhan-first-custody-bailiff-v1-20260716t1503z-default-capture
  • assigns the same exact packet
  • selects rite choice 7, then event option 0
  • proves clearance of all five pending markers, sponsor capture, miss, character-card loss, default scar, retained counterreceipt, and sponsor_only

Non-goals

• Not a generic guard recruitment.
• Not a raw character-count addition.
• Not a new verdict or appeal court.
• Not a duplicate of claimant briefing order.
• Not a free fix for false-service rows.
• Not valid unless first custody mutates 裴栈, the slip, and later route acceptance.