Audience Stability Floor / 观众稳定性下限

Audience Stability Floor is the corporate entertainment-stability pressure that turns custody, archive, voice, sponsor, fan oxygen, and blackout fallout into playable broadcast management.

It is not a global mood bar and not a replacement for Broadcast Schedule. The floor only enters play when a real broadcast promise risks becoming commercially unstable: audience attention is falling, a sponsor demands clean reassurance, public receipts contradict the show, or a blackout scar threatens the next slot.

Playable question

When the public can no longer accept the broadcast as safe entertainment, does the production stabilize attention by telling the truth, buying a clean patch, letting counter-programming carry the audience, compressing the schedule, or hiding the breach until churn becomes irreversible?

Every answer must move costs between at least two claimant surfaces.

State-triggered entry

Offer this mechanic when all of the following are true:

  1. a broadcast-facing object is live or scarred: Last Performance, a sponsor relief surface, a fan oxygen ledger, a public receipt, a pirate relay, a memorial air copy, or a Blackout Incident;
  2. the audience floor is uncertain: audience_stability, audience_churn, broadcast_floor_breach, public_grief_stability, fan_oxygen_resentment, sponsor_stop_loss_pressure, inspection_heat, or black_screen_slots is unresolved;
  3. at least two factions can contest the stabilizing move: sponsor desk, fan public, inspector, archive bureau, editor, artist, pirate relay, or schedule board;
  4. a playable proof or liability object exists: source receipt, fan ledger, voice receipt, cutroom proof, inspector token, schedule slot, blackout scar, or sponsor relief object.

The floor is driven by state and claimant pressure. It never opens from a fixed numbered trigger.

Core states

StateMeaningRequired play effect
floor_metAudience attention is stable enough for the current promise.No forced stability rite is required, but costs can still accumulate.
volatile_but_legibleThe audience is unsettled but still understands what happened.Public receipt, fan, or editor branches can stabilize without sponsor capture.
ratings_floor_breachThe entertainment-stability promise has fallen below contract floor.A stabilizing rite or blackout/fold risk must be offered.
sponsor_clean_patchSponsor funds a clean reassurance cut.Immediate volatility drops while capture, fraud, or public distrust rises.
public_receipt_floorThe breach is stabilized by visible proof and public naming.Legitimacy improves while sponsor/inspection/schedule pressure rises.
pirate_attention_bridgeUnofficial relay or fan channel carries audience attention.Churn is slowed while relay custody, inspection, or sponsor conflict rises.
schedule_compressed_floorThe production protects attention by moving, merging, or delaying a slot.Audience drop is contained while schedule capacity or blackout debt worsens.
audience_churn_spiralThe breach is hidden or mishandled until audience loss hardens.Future offers become more expensive, sponsor ownership rises, or a blackout scar persists.

Branch families

Branch A — Public receipt stabilization

The player names the contradiction, publishes a lawful receipt, or lets a witness explain the breach on screen.

Expected outcomes:

  • set public_receipt_floor or keep volatile_but_legible;
  • improve audience_stability, public_receipt_legitimacy, or fan_oxygen_balance;
  • increase sponsor_stop_loss_pressure, inspection_heat, schedule_pressure, or archive_debt.

Branch B — Sponsor clean patch

The player accepts a sponsor-funded reassurance cut, relief pledge, or branded grief package.

Expected outcomes:

  • set sponsor_clean_patch;
  • reduce broadcast_floor_breach or audience_churn immediately;
  • increase contract_capture, archive_fraud, voice_integrity_risk, public_receipt_distrust, or sponsor_escrow_debt.

Branch C — Pirate or fan attention bridge

The player routes unstable audience attention through fan oxygen queue witnesses, pirate relay, or unofficial public commentary.

Expected outcomes:

  • set pirate_attention_bridge or fan_attention_bridge;
  • reduce audience_churn or keep a schedule slot from folding;
  • increase inspection_heat, relay_custody_risk, fan_oxygen_resentment, or sponsor_stop_loss_pressure.

Branch D — Schedule compression

The player moves, merges, delays, or collapses a broadcast slot to keep the audience floor from becoming an immediate failure.

Expected outcomes:

  • set schedule_compressed_floor;
  • reduce immediate broadcast_floor_breach;
  • increase schedule_slots_occupied, contract_timer_risk, black_screen_slots, or blackout debt.

Branch E — Hide or ignore the breach

The player suppresses proof, hides the public explanation, or lets a clean ending stand without solving audience trust.

Expected outcomes:

  • set audience_churn_spiral, floor_breach_hidden, or clean_patch_backlash;
  • worsen audience_churn, public_grief_stability, fan_oxygen_resentment, or inspection_heat;
  • future public receipt, pirate relay, sponsor negotiation, or schedule recovery costs increase.

Required inputs

A stability action must include:

  • one broadcast or schedule object;
  • one proof, liability, or attention object;
  • one claimant or handler;
  • one explicit branch intention: publish, patch, bridge, compress, expose, or suppress.

Valid existing integration surfaces include Sponsor Oxygen Triage, Route Assets and Custody, Orion Breath, Inspector Rhee Archive, Han Cutroom, and 海盗频段童声.

Counter contract

Every resolution must mutate at least two of:

  • audience_stability
  • audience_churn
  • broadcast_floor_breach
  • public_grief_stability
  • public_receipt_legitimacy
  • public_receipt_distrust
  • fan_oxygen_balance
  • fan_oxygen_resentment
  • sponsor_stop_loss_pressure
  • sponsor_escrow_debt
  • contract_capture
  • inspection_heat
  • archive_debt
  • archive_fraud
  • relay_custody_risk
  • schedule_slots_occupied
  • black_screen_slots

Non-goals

  • Not a global morale bar.
  • Not a fixed numbered trigger.
  • Not a clean sponsor win.
  • Not a replacement for schedule-slot pressure.
  • Not an ending-only mood consequence.
  • Not satisfied unless branch state changes later offers, costs, tags, counters, or route availability.