K-404 Custody Return Hearing / K-404 羁押归还听证

K-404 Custody Return Hearing is the assignable rite that resolves a K-404 羁押错配案卷. It asks whether the producer can prove a route asset belongs to the apparent claimant, split the record, quarantine it, or prevent a rival faction from taking the first narration.

The rite is state-triggered. It opens from a concrete custody mismatch, not from fixed turn count.

Assignment slots

rite: storyteller.rite.k404_custody_return_hearing.v1
required:
  docket: storyteller.card.k404_custody_mismatch_docket.v1
  contested_object: <object id>
  route_asset_state_before: <state>
  apparent_claimant: <claimant>
  rival_claimant: <claimant or explicit_absence>
  terminal_index_state: <K-404 index state>
  proof_anchor_or_absence: <receipt, seal, checksum, fan oath, route log, witness name, public queue, explicit_absence>
assignable:
  handler: han_yanshuang | yu_lan | shen_luo | baiya | inspector_rhee | fan_witness | archive_clerk | service_runner | explicit_absence
  access_support: facility_pass | archive_seal | public_cover | sponsor_language | editor_checksum | route_log | explicit_absence
  selected_posture: verify_return | split_record | inspector_quarantine | public_notice | sponsor_settlement | edit_mask | suppress_terminal | abandon
price:
  money | favor_debt | inspection_heat | sponsor_pressure | edit_debt | public_distrust | fan_oxygen_resentment | terminal_exposure | handler_burden | route_delay | explicit_failure

Branch families

Verify return

The producer proves custody with a credible anchor and returns the object to a usable route state.

Expected result:

• route_asset_state_after becomes protected, route_asset, lawful_only, or public_only;
• custody_gap, false_owner, or route_block decreases;
• inspection_heat, terminal_exposure, handler_burden, or future_claim_cost rises.

Split record

K-404 records two incompatible but preserved claims.

Expected result:

• future route can choose public, lawful, editor, sponsor, or recovery side explicitly;
• false_owner is contained;
• source_ambiguity, archive_debt, public_receipt_distrust, or reality_drift rises.

Inspector quarantine

The object is kept from immediate use to stop a false return.

Expected result:

• fraud, contradiction, or false-owner pressure drops;
• current route use becomes delayed, blocked, costlier, or recovery-only;
• inspection_heat, bureau_favor_debt, fan_oxygen_resentment, or schedule_pressure rises.

Public notice

The producer uses fan witness, historian note, public queue, or pirate relay to prevent private capture.

Expected result:

• public legitimacy or fan witness value rises;
• sponsor, inspection, exposure, or route safety pressure rises;
• K-404 may become a public witness and therefore a reprisal target.

Sponsor settlement

The producer accepts sponsor language, money, or waiver to clear immediate docket pressure.

Expected result:

• budget or sponsor stop-loss pressure improves;
• contract_capture, public_receipt_distrust, artist_boundary_risk, or future blackmail rises;
• public or artist side becomes costlier.

Edit mask

The producer assigns Baiya, editor checksum, alias, or cutroom patch to make the object usable without exposing source custody.

Expected result:

• direct targeting or black-screen risk drops;
• edit_debt, source_ambiguity, archive_debt, or future_fraud_cost rises;
• later proof may require reveal, checksum, apology, or sacrifice.

Suppress terminal

The producer hides, locks, or overrides K-404 rather than resolving the mismatch.

Expected result:

• immediate claimant pressure may drop;
• terminal_suppressed, terminal_hostile_witness, unclaimed_archive_decay, or wrong_return_recorded becomes durable;
• at least one future route becomes blocked, hostile, captured, or recovery-only.

Abandon

No credible handler, proof anchor, or cost is assigned.

Expected result:

• rival claimant or default actor gains first narration;
• the mismatch emits a default event or equivalent consequence;
• route asset state becomes captured, false_owner, hostile, blocked, or recovery_only.

Required deltas

Every resolved branch must mutate at least three counters or durable states. At least one is relief, one is cost, and one changes future route availability.

Suggested surfaces:

• custody_gap
• route_asset_usability
• false_custody_owner
• terminal_exposure
• terminal_trust
• inspection_heat
• sponsor_stop_loss_pressure
• contract_capture
• fan_oxygen_resentment
• public_receipt_legitimacy
• public_receipt_distrust
• edit_debt
• source_ambiguity
• archive_debt
• future_claim_cost
• route_blocked
• recovery_route_cost

Failure cases

The rite fails its purpose if it resolves with no docket, no contested object, no claimant conflict or explicit absence, no proof anchor or explicit absence, no cost, or no future route effect.