Inspection Shadow Crew Custody Storyline / 监察影子组羁押线

This page keeps the existing shadow crew package but removes its old fixed-turn framing. The file path is legacy-compatible; the canonical storyline is state-triggered field custody.

Inspection Shadow Crew Custody begins when a proof object must physically move through a dangerous backstage chain before it can become lawful, public, edited, hidden, or enforceable. The player must decide who carries it, who covers the carrier, who can contest the handoff, and what cost survives after the transfer.

Why this is the next useful expansion

The current corpus has strong proof and custody systems: Evidence Carryover Fork makes old proof return, Proof Burden Reassignment makes successful proof need a holder, and Route Assets and Custody makes carriers and proof objects durable.

The weak spot is not another ruling. The weak spot is field movement. If 韩砚霜, 郁蓝, 白鸦, 沈洛, or a sponsor desk can solve custody without a carrier, permit, receipt, corridor risk, or explicit absence, management/RPG play becomes too top-heavy. This storyline forces the service-corridor layer to matter.

Primary playable question

When contested proof must cross the floor, does the player:

  • authorize a low-rank carrier under lawful cover;
  • route the carrier through public/fan/historian receipt;
  • mask the carrier through black-box edit work;
  • bypass or suppress the carrier with high-rank pressure;
  • sacrifice the permit or carrier to protect stronger proof;
  • let the carrier be captured, missed, or turned hostile?

Every answer must change future route access, carrier state, proof burden, claimant pressure, or counter cost.

State-triggered entry

Open this storyline only when all conditions below are present:

  1. a movable or physically uncertain proof object exists;
  2. that object can affect a current or future route, custody claim, proof burden, public receipt, consent debt row, archive order, or broadcast reality state;
  3. at least two factions can contest the handoff;
  4. a carrier, permit, witness, runner, clerk, fan delegate, editor source, or explicit absence can be represented;
  5. at least one route, rite, follower state, card state, or counter can mutate if the transfer succeeds or fails.

Do not open this storyline from a fixed numbered turn, day interval, chapter quota, raw page count, lens-health state, or generic upkeep phase. Old ids may remain in implementation data, but replay logic must prove state pressure.

Content pack

Mechanism

NPC / route asset

Card

Rite

  • Shadow Evidence Transfer resolves the carrier, cover, proof object, and claimant pressure. Its legacy id may remain, but it must be offered from contested custody state.

Event

  • Shadow Crew Custody Leak fires or arms when the handoff lacks cover, becomes exposed, is suppressed, or is sacrificed.

Core cast and functions

  • Han Yanshuang can give lawful cover, oath pressure, or inspection debt.
  • Yu Lan can convert a carrier into public receipt pressure and fan witness exposure.
  • Baiya can mask identity, checksum the packet, or contaminate source clarity.
  • Shen Luo can negotiate manager/sponsor cover while increasing contract capture risk.
  • Sponsor desk can fund quiet movement or suppress the carrier, but ownership debt remains.
  • Production desk can keep the carrier neutral, but handler burden, payroll leak, and recovery cost rise.

A named actor cannot replace the carrier. The branch must record the carrier or explicit absence.

Storyline sequence

Beat 1 — Proof has to cross a floor

A contested object becomes physically relevant. It may be a fan oxygen receipt, archive copy, black-box fragment, memorial air receipt, consent printout, witness stub, route-asset packet, or voice custody receipt.

The object is not useful just because it exists. It must reach a lawful desk, public witness chain, editor cutroom, production safe room, sponsor desk, archive table, or recovery route.

Beat 2 — Carrier or absence becomes visible

Create or update a carrier row with:

field_custody_row:
  proof_object: <object id>
  claimant_factions:
    - <claimant one>
    - <claimant two>
  carrier_before: crew_unseen | crew_offer_ready | runner_authorized | neutral_route_asset | suppressed_carrier | hostile_leak_source | captured_carrier | explicit_absent
  permit_or_cover: inspection_shadow_crew_permit | audit_oath | public_receipt | editor_mask | sponsor_cover | none
  affected_route_asset: <route or asset id>
  risk_if_ignored: leak | false_owner | proof_default | capture | route_costlier | recovery_only | blocked

Beat 3 — Evidence transfer choice

Offer Shadow Evidence Transfer or equivalent once the row is concrete. Valid branches include lawful chain, public receipt chain, editor mask, managed bypass, suppression, sacrifice, leak, capture, and hostile carrier.

Beat 4 — Carrier and route state mutate

The selected branch must mutate both a carrier/absence state and a route/proof state.

Carrier states include:

  • runner_authorized
  • lawful_chain_witness
  • public_receipt_carrier
  • editor_masked_carrier
  • neutral_route_asset
  • suppressed_carrier
  • hostile_leak_source
  • captured_carrier
  • sacrificed_permit
  • explicit_absent

Route/proof states include:

  • protected
  • lawful_only
  • public_only
  • costlier
  • contradiction_pending
  • split_canon
  • proof_burden_holder_changed
  • false_owner_pressure
  • recovery_only
  • blocked

Beat 5 — Leak, payroll, or proof-burden aftermath

A successful carrier does not become a free permanent key. If the carrier survives, they may enter Protected Witness Payroll. If the carrier becomes the only chain proof holder, they can feed Proof Burden Reassignment. If the object returns later, it can feed Evidence Carryover Fork.

If the player hides, suppresses, underpays, overuses, sells, or abandons the carrier, Shadow Crew Custody Leak fires or becomes default-ready.

Branch matrix

BranchImmediate reliefCost/scarFuture state
Lawful chainadmissibility, custody clarity, false-owner pressure downinspection heat, bureau debt, lawful-only routing, runner risklawful_chain_witness, lawful_only, protected
Public receipt chainprivate capture blocked, public legitimacy upsponsor pressure, fan liability, public exposure, inspection heatpublic_receipt_carrier, public_only, costlier
Editor maskretaliation risk or continuity hazard downedit debt, source ambiguity, archive debt, public distrusteditor_masked_carrier, split_canon, contradiction_pending
Production neutral routecarrier remains assignable without faction capturehandler burden, payroll leak, future recovery costneutral_route_asset, protected-but-costlier
Sponsor/manager coverimmediate slot or money pressure downcontract capture, public distrust, ownership debtsuppressed_or_sponsor_carried, captured, recovery_only
Suppress/bypassshort silence or fewer immediate costsunresolved custody gap, harder future transfer, proof burden risksuppressed_carrier, explicit_absent, costlier
Sacrifice permit/carrierprotects stronger proof or stops leak nowlost carrier, legitimacy debt, witness hostilitysacrificed_permit, hostile_leak_source, recovery_only
Leak/capture/hostilenone, or only forced public truthfalse owner, duplicate claim, hostile testimony, blocked routehostile_leak_source, captured_carrier, false_owner_pressure

Counter contract

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

Primary counters:

  • custody_clarity
  • custody_gap
  • proof_legibility
  • proof_burden
  • route_asset_pressure
  • runner_risk
  • payroll_leak
  • handler_burden
  • inspection_heat
  • bureau_favor_debt
  • archive_signature_legitimacy
  • archive_debt
  • public_receipt_legitimacy
  • public_receipt_distrust
  • fan_oxygen_liability
  • fan_oxygen_resentment
  • sponsor_stop_loss_pressure
  • contract_capture
  • edit_debt
  • source_ambiguity
  • continuity_hazard
  • false_owner_pressure
  • future_recovery_cost

Missability and recovery

This storyline is missable when the player treats physical custody as solved by authority, money, public support, or edit skill alone.

Missed states:

  • carrier_absent_unrecorded
  • suppressed_carrier
  • hostile_leak_source
  • captured_carrier
  • sacrificed_permit
  • false_owner_pressure_hardened
  • proof_burden_default_ready
  • recovery_only_transfer

Recovery is allowed only through visible cost:

  • reopen transfer with a different carrier;
  • pay witness payroll or safehouse cost;
  • seek audit oath and accept lawful-only routing;
  • publish public receipt and accept sponsor/fan backlash;
  • let editor mask the source and accept archive debt;
  • rescue or exchange a captured carrier;
  • sacrifice a weaker route asset to preserve the proof chain;
  • accept split-canon and continue with lawful/public/editor divergence.

Replay evidence expectation

A correct implementation proves both a carrier-success branch and a carrier-negative branch from state pressure, not from turn count.

storyline_id: storyteller.storyline.inspection_shadow_crew_custody.v2
session_id: lens-storyteller-inspection-shadow-crew-custody-v2-<timestamp>
seed: <deterministic seed>
provenance_turn_range: <optional debug field only>
entry_state:
  trigger_kind: state_pressure
  movable_or_uncertain_proof_present: true
  claimant_factions_count_min: 2
  carrier_or_explicit_absence_present: true
  affected_route_or_counter_present: true
  no_fixed_turn_trigger: true
offered_choices:
  - recruit_or_authorize_carrier
  - lawful_chain_cover
  - public_receipt_cover
  - editor_mask
  - managed_bypass_or_suppress
  - sacrifice_or_abandon
assigned_slots:
  proof_object: <object id>
  carrier: cen_wei | lin_qiao | fan_delegate | archive_clerk | explicit_absent | equivalent
  permit_or_cover: inspection_shadow_crew_permit | audit_oath | public_receipt | editor_mask | sponsor_cover | none
  handler: han_yanshuang | yu_lan | baiya | shen_luo | sponsor | production | none
branch_result:
  selected_branch: <branch>
  carrier_state_before: <state>
  carrier_state_after: <state>
  route_or_proof_state_after: <state>
  event_seen_or_armed: storyteller.event.shadow_crew_custody_leak | none
  counter_deltas:
    relief:
      - <relief counter/state>
    cost:
      - <cost counter/state>

Non-goals

  • Not a fixed-turn package.
  • Not a generic crew-card generator.
  • Not a raw scale-count satisfaction page.
  • Not a governance/process page.
  • Not a free universal fix for archive, sponsor, fan, memorial, voice, proof, or consent pressure.
  • Not valid unless a physical carrier/permit/proof/absence changes future route access, claimant pressure, carrier state, or cost.