Audience Stability Triage

Audience Stability Triage is the assignable management rite for resolving Ratings Floor Breach. It asks the player to choose what keeps the audience watching after a broadcast becomes unstable: public proof, sponsor patch, unofficial attention, schedule compression, or suppression.

The rite belongs to 观众稳定性下限 and writes its result into Audience Stability Index.

Inputs

Required:

• Audience Stability Index in a volatile, breached, patched, bridged, compressed, or churn state;
• one broadcast-facing object: Last Performance, a sponsor relief surface, a fan oxygen ledger, a public receipt, a pirate relay, or a Blackout Incident;
• one proof, liability, or attention object: Voice Receipt, 未剪辑真唱母带, Pirate Frequency Relay Token, a sponsor escrow promise, a cutroom receipt, a fan oxygen stub, an inspector token, or a schedule slot;
• one assigned handler or explicit absence state.

Optional but branch-changing:

• Orion Breath for clean patch, escrow, or liability freeze pressure;
• Inspector Rhee Archive for audit cost, public naming, or suppression risk;
• Han Cutroom for source-proof public explanation or edited clean patch;
• 海盗频段童声 for pirate attention bridge or relay custody risk.

Branches

Branch A — Public receipt stabilization

The player assigns a receipt, witness, final-take source, or visible contradiction and lets the audience understand why the broadcast is unstable.

Expected result:

• 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;
• later sponsor clean patch and suppression branches become more expensive or more openly contested.

Branch B — Sponsor clean patch

The player assigns Orion, a sponsor relief surface, or a clean cut to hold audience attention with money and polish.

Expected result:

• set sponsor_clean_patch;
• audience_churn -1 or broadcast_floor_breach -1;
• contract_capture +1, public_receipt_distrust +1, archive_fraud +1, sponsor_escrow_debt +1, or voice_integrity_risk +1;
• public receipt, artist trust, fan oxygen, or inspector branches retain a later objection.

Branch C — Pirate attention bridge

The player assigns a relay token, fan queue witness, or unofficial commentator to carry the audience while the official channel remains contested.

Expected result:

• set pirate_attention_bridge or fan_attention_bridge;
• audience_churn -1, public_grief_stability +1, or schedule_slot_saved +1;
• inspection_heat +1, relay_custody_risk +1, fan_oxygen_resentment +1, or sponsor_stop_loss_pressure +1;
• future relay custody or fan oxygen accounting becomes harder unless protected.

Branch D — Schedule compression

The player assigns a schedule slot, license desk, or folded-contract handler to move, merge, delay, or shorten the unstable broadcast promise.

Expected result:

• 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;
• a later Broadcast Schedule or Blackout Incident surface must remember the scar.

Branch E — Suppress or hide the breach

The player assigns no valid proof, hides the receipt, buries fan accounting, or uses a clean ending without naming the cost.

Expected result:

• set audience_churn_spiral, floor_breach_hidden, clean_patch_backlash, or stability_floor_missed;
• audience_churn +1, public_grief_stability -1, fan_oxygen_resentment +1, inspection_heat +1, or black_screen_slots +1;
• later public receipt, pirate relay, sponsor negotiation, or schedule recovery options are locked or more expensive.

Resolution requirements

Every branch must:

1. change Audience Stability Index or an equivalent durable route state;
2. mutate at least two counters;
3. record assigned cards, handler, proof, or explicit absence;
4. preserve at least one sponsor, fan, inspector, archive, relay, or schedule cost;
5. alter at least one later option, tag, cost, or route availability.

Failure and recovery

A hidden or missed floor may be recovered only by accepting a scar:

• publish the breach later with public_receipt_distrust already raised;
• use sponsor money while adding contract_capture or sponsor_escrow_debt;
• ask pirate or fan relay for help while increasing relay_custody_risk;
• compress the schedule and risk blackout debt;
• satisfy an inspector or editor proof branch at higher cost.

Non-goals

• Not a morale action.
• Not a fixed numbered trigger.
• Not a free rescue for a failing schedule slot.
• Not a generic PR statement; the assigned proof, handler, or explicit absence must change branch results.