Cutroom Priority Queue / 剪辑室优先队列机制

Cutroom Priority Queue is the mechanism that turns edit-room scarcity into route state.

It sits below the broad 制作分诊台机制 and above terminal 结局伤痕账本机制. Production triage says which crisis gets a lane. The cutroom queue says which scarred version actually reaches the cut, which version is delayed or defaulted, and which claimant becomes privileged or harmed by the edit.

The mechanism exists because late Storyteller play can otherwise launder consequences through a single invisible editor action: public scar, sponsor patch, lawful quarantine, split copy, proxy testimony, and recovery repair all ask for the same cutroom authority, but without a queue the implementation can let them all succeed.

Core rule

When two or more contested versions require the same cutroom bottleneck, the player must choose priority, split the copy with cost, mark recovery-only, suppress or trade a row, or allow a default actor to cut by absence.

The mechanism is invalid if the edit lane behaves as infinite.

Tracked objects

The mechanism is represented by:

State model

cutroom_queue:
  queue_id: <stable id>
  source_session_id: <session id if inherited>
  bottleneck: edit_lane | editor | checksum_authority | source_copy | legal_cut_window | sponsor_review | public_cover | recovery_repair
  rows:
    - row_id: <stable id>
      source_storyline: production_triage_desk | editor_han_cutroom | ending_scar_ledger | stabilization_liability_handoff | proxy_posture_chain | route_assets_and_custody | equivalent
      cut_object_type: public_scar | private_clean_patch | split_copy | recovery_repair | black_box_insert | proxy_testimony | sponsor_replacement | refusal_marker
      claimant_prioritized: <claimant asking for priority>
      claimant_harmed: <claimant harmed if prioritized>
      required_handler: <handler or explicit_absence>
      proof_carrier: <carrier or explicit_absence>
      queue_state: pending | contested | overbooked | held | split_required | recovery_only | default_ready | prioritized | delayed | split | suppressed | public_cut | private_cut | defaulted | contradiction_pending
      default_if_ignored: <default state>
      future_route_effect: <route effect>
  selected_row_id: <row or none>
  rival_row_ids: []
  last_resolution: priority | split | recovery_only | suppress_trade | default | unresolved

Entry conditions

Open or update the mechanism when:

  1. there are at least two live cutroom rows;
  2. a shared bottleneck prevents all rows from resolving cleanly;
  3. at least one row inherits a scar, proxy posture, stabilization ticket, route asset custody state, public receipt, lawful seal, edit checksum, sponsor contract, or black-box contradiction;
  4. at least one row has a concrete default if ignored;
  5. the choice can mutate future route access, proof custody, ending eligibility, proxy posture, public legitimacy, stabilization liability, or broadcast reality.

The mechanism has no fixed numbered trigger and no calendar-only trigger.

Resolution algorithm

1. Build rows from live scars and proofs

Eligible source surfaces include:

  • 结局伤痕账本 rows that need final presentation;
  • 代理人姿态案卷 rows carrying testimony, signature, relay, or human proof;
  • stabilization tickets that need a public, private, lawful, split, or recovery cut;
  • route assets whose copy, room, body, voice, or receipt cannot be edited twice;
  • Han/Baiya/editor custody rows from Han Cutroom Storyline and related editor pressure;
  • production triage tickets that name edit, legal edit, public cut, archive checksum, sponsor review, black-box insert, or recovery repair.

2. Detect a bottleneck

A bottleneck exists when two or more rows require the same scarce authority:

  • edit_lane — only one cut can be actively worked;
  • editor — Han, Baiya, or equivalent handler cannot safely carry every cut;
  • checksum_authority — one edit checksum decides admissibility;
  • source_copy — one fragile source copy cannot become every version;
  • legal_cut_window — lawful approval cannot cover public and private contradiction together;
  • sponsor_review — sponsor delay or approval can be spent once;
  • public_cover — one public explanation cannot protect contradictory cuts;
  • recovery_repair — the route can be kept repairable, not cleaned.

3. Require a visible choice

剪辑室优先听证 must select one row and mutate at least one rival row.

Valid 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.

4. Write consequences to durable surfaces

A resolution must update at least one external surface:

  • ending scar state;
  • proxy posture;
  • stabilization liability;
  • route asset custody;
  • production triage board;
  • broadcast reality / black-screen pressure;
  • sponsor, inspector, archive, editor, public, artist, witness, pirate, or route claimant posture.

5. Preserve the skipped scar

Any unselected row must become delayed, split, recovery-only, default-ready, public-only, lawful-only, captured, hostile, contradiction-pending, or explicitly resolved with a named cost.

Unselected rows cannot vanish.

Counter and state deltas

Common deltas:

  • edit_debt +1
  • cutroom_trust +1/-1
  • public_receipt_legitimacy +1/-1
  • public_receipt_distrust +1
  • sponsor_stop_loss_pressure +1/-1
  • inspection_heat +1/-1
  • archive_debt +1
  • source_ambiguity +1
  • reality_drift +1
  • witness_exposure +1
  • fan_oxygen_resentment +1/-1
  • proxy_hostility +1
  • route_asset_pressure +1
  • black_screen_slots +1
  • recovery_cost +1

Every positive relief must be paired with at least one visible cost or scar.

Branch families

Public scar priority

Privileged claimant: fan public, artist, witness, historian, pirate, public audience, or split public proof.

Harmed claimant: sponsor, archive, inspector, editor, or private owner.

Result: public route opens with retaliation, audit, or exposure.

Private or lawful priority

Privileged claimant: sponsor, inspector, archive, editor, or lawful holder.

Harmed claimant: fan public, artist, witness, pirate, route claimant, or public audience.

Result: private capture, lawful-only use, or public route cost increase.

Split copy

Privileged claimant: split.

Harmed claimant: exclusive owner.

Result: split canon or contradiction pending; no single clean owner.

Recovery-only mark

Privileged claimant: none or recovery claimant.

Harmed claimant: clean ending claimant.

Result: clean closure blocked; route remains repairable.

Suppress or trade

Privileged claimant: buyer or suppressor.

Harmed claimant: named omitted claimant.

Result: immediate relief with hostile proxy, captured route asset, public distrust, or ending cost.

Default

Privileged claimant: whoever cuts by absence.

Harmed claimant: the row that lacked lane, handler, proof, or protection.

Result: 剪辑室优先违约.

Integration boundaries

  • With 制作分诊台机制, this mechanism is the edit-specific bottleneck after the broad desk has identified simultaneous crises.
  • With 代理人姿态链机制, testimony, signatures, and public voices become cutroom rows instead of free proof.
  • With 结局伤痕账本机制, the selected or skipped cut determines which terminal family is blocked, costlier, split, captured, or recovery-only.
  • With Route Assets and Custody, source copies, bodies, rooms, proof, and proxies can be captured or preserved by edit priority.

Failure cases

The mechanism fails if:

  • fewer than two rows exist and no opportunity cost is visible;
  • every row resolves through one editor assignment;
  • selected and unselected rows produce equivalent outcomes;
  • missing handler, lane, proof, or support has no default event;
  • public scar, private clean, split, and recovery-only all collapse into one generic cut;
  • a skipped scar does not remain inspectable;
  • ending eligibility changes without recording claimant privilege, harmed claimant, proof carrier, and future route effect;
  • any trigger uses a fixed numbered turn.

Minimal replay evidence

mechanic: storyteller.mechanics.cutroom_priority_queue.v1
queue_id: <stable id>
source_session_id: <session id if inherited>
bottleneck: <bottleneck>
row_count_min: 2
selected_row_id: <row>
rival_row_ids: []
choice_family: public_scar_priority | private_lawful_priority | split_copy | recovery_only | suppress_trade | default
selected_state_after: <state>
rival_state_after: <state>
claimant_prioritized: <claimant>
claimant_harmed: <claimant>
proof_carrier_after: <carrier>
future_route_effect: <effect>
external_surface_mutated: ending_scar_ledger | proxy_posture_docket | stabilization_liability_ticket | route_asset | production_triage_board | broadcast_reality
no_fixed_turn_trigger: true

Non-goals

  • Not a bulk rite generator.
  • Not a generic editing skill tree.
  • Not a turn-count deadline.
  • Not a replacement for Production Triage Desk.
  • Not a replacement for Han Cutroom’s character storyline.
  • Not a clean bridge that lets public, private, lawful, split, and recovery cuts all succeed together.