Shadow Evidence Transfer / 影子证据转运

A management/RPG rite for moving contested proof through dangerous field custody. The bound game id remains rite.turn54_shadow_evidence_transfer, but the canonical trigger is state pressure, not a fixed turn number.

The rite belongs to Inspection Shadow Crew Custody. Its executable character-lens form is offered only when the named contested packet, Cen Wei, permit, two claimants, handler, narrow cover, and future reader are all present. explicit_absence is a possible terminal result, not an assignment substitute.

Exact executable starter packet

The character-lens runtime uses exactly eight starter objects and exactly eight required slots:

SlotExact accepted object
runnercard-storyteller-cen-wei-temporary-chain-runner
permitcard-storyteller-inspection-shadow-crew-permit
proof_objectstoryteller.card.cen_wei_contested_proof_packet.v1
archive_claimantstoryteller.card.cen_wei_archive_claimant.v1
rival_claimantstoryteller.card.cen_wei_public_claimant.v1
handlerstoryteller.card.cen_wei_chain_handler.v1
coverstoryteller.card.cen_wei_custody_cover.v1
future_readerstoryteller.card.cen_wei_future_chain_reader.v1

All eight objects must be present in the player’s hand. Every slot is required, and every slot’s accepts list contains only its listed object. The runtime rejects:

  • a card assigned to the wrong slot;
  • another character, permit, claimant, handler, cover, or reader as a substitution;
  • tag-only, generic any, equivalent, or virtual objects;
  • omitted slots or objects missing from hand;
  • a rite request with no selected choice;
  • a branch/assignment mismatch.

This is deliberately stricter than the wider design vocabulary. A high-rank actor, abstract authority, or explicit-absence placeholder cannot replace Cen Wei or any of the other seven executable objects.

Branches

authorize_runner_lawful_custody - lawful chain

Assign a carrier with lawful inspection/archive cover.

Outcome:

  • carrier becomes lawful_chain_witness or neutral_route_asset;
  • custody clarity, proof legibility, or archive signature legitimacy improves;
  • inspection heat, bureau favor debt, lawful-only routing, or runner risk rises.

route_runner_to_public_receipt - public receipt chain

Assign a carrier through 郁蓝, fan oxygen witnesses, pirate relay, or public receipt pressure.

Outcome:

  • carrier becomes public_receipt_carrier;
  • public receipt legitimacy or private-capture resistance improves;
  • sponsor stop-loss pressure, fan oxygen liability, public exposure, or inspection heat rises.

mask_runner_under_editor_checksum - editor mask

Use 白鸦, black-box checksum, alias, redaction, or cutroom continuity to hide the carrier/source.

Outcome:

  • carrier becomes editor_masked_carrier;
  • witness retaliation risk or continuity hazard drops;
  • edit debt, archive debt, source ambiguity, or public receipt distrust rises.

retain_runner_as_production_neutral - production-neutral route

Keep the carrier inside production rather than giving them to a faction.

Outcome:

  • carrier becomes neutral_route_asset;
  • future transfer option or faction-capture delay improves;
  • handler burden, payroll leak, or future recovery cost rises.

accept_sponsor_cover_capture - sponsor capture

Let sponsor/manager cover fund or quiet the transfer.

Outcome:

  • immediate slot, cash, or retaliation pressure may improve;
  • carrier becomes sponsor-covered, suppressed, or captured;
  • contract capture, public distrust, ownership debt, or recovery cost rises.

suppress_runner_access - managed suppression

Use authority, audit shortcut, sponsor lock, production silence, or refusal to bypass the carrier slot.

Outcome:

  • immediate pressure may fall;
  • suppressed_carrier, explicit_absence, or unresolved custody gap is recorded;
  • future proof movement, proof burden, or receipt counterclaim becomes costlier.

sacrifice_runner_permit - sacrifice permit

Burn the permit, expose the runner, or sacrifice the carrier to protect stronger proof.

Outcome:

  • short-term collapse may be prevented;
  • carrier becomes sacrificed_permit, hostile_leak_source, or unavailable;
  • witness debt, legitimacy debt, false-owner pressure, or recovery cost rises.

abandon_runner_to_pirate_loop - hostile default

Allow the carrier, packet, or permit to fall into another claimant’s hands.

Outcome:

  • carrier becomes hostile_leak_source or captured_carrier;
  • Shadow Crew Custody Leak fires or arms;
  • future route becomes costlier, recovery-only, false-owner pressured, or blocked.

Resolution contract

Every resolution must mutate at least three counters or durable states. At least one must be relief and one must be cost.

resolution:
  selected_option_id: authorize_runner_lawful_custody | route_runner_to_public_receipt | mask_runner_under_editor_checksum | retain_runner_as_production_neutral | accept_sponsor_cover_capture | suppress_runner_access | sacrifice_runner_permit | abandon_runner_to_pirate_loop
  selected_branch: lawful_chain | public_receipt_chain | editor_mask | production_neutral_route | sponsor_cover | managed_bypass_or_suppress | sacrifice_carrier_or_permit | leak_capture_or_hostile
  carrier_state_before: <state>
  carrier_state_after: <state>
  route_or_proof_state_after: <state>
  counter_deltas:
    relief:
      - <relief counter/state>
    cost:
      - <cost counter/state>
  event_seen_or_armed: storyteller.event.shadow_crew_custody_leak | none

Failure cases

The rite is invalid if:

  • it appears from a fixed turn count rather than contested proof state;
  • the proof object is unnamed;
  • the carrier slot is erased by a high-rank actor;
  • fewer than two claimant factions are represented;
  • any of the eight exact starter objects is missing, virtual, substituted, assigned to the wrong slot, or absent from hand;
  • no branch choice is supplied;
  • success has no cost;
  • negative outcomes do not change future route access, carrier state, proof burden, or claimant pressure.

Non-goals

  • Not a fixed-turn rite despite the legacy game id.
  • Not a generic evidence move.
  • Not a free lawful custody repair.
  • Not valid unless carrier state and route/proof state both mutate.