Adverse Coalition Lock / 反向同盟锁线

Adverse Coalition Lock is the pressure storyline for the moment when two or more previously costed factions stop acting separately and combine their claims against a route asset that the player already made useful.

A sponsor may have lost public wording. An inspector may have spent lawful cover. An editor may have withheld source custody. A fan public may have paid oxygen legitimacy. A claimant may have been deferred by mandate triage. Alone, each row is already playable through existing systems. Together, they can form a hostile lock that no single clean route can answer.

Why this is the next useful expansion

The current wiki is strong at local pressure:

• 派系承诺账本 makes faction leverage finite and can produce coalition_formed.
• 三钥羁押撞锁线 makes sponsor, inspector, and cutroom keys collide around one asset.
• 执行授权枯竭线 makes enforcement service finite after multiple valid rows exist.
• 播出合法性转轨线 makes future channel acceptance explicit.
• Route Assets and Custody makes people, proofs, and copies persist as route assets.

The gap is adversarial coordination. After the producer wins several small battles, losing factions should be able to coordinate. If the player cannot see and break that coordination, victories become either too clean or too randomly punished. This storyline turns coalition pressure into a card, rite, event, and lensable oracle.

Primary playable question

When two factions combine their previous spend, loss, silence, law, money, edit custody, public attention, or claimant injury into a lock over the same target, does the producer break the coalition with contradiction, split its members, buy a stand-down, freeze the target, release a decoy, or let the lock harden into capture?

Every answer must preserve the source victories and source costs. A coalition is not a retcon; it is a later use of remembered scars.

State-triggered entry

Open this storyline only when all of the following are true:

1. a named target asset, proof object, person, copy, public receipt, lawful record, edit version, or broadcast slot has prior use or relief;
2. at least two faction rows share that target;
3. each member row has prior spend, loss, denied control, exposed contradiction, unpaid debt, or harmed claimant memory;
4. the combined demand can block, capture, narrow, harden, or make costlier at least one current or future route;
5. the player has at least three plausible responses among contradiction, split, stand-down, freeze, decoy, or default;
6. source provenance can be recorded.

This storyline must never open from fixed numbered turn, day interval, chapter quota, raw content count, lens-health state, or generic escalation label.

Content pack

Mechanic

• 反向同盟锁机制 defines coalition rows, lock states, branch families, counter contract, miss/recovery, and replay evidence shape.

Card

• 反向同盟案卷 records the target, member rows, member spend/loss, combined terms, contradiction or absence, harmed claimant, branch response, and future route effect.

Rite

• 反向同盟破锁听证 is the assignable hearing where the player breaks, splits, buys down, freezes, decoys, or defaults the coalition.

Event

• 同盟锁死硬化 fires or arms when the coalition narrates the target first, is hidden, is falsely dissolved, or is accepted without cost.

Core actors and functions

• Han Yanshuang can force lawful contradiction, freeze a lock under oath, or make coalition terms admissible at the cost of inspection heat and bureau debt.
• Yu Lan can expose coalition terms publicly, preserving public receipt legitimacy while raising retaliation, sponsor pressure, and public witness risk.
• Shen Luo can buy a stand-down or separate members through manager language, but contract capture and future blackmail rise.
• Baiya can produce checksum contradiction, decoy release, or edit escrow, but source ambiguity and edit debt rise.
• Orion Breath, Inspector Rhee Archive, and Han Cutroom are common coalition members, but they are not the only possible members.

Storyline sequence

Beat 1 — A useful target attracts remembered enemies

A target from route custody, legality conversion, enforcement triage, three-key custody, witness payroll, public receipt, archive order, or cutroom priority becomes useful again.

The game checks whether two or more rows share the target and whether each row has remembered spend or loss. If yes, create or update 反向同盟案卷.

Beat 2 — Coalition terms become visible

The docket names the coalition members and combined lock terms.

Valid examples:

• sponsor escrow plus inspector seizure notice creates a release gate;
• inspector oath plus editor checksum creates source freeze;
• sponsor money plus editor clean copy creates private copy capture;
• archive notice plus claimant grief ownership creates false-owner pressure;
• fan public plus pirate timestamp creates public-only gate;
• sponsor retainer plus archive silence creates quiet coalition.

Beat 3 — The player chooses how to break or carry the lock

Run 反向同盟破锁听证. The rite requires target, member rows, proof or explicit absence, handler or explicit absence, cost/collateral, and selected response.

Beat 4 — Target state mutates

The target must not return to a clean pre-coalition state. It becomes one of:

• unlocked with scar;
• public-audited;
• lawful-conversion-required;
• split-custody;
• sponsor-gated;
• quarantined;
• contradiction-pending;
• decoyed;
• captured;
• hostile;
• false-owner;
• recovery-only.

Beat 5 — Future routes inherit the coalition scar

At least one future route, rite, or assignment must change. Accepted changes include costlier use, channel limitation, required conversion, public audit, lawful appeal, sponsor gate, edit-source reveal, witness rescue, route-asset exchange, or recovery-only use.

Branch matrix

Branch	Immediate relief	Cost/scar	Future effect
Break by contradiction	Coalition story weakens; false owner pressure falls.	Inspection heat, public exposure, source ambiguity, or faction hostility rises.	Unlocked with scar, public audit required, lawful conversion required.
Split coalition	One member loses clean pressure.	Unserved member retaliation or watchlist remains.	Split custody, costlier route, public-only/lawful-only/sponsor-only/editor-only.
Buy stand-down	Current route opens or lockout delays.	Contract capture, bureau debt, edit debt, fan resentment, or blackmail rises.	Sponsor gate, future debt, recovery cost.
Freeze target	Coalition cannot narrate target first.	Schedule, route, handler, public, or sponsor pressure rises.	Quarantined, delayed, recovery-only.
Decoy release	Primary asset survives immediate lock.	Source ambiguity, edit debt, public distrust, or future fraud rises.	Split canon, contradiction pending, costlier route.
Default harden	Coalition resolves the target first.	Target capture, false owner, hostility, channel-only lock, or recovery-only state.	Rescue, conversion, appeal, counterproof, or route block.

Counter contract

Every branch must mutate at least three counters or durable states, with at least one relief and one cost unless the selected branch is default hardening.

Expected surfaces:

• coalition_pressure
• coalition_lock_strength
• coalition_trace_legitimacy
• route_asset_pressure
• custody_gap
• false_owner_pressure
• sponsor_stop_loss_pressure
• contract_capture
• inspection_heat
• bureau_favor_debt
• archive_debt
• edit_debt
• source_ambiguity
• public_receipt_legitimacy
• public_receipt_distrust
• fan_oxygen_resentment
• pirate_exposure
• witness_retaliation_risk
• handler_burden
• future_blackmail_cost
• future_recovery_cost
• black_screen_pressure.

Missability and recovery

This storyline is missed when the implementation treats coalition pressure as ambient difficulty, records only one member row, allows an asset to be captured without combined terms, or lets the player dissolve a coalition without cost.

Recovery is allowed only through visible scar:

• public contradiction with exposure;
• lawful appeal with bureau debt;
• sponsor unwind with capture scar;
• edit-source reveal with source ambiguity;
• witness or route-asset rescue;
• fan oxygen bond;
• recovery-only broadcast.

Replay evidence expectation

storyline_id: storyteller.storyline.adverse_coalition_lock.v1
session_id: lens-storyteller-adverse-coalition-lock-v1-<timestamp>
seed: <deterministic-seed>
source_inventory:
  target_asset_id: <asset/proof/person/copy/slot>
  target_asset_state_before: <state>
  member_rows:
    - source_surface: <surface>
      source_session_id: <source session or explicit absence>
      faction: <faction>
      prior_spend_or_loss: <state>
      demanded_control: <control>
    - source_surface: <surface>
      source_session_id: <source session or explicit absence>
      faction: <faction>
      prior_spend_or_loss: <state>
      demanded_control: <control>
entry_state:
  coalition_rows_min: 2
  rows_share_target: true
  combined_lock_terms_present: true
  future_route_effect_possible: true
  no_fixed_turn_trigger: true
offered_choices:
  - storyteller.card.adverse_coalition_docket.v1
  - storyteller.rite.adverse_coalition_break_hearing.v1
  - break_by_contradiction
  - split_coalition
  - buy_standdown
  - freeze_target
  - decoy_release
  - default_harden
branch_result:
  selected_branch: <branch>
  coalition_state_after: <state>
  target_asset_state_after: <state>
  emitted_event: storyteller.event.coalition_lock_hardening.v1 | none
  future_route_effect: <effect>
  counter_deltas:
    relief:
      - <relief>
    cost:
      - <cost>
assertions:
  - source_rows_preserved
  - entry_state_driven
  - coalition_members_min_two
  - target_asset_shared
  - branch_outcomes_diverge
  - future_route_effect_mutates

Non-goals

• Not a fixed-turn revenge chapter.
• Not a generic faction alliance simulator.
• Not a replacement for faction commitment, three-key custody, mandate exhaustion, broadcast legality, or route custody.
• Not raw lens count satisfaction.
• Not a governance page.
• Not valid unless coalition lock changes target state, future route use, and at least one pressure surface.