Broadcast Stability Escrow / 稳播托管线

Broadcast Stability Escrow is the pressure storyline for a public version that is watchable enough to keep airing but not stable enough to become clean corporate reality.

The existing character route for 稳播精算师 asks what happens to the actuary. This system storyline asks the broader operational question: which reader owns the price of keeping a contested version on air, and what future route must pay when that price was wrong?

Playable question

When audience attention, reality drift, sponsor pressure, inspection heat, editor smoothing, or blackout risk all point at the same public version, does the producer:

  • certify a public table and expose the price;
  • sign a sponsor rate card and accept capture;
  • attach an inspector hold and delay clean use;
  • smooth through edit continuity while leaving truth unsettled;
  • recruit or protect 梁雾 as a future clearance witness;
  • suppress the table and invite repricing;
  • abandon the quote until blackout risk or a rival claimant owns it?

Every answer must keep stability separate from truth. A version can be stable but false, truthful but unairable, sponsor-clean but publicly distrusted, or editor-legible but legally expensive.

State-triggered entry

Open this storyline only from live pressure:

entry_state_required:
  trigger_kind: state_pressure
  public_version_or_patch_exists: true
  audience_or_drift_pressure_live: true
  claimant_surface_count_min: 2
  clearance_decision_can_change_future_route: true
  stability_quote_or_explicit_absence_visible: true
  liang_wu_state_or_explicit_absence_visible: true
  future_reader_consumes_clearance_state: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_audience_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Valid entry sources include volatile audience floor, reality drift, sponsor stop-loss order, inspector hold, editor smoothing quote, fan oxygen receipt, public table leak, schedule compression, K-404 custody mismatch, or blackout scar.

Bound content pack

  • 稳播托管机制 defines clearance states, branch families, counter surfaces, handler limits, and failure states.
  • 稳播清算案卷 records the public version, explanation, contradicting object, claimant surfaces, 梁雾 state, quote, route-asset state, and default risk.
  • 稳播清算听证 resolves public table, sponsor rate card, inspector hold, editor smoothing, recruited witness, suppression, or abandonment.
  • 清算台重估 fires when the table is hidden, captured, contradicted, under-proved, or repriced by a rival reader.
  • Broadcast Stability Escrow Lens observes state-triggered entry, branch divergence, 梁雾 mutation, and future repricing.

Storyline spine

Beat 1 - The public version is not clean

A final edit, memorial cut, sponsor explanation, counter-broadcast custody fork, public receipt floor, fan oxygen explanation, editor patch, inspection hold, route-asset recovery claim, or blackout-scarred schedule version is already visible.

At least two claimant surfaces can price that version: sponsor, inspector, editor, public table, archive, fan oxygen, pirate relay, schedule board, artist boundary, or explicit absence.

Beat 2 - The docket quotes the risk

Create or update Stability Clearance Docket. It must not be a memo or scorecard. It must name the version, the reason the audience can keep watching, the object that can contradict the version, 梁雾’s current state, and the default risk.

stability_clearance_row:
  public_version: <aired_or_patch_or_counter_broadcast_version>
  stability_explanation: public_receipt | sponsor_patch | inspector_hold | editor_smoothing | fan_bridge | schedule_compression | explicit_absence
  contradicting_or_risk_object: <receipt_checksum_stop_loss_order_audit_stamp_fan_ledger_blackout_scar_or_absence>
  claimant_surfaces:
    - sponsor | inspector | editor | public_receipt | archive | fan_oxygen | pirate_relay | schedule_board | artist | explicit_absence
  liang_wu_state_before: offered_stability_actuary | protected_rate_witness | sponsor_captured_signature | inspector_locked_witness | suppressed_actuary | explicit_absence
  clearance_quote_before: unpriced | affordable | punitive | captured | denied | public_table | inspector_hold
  route_asset_state_before: <state_or_explicit_absence>
  default_risk: churn_spiral | sponsor_capture | inspection_hold | blackout_reprice | false_stability_owner
  future_reader_or_route: <future consumer>

Beat 3 - The player chooses who prices reality

Run Stability Clearance Hearing. The assignment must name the docket, public version, explanation, actuarial witness or explicit absence, proof/liability object, handler, selected posture, and price.

Beat 4 - Stability mutates a future route

The branch must produce both relief and cost. Public table can improve legitimacy while raising sponsor pressure. Sponsor rate card can lower churn while increasing contract capture. Inspector hold can block false owners while making later release lawful-only. Editor smoothing can make attention legible while increasing edit debt. Recruiting 梁雾 can lower future hidden-breach risk while making audit more visible.

Beat 5 - Repricing becomes durable

If the table is suppressed, underfilled, captured, or contradicted, Clearance Desk Repricing records the failed posture, repricing claimant, 梁雾 state before/after, quote after, and future route effect.

Branch map

BranchImmediate reliefCost/scarFuture state
Public tableaudience stability, public legitimacy, or drift clarity improvessponsor pressure, inspection heat, or 梁雾 exposure risespublic_table_required, future_clearance_legible
Sponsor rate cardchurn, stop-loss, or slot pressure dropscontract capture, escrow debt, public distrustsponsor_only, public_objection_costlier
Inspector holdfalse stability owner and archive fraud are blockedinspection heat, schedule occupation, premiumlawful_only, release_requires_clearance_hearing
Editor smoothingattention and continuity improveedit debt, public distrust, drift riskchecksum_or_public_table_required
Recruit witnessfuture clearance becomes legiblepremium, handler burden, exposureroute_asset.liang_wu_clearance_witness
Suppress tableimmediate slot pressure may dropfuture clearance cost, churn, blackout riskcostlier, hostile, blackout_recovery_required
Abandon quoteno price is paid nowclaimant files first, quote captured or deniedsponsor_only, lawful_only, recovery_only

No branch may make the same version clean for public, sponsor, inspector, editor, route asset, fan oxygen, archive, and schedule readers at once.

Missability and recovery

The storyline is missed when implementation treats stability as a global meter, lets sponsor wording clear public reality without distrust or debt, lets editor smoothing remove drift without edit cost, or lets a suppressed table disappear without future repricing.

Recovery requires visible cost: public table recovery, inspector hold, sponsor unwind, editor checksum addendum, recruited clearance witness, blackout recovery, or a later clearance quote recall.

Replay evidence expectation

storyline_id: storyteller.storyline.broadcast_stability_escrow.v1
session_id: lens-broadcast-stability-escrow-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  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
offered:
  card: storyteller.card.stability_clearance_docket.v1
  rite: storyteller.rite.stability_clearance_hearing.v1
branch_result:
  selected_posture: public_table | sponsor_rate_card | inspector_hold | editor_smoothing | recruit_witness | suppress_table | abandon
  escrow_state_after: public_table_certified | sponsor_rate_card_signed | inspector_hold_attached | editor_smoothing_quote | route_asset_clearance_witness | clearance_suppressed | clearance_denied | blackout_risk_repriced
  liang_wu_state_after: <state>
  future_route_effect: <effect>
  event_seen_or_armed: storyteller.event.clearance_desk_repricing.v1 | none
  counter_deltas:
    relief: []
    cost: []
    future: []

Non-goals

  • Not a generic ratings scene.
  • Not a fixed press-cycle beat.
  • Not a sponsor-clean approval button.
  • Not an editor retcon.
  • Not satisfied by stability without truth, reader scope, 梁雾 state, and future repricing.