Scar Convergence Desk / 伤痕汇流台线

Scar Convergence Desk is a mid/late campaign pressure storyline for the moment when several previous scarred successes all point at the same stabilizer.

The stabilizer may be a handler, proof object, public wording, lawful seal, sponsor release, edit checksum, artist boundary, facility room, route asset, or broadcast slot. Earlier systems may each have made a correct local decision: settle the aftershock, resurface a dormant claim, split a future reader, pawn a route asset, survive insolvency, or carry proof forward. The local decisions are still true. The problem is that the current route now wants one of their shared objects to be clean.

This storyline asks:

When the campaign history proves that a stabilizer is no longer clean, how does the producer keep the broadcast moving without laundering every scar into nothing?

Why this is the next useful expansion

The current green corpus is already strong at local consequence:

• 和解反震账本 preserves relief and debt after a settlement.
• 休眠认领复燃线 brings old rows back when they become relevant.
• 反向同盟锁线 lets factions coordinate over a target.
• 裁定读者冲突线 prevents one row from satisfying incompatible future readers.
• 播出破产账本线 makes unpaid relief collide with creditors and collateral.
• 导出证据回流分岔线 proves that prior evidence can return as current pressure.

The next product gap is convergence, not another local ledger. After enough scarred successes, the game needs a way to say: this same handler, proof, public word, seal, release, checksum, room, slot, or route asset is now claimed by several preserved histories, and it cannot be used as a universal clean key.

This content pack makes that state playable.

State-triggered entry

Open this storyline when all conditions below are true:

1. a current route, rite, public statement, legal conversion, ending posture, producer-license review, or route-asset use requests a stabilizer;
2. that stabilizer is touched by preserved source rows from prior consequences;
3. the source rows carry scars that materially conflict with clean use;
4. at least one harmed or deferred claimant would be hidden if the stabilizer were used cleanly;
5. a future reader will consume the result;
6. the player can choose among costed responses;
7. no entry condition depends on fixed turn count, day interval, chapter quota, raw content count, raw scar count, dashboard state, or lens health.

Scar Convergence Desk can require multiple source rows, but the number is never the trigger by itself. The trigger is the clean-use conflict.

Content pack

Mechanism

• 伤痕汇流台机制 defines stabilizers, convergence entry, branch contract, collapse, counters, and replay evidence.

Card

• 伤痕汇流案卷 records the current surface, shared stabilizer, source scar rows, harmed claimants, conflict kind, default narrator, future reader, and available responses.

Rite

• 伤痕汇流听证 is the assignable hearing where the player consolidates, appoints trustee, splits readers, pawns clean route, retires, quarantines, or suppresses the convergence.

Event

• 伤痕汇流塌陷 fires or arms when source rows are hidden, harmed claimants are omitted, a stabilizer is falsely marked clean, the hearing is underfilled, or a default narrator moves first.

Storyline spine

Beat 1 — The current route asks for clean use

The producer tries to use a stabilizer as if it still has clean authority.

Examples:

• a producer-license review asks for a lawful seal that was previously narrowed by public-reader conflict;
• a clean route wants the same public wording that a sponsor release and fan refund both scarred;
• an ending posture wants an artist boundary that earlier content made public-only;
• a correction slot wants an edit checksum that evidence carryover marked contradiction-pending;
• a facility room is needed for a claimant, but adverse coalition and dormant claim rows both attach harmed parties to the same room;
• a broadcast slot is needed to air, but insolvency and ending scar rows both own future claims on it.

Beat 2 — Source scars converge

The game creates or updates 伤痕汇流案卷.

The docket names the source rows and explains why clean use would hide them. It does not list every old row. It selects only rows materially tied to the current stabilizer.

Beat 3 — The player seats the convergence

The player runs 伤痕汇流听证.

The hearing demands concrete assignments:

• handler or explicit absence;
• proof bridge or explicit absence;
• authority or explicit absence;
• sacrifice/collateral or explicit absence;
• protected boundary or explicit absence;
• future reader.

Beat 4 — The stabilizer changes state

The stabilizer must not return to clean. It becomes one of:

• accepted with scar;
• trustee-carried;
• split by future reader;
• clean route pawned;
• retired with scar;
• quarantined;
• contradiction-pending;
• captured;
• hostile;
• false-clean hardened;
• recovery-only.

Beat 5 — Future route consumes the scar

At least one future surface must read the result:

• Producer License and Pressure tightens, stays, or surcharges review;
• Route Assets and Custody changes availability, custody, protection, capture, or recovery-only state;
• Broadcast Reality records drift or split acceptance;
• 结局伤痕账本线 blocks clean laundering;
• 处理人负荷账本 consumes trustee or handler cost;
• 经营压缩台 reads false-clean hardening as captured metric pressure;
• 制作分诊台 prices the slot, facility, or attention cost.

Branch map

Branch	Immediate relief	Cost/scar	Future effect
Consolidate with sacrifice	one carried interpretation becomes usable	sacrificed asset/favor/slot/trust; losing rows remain scarred	accepted with scar; clean route blocked elsewhere
Appoint scar trustee	contradiction becomes manageable through carrier	trustee burden, exposure, capture risk, public/legal/sponsor cost	trustee required; route recovery-only if trustee is lost
Split future readers	selected readers accept scoped uses	source ambiguity, archive debt, public distrust, correction pressure	lawful-only/public-only/sponsor-only/artist-boundary-only split
Pawn clean route	immediate route opens	clean future, clean ending, clean license, or clean public word is pawned	costlier or recovery-only until bought back
Retire stabilizer	false clean use is blocked	current route blocked/costlier; public grief or sponsor/inspection pressure rises	substitute required; clean laundering blocked
Quarantine convergence	fraud, false owner, or drift pressure falls	delay, facility pressure, audience churn, inspection heat	follow-up hearing or recovery-only path
Suppress and collapse	no true relief	collapse event; narrator captures or hardens the stabilizer	route blocked/costlier/captured/recovery-only; drift or license pressure rises

Counter contract

Every branch must mutate at least three counters or durable states. Non-collapse branches require at least one relief and at least one cost.

Core surfaces:

• scar_convergence_pressure
• shared_stabilizer_integrity
• future_reader_acceptance
• producer_license_pressure
• route_asset_pressure
• public_receipt_legitimacy
• public_receipt_distrust
• inspection_heat
• bureau_favor_debt
• sponsor_stop_loss_pressure
• contract_capture
• artist_refusal_respected
• artist_refusal_violation
• voice_integrity_risk
• edit_debt
• archive_debt
• source_ambiguity
• handler_burden
• facility_access_pressure
• broadcast_slot_scar
• future_recovery_cost
• black_screen_pressure
• reality_drift

Missability and recovery

The storyline is missed when implementation:

• treats a scarred stabilizer as clean;
• counts scars without naming the current clean-use conflict;
• erases a harmed claimant to unlock a route;
• makes all future readers accept one corrected state;
• hides source rows behind summary prose;
• offers only a passive penalty instead of a costed branch;
• triggers from fixed turn count or generic late-game escalation.

Recovery is allowed only with visible cost:

• public correction or addendum;
• lawful appeal or producer-license stay;
• sponsor release scar;
• edit-source reveal;
• handler replacement or trustee rescue;
• facility quarantine;
• route asset sacrifice;
• broadcast-slot loss;
• recovery-only path.

Replay evidence expectation

storyline: storyteller.storyline.scar_convergence_desk.v1
session_id: lens-scar-convergence-desk-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  current_surface: <surface id>
  requested_clean_use: <use>
  shared_stabilizer: <stabilizer id>
  impossible_clean_use: true
  no_fixed_turn_trigger: true
source_inventory:
  source_rows:
    - source_row_id: <row>
      source_surface: <surface>
      source_session_id: <session or in-world source id>
      scar_state: <state>
      claimant_harmed_or_deferred: <claimant>
      conflict_with_stabilizer: <reason>
    - source_row_id: <row>
      source_surface: <surface>
      source_session_id: <session or in-world source id>
      scar_state: <state>
      claimant_harmed_or_deferred: <claimant>
      conflict_with_stabilizer: <reason>
offered:
  card: storyteller.card.scar_convergence_docket.v1
  rite: storyteller.rite.scar_convergence_hearing.v1
branch_result:
  selected_response: consolidate_with_sacrifice | appoint_scar_trustee | split_future_readers | pawn_clean_route | retire_stabilizer | quarantine_convergence | suppress_and_collapse
  stabilizer_state_after: <state>
  future_reader_effect: <effect>
  emitted_event: storyteller.event.scar_convergence_collapse.v1 | none_if_valid
  counter_deltas:
    relief: []
    cost: []
    future: []
assertions:
  source_rows_preserved: true
  clean_use_conflict_visible: true
  no_raw_count_trigger_without_conflict: true
  branch_outcomes_diverge: true
  no_universal_clean_key: true
  future_reader_consumes_result: true

Non-goals

• Not a fixed-turn finale.
• Not a generic scar threshold.
• Not a dashboard/replay governance page.
• Not a backlog clean-up system.
• Not a replacement for aftershock, dormant claim, coalition, reader collision, insolvency, or evidence carryover.
• Not satisfied by adding more rows; it is satisfied only when a current stabilizer and future reader are changed by preserved scars.