裴栈 / 首接保全员

裴栈 is a claimant-floor bailiff who stamps the first durable receipt on a false-service claimant row. He is not a judge, inspector, sponsor agent, or public historian. His power is smaller and more dangerous: when a false-service row reaches the floor, his slip decides who can later claim to have received it first.

He exists to make 首接保全裁断机制 concrete. If protected, he can keep the first copy scoped. If captured, absent, or overrun, the wrong reader may become the first holder; the separate explicit-absence recovery rite can instead preserve a scar and narrow later use without pretending Pei Zhan still occupies the handler slot.

His full progression lives in 首接保全员 Storyline and is tested by 裴栈首接保全员 Lens.

Gameplay role

裴栈 is a route-asset NPC for the seam between 误服裁定认领升级线, 认领人现场接待线, and 裁定读者冲突线.

• Recruitment is exact: only First Custody Arbitration choice 4, floor_carrier_first, sets pei_zhan.recruited, changes him to route_asset_first_custody_witness, and grants route_asset.pei_zhan_first_custody_witness.
• Missable: choice 2, sponsor_first, captures and removes him immediately. Choice 7, default_capture, leaves him default_pending; resolving First Custody Default option 0, sponsor_capture, then clears both Pei/slip pending-state markers and the three trigger flags, sets pei_zhan.captured and pei_zhan.missed, removes his card, preserves the original slip, and adds the scar counterreceipt.
• Capturable: if Shen Luo or a sponsor counterdesk owns the slip, 裴栈 can sign a private first copy that calms the slot while poisoning public or lawful use.
• Dangerous when hostile: if the assigned gate is rejected, the slip is forged, or a public crush overrides the scoped reader, he becomes hostile_chain_bailiff and can testify that the producer knowingly let the wrong reader receive the row first.

Exact runtime packet

裴栈 is the required handler_or_absence object inside the character-bound thirteen-object assignment packet. Despite the slot label, this rite accepts only character.pei_zhan_first_custody_bailiff. The separate system packet uses card.storyteller.first_custody_handler_explicit_absence.v1 when no active handler remains. The other twelve assigned objects are the false-service claimant row, first-custody slip, preserved source ruling, candidate-reader table, selected-reader record, excluded-reader schedule, proof bundle, intake gate, support witness, posture register, cost ledger, and named future reader.

The hearing rejects substitutions: every slot is required, each slot accepts one exact runtime id, all assigned objects must be in hand, and one of the eight stable rite choices must be selected. This exactness is what keeps his stamp local: it proves one named first custody and does not grant consent, adjudication, sponsor release, archive ownership, or universal broadcast permission.

Character states

pei_zhan_state_any:
  - unseen_chain_bailiff
  - offered_first_custody_bailiff
  - protected_public_witness
  - lawful_chain_witness
  - split_custody_bailiff
  - boundary_quarantine_guard
  - route_asset_first_custody_witness
  - default_pending
  - sponsor_captured_signature
  - pirate_overrun_witness
  - management_absent_signer
  - hostile_chain_bailiff
  - missed_first_custody_route

Entry hooks

裴栈 should enter through state pressure, not a fixed sequence position. Valid entry examples:

• a 误服裁定认领行 exists and public, lawful, sponsor, artist, floor, or pirate readers contest first receipt;
• a claimant floor gate is pressured and the row must name who received it;
• a future route tries to cite a false-service row without a first custody slip;
• a sponsor or management report claims the row was already handled;
• a pirate relay or public historian has the first copy before official intake;
• an artist, witness, voice/body carrier, or floor carrier demands boundary-first receipt.

Costs

A useful 裴栈 branch must always price first custody:

• first_custody_legitimacy
• proof_chain_integrity
• public_receipt_legitimacy
• public_receipt_distrust
• inspection_heat
• sponsor_stop_loss_pressure
• contract_capture
• archive_debt
• floor_lane_load
• handler_burden
• false_first_claimant
• future_route_acceptance
• route_recovery_cost

Every rite branch writes exactly five counter deltas. The recruit replay for choice 4 records physical_proof_credibility +3, route_asset_integrity +2, floor_lane_load +3, handler_burden +2, and crew_refusal_risk +1.

Runtime evidence

• lens/replays/pei-zhan-first-custody-bailiff.recruit.replay.json assigns all thirteen objects and selects choice 4, proving recruitment plus route_asset.pei_zhan_first_custody_witness.
• lens/replays/pei-zhan-first-custody-bailiff.default-capture.replay.json assigns the same packet, selects choice 7, then resolves event.storyteller.first_custody_default.v1 option 0, proving sponsor capture, miss, Pei Zhan card loss, original-slip retention, first_custody.default_scar, and card.storyteller.first_custody_scar_counterreceipt.v1.

Relationships

• Han Yanshuang can make his slip lawful but risks turning public receipt into an appeal queue.
• Shen Luo can keep his slip sponsor-safe but risks private first custody.
• Yu Lan can protect the public copy but raises witness exposure and public-only use.
• 海盗频段童声 can make unofficial first custody impossible to erase.

Non-goals

• Not a universal resolver for claimant rows.
• Not a generic floor guard.
• Not a clean legal authority.
• Not a fixed-turn encounter.
• Not valid unless his stamp changes which future reader can use the false-service row first.