Broadcast Stability Escrow / 稳播托管机制

Broadcast Stability Escrow is the mechanism that holds a public version between three questions:

  1. Can the audience keep watching this explanation?
  2. Can the corporation insure, sponsor, inspect, or edit it without immediate collapse?
  3. Who owns the price when it later proves unstable?

It is the missing bridge between Audience Stability Floor Storyline, 播出实在漂移审计, and Route Assets and Custody. It makes corporate entertainment-stability pressure playable through 稳播精算师.

Design promise

A correct implementation must prove that stability is not the same as truth. A public version may be false but stable, truthful but unairable, sponsor-clean but publicly distrusted, or editor-legible but legally expensive.

The player can clear, publish, price, hold, smooth, recruit, suppress, or abandon the version. Every result creates a route asset, a rate debt, or a future repricing risk.

State model

broadcast_stability_escrow_state_any:
  - no_clearance_needed
  - clearance_requested
  - escrow_open
  - public_table_certified
  - sponsor_rate_card_signed
  - inspector_hold_attached
  - editor_smoothing_quote
  - route_asset_clearance_witness
  - clearance_suppressed
  - clearance_denied
  - blackout_risk_repriced

escrow_open means the version has not yet become clean corporate reality. It is still priced by claimants.

Entry predicate

The mechanism activates from state pressure, not a fixed numbered trigger:

entry_requires_all:
  - public_version_or_patch_exists: true
  - audience_or_drift_pressure_live: true
  - claimant_surface_count_min: 2
  - clearance_decision_can_change_future_route: true
  - no_fixed_turn_trigger: true

Valid entry sources include volatile Audience Stability Index, Reality Drift Docket, sponsor stop-loss order, inspector hold, editor smoothing quote, fan oxygen receipt, public table leak, schedule compression, K-404 custody mismatch, or blackout scar.

Required surfaces

  • 稳播精算师 — route-asset NPC whose state carries the clearance table.
  • 稳播清算案卷 — card that stores public version, claimants, quote, proof, and default risk.
  • 稳播清算听证 — assignable action that prices or clears the version.
  • 清算台重估 — event that fires when a table is suppressed, captured, underfilled, or contradicted.

Branch rules

Public table certified

The player makes the table legible through public proof, historian witness, fan oxygen receipt, inspector-visible audit, or source proof.

escrow_state_after: public_table_certified
liang_wu_state_after: protected_rate_witness | recruited_clearance_witness
relief_any: [audience_stability_up, public_receipt_legitimacy_up, reality_drift_down]
cost_any: [sponsor_stop_loss_pressure_up, inspection_heat_up, liang_wu_exposure_up]
future_route_effect: public_table_required | future_clearance_legible

The player lets sponsor or contract language absorb attention risk.

escrow_state_after: sponsor_rate_card_signed
liang_wu_state_after: sponsor_captured_signature | missed_clearance_route
relief_any: [audience_churn_down, sponsor_stop_loss_pressure_down, schedule_pressure_down]
cost_any: [contract_capture_up, stability_escrow_debt_up, public_receipt_distrust_up]
future_route_effect: sponsor_only | public_objection_costlier

Inspector hold attached

The player accepts lawful delay and audit heat to keep a false stable owner from hardening.

escrow_state_after: inspector_hold_attached
liang_wu_state_after: inspector_locked_witness | protected_rate_witness
relief_any: [archive_fraud_down, reality_drift_down, false_stability_owner_blocked]
cost_any: [inspection_heat_up, schedule_slots_occupied_up, clearance_premium_up]
future_route_effect: lawful_only | release_requires_clearance_hearing

Editor smoothing quote

The player lets edit continuity keep attention legible while leaving truth unsettled.

escrow_state_after: editor_smoothing_quote
liang_wu_state_after: editor_smoothing_collaborator | suppressed_actuary
relief_any: [audience_churn_down, continuity_hazard_down]
cost_any: [edit_debt_up, public_receipt_distrust_up, reality_drift_up]
future_route_effect: checksum_or_public_table_required

Route asset clearance witness

The player protects 梁雾 and pays the premium to recruit the clearance table as persistent route support.

escrow_state_after: route_asset_clearance_witness
liang_wu_state_after: recruited_clearance_witness
add_route_asset: route_asset.liang_wu_clearance_witness
relief_any: [future_clearance_legibility_up, public_receipt_legitimacy_up]
cost_any: [clearance_premium_up, handler_burden_up, inspection_heat_up]
future_route_effect: lower_future_hidden_breach_risk_but_more_visible_audit

Suppressed, denied, or repriced

The player hides the table, underfills the hearing, lets a claimant file first, or abandons the state until it becomes a black-screen risk.

escrow_state_after_any: [clearance_suppressed, clearance_denied, blackout_risk_repriced]
liang_wu_state_after_any: [suppressed_actuary, hostile_actuarial_witness, missed_clearance_route]
relief_any: [immediate_slot_pressure_down]
cost_any: [audience_churn_up, future_clearance_cost_up, black_screen_slots_up]
future_route_effect: costlier | hostile | blackout_recovery_required

Counter contract

Every resolution must mutate at least three counters or durable states:

  • audience_stability
  • audience_churn
  • reality_drift
  • continuity_hazard
  • clearance_premium
  • stability_escrow_debt
  • liang_wu_exposure
  • future_clearance_cost
  • sponsor_stop_loss_pressure
  • contract_capture
  • inspection_heat
  • public_receipt_legitimacy
  • public_receipt_distrust
  • edit_debt
  • schedule_slots_occupied
  • black_screen_slots

Integration rules

  • With 观众稳定性下限, this mechanism prices the explanation that keeps the audience from leaving.
  • With 播出实在漂移, this mechanism prices a contradictory public version before it is patched, filed, or hardened.
  • With 沈洛合同捕获分岔机制, sponsor or legal relief can lower immediate pressure but must expose contract_capture and stability_escrow_debt.
  • With Broadcast Schedule, denial and blackout repricing may occupy or scar slots.
  • With Route Assets and Custody, 梁雾 herself is a route asset that can be protected, recruited, captured, suppressed, or made hostile.

Failure states

The mechanism fails if implementation allows any of these:

  • stability clearance without a concrete docket;
  • sponsor clean patch reducing churn without capture, debt, or distrust;
  • editor smoothing removing drift without edit debt or public distrust;
  • public table improving legitimacy without exposure, inspection, or sponsor cost;
  • 梁雾 remaining unchanged after recruit, capture, suppression, or repricing;
  • suppressed table disappearing without future clearance cost;
  • fixed turn count being used as canonical trigger.

Non-goals

  • Not a global score.
  • Not governance.
  • Not a generic ratings system.
  • Not a free cleanup for audience stability.
  • Not a replacement for proof, custody, sponsor, inspector, or editor branches.
  • Not satisfied unless route state, character state, assigned objects, and counter deltas are visible.