Narration Priority Stack / 叙述优先栈机制

This mechanism resolves the moment when multiple claimants can make a contested version real by narrating first.

It sits after systems that create armed narrators: insolvency defaults, briefing leak/preemption, dormant claim breaches, counter-broadcast forks, correction/cutroom defaults, archive seals, route-asset claims, and blackout folds. Those systems decide who has a right or opportunity to speak. Narration Priority Stack decides what happens when several of those rights target the same version at the same time.

Mechanic promise

When two or more active narration claims target the same broadcast version, route asset, proof object, correction row, or public/lawful record, the implementation must show the conflict before any voice silently wins.

The player must be able to seat a voice, counter a voice, split the window, escrow the proof, black out the unsafe version, or suffer hostile capture.

The mechanism fails if a preferred default narrator, leaked notice, injunction, countercopy, pirate relay, source release, or refusal route becomes reality without visible priority state.

Inputs

Accept rows from:

• 播出破产账本机制 when a row has default_narrator, preferred_default_narrator, or equivalent;
• 认领告知顺序机制 when first notice creates leak, injunction, countercopy, refusal, source capture, or no-notice default;
• 休眠认领复燃机制 when a resurfaced row becomes hostile, captured, or breach-ready;
• correction, cutroom, archive, counter-broadcast, public contrition, witness, handler, sponsor, and route-asset systems that produce a voice capable of becoming first reality.

State model

Every active claim on 叙述优先栈 needs six durable parts:

1. Target version — what would become real.
2. Claimant voice — who can speak, seal, leak, countercopy, testify, refuse, archive, or black out first.
3. Narration right — why the voice is allowed to act.
4. Priority basis — why this voice may beat rivals.
5. Proof/channel — what makes the voice credible or what absence makes it dangerous.
6. Excluded claimants and future route effect — who loses and what becomes harder later.

Minimal schema:

narration_priority_claim:
  claim_id: <stable id>
  source_surface: <surface>
  target_version: <version id>
  claimant: <claimant>
  narration_right: default | leak | injunction | countercopy | source_release | refusal | testimony | archive_seal | blackout_fold | public_receipt | lawful_record
  priority_basis: first_notice | unpaid_creditor | proof_custody | channel_access | legal_seal | fan_receipt | route_asset_custody | explicit_absence
  proof_anchor_or_absence: <proof id or explicit_absence>
  channel_or_absence: <channel or explicit_absence>
  excluded_claimants: []
  claim_state: claim_pending | claim_seated | claim_countered | claim_split | claim_escrowed | claim_preempted | claim_hostile | claim_captured | claim_blackout_fold | claim_recovery_only
  future_route_effect: protected | costlier | blocked | captured | hostile | public_only | lawful_only | split_canon | contradiction_pending | recovery_only | blackout_pressure_up

Priority rules

A voice can win priority only if it has at least one priority basis:

• first notice before rival claimants;
• unpaid creditor right from an insolvency row;
• proof custody or edit checksum;
• channel access to broadcast slot, pirate frequency, lawful archive, or sponsor countercopy;
• legal seal or archive warrant;
• fan receipt or public witness queue;
• route asset custody;
• blackout authority when no safe voice exists;
• explicit absence that makes rival proof fail.

The same proof or channel cannot seat every claimant cleanly. If reused, claims must split, escrow, counter, or create route cost.

Resolution branches

Seat one narrator

One voice becomes first reality. Rival claims remain excluded, countered, default-ready, or recovery-only.

Required mutations: selected claimant relief, excluded claimant cost, and target version route effect.

Counterclaim

A rival proof, caller, checksum, public receipt, legal seal, sponsor escrow, handler, or route asset blocks a preemptive voice.

Required mutations: preemptive claim worsens or delays, countering surface pays cost, and future correction/appeal/audit cost changes.

Split narration window

Two voices are allowed under explicit terms. The version becomes split rather than clean.

Required mutations: split canon or contradiction state, future route audit/appeal, and claimant retaliation or ambiguity.

Escrow and delay

Proof, channel, or route asset custody is locked behind another surface. This prevents hostile capture but creates schedule, insolvency, public delay, or inspection cost.

Blackout fold

The implementation allows absence to speak when every available voice would create false clean reality. This must preserve proof while increasing black-screen, audience, and ending-scar pressure.

Hostile capture

When the player omits the row, hides excluded claimants, lacks proof/channel, breaks split terms, or lets a preemptive claim expire uncontested, 敌性叙述夺取 fires or becomes default-ready.

Counter and durable-state deltas

Each resolution changes at least three surfaces, chosen from:

• broadcast_reality_drift
• route_asset_pressure
• claimant_retaliation_pressure
• sponsor_preemption_pressure
• contract_capture
• inspection_heat
• archive_debt
• public_receipt_legitimacy
• public_panic
• edit_debt
• source_ambiguity
• fan_oxygen_liability
• handler_burden
• slot_pressure
• audience_stability
• black_screen_pressure
• ending_scar_pressure

At least one delta must be relief and at least one must be cost.

Integration notes

• A broadcast insolvency row with a named default narrator should become a narration claim if another claimant can also speak for the same target version.
• A claimant briefing leak should become a narration claim if the pending action has not resolved.
• A dormant claim breach should become a narration claim if the old row can seize current public or lawful meaning.
• A counter-broadcast fork should feed its rival carriers into this stack when both target the same version.
• A correction or cutroom branch can use this stack when the public version and lawful/source version cannot both be first.
• Ending scar systems can inherit captured, split, blackout, or recovery-only version states.

Non-goals

• Not initiative order.
• Not a turn phase.
• Not a general priority queue.
• Not a governance checklist.
• Not raw content volume.
• Not valid if it hides proof/channel or excluded claimant accounting.
• Not valid if hostile capture has no future route effect.