Cutroom Priority Queue / 剪辑室优先队列线

Cutroom Priority Queue is a pressure-system storyline about the moment when the producer has enough proof to cut several versions, but not enough edit-room authority to cut them all.

It deepens the existing late-game chain without adding filler endings. 制作分诊台 already makes crises simultaneous. Han Cutroom Storyline already makes the editor a person. 结局伤痕账本线 already makes ending scars inherit. The missing lane is the cutroom bottleneck that decides which scarred version becomes the broadcast artifact and which version is delayed, captured, split, recovery-only, or defaulted.

Primary playable question

When public scar, sponsor patch, lawful quarantine, split copy, proxy testimony, refusal marker, black-box insert, and recovery repair all want the same cutroom authority, which version does the producer prioritize — and what durable scar does the skipped version keep?

Every branch must show:

• at least two live cutroom rows;
• the shared bottleneck;
• the selected row;
• the rival row that changes because of the selection;
• the claimant privileged by the cut;
• the claimant harmed by the cut;
• the proof carrier used or missing;
• the future route effect.

Why this expansion matters now

The current satisfied surface proves that many late-game costs can exist: stabilization tickets, recourse releases, proxy postures, clean-ending seizures, public scars, route assets, and black-box contradictions. The remaining design risk is an invisible final-cut pass where the implementation turns all of those costs into one clean version.

This storyline prevents that by forcing edit-room opportunity cost. It should make the player feel that an editor, checksum, source copy, lawful cut window, sponsor review, public cover, or recovery repair window is a finite resource.

Bound mechanism and content objects

This storyline binds:

• 剪辑室优先队列机制;
• 剪辑室优先案卷;
• 剪辑室优先听证;
• 剪辑室优先违约.

State-triggered entry

Open this storyline when all of the following are true:

1. at least two unresolved cut objects are live;
2. the cut objects share one bottleneck: edit lane, editor, checksum authority, source copy, legal cut window, sponsor review slot, public cover, or recovery repair window;
3. at least one object is inherited from a scar-bearing source such as ending scar, stabilization liability, proxy posture, production triage, clean-ending seizure, recourse release, route asset custody, or black-box contradiction;
4. at least one rival object has a real default if ignored;
5. a priority choice can still mutate future route access, proof custody, ending eligibility, proxy posture, public legitimacy, stabilization liability, or broadcast reality.

This storyline must never open from a fixed numbered turn.

Storyline spine

Beat 1 — Several versions arrive at the cutroom

The player receives or updates 剪辑室优先案卷. The docket lists two or more rows.

Common row pairs:

• public scar verdict cut versus sponsor clean patch;
• lawful inspector quarantine versus fan countercut;
• split copy preservation versus archive single-owner registration;
• proxy testimony insert versus sponsor replacement voice;
• artist refusal marker versus recovery-only repair;
• black-box contradiction insert versus schedule-safe patch.

Beat 2 — The bottleneck is named

The row pair must share a bottleneck. A named character alone is not enough; the page must show which scarce thing is being consumed.

Examples:

• Han can work one final take, not every contradictory cut;
• Baiya can preserve one black-box checksum before suspicion rises;
• Shen Luo can buy one sponsor delay, not public and private safety together;
• Han Yanshuang or Inspector Rhee can cover one lawful cut window;
• Yu Lan can mobilize one public receipt before witness exposure rises;
• a single source copy cannot become public scar, private clean version, and split canon without cost.

Beat 3 — The hearing chooses priority

The player opens 剪辑室优先听证. The rite selects one row and forces a rival row to change.

Valid player choices:

• prioritize public scar cut;
• prioritize private or lawful cut;
• split cutroom copy;
• mark recovery-only;
• suppress or trade a row;
• fail/default by absence.

Beat 4 — Relief creates edit debt

The selected row gains relief. The rival row becomes delayed, split, recovery-only, default-ready, public-only, lawful-only, captured, hostile, contradiction-pending, or explicitly resolved with a named cost.

The branch must mutate at least one external surface: ending scar ledger, proxy posture docket, stabilization liability ticket, route asset, production triage board, broadcast reality, or claimant posture.

Beat 5 — Absence cuts by itself

If the player lacks handler, lane, proof carrier, public cover, lawful cover, sponsor review, recovery mark, or split-copy support, 剪辑室优先违约 fires.

The default is not neutral. Sponsor, inspector, archive, editor, fan public, proxy, blackout system, contradiction, or route asset cuts by absence.

Branch families

Branch A — Public scar priority

The producer chooses the version that makes harm visible: public receipt, fan oath, artist refusal, witness testimony, pirate relay, historian fragment, proxy statement, or black-box contradiction.

Relief:

• public legitimacy rises;
• private capture is blocked or costlier;
• ending scar remains inspectable.

Cost:

• sponsor stop-loss pressure, inspection heat, witness exposure, edit debt, source ambiguity, or fan vulnerability rises.

Future route effect:

• public audit required;
• ending unlocked with scar;
• private clean route blocked or costlier.

Branch B — Private or lawful priority

The producer gives priority to sponsor, inspector, archive, editor, or lawful custody.

Relief:

• slot stability improves;
• black-screen risk or sponsor default pressure falls;
• lawful proof may become admissible.

Cost:

• public receipt, artist refusal, witness or pirate proof, fan oxygen, split copy, or route claimant is harmed.

Future route effect:

• private capture;
• lawful-only ending state;
• public route costlier or recovery-only.

Branch C — Split cutroom copy

The producer spends support to preserve two incompatible versions.

Relief:

• false owner is blocked;
• public and formal copies survive;
• exclusive terminal truth is delayed.

Cost:

• source ambiguity, archive debt, reality drift, handler fatigue, public distrust, or edit debt rises.

Future route effect:

• split canon;
• contradiction pending.

Branch D — Recovery-only mark

The producer records that a route can be repaired later but cannot become clean through this cut.

Relief:

• lost route stays callable;
• false-clean laundering is blocked.

Cost:

• recovery cost, hostile claimant, clean terminal blockage, or black-screen pressure remains.

Future route effect:

• recovery-only terminal;
• ending costlier.

Branch E — Suppress or trade row

The producer hides, trades, sells, quarantines, or delays a row in exchange for immediate relief.

Relief:

• one claimant is satisfied;
• immediate pressure drops.

Cost:

• the harmed claimant is named;
• proxy hostility, route asset capture, public distrust, contract capture, bureau favor debt, or source ambiguity rises.

Future route effect:

• route captured;
• proxy hostile;
• ending blocked or costlier.

Branch F — Cut by absence

The producer cannot credibly staff the cut.

Relief:

• none, unless a public leak incidentally blocks a false owner.

Cost:

• 剪辑室优先违约 hardens a default version.

Future route effect:

• private capture;
• public audit required;
• route asset captured;
• proxy hostile;
• recovery-only terminal;
• contradiction pending;
• black-screen pressure up.

Character hooks

This storyline should use characters as finite handlers, not as free solutions.

• Han Cutroom can make a final-cut row credible, but the rival row must gain edit debt, witness exposure, or default pressure.
• Baiya can preserve black-box ambiguity, but checksum suspicion or reality drift rises.
• Yu Lan can carry public proof, but public retaliation, witness exposure, or sponsor pressure rises.
• Shen Luo can buy sponsor delay, but contract capture or manager debt rises.
• Han Yanshuang and Inspector Rhee Archive can make a lawful cut admissible, but quarantine pressure or bureau debt rises.

Integration notes

• With 制作分诊台, this storyline is entered after the broad desk exposes an edit bottleneck.
• With 代理人姿态链, testimony and public voices become queue rows whose carriers can be harmed or protected.
• With 稳定化责任交接线, a stabilization ticket can require an edit carrier and later mature if the row is skipped.
• With 洁净结局扣押链, sponsor or editor clean cuts can capture the route unless a public, split, or recovery row survives.
• With 追偿放行线, released assets may require lawful-only, public-only, split, or scarred cuts.
• With Route Assets and Custody, a source copy, room, body, proof, or proxy can be captured, protected, split, sacrificed, or recovery-only because of edit priority.

Missability and recovery

The storyline is missable when the implementation treats the edit lane as invisible or infinite. Missed rows must not vanish. They should become default-ready, hostile, captured, public-only, lawful-only, recovery-only, contradiction-pending, or black-screen pressure.

Recovery is allowed only with a scar:

• public correction after private cut;
• lawful appeal after fan countercut;
• sponsor buyback after hostile leak;
• split copy import after single-owner archive;
• proxy rescue after exposed testimony;
• black-box reopening after checksum patch;
• route asset sacrifice after recovery window loss.

Replay/session evidence shape

storyline: storyteller.storyline.cutroom_priority_queue.v1
session_id: lens-cutroom-priority-queue-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  queue_id: <stable id>
  bottleneck: edit_lane | editor | checksum_authority | source_copy | legal_cut_window | sponsor_review | public_cover | recovery_repair
  rows:
    - row_id: <row_a>
      cut_object_type: <type>
      claimant_prioritized: <claimant>
      claimant_harmed: <claimant>
      proof_carrier: <carrier>
      default_if_ignored: <state>
    - row_id: <row_b>
      cut_object_type: <type>
      claimant_prioritized: <claimant>
      claimant_harmed: <claimant>
      proof_carrier: <carrier>
      default_if_ignored: <state>
branch_runs:
  public_or_private_priority:
    selected_row_id: <row>
    rival_row_id: <row>
    selected_state_after: <state>
    rival_state_after: <state>
  default:
    event: storyteller.event.cutroom_priority_default.v1
    row_id: <row>
assertions:
  - row_count_min_two
  - shared_bottleneck_visible
  - selected_row_changes_rival_row
  - claimant_privileged_and_harmed_named
  - proof_carrier_or_absence_named
  - future_route_effect_written
  - no_fixed_turn_trigger

Non-goals

• Not a new chapter phase.
• Not a turn-count progression.
• Not a raw ending-count expansion.
• Not a generic edit minigame.
• Not a replacement for Han Cutroom’s character storyline.
• Not a replacement for Production Triage Desk.
• Not a way to satisfy public, private, lawful, split, and recovery branches in one clean action.