First Custody Arbitration / 首接保全裁断机制

First Custody Arbitration is the mechanism that decides who receives the first durable custody slip for a false-service claimant row when multiple readers can plausibly claim the first copy.

It sits between 误服裁定认领升级机制, 认领人现场接待线, and 裁定读者冲突线. The source ruling is preserved. The false-service row remains visible. The new state is the first custody slip: who held, stamped, or publicly numbered the row before later systems cited it.

This mechanism deliberately differs from 认领告知顺序线. Briefing order is pre-action notice. First custody is post-row custody: after the row exists, which reader can later say, “I received it first.”

Design problem

The current mesh now proves that false-service defaults create claimant rows. It also proves that reader collisions can happen when future readers disagree. The remaining seam is the first custody artifact between those systems.

Without this mechanism, a false-service row can silently become a universal receipt. A sponsor counterdesk, public queue, inspector seal, artist boundary, floor carrier, pirate relay, or management metric could all pretend to be the first valid holder. First Custody Arbitration forces that first holder to be explicit, costly, scoped, and replayable.

State-triggered entry

Open this mechanism only when all are true:

entry_state:
  trigger_kind: state_pressure
  false_service_claimant_row_present: true
  source_ruling_or_row_preserved: true
  first_custody_slip_present_or_expected: true
  candidate_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

Valid candidate readers include public/fan, pirate relay, lawful archive, inspector, sponsor counterdesk, management metric, artist boundary, witness, floor carrier, route asset, editor/source checksum, or explicit absence.

Core objects

• 首接保全回执 is one object in the exact thirteen-object assignment packet and records the selected local custody state.
• card.storyteller.first_custody_handler_explicit_absence.v1 is the only valid handler-slot object for the no-Pei system recovery packet.
• 首接保全裁断 documents two strict rites: the eight-choice Pei Zhan character arbitration and the one-choice explicit handler-absence recovery.
• 首接保全默认 consumes choice 7 pending state and resolves one of four durable capture/miss scars.

Exact assignment packets

Both rites use the same twelve shared assigned hand objects:

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. card.storyteller.first_custody_support_witness.v1
10. card.storyteller.first_custody_posture_register.v1
11. card.storyteller.first_custody_cost_ledger.v1
12. card.storyteller.false_service_future_reader.v1

The character packet adds character.pei_zhan_first_custody_bailiff as the thirteenth handler object. The system absence packet instead adds card.storyteller.first_custody_handler_explicit_absence.v1, and it is executable only when Pei Zhan is not in hand.

All slots are required, the assigned cards must be in hand, and each slot accepts only its named object. Neither packet can use substitution or virtual placeholders. Both prove local first custody only; neither grants universal receipt, consent, adjudication, sponsor release, archive ownership, or universal broadcast permission.

Reader families and acceptance rules

Reader	Requires	Rejects
Public / fan / historian	visible number, public receipt, witnessable terms	private-only sponsor or sealed archive first copy
Pirate relay	copyable proof and public memory path	management-only cleanliness and silent lawful freeze
Lawful archive / inspector	admissible proof chain, source row, gate, authority	unnumbered crowd copy or sponsor-only relief
Sponsor / management	countercopy, stop-loss framing, reportable relief	public-first scar that increases contract exposure
Artist / witness / refusal holder	boundary notice, consent/refusal surface, safe carrier	route unlock before boundary receipt
Floor carrier / crew	real lane capacity, named handler, safety debt	authority-only receipt that ignores floor load
Route asset / future route	scoped future use and recovery cost	universal clean key with no scar

State machine

states:
  - first_custody_expected
  - first_custody_slip_created
  - public_first_receipt
  - lawful_first_receipt
  - sponsor_first_countercopy
  - boundary_first_receipt
  - floor_carrier_first_receipt
  - split_custody_slip
  - recovery_only_custody
  - default_pending_first_custody
  - default_captured_first_custody
  - false_first_custody_hardened

The source ruling and false-service row are never erased. A branch changes who can use them later.

Branch contract

Every character-rite branch writes exactly five counter deltas and one distinct 裴栈/slip/future-route triplet:

Choice	Branch	Durable triplet
0	public_first	protected_public_witness / public_first_receipt / public_table_required
1	lawful_first	lawful_chain_witness / lawful_first_receipt / lawful_only
2	sponsor_first	sponsor_captured_signature / sponsor_first_countercopy / sponsor_only
3	boundary_first	boundary_quarantine_guard / boundary_first_receipt / boundary_gated
4	floor_carrier_first	route_asset_first_custody_witness / floor_carrier_first_receipt / floor_gate_required
5	split_custody	split_custody_bailiff / split_custody_slip / contradiction_pending
6	quarantine_or_refuse	hostile_chain_bailiff / recovery_only_custody / recovery_only
7	default_capture	default_pending / default_pending_first_custody / first_custody_default_pending

Choice 4 alone recruits 裴栈 and grants route_asset.pei_zhan_first_custody_witness. Choice 7 alone arms first_custody.default_pending, event.first_custody_default.armed, and future_route.first_custody_default_pending; it is incomplete until the default event resolves.

The separate system rite exposes only record_explicit_handler_absence. It writes slip.state.recovery_only_custody, future_route.recovery_only, and the scar counterreceipt without mutating any pei_zhan.* or route_asset.* state. It preserves historical capture/branch flags but clears superseded sponsor, default-captured, false-first, public-hostile, or blocked current slip/route states. Its five exact deltas are false_owner_risk -2, first_custody_absence_legibility +3, route_recovery_cost +4, claimant_hostility +2, and future_correction_cost +3.

Primary surfaces:

surfaces:
  - first_custody_legitimacy
  - first_custody_slips_open
  - false_service_exposed
  - claimant_row_received
  - proof_chain_integrity
  - custody_clarity
  - public_receipt_legitimacy
  - public_receipt_distrust
  - sponsor_stop_loss_pressure
  - contract_capture
  - inspection_heat
  - archive_debt
  - bureau_favor_debt
  - fan_oxygen_resentment
  - artist_refusal_respected
  - witness_exposure
  - floor_lane_load
  - crew_refusal_risk
  - handler_burden
  - reader_collision
  - false_first_claimant
  - claimant_hostility
  - future_route_acceptance
  - route_recovery_cost

Integration rules

• With 误服裁定认领升级线, this mechanism opens only after a claimant-facing default has become a concrete row.
• With 认领人现场接待线, first custody must name the gate or floor lane that received or failed to receive the row.
• With 裁定读者冲突线, the first custody slip becomes the preserved source row for later reader incompatibility.
• With 认领告知顺序线, first custody may use prior notice state, but cannot replace physical/public/lawful receipt.
• With 认领撞锁, a first custody slip can become a route asset or false owner.
• With 经营压缩台, management cannot report the false-service row as clean unless the first custody scar is visible.

Failure modes

The mechanism fails if any are true:

• false-service row exists but no first receiving reader is recorded;
• one stamp or handler satisfies all readers with no cost;
• excluded readers are not named or explicitly scoped;
• sponsor, law, public queue, artist boundary, floor carrier, edit checksum, or management metric can receive first custody for free;
• future route acceptance is unchanged across first-reader choices;
• missed first custody does not harden into false-first, public-only, lawful-only, sponsor-only, boundary-gated, hostile, blocked, or recovery-only state;
• entry depends on fixed turn, day, week, chapter, dashboard, or raw content count.

Replay evidence shape

• lens/replays/pei-zhan-first-custody-bailiff.recruit.replay.json uses all thirteen assignments and choice 4; it proves pei_zhan.recruited, the route-asset flag, floor receipt, floor-gated future use, and five exact deltas.
• lens/replays/pei-zhan-first-custody-bailiff.default-capture.replay.json uses the same packet and choice 7, then resolves First Custody Default option 0; it proves pending-flag clearance, sponsor capture, miss, character-card loss, default scar, and retained counterreceipt.
• lens/replays/first-custody-arbitration.explicit-absence-recovery.replay.json continues from the post-default no-Pei state, assigns the twelve shared objects plus the explicit-absence card, and proves one recovery-only branch with no character or route-asset mutation.

Non-goals

• Not a new ruling.
• Not a turn-count aftermath.
• Not a crowd-control scene.
• Not a duplicate of briefing order.
• Not a replacement for false-service escalation, claimant floor intake, or reader collision.
• Not valid unless first custody is concrete, scoped, costly, and consumed by a later reader.