First Custody Default / 首接保全默认

First Custody Default is the Pei Zhan character-path default. It fires when the exact character packet selects choice 7 but awards no scoped first reader. No-active-handler system recovery uses rite.storyteller.first_custody_handler_absence_recovery.v1 after Pei Zhan leaves; it does not invoke this event by itself.

This event is specific to first custody. 误服裁定认领硬化 hardens the claimant row. First Custody Default records who grabbed the first receipt, who was excluded, and how later readers inherit that scar.

Entry condition

entry_state:
  trigger_kind: state_pressure
  trigger_priority: 13200
  first_custody.default_pending: true
  event.first_custody_default.armed: true
  future_route.first_custody_default_pending: true
  pei_zhan_card_present: true
  event_not_already_resolved: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true

The thirteen assigned objects remain complete. Valid failure causes are semantic rejection after assignment: no credible reader is awarded, the assigned handler refuses or is treated as absent, the assigned gate is rejected as invalid, a sponsor countercopy captures the result, public overrun wins first copy, or a future route cites the row before custody is scoped.

The exact executable entry is produced by First Custody Arbitration choice 7, default_capture. The rite writes the three pending flags above plus pei_zhan.state.default_pending and slip.state.default_pending_first_custody; this event consumes and clears all five markers.

Event payload

event_payload:
  event_id: event.storyteller.first_custody_default.v1
  source_false_service_row: card.storyteller.false_service_claimant_row.v1
  expected_slip: card.storyteller.first_custody_slip.v1
  source_ruling_or_row: <source>
  default_capture_reader: sponsor | pirate_relay | management | no_reader
  excluded_reader: <reader or explicit_absence>
  failed_input: private_countercopy | public_overrun | assigned_handler_refused | assigned_gate_rejected
  pei_zhan_state_after: sponsor_captured_signature | pirate_overrun_witness | management_absent_signer | hostile_chain_bailiff
  slip_state_after: default_captured_first_custody | false_first_custody_hardened | recovery_only_custody
  future_route_effect: sponsor_only | public_only_hostile | blocked | recovery_only
  retained_evidence: card.storyteller.first_custody_scar_counterreceipt.v1
  exact_counter_delta_count: 5

The event fails if it increments heat without naming the capturing reader, excluded reader or explicit absence, failed input, future route effect, and recovery hook or terminal.

Exact default branches

The option order is stable:

Option	Branch	Capture reader / failed input	裴栈 and slip result	Future effect	Exact counter deltas
0	sponsor_capture	sponsor / private_countercopy	captured + missed; sponsor_captured_signature; default_captured_first_custody	sponsor_only	immediate_assignment_burden -2, contract_capture +5, public_receipt_distrust +3, route_recovery_cost +3, false_first_claimant +2
1	pirate_overrun	pirate relay / public_overrun	hostile + missed; pirate_overrun_witness; false_first_custody_hardened	public_only_hostile	false_service_exposed +3, pirate_relay_heat +5, inspection_heat +3, claimant_hostility +2, route_recovery_cost +2
2	management_absent_signer	management / assigned_handler_refused	missed; management_absent_signer; false_first_custody_hardened	blocked	management_reporting_relief +2, false_first_claimant +5, route_blocked +4, public_receipt_distrust +3, future_correction_cost +3
3	recovery_only_chain	no reader / assigned_gate_rejected	hostile + missed; hostile_chain_bailiff; recovery_only_custody	recovery_only	false_owner_risk -2, route_recovery_cost +5, claimant_hostility +4, crew_refusal_risk +3, future_correction_cost +3

Every option removes character.pei_zhan_first_custody_bailiff, grants card.storyteller.first_custody_scar_counterreceipt.v1, sets first_custody.default_scar, and clears the pending rite/event/route flags plus pei_zhan.state.default_pending and slip.state.default_pending_first_custody.

The payload codes assigned_handler_refused and assigned_gate_rejected do not mean the exact packet omitted those assignments. They record semantic rejection of the assigned handler or intake gate during resolution.

Proven option-0 terminal

lens/replays/pei-zhan-first-custody-bailiff.default-capture.replay.json selects rite choice 7 and then event option 0. Its final state proves:

• 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
• event_resolved.event.storyteller.first_custody_default.v1

The replay’s cumulative counters include both the choice-7 pending cost and the option-0 capture cost: immediate_assignment_burden -4, false_first_claimant +6, route_blocked +3, route_recovery_cost +6, contract_capture +7, and public_receipt_distrust +3.

Recovery hooks

Recovery must preserve the scar:

• after Pei Zhan is removed, run rite.storyteller.first_custody_handler_absence_recovery.v1 with the explicit-absence card and all twelve shared assignment objects;
• publish late public receipt and accept sponsor or inspection cost;
• attach lawful monitor and accept public delay;
• repair floor lane and crew burden;
• protect artist/witness boundary and accept route narrowing;
• split custody into scoped public, lawful, sponsor, boundary, or route copies;
• accept public-only, lawful-only, sponsor-only, boundary-gated, hostile, or recovery-only future use.

Non-goals

• Not a timer expiry.
• Not a random backlash event.
• Not a replacement for false-service hardening or reader-collision default.
• Not valid unless a first custody scar changes later reader acceptance.