First Custody Arbitration / 首接保全裁断

First Custody Arbitration is the shared canon page for two assignable rites that resolve a 首接保全回执 when a 误服裁定认领行 has more than one plausible first receiver.

rite.storyteller.first_custody_arbitration.v1 is the Pei Zhan character hearing. rite.storyteller.first_custody_handler_absence_recovery.v1 is the system recovery hearing used only when Pei Zhan is absent. Both decide first custody state, not truth: they preserve the source ruling and false-service row, then scope later use of the receipt.

Entry condition

entry_state:
  trigger_kind: state_pressure
  false_service_claimant_row_present: true
  first_custody_slip_present_or_expected: true
  readers_min: 2
  readers_have_incompatible_first_custody_rules: true
  future_route_effect_if_unresolved_present: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true

The rite must not open from a turn number, chapter beat, cleanup phase, week/day timer, dashboard health state, or raw content count.

Pei Zhan character assignment

assignment:
  rite_id: rite.storyteller.first_custody_arbitration.v1
  exact_assignment_count: 13
  selected_false_service_row: card.storyteller.false_service_claimant_row.v1
  selected_slip: card.storyteller.first_custody_slip.v1
  source_ruling_or_row: card.storyteller.first_custody_source_ruling.v1
  candidate_readers: card.storyteller.first_custody_candidate_readers.v1
  selected_first_reader_or_absence: card.storyteller.first_custody_selected_reader.v1
  excluded_or_scoped_readers: card.storyteller.first_custody_excluded_readers.v1
  proof_or_absence: card.storyteller.first_custody_proof_bundle.v1
  intake_gate_or_absence: card.storyteller.first_custody_intake_gate.v1
  handler_or_absence: character.pei_zhan_first_custody_bailiff
  support_or_absence: card.storyteller.first_custody_support_witness.v1
  selected_posture: card.storyteller.first_custody_posture_register.v1
  accepted_cost: card.storyteller.first_custody_cost_ledger.v1
  future_reader: card.storyteller.false_service_future_reader.v1

A public number, lawful stamp, sponsor payment, archive seal, edit checksum, famous handler, or management report cannot substitute for any object above. In this character rite, handler_or_absence accepts Pei Zhan only. All thirteen slots are required, every slot has one exact accepted id, every assigned object must be in hand, and a selected option is mandatory.

Explicit handler-absence recovery assignment

The system rite uses the same twelve non-handler objects, but replaces the handler object exactly:

assignment:
  rite_id: rite.storyteller.first_custody_handler_absence_recovery.v1
  exact_assignment_count: 13
  shared_objects: same_twelve_non_handler_objects_as_character_rite
  handler_or_absence: card.storyteller.first_custody_handler_explicit_absence.v1
  pei_zhan_card_present: false
  selected_option: record_explicit_handler_absence

This rite rejects Pei Zhan presence, Pei Zhan substitution, any other handler-slot object, virtual placeholders, missing cards, and no-choice resolution. It retains card.storyteller.first_custody_scar_counterreceipt.v1, writes recovery-only slip and route state, clears superseded current slip/route flags, preserves prior capture/branch history, and cannot mutate a character or route asset.

Branch families

The option order is a stable runtime contract:

Choice	Branch	裴栈 state	Slip state	Future effect	Exact counter deltas
0	public_first	protected_public_witness	public_first_receipt	public_table_required	public_receipt_legitimacy +3, false_service_exposed +2, witness_exposure +2, public_receipt_distrust +1, handler_burden +1
1	lawful_first	lawful_chain_witness	lawful_first_receipt	lawful_only	proof_chain_integrity +3, custody_clarity +2, inspection_heat +1, archive_debt +2, bureau_favor_debt +1
2	sponsor_first	sponsor_captured_signature	sponsor_first_countercopy	sponsor_only	sponsor_stop_loss_pressure -2, immediate_assignment_burden -1, contract_capture +4, public_receipt_distrust +2, future_route_cost +2
3	boundary_first	boundary_quarantine_guard	boundary_first_receipt	boundary_gated	artist_refusal_respected +3, boundary_harm_prevented +2, inspection_heat +1, source_ambiguity +2, route_recovery_cost +2
4	floor_carrier_first	route_asset_first_custody_witness	floor_carrier_first_receipt	floor_gate_required	physical_proof_credibility +3, route_asset_integrity +2, floor_lane_load +3, handler_burden +2, crew_refusal_risk +1
5	split_custody	split_custody_bailiff	split_custody_slip	contradiction_pending	private_capture_resistance +3, custody_clarity +1, source_ambiguity +3, archive_debt +2, future_correction_cost +2
6	quarantine_or_refuse	hostile_chain_bailiff	recovery_only_custody	recovery_only	false_owner_risk -3, boundary_breach_risk -2, route_recovery_cost +4, claimant_hostility +3, crew_refusal_risk +2
7	default_capture	default_pending	default_pending_first_custody	first_custody_default_pending	immediate_assignment_burden -2, false_first_claimant +4, route_blocked +3, route_recovery_cost +3, contract_capture +2

Choice 4 is the only recruitment branch. It sets pei_zhan.recruited and route_asset.pei_zhan_first_custody_witness. Choice 2 captures, misses, and removes 裴栈 immediately. Choice 7 does not resolve the miss by itself: it sets first_custody.default_pending, event.first_custody_default.armed, and future_route.first_custody_default_pending, after which the priority default event must resolve.

The system rite has one separate stable option:

Option	Branch	Slip / future state	Exact counter deltas
0	record_explicit_handler_absence	recovery_only_custody / recovery_only	false_owner_risk -2, first_custody_absence_legibility +3, route_recovery_cost +4, claimant_hostility +2, future_correction_cost +3

Completion rule

A branch is complete only when it records:

result:
  slip_state_after: <state>
  selected_first_reader_state_after: <state>
  excluded_reader_states_after: []
  source_false_service_row_state_after: <state>
  future_reader_effect: <effect>
  counter_deltas:
    relief: []
    cost: []
    future: []

Every branch writes exactly five counter deltas. At least one served branch and one default/capture branch must produce different durable states from the same exact thirteen-object packet.

Failure examples

The rite fails if:

• it reruns the old ruling;
• it treats first custody as flavor;
• it lets one stamp satisfy public, lawful, sponsor, artist, floor, and route readers for free;
• it chooses a first reader without naming excluded readers;
• all postures return the same future route behavior;
• it depends on fixed turn, day, week, chapter, or raw count trigger.

Replay evidence

• lens/replays/pei-zhan-first-custody-bailiff.recruit.replay.json proves all thirteen exact assignments with rite choice 4, then records the recruited route-asset terminal state.
• lens/replays/pei-zhan-first-custody-bailiff.default-capture.replay.json proves the same assignments with rite choice 7, the automatic First Custody Default trigger, and event option 0.
• lens/replays/first-custody-arbitration.explicit-absence-recovery.replay.json continues after the default removes Pei Zhan, assigns the explicit-absence card in the handler slot, and resolves the one-option recovery rite without character or route-asset mutation.

The default replay must finish with all three pending flags plus pei_zhan.state.default_pending and slip.state.default_pending_first_custody cleared, first_custody.default_reader.sponsor, first_custody.failed_input.private_countercopy, pei_zhan.captured, pei_zhan.missed, pei_zhan.state.sponsor_captured_signature, slip.state.default_captured_first_custody, future_route.sponsor_only, character-card loss, and the retained scar counterreceipt.

Non-goals

• Not a new court verdict.
• Not a generic crowd gate scene.
• Not advance-notice briefing.
• Not valid unless first custody mutates future route acceptance.