Appeal Retaliation Counterpressure / 申诉报复反压线

Appeal Retaliation Counterpressure is a pressure-system storyline for the moment after a captured metric appeal has produced retaliation.

It follows 指标捕获申诉线 but does not replace it. The appeal already failed, was suppressed, was underfilled, was bought without discoverable release, or lacked a future reader. Now someone has used that gap to harden a false-clean report, discredit the claimant, reverse lawful status, recapture a route asset, leak against a crew carrier, or force recovery-only access.

The primary playable question is:

Can the producer turn a retaliation author’s pressure trace into counterpressure without pretending the original appeal became clean?

Why this is the next useful expansion

The current green corpus already has:

• 指标捕获申诉线, which makes false-clean metrics appealable and punishes underfilled appeals;
• 派系承诺账本, which makes factions spend finite leverage;
• 证人报复链, which handles retaliation against a protected person;
• Producer License and Pressure, Route Assets and Custody, public contrition, correction slot, and legality conversion as downstream readers.

The remaining product gap is retaliation counterplay. A retaliation default should not be only punishment, and it should not be a free recovery route. It should become a management/RPG problem where the player assigns trace, handler, shield, price, and future reader.

This storyline creates that middle layer.

State-triggered entry

Open this storyline when all are true:

1. a source appeal/default exists, usually 指标申诉报复默认;
2. a captured report, challenged metric, hidden debt, or appealed route asset is still future-relevant;
3. a retaliation author is visible or can be represented as explicit absence;
4. retaliation changed a report, public table, lawful status, crew witness, quote, route asset, producer-license surface, or recovery path;
5. a pressure trace exists or absence is explicit: receipt, oath, checksum, side letter, notice, witness, leak, public backfire, route recapture trace, or missing proof;
6. the player can assign a counterpressure mode, handler, shield, price, and future reader, or record explicit no-answer;
7. the route has not reached terminal clean correction, terminal seizure, final public discharge, final witness loss, or irreversible route lock;
8. no entry condition depends on fixed turn count, day interval, phase quota, chapter quota, raw page count, dashboard state, or lens-health state.

Content pack

Mechanism

• 申诉报复反压机制 defines the state machine, assignment contract, branch contract, counters, and replay evidence.

Card

• 申诉报复账本 records source default, author, demanded control, trace, slots, and future reader.

Rite

• 申诉报复反压听证 resolves public trace exposure, lawful stay, sponsor release call, route asset counterseal, witness shelter, baited overcommitment, or explicit no-answer.

Event

• 申诉压力反转 records the scarred result and preserves the original retaliation.

Storyline spine

Beat 1 — Retaliation leaves a trace

A failed or suppressed appeal arms retaliation. The author may be a board, sponsor, inspector, editor, fan public, crew table, route-asset claimant, or blackout system.

The retaliation must be concrete:

retaliation_source:
  source_retaliation_event: storyteller.event.metric_appeal_retaliation_default.v1 | equivalent
  captured_report_id: <id>
  retaliation_author: <author>
  retaliation_vector: discredit | sponsor_retainer | lawful_reversal | public_backfire | crew_leak | route_asset_recapture | false_clean_hardened | recovery_only | equivalent
  demanded_control: report_state | release_wording | legal_status | public_table | route_asset | witness | quote | producer_license | equivalent

Beat 2 — Ledger converts punishment into assignment surface

Create 申诉报复账本. The card must show trace state and assignment slots. Missing proof is allowed only as explicit absence.

ledger_open:
  pressure_trace_state: absent | weak | recorded | admissible | public | poisoned
  selected_mode_or_absence: <mode_or_absence>
  handler_or_absence: <handler_or_absence>
  shield_or_absence: <shield_or_absence>
  price_or_absence: <price_or_absence>
  future_reader: <reader>

Beat 3 — Counterpressure hearing forces costed branch

Offer 申诉报复反压听证. The player chooses:

• expose the trace publicly;
• seek a lawful stay;
• force a sponsor release call;
• counterseal or quarantine a route asset;
• shelter a witness or carrier;
• bait the author into overcommitment;
• give no answer and let retaliation harden.

No branch may create clean universal success.

Beat 4 — Future reader consumes the scar

At least one downstream reader must accept, reject, surcharge, or narrow future use:

• Producer License and Pressure opens, stays, or tightens review;
• Route Assets and Custody changes asset availability;
• 派系承诺账本 consumes author reserve, exhaustion, hostility, or coalition pressure;
• 证人报复链 consumes sheltered, exposed, or poisoned person state;
• 公开悔过账本 demands addendum or public table scar;
• 更正档期竞拍线 prices the repair;
• 播出合法性转轨线 gates lawful use.

Branch map

Branch	Relief	Cost/scar	Future state
Public trace exposure	trace legitimacy, hidden debt legibility, public receipt legitimacy	witness exposure, sponsor pressure, fan oxygen liability, distrust	public-table-required, addendum, scarred reopening
Lawful stay	recapture/reversal/license pressure pauses	inspection heat, bureau debt, archive debt, delay	lawful-only, stay-bound, appeal-required
Sponsor release call	private retaliation weakens, release record visible	contract capture, naming pressure, distrust, blackmail	sponsor-release-required, surcharge
Route asset counterseal	route asset integrity or custody clarity improves	quarantine, route pressure, archive debt, inspection heat	counterseal-required, recovery-only until release
Witness shelter	carrier or crew leak pressure falls	payroll leak, handler burden, exposure, fan liability	witness-shelter-required, reprisal chain armed
Bait overcommitment	author reserve exposed, trace legitimacy rises	faction hostility, coalition pressure, future blackmail	costlier, coalition-bound, scarred reopening
Explicit no answer	no relief	retaliation hardens, license/public/route costs rise	blocked, costlier, sponsor-only, lawful-only, public-table-required, recovery-only

Missability and recovery

This storyline is missed when implementation:

• lets retaliation remain mood text or generic reputation damage;
• lets the player undo retaliation without identifying author, trace, handler, shield, price, and future reader;
• deletes the source appeal/default;
• lets sponsor release erase hidden debt;
• reopens a route without scar, surcharge, lawful stay, public table, quarantine, counterseal, or future cost;
• triggers from fixed turn count, day count, phase quota, raw content count, or lens-health state.

Recovery is allowed only at higher cost:

• reopen counterpressure with stronger trace;
• accept public exposure and sponsor backlash;
• buy lawful stay and bureau debt;
• quarantine or split the route asset;
• shelter the witness and accept payroll or handler pressure;
• expose overcommitment and accept hostility or coalition pressure;
• accept recovery-only until a future reader consumes the scar.

Replay evidence expectation

storyline_id: storyteller.storyline.appeal_retaliation_counterpressure.v1
session_id: lens-appeal-retaliation-counterpressure-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  source_retaliation_event_present: true
  retaliation_author_present: true
  pressure_trace_or_explicit_absence_visible: true
  future_reader_present: true
  no_fixed_turn_trigger: true
source:
  source_retaliation_event: storyteller.event.metric_appeal_retaliation_default.v1
  captured_report_id: <id>
  captured_metric: <metric>
  hidden_debt: <state>
offered:
  card: storyteller.card.appeal_retaliation_ledger.v1
  rite: storyteller.rite.appeal_retaliation_counterpressure_hearing.v1
branch_runs:
  counterpressure_branch:
    selected_counterpressure_mode: public_trace_exposure | lawful_stay | sponsor_release_call | route_asset_counterseal | witness_shelter | bait_overcommitment
    handler_or_absence: <handler_or_absence>
    shield_or_absence: <shield_or_absence>
    price_or_absence: <price_or_absence>
    event_seen_or_armed: storyteller.event.appeal_pressure_reversal.v1
    reversal_state_after: <state>
    counter_deltas: {}
    future_route_effect: <effect>
  failed_branch:
    selected_counterpressure_mode: explicit_no_answer
    event_seen_or_armed: storyteller.event.appeal_pressure_reversal.v1
    reversal_state_after: counterpressure_failed | recovery_only
    counter_deltas: {}
    future_route_effect: <effect>
assertions:
  - entry_is_state_triggered
  - source_retaliation_preserved
  - ledger_records_author_trace_slots_and_future_reader
  - hearing_branches_diverge
  - success_has_relief_cost_and_future_gate
  - failed_counterpressure_hardens_retaliation
  - downstream_reader_consumes_result
  - no_fixed_turn_trigger

Non-goals

• Not a filler aftermath scene.
• Not governance or dashboard methodology.
• Not a second clean appeal.
• Not a generic faction reputation route.
• Not a global revenge meter.
• Not a fixed turn or fixed day trigger.
• Not a way to erase failed appeal cost.