Claimant Collision Lock Storyline / 认领撞锁

Claimant Collision Lock is a non-character pressure storyline for the moment after Storyteller has successfully created a route asset and the asset becomes too valuable to remain singular.

The sponsor wants to package it. The editor or black-box wants to turn it into a coherent public cut. The inspector or archive wants to seize the admissible copy. Public witnesses, fans, artists, or pirate memories may refuse all private versions. The player must decide whether to set claimant priority, split route copies, quarantine the unsafe copy, accept capture, burn the asset, or let a false owner harden.

Primary playable question

When a route asset has multiple live owners, who gets first executable custody — and what does the asset become afterward?

Every answer should preserve the earlier success as history while changing future route access, cost, and pressure.

Why this is the next useful expansion

The current wiki surface already has strong single-conflict systems: oxygen claims, memorial rights contempt, broadcast reality drift, route assets, voice custody, and sponsor liability. The remaining design gap is collision after success.

Without this storyline, a successful branch can accidentally erase older work: a sponsor settlement may overwrite a public witness; an editorial patch may erase inspector admissibility; an archive seizure may make a fan-funded route asset disappear as if it was never recruited. Claimant Collision Lock makes that overwrite playable.

It is not raw lens volume. It is a bridge that turns cross-system pressure into durable route mutation.

State-triggered entry

Open this storyline when all of the following are true:

  1. a route asset exists in a durable state from Route Assets and Custody: recruited, protected, route_asset, hostile, captured, false_owner, quarantined, or equivalent;
  2. at least three claimant families can alter the asset, or one missing family is explicitly important as a blocked/absent claimant;
  3. one claimant has offered a resolution that would suppress, capture, reframe, or devalue another claimant’s future use;
  4. at least one pressure counter is active: route_asset_pressure, sponsor_stop_loss_pressure, contract_capture, edit_debt, archive_debt, inspection_heat, public_receipt_legitimacy, fan_oxygen_resentment, reality_drift, continuity_hazard, or black_screen_slots;
  5. the asset has not already been assigned claimant priority, split, quarantined, captured, burned, or hardened.

This storyline must never trigger from a fixed numbered turn. It is entered from route-asset state and claimant pressure.

Content pack

Mechanic

  • 认领撞锁 — defines claimant families, collision states, branch contract, and replay evidence shape.

Card

  • 认领撞锁案卷 — records the route asset, sponsor/editor/inspector/public claims, public anchor or absence, collision state, and deltas.

Rite

  • 认领撞锁听证 — assignable management action that chooses claimant priority, split copies, quarantine, or failure.

Event

  • 路线资产扣押播报 — visible event when a claimant seizes, packages, cuts, quarantines, counters, or hardens the asset.

Primary actors

  • Orion Breath — sponsor claim, breath escrow, stop-loss, clean-ending, relief packaging.
  • Shen Luo — contract containment, settlement language, sponsor bridge, future capture cost.
  • Han Cutroom — cutroom receipt, final cut, source proof, hostile editorial witness.
  • Baiya — black-box copy, checksum, redaction, replay-safe or fraud-prone patch.
  • Inspector Rhee Archive — admissible copy, voice/archive seizure, quarantine, audit shield.
  • Han Yanshuang — white-glove pressure, official lock, sanction, route-safe appeal.
  • Yu Lan — public receipt, historian counterproof, fan-facing memory, public anchor.

Core route states

Route stateMeaningRequired consequence
collision_detectedDurable route asset has competing claimants.Offer docket/hearing or equivalent action.
priority_setOne claimant controls first use.One route improves; at least two claimant debts remain.
sponsor_priority_settlementSponsor/manager controls the asset’s first public use.Sponsor pressure falls; capture/distrust/fan/inspection debt rises.
editorial_priority_cutEditor/black-box controls asset legibility.Continuity improves; edit/archive/fraud/public distrust debt rises.
inspector_priority_sealInspector/archive controls admissible copy.Custody/fraud improves; inspection, bureau, sponsor, public, or schedule cost rises.
route_copies_splitAsset becomes plural across route futures.Multiple future actions unlock; drift/debt rises.
quarantined_collision_copyUnsafe copy is contained.Fraud/blackout risk improves; public grief/fan/sponsor/schedule cost rises.
asset_capturedA claimant removes asset from clean player use.Recovery, appeal, exchange, or counterproof required.
burned_assetPlayer spends asset to protect another route.Immediate pressure may drop; future option is lost or scarred.
false_owner_hardenedWrong claimant becomes visible owner.Later custody clean-success becomes harder or impossible.

Branch model

Branch A — Sponsor priority settlement

The player assigns sponsor or manager priority through Orion, Shen Luo, stop-loss language, relief funding, escrow receipt, or clean-ending contract.

Expected outcomes:

  • collision_resolution = sponsor_priority_settlement or asset_captured_by_sponsor;
  • sponsor_stop_loss_pressure -1 or immediate schedule pressure improves;
  • contract_capture +1;
  • at least one public, fan, inspector, editor, archive, or artist pressure worsens.

Branch B — Editorial continuity priority

The player assigns editor, cutroom, black-box, checksum, source cut, or continuity patch.

Expected outcomes:

  • collision_resolution = editorial_priority_cut or asset_converted_to_cut;
  • continuity_hazard -1, audience_churn -1, or route legibility improves;
  • edit_debt +1 plus archive debt, public receipt distrust, future fraud, or voice/body risk;
  • sponsor or inspector options remain contested, not deleted.

Branch C — Inspector/archive priority

The player assigns Inspector Rhee, Han Yanshuang, audit proof, archive docket, quarantine seal, or lawful custody object.

Expected outcomes:

  • collision_resolution = inspector_priority_seal, asset_seized_for_audit, or quarantine_copy_created;
  • archive_fraud -1, custody_clarity +1, or lawful route access improves;
  • inspection_heat +1, bureau_favor_debt +1, sponsor pressure, public grief, or schedule cost rises;
  • at least one sponsor/editor/public path becomes delayed or requires appeal.

Branch D — Public split copies

The player assigns Yu Lan, fan queue, artist refusal, pirate memory, source proof, or audience-stability reason as a public anchor and accepts plural custody.

Expected outcomes:

  • collision_resolution = route_copies_split or public_anchor_copy_created;
  • public_receipt_legitimacy +1, fan_oxygen_balance +1, or witness route access improves;
  • reality_drift +1, inspection_heat +1, sponsor_stop_loss_pressure +1, or archive_debt +1;
  • at least two route copies have different future costs.

Branch E — Quarantine unsafe copy

The player proves the asset is unsafe, fraudulent, consent-unclear, or too contradictory to air/package now.

Expected outcomes:

  • collision_resolution = quarantined_collision_copy;
  • archive_fraud -1, black_screen_slots -1, voice_integrity_risk -1, or false-owner risk decreases;
  • fan_oxygen_resentment +1, public_grief_stability -1, sponsor_stop_loss_pressure +1, or schedule pressure rises.

Branch F — Capture, burn, miss, or false owner

The player lacks a credible claimant, lacks opposing proof, suppresses public anchor, blocks inspector access, or lets a claimant seize the asset by inertia.

Expected outcomes:

  • collision_resolution = claimant_collision_missed, asset_captured, burned_asset, or false_owner_hardened;
  • route_asset_pressure +1, archive_debt +1, reality_drift +1, fan_oxygen_resentment +1, black_screen_slots +1, or contract_capture +1;
  • at least one future rite is blocked, harder, or requires recovery.

Counter contract

At least three counters or durable states must change on resolution or hardening:

  • route_asset_pressure
  • sponsor_stop_loss_pressure
  • contract_capture
  • edit_debt
  • archive_debt
  • inspection_heat
  • bureau_favor_debt
  • custody_clarity
  • public_receipt_legitimacy
  • public_receipt_distrust
  • fan_oxygen_resentment
  • reality_drift
  • continuity_hazard
  • black_screen_slots
  • false_owner_hardened

Multi-session continuity expectation

This storyline is especially useful for durable replay validation. A correct implementation should show that a branch in one session creates or mutates an asset, and a later session can load that asset into a collision state without losing the earlier provenance.

Expected evidence:

  • original route asset source session id and seed;
  • current collision session id and seed;
  • asset prior state from the earlier branch;
  • live claimant families;
  • offered hearing choices and blocked reasons;
  • selected assignments;
  • outcome state and deltas;
  • future route access changes.

Missability and recovery

The storyline is missable when the player sells the asset to a clean sponsor package, relies on an editorial cut without public/admissible proof, ignores inspector seizure until the asset is removed, or suppresses public anchor long enough for a false owner to harden.

Recovery is allowed only at higher cost:

  • appeal an inspector seizure;
  • recover captured asset through exchange;
  • publish counter-receipt with sponsor backlash;
  • split route copies and accept drift;
  • quarantine unsafe copy and accept public grief;
  • replace the burned asset with a weaker substitute.

Integration notes

Non-goals

  • Not a fixed-turn late-game episode.
  • Not a generic legal hearing.
  • Not a filler lens to raise count.
  • Not a clean merge of sponsor, editor, inspector, and public interests.
  • Not a retcon of previous branch success; earlier asset provenance must remain visible.