First Custody Arbitration / 首接保全裁断线

First Custody Arbitration is the system-facing storyline for the moment a false-service claimant row has become real enough that more than one reader can claim the first durable receipt.

Pei Zhan First-Custody Bailiff proves the human route: the bailiff can be protected, recruited, captured, missed, or made hostile. This storyline owns the broader first-custody surface. When 裴栈 is absent, captured, or already removed, card.storyteller.first_custody_handler_explicit_absence.v1 and rite.storyteller.first_custody_handler_absence_recovery.v1 provide the concrete system path instead of substituting a virtual handler.

Gap diagnosis

The current mesh can create false-service claimant rows, push those rows through floor intake, and later expose reader collisions. The remaining seam is the receipt between those systems.

Without this storyline, implementation can jump from false service row exists to future reader cites it, or let sponsor, lawful, public, artist-boundary, floor-carrier, route-asset, and management readers all treat one first stamp as universal clean custody. That is too clean. First custody must name who received the row first, who was excluded or scoped, which gate or proof made the receipt credible, and how future routes inherit the scar.

Primary playable question

When a false-service row needs its first durable custody slip, does the producer give first receipt to the public queue, lawful archive, sponsor counterdesk, artist or witness boundary, floor carrier, split table, quarantine, refusal record, or default capture?

Every branch must name:

• source false-service row and preserved ruling or row;
• candidate first readers;
• selected first reader, or explicit absence;
• excluded or scoped readers;
• proof, intake gate, and handler, or explicit absence for each;
• selected custody posture;
• slip state after;
• future route or reader effect.

State-triggered entry

Open this storyline only from live first-custody pressure:

entry_state_required:
  trigger_kind: state_pressure
  false_service_claimant_row_present: true
  source_ruling_or_row_preserved: true
  first_custody_slip_present_or_expected: true
  candidate_first_readers_min: 2
  readers_have_incompatible_first_custody_rules: true
  proof_or_gate_can_be_named_or_explicitly_absent: true
  future_route_effect_if_unresolved_present: true
  player_can_arbitrate_or_record_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Valid entry sources include false-service claimant hardening, enforcement load default, claimant floor intake, ruling reader collision, claimant briefing order, management compression, route-asset custody, public receipt pressure, sponsor countercopy, lawful archive seal, artist boundary notice, floor carrier refusal, or pirate relay receipt.

Bound content pack

• First Custody Arbitration defines entry, reader families, first-receipt states, branch contract, default conditions, and replay evidence.
• First Custody Slip records the source false-service row, receiving reader, excluded readers, proof/gate/handler, posture, state after, and future effect.
• card.storyteller.first_custody_handler_explicit_absence.v1 records that no active handler remains assigned for recovery without impersonating a person, gate, proof object, or route asset.
• First Custody Arbitration covers two executable rites: the eight-choice Pei Zhan character arbitration and the one-choice explicit handler-absence recovery.
• First Custody Default fires or arms when first custody is hidden, wrong-gated, privately captured, publicly overrun, or treated as a universal key.
• Pei Zhan First-Custody Bailiff remains the character-bound worker route, not the whole system.

Storyline spine

Beat 1 - A false-service row becomes a custody object

A false-service row has already escaped pure warning status. A claimant, public queue, lawful archive, sponsor desk, artist boundary, floor carrier, pirate relay, route asset, or management table can now say it received the row first.

The source row remains visible:

source_lock:
  source_false_service_row: card.storyteller.false_service_claimant_row.v1
  source_ruling_or_row: <source>
  source_default_event: event.storyteller.enforcement_load_default.v1 | equivalent
  source_history_preserved: true

Beat 2 - The slip separates first reader from future reader

Create or refresh First Custody Slip.

The slip must keep these locks separate:

first_custody_locks:
  source_lock:
    source_false_service_row: card.storyteller.false_service_claimant_row.v1
    source_ruling_or_row: <source>
    source_history_preserved: true
  receipt_lock:
    receiving_surface: public_number | lawful_archive | sponsor_counterdesk | artist_boundary | floor_carrier | pirate_relay | management_metric | quarantine | equivalent
    first_receiving_reader: <reader or explicit_absence>
    excluded_or_scoped_readers:
      - <reader>
    proof_or_absence: <proof object or explicit_absence>
    intake_gate_or_absence: <gate/lane or explicit_absence>
    handler_or_absence: <handler or explicit_absence>
  posture_lock:
    stamp_posture: public_first | lawful_first | sponsor_first | boundary_first | floor_carrier_first | split_custody | quarantine | refused | default_capture
    slip_state_after: <state>
  future_lock:
    future_reader_or_route: <reader or route>
    future_route_effect: accepted_with_cost | public_only | lawful_only | sponsor_only | boundary_gated | split_canon | blocked | hostile | recovery_only | contradiction_pending

The row fails if it stores only first reader, handled, public number, sponsor receipt, or lawful seal.

Beat 3 - Arbitration chooses scoped first custody

Run the character-bound rite.storyteller.first_custody_arbitration.v1 before any downstream reader can cite the row as clean receipt while 裴栈 is available.

Valid postures:

• public_first
• lawful_first
• sponsor_first
• boundary_first
• floor_carrier_first
• split_custody
• quarantine_or_refuse
• default_capture

A public number, lawful stamp, sponsor payment, archive seal, edit checksum, famous handler, or management report may support a branch, but it cannot satisfy every reader without excluded-reader and future-route scars.

If 裴栈 is absent, captured, or removed, use rite.storyteller.first_custody_handler_absence_recovery.v1. Its exact thirteen-object packet replaces only the handler object with card.storyteller.first_custody_handler_explicit_absence.v1, exposes only record_explicit_handler_absence, retains the scar counterreceipt, and writes recovery-only custody without changing character or route-asset state.

Beat 4 - Future readers inherit first-custody state

At least one later route, hearing, claimant row, route asset, report, public statement, lawful annex, sponsor package, floor gate, or broadcast-reality reader must consume slip_state_after and future_route_effect.

If future play cites the false-service row while selected reader, excluded reader, gate, proof, handler, or future effect is hidden, First Custody Default fires or remains armed.

Branch matrix

Branch	Immediate relief	Cost/scar	Future state
Public first	public receipt legitimacy and private-capture resistance improve	sponsor pressure, inspection heat, witness exposure, or handler burden rises	public-only, accepted-with-cost, or claimant-collision-ready
Lawful first	proof chain and custody clarity improve	public delay, bureau debt, audience distrust, or sponsor pressure rises	lawful-only, audit-required, appeal-required, or blocked-until-notice
Sponsor first	stop-loss, slot, budget, or management pressure drops	contract capture, public distrust, fan resentment, or future audit rises	sponsor-only, appeal-required, correction-cost-due, or false-first-risk
Boundary first	artist, witness, body, voice, or refusal boundary is protected	route unlock narrows, sponsor promise worsens, handler burden rises	boundary-gated, narrowed, delayed, or recovery-only
Floor carrier first	physical proof reaches a credible lane	floor load, crew refusal, or schedule pressure rises	safety-only, costlier, or accepted-with-floor-debt
Split custody	private capture and lawful overreach are reduced	source ambiguity, archive debt, correction cost, or distrust rises	split-canon, scoped-public-lawful, or contradiction-pending
Quarantine/refusal	false owner, fraud, or boundary breach risk falls	current route blocks, sponsor/public pressure rises, claimant hostility rises	blocked, hostile, boundary-gated, or recovery-only
Default capture	no true relief, or only short pressure relief for the loudest reader	first custody hardens as false-first or captured	public-only, lawful-only, sponsor-only, boundary-gated, hostile, blocked, or recovery-only
Explicit absence	current no-active-handler state becomes legible	recovery, hostility, and correction costs remain visible	recovery-only; no Pei Zhan or route-asset mutation

No constructive branch may make one receipt satisfy public, lawful, sponsor, artist-boundary, floor, management, route-asset, and broadcast-reality readers cleanly.

Counter contract

Every resolved branch must mutate at least one relief surface, one cost surface, and one future reader or route surface.

Accepted relief surfaces include first_custody_legitimacy, proof_chain_integrity, public_receipt_legitimacy, custody_clarity, artist_refusal_respected, floor_gate_legibility, and false_service_exposed.

Accepted cost surfaces include inspection_heat, sponsor_stop_loss_pressure, contract_capture, public_receipt_distrust, archive_debt, handler_burden, floor_lane_load, crew_refusal_risk, and witness_exposure.

Accepted future states include accepted_with_cost, public_only, lawful_only, sponsor_only, boundary_gated, split_canon, claimant_collision_ready, blocked, hostile, and recovery_only.

Missability and recovery

This storyline is missed when a false-service row is later cited, settled, packaged, reported, broadcast, or converted without a first custody slip or explicit absence.

Missed states include:

• first_custody_slip_absent;
• selected_first_reader_missing;
• excluded_reader_hidden;
• proof_or_gate_absent;
• sponsor_captured_first_receipt;
• lawful_freeze_first;
• public_queue_crush_first;
• boundary_accuser_first;
• future_route_cited_unscoped;
• recovery_only_custody.

Recovery must keep the scar visible: reopen arbitration with excluded readers, publish late public receipt, attach lawful monitor, repair the floor lane, protect boundary holder, split custody, challenge sponsor countercopy, or accept public-only, lawful-only, sponsor-only, boundary-gated, blocked, hostile, or recovery-only use.

The executable post-default recovery proof is lens/replays/first-custody-arbitration.explicit-absence-recovery.replay.json: choice 7 arms the default, event option 0 removes 裴栈 and clears all pending state, and the explicit-absence rite then resolves the same twelve shared objects plus the absence card.

Non-goals

• Not a new verdict.
• Not a briefing-order replacement.
• Not a generic queue ticket.
• Not a duplicate of Pei Zhan’s recruitable character route.
• Not a clean stamp for all future readers.
• Not valid unless first custody is concrete, scoped, costly, and consumed by later play.