First Custody Arbitration Lens / 首接保全裁断 Lens
This lens observes whether First Custody Arbitration and First Custody Arbitration prevent a false-service claimant row from becoming clean universal receipt merely because one desk stamped it first.
The character lens for Pei Zhan First-Custody Bailiff proves the worker route. This lens proves the system contract: first custody must expose source row, selected first reader, excluded readers, proof/gate/handler state, slip posture, durable default, and future route effect before downstream play can cite the row. When 裴栈 is absent, captured, or already removed, the system must use a distinct explicit-absence object and recovery rite rather than pretending the character still filled the handler slot.
Observable promise
A passing implementation must show:
- source false-service row;
- preserved source ruling or row;
- at least two 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;
- durable default when first custody is hidden, false, captured, overrun, or universalized.
The lens fails if implementation stores only handled, first reader, public number, sponsor receipt, lawful seal, queue order, or claimant notified.
Entry oracle
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: trueThe lens fails if entry comes from a fixed turn, fixed day, raw row count, generic office visit, dashboard state, lens health, or Pei Zhan recruitment checklist.
Slip oracle
First Custody Slip must keep source row, receipt, posture, and future effect separate.
first_custody_slip_required:
source:
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
receipt:
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:
stamp_posture: public_first | lawful_first | sponsor_first | boundary_first | floor_carrier_first | split_custody | quarantine | refused | default_capture
slip_state_after: public_first_receipt | lawful_first_receipt | sponsor_first_countercopy | boundary_first_receipt | floor_carrier_first_receipt | split_custody_slip | quarantine_no_first_reader | refused_with_record | default_captured_first_custody | recovery_only_custody
result:
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_pendingThe slip fails if it records a false-service row without selected reader, excluded reader, proof/gate/handler or explicit absence, and future effect.
Arbitration oracle
First Custody Arbitration must expose these branch families:
public_firstlawful_firstsponsor_firstboundary_firstfloor_carrier_firstsplit_custodyquarantine_or_refusedefault_capture
Each branch must include relief, cost, and future_reader or future_route_effect. No branch may make one first receipt satisfy public, lawful, sponsor, artist-boundary, floor, management, route-asset, and broadcast-reality readers cleanly.
Explicit handler-absence recovery
The system wrapper must also expose rite.storyteller.first_custody_handler_absence_recovery.v1. It uses the same twelve non-handler assignment objects as the character rite, but the handler slot accepts only card.storyteller.first_custody_handler_explicit_absence.v1.
The recovery rite must:
- reject execution while
character.pei_zhan_first_custody_bailiffremains in hand; - reject Pei Zhan, substitutions, virtual placeholders, missing assignments, and no-choice resolution;
- expose only
record_explicit_handler_absence; - write exactly five counter deltas;
- retain
card.storyteller.first_custody_scar_counterreceipt.v1; - set
slip.state.recovery_only_custodyandfuture_route.recovery_only; - clear superseded sponsor, default-captured, false-first, public-hostile, and blocked current slip/route flags while preserving historical capture and branch flags;
- leave all
pei_zhan.*androute_asset.*state unchanged.
Default oracle
First Custody Default must record:
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 | management | pirate_relay | lawful_archive | public_queue | floor_carrier | artist_boundary | no_reader | equivalent
excluded_reader: <reader or explicit_absence>
failed_input: assigned_handler_refused | assigned_gate_rejected | wrong_gate | no_proof | private_countercopy | public_safety_absent | lawful_notice_absent | future_route_cited_unscoped | equivalent
default_state_after: false_first_custody | sponsor_captured_first_receipt | pirate_first_custody | lawful_freeze_first | public_queue_crush_first | boundary_accuser_first | floor_carrier_refusal_first | recovery_only_custody
future_route_effect: blocked | hostile | public_only | lawful_only | sponsor_only | boundary_gated | recovery_only | contradiction_pending | costlier
recovery_hook_or_terminal: <hook or terminal>
counter_deltas:
relief: []
cost: []
future: []The default fails if it is only heat, delay, or angry claimant mood without capturing reader, excluded reader, failed input, future route effect, and recovery hook or terminal.
Replay evidence
lens/replays/first-custody-arbitration.explicit-absence-recovery.replay.json must prove a real post-default transition: the character arbitration selects default_capture, the priority default removes 裴栈 and clears all five pending markers, then the explicit-absence recovery rite accepts the exact no-Pei packet. The terminal state must retain historical sponsor capture, clear the superseded sponsor-only/current-slip flags, expose recovery-only custody, and add no Pei Zhan or route-asset mutation.
Progress metric
firstCustodyArbitrationProgress = 0..9:
0: no false-service row is visible.1: source false-service row and preserved source ruling or row are visible.2: two or more candidate first readers are visible.3: selected first reader and excluded/scoped readers are visible or explicitly absent.4: proof, intake gate, and handler are visible or explicitly absent.5: First Custody Slip separates source, receipt, posture, and future locks.6: arbitration resolves a branch with relief, cost, and future effect.7: first custody state is consumed by a downstream reader or route.8: hidden, false, captured, overrun, or universalized custody arms a durable default with recovery scar.9: after Pei Zhan is absent or captured, the exact explicit-absence packet resolves recovery-only custody without character or route-asset mutation.
Non-goals
- Not a new ruling.
- Not a claimant briefing-order lens.
- Not a Pei Zhan recruitment lens.
- Not a generic queue or priority lens.
- Not valid if one first stamp has no selected reader, excluded reader, gate/proof/handler, cost, and future mutation.