Ratings Floor Breach

Ratings Floor Breach fires when the audience-stability promise stored by Audience Stability Index drops below the contract floor. The breach is not a generic loss of popularity. It is a public-facing management crisis: the next broadcast may still air, but the reason the audience keeps watching must be made playable.

The event belongs to 观众稳定性下限. It connects sponsor relief, public receipt, pirate relay, and schedule compression into one stateful fork.

Entry conditions

Offer this event when all of the following are true:

1. Audience Stability Index is ratings_floor_breach, volatile_but_legible, sponsor_clean_patch, pirate_attention_bridge, schedule_compressed_floor, or audience_churn_spiral;
2. at least one broadcast or route object is exposed to the public: Last Performance, a sponsor relief surface, a custody contradiction, a fan oxygen queue, a pirate relay, or a Blackout Incident;
3. at least two claimant factions can contest the explanation: sponsor desk, fan public, inspector, archive bureau, editor, artist, pirate relay, or schedule board;
4. at least one pressure counter is live: audience_churn, broadcast_floor_breach, public_grief_stability, fan_oxygen_resentment, sponsor_stop_loss_pressure, inspection_heat, contract_capture, or black_screen_slots.

The event is state-triggered by a breach or unstable floor. It never opens from a fixed numbered trigger.

Offered choices

Choice A — Name the breach on air

The player uses public receipt, witness proof, or a visible contradiction to explain why the broadcast is unstable instead of selling a clean lie.

Expected outcome:

• set public_receipt_floor or volatile_but_legible;
• audience_stability +1, public_receipt_legitimacy +1, or fan_oxygen_balance +1;
• sponsor_stop_loss_pressure +1, inspection_heat +1, archive_debt +1, or schedule_pressure +1.

Choice B — Buy a sponsor clean patch

The player accepts sponsor-funded relief, a branded grief segment, or an edited reassurance package.

Expected outcome:

• set sponsor_clean_patch;
• audience_churn -1 or broadcast_floor_breach -1;
• contract_capture +1, public_receipt_distrust +1, archive_fraud +1, or sponsor_escrow_debt +1.

Choice C — Bridge attention through unofficial relay

The player lets fan channels, pirate relay, or unofficial commentary hold the audience while the official broadcast remains unstable.

Expected outcome:

• set pirate_attention_bridge or fan_attention_bridge;
• audience_churn -1 or public_grief_stability +1;
• inspection_heat +1, relay_custody_risk +1, fan_oxygen_resentment +1, or sponsor_stop_loss_pressure +1.

Choice D — Compress the schedule

The player moves, merges, shortens, delays, or folds a slot to prevent immediate abandonment.

Expected outcome:

• set schedule_compressed_floor;
• broadcast_floor_breach -1 or audience_churn -1;
• schedule_slots_occupied +1, contract_timer_risk +1, black_screen_slots +1, or blackout debt rises.

Choice E — Hide the breach

The player suppresses receipts, buries fan accounting, or lets the clean ending stand without repairing audience trust.

Expected outcome:

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

Follow-up hooks

• Can pull 冠名氧气分诊 if sponsor relief is used to stabilize the floor.
• Can cite Voice Contradiction when public explanation depends on body/voice proof.
• Can use Pirate Frequency Relay Token when unofficial attention becomes the bridge.
• Can scar Broadcast Schedule or feed Blackout Incidents if compression or hiding fails.

Non-goals

• Not a popularity cutscene.
• Not a fixed numbered trigger.
• Not a clean way to delete sponsor, fan, inspector, archive, or schedule pressure.
• Not a terminal ending by default; it is a fork that changes later costs and route availability.