Settlement Aftershock Breach / 和解反震破口

Settlement Aftershock Breach is the visible event when a prior settlement, split, quarantine, public receipt, sponsor package, audit seal, or editorial patch fails under later pressure.

It turns unpaid settlement debt into a public, sponsor, inspector, edit, archive, fan, or route-asset consequence.

Event trigger

Fire this event when the state contains one of:

• 和解反震账本 with state breached, hardened, silent_debt_hardened, false_settlement_owner, or equivalent;
• 和解反震复核 resolves without credible handler, opposing proof, or cost;
• a prior branch from 认领撞锁, 播出实在漂移审计, Audience Stability Floor Storyline, Oxygen Claim Exchange Storyline, or Memorial Rights Contempt Storyline carries debt into a later state and fails to pay it.

This event is not scheduled by turn count. It is fired by unpaid state and failed review.

What the player sees

The broadcast does not simply say the earlier settlement failed. It shows which surface broke first:

Breach surface	Public description	Required state mutation
Sponsor desk	The sponsor reopens stop-loss because the earlier relief no longer protects the slot.	sponsor_stop_loss_pressure +1, contract_capture +1, route cost rises, or sponsor capture begins.
Fan public	The fan oxygen ledger rejects the settlement as unpaid, false, or privately captured.	fan_oxygen_resentment +1, public_receipt_distrust +1, audience or route pressure rises.
Inspector/archive	The audit body refuses the settlement copy, seal, or proof chain.	inspection_heat +1, archive_debt +1, custody_clarity -1, or lawful route access is delayed.
Editor/black-box	The cut cannot keep continuity without creating new edit debt.	edit_debt +1, continuity_hazard +1, reality_drift +1, or future fraud cost rises.
Broadcast reality	The aired version and receipt version both remain public.	reality_drift +1, black_screen_slots +1, audience_churn +1, or double reality hardens.
Route asset	The resolved asset becomes captured, hostile, sacrificed, or falsely owned.	future use becomes blocked, costlier, or recovery-only.

Branch outcomes

Sponsor breach

A quiet sponsor reconciliation breaks because fan, archive, public, or edit proof remains unpaid.

Expected deltas:

• sponsor_stop_loss_pressure +1
• contract_capture +1
• one of public_receipt_distrust +1, inspection_heat +1, fan_oxygen_resentment +1, or route_asset_pressure +1

Public breach

A public receipt or fan refund is rejected as staged, underfunded, or captured.

Expected deltas:

• fan_oxygen_resentment +1
• public_receipt_distrust +1 or public_receipt_legitimacy -1
• one of sponsor_stop_loss_pressure +1, audience_churn +1, or inspection_heat +1

Compliance breach

An inspector or archive body reopens the source copy, seal, or route asset because the settlement record cannot prove custody.

Expected deltas:

• inspection_heat +1
• archive_debt +1 or archive_fraud +1
• one of schedule_slots_occupied +1, sponsor_stop_loss_pressure +1, or custody_clarity -1

Editorial breach

The edit, checksum, or black-box patch keeps one surface legible but exposes a contradiction elsewhere.

Expected deltas:

• edit_debt +1
• continuity_hazard +1 or future_fraud_cost +1
• one of public_receipt_distrust +1, archive_debt +1, or reality_drift +1

Route asset breach

The earlier settlement owner hardens into a wrong owner or the asset exits clean use.

Expected deltas:

• route asset state becomes captured, hostile, sacrificed, false_owner, breached, or equivalent;
• route_asset_pressure +1 or false_owner_hardened +1;
• at least one future rite is blocked, costlier, or requires appeal/recovery.

Recovery hooks

After this event, the player may recover only through a costed path:

• reopen 和解反震复核 with stronger proof;
• escalate into 实在漂移审计;
• feed pressure back into Audience Stability Triage;
• accept route capture and then use 认领撞锁听证 or equivalent recovery;
• sacrifice a route asset, sponsor favor, edit patch, public apology, fan refund, or archive favor.

Non-goals

• Not a random crisis card.
• Not a mood event.
• Not proof that the earlier branch was invalid.
• Not a turn-based punishment.
• Not a clean loss screen; breach must create recovery, mutation, or hostile-route pressure.