Appeal Retaliation Counterpressure / 申诉报复反压机制

Appeal Retaliation Counterpressure is the mechanism for turning a visible retaliation against a captured metric appeal into a managed pressure surface.

指标捕获申诉机制 already proves that an underfilled appeal can arm 指标申诉报复默认. This mechanism starts after that default. It does not reopen the appeal. It asks whether the producer can identify the retaliation author, record their trace, assign a counterpressure handler, and force a future reader to treat the retaliation as scarred evidence rather than invisible punishment.

Design purpose

The current corpus has strong first-order appeal, finite faction commitment, and witness reprisal coverage. The missing play surface is counterplay after retaliation has already happened.

Without this mechanism, failed appeals risk becoming one-way punishment. With it, failure can create a second management problem:

• who retaliated;
• what pressure trace they left;
• what reserve or authority they spent;
• who can handle the counterpressure;
• what shield or price is assigned;
• which future reader consumes the result;
• what scar remains even when pressure is reversed.

State-triggered entry

Open this mechanism only from live retaliation state:

entry_state:
  trigger_kind: state_pressure
  source_retaliation_event_present: true
  source_retaliation_event: storyteller.event.metric_appeal_retaliation_default.v1 | equivalent
  captured_report_id_present: true
  captured_metric_present: true
  hidden_debt_present: true
  retaliation_author_present: true
  pressure_trace_or_explicit_absence_visible: true
  future_reader_present: true
  no_fixed_turn_trigger: true

It must never open from fixed turn count, day count, phase quota, raw content count, dashboard state, or lens-health state.

Content surfaces

Ledger card

申诉报复账本 stores the source appeal/default, retaliation row, pressure trace, assignment slots, and future reader.

Counterpressure hearing

申诉报复反压听证 resolves public trace exposure, lawful stay, sponsor release call, route asset counterseal, witness shelter, baited overcommitment, or failed counterpressure.

Pressure reversal event

申诉压力反转 records the durable result. It preserves source retaliation and mutates future route access.

Required state model

appeal_retaliation_counterpressure_state:
  unopened: retaliation exists but no ledger has been created
  retaliation_logged: author and source default are visible
  trace_absent: retaliation exists but trace proof is missing
  trace_recorded: pressure trace is stored but not yet admissible
  counterpressure_open: player can assign mode handler shield price and future reader
  public_trace_exposed: retaliation trace becomes public or addendum-bearing
  lawful_stay: retaliation is paused by oath, order, or producer-license stay
  sponsor_release_called: private retaliation is forced into discoverable release or surcharge
  route_asset_countersealed: route asset is protected, split, quarantined, or scarred
  witness_sheltered: carrier, crew witness, public receipt holder, or historian is protected at cost
  author_overcommitted: retaliation author spends into contradiction and becomes exhausted or hostile
  pressure_split: one reader accepts while another surcharges or rejects
  counterpressure_failed: missing slot hardens retaliation
  recovery_only: future route is possible only through higher-cost recovery

A satisfying implementation must expose durable states equivalent to at least eight of these. The state cannot be hidden inside prose.

Assignment contract

The player must assign or explicitly omit:

assignment_contract:
  ledger: storyteller.card.appeal_retaliation_ledger.v1
  source_retaliation_event: storyteller.event.metric_appeal_retaliation_default.v1 | equivalent
  captured_report_id: <id>
  retaliation_author: <author>
  retaliation_vector: <vector>
  pressure_trace_or_absence: <trace_or_absence>
  selected_counterpressure_mode: public_trace_exposure | lawful_stay | sponsor_release_call | route_asset_counterseal | witness_shelter | bait_overcommitment | explicit_no_answer
  handler_or_absence: <handler_or_absence>
  shield_or_absence: <shield_or_absence>
  price_or_absence: <price_or_absence>
  future_reader: <reader>

No assignment may be implied by famous-character presence, faction mood, legal authority, sponsor money, public outrage, or generic route pressure.

Branch contract

Public trace exposure

Turns recorded retaliation into public table, public receipt, unauthorized history, or addendum evidence.

Required effects:

• relief: trace or hidden debt becomes more legible;
• cost: exposure, sponsor pressure, fan oxygen liability, or public distrust rises;
• future: public table, addendum, or scar is required.

Lawful stay

Pauses retaliation through oath, legal hold, archive order, or producer-license stay.

Required effects:

• relief: reversal, seizure, recapture, or license pressure pauses;
• cost: inspection heat, bureau favor debt, archive debt, or release delay rises;
• future: lawful-only, stay-bound, or appeal-required state persists.

Sponsor release call

Forces a sponsor or private claimant to attach discoverability to a retaliation settlement.

Required effects:

• relief: private retaliation weakens;
• cost: contract capture, naming-rights pressure, public distrust, or future blackmail rises;
• future: sponsor release or surcharge is required;
• hidden debt cannot be deleted.

Route asset counterseal

Protects the route asset from recapture or false-clean hardening.

Required effects:

• relief: asset integrity or custody clarity improves;
• cost: quarantine, archive debt, route pressure, or inspection heat rises;
• future: counterseal, release, recovery-only, or costlier use is required.

Witness shelter

Protects a pressure carrier, crew witness, public receipt holder, or unauthorized historian.

Required effects:

• relief: witness retaliation or crew leak pressure decreases;
• cost: payroll leak, handler burden, exposure, or fan oxygen liability rises;
• future: 证人报复链 may consume sheltered, exposed, or poisoned person state.

Baited overcommitment

Lets the author spend retaliation into a contradiction or trace trap.

Required effects:

• relief: trace legitimacy, route scar opening, or faction exhaustion improves;
• cost: faction hostility, coalition pressure, inspection heat, or future blackmail rises;
• future: 派系过度承诺破口 fires or is recorded.

Failed counterpressure

Missing trace, handler, shield, price, or future reader hardens retaliation.

Required effects:

• source retaliation remains visible;
• future route becomes blocked, costlier, sponsor-only, lawful-only, public-table-required, counterseal-required, or recovery-only;
• at least three durable states move.

Counter contract

Every non-default resolution must include:

counter_deltas_required:
  relief: at_least_one
  cost: at_least_one
  future_reader_or_route_effect: at_least_one

Failed counterpressure must include at least three durable changes and may include no relief.

Primary counters and states:

• appeal_retaliation_counterpressure_state
• retaliation_pressure
• retaliation_author_posture
• trace_legitimacy
• false_clean_hardening
• hidden_debt_legibility
• producer_license_pressure
• public_receipt_legitimacy
• public_receipt_distrust
• sponsor_stop_loss_pressure
• contract_capture
• inspection_heat
• bureau_favor_debt
• archive_debt
• route_asset_pressure
• route_asset_integrity
• witness_exposure
• handler_burden
• fan_oxygen_liability
• edit_debt
• faction_exhaustion
• faction_hostility
• coalition_pressure
• future_recovery_cost

Future readers

At least one downstream reader must consume the result:

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

Replay evidence shape

mechanic_id: storyteller.mechanic.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
  no_fixed_turn_trigger: true
ledger:
  card: storyteller.card.appeal_retaliation_ledger.v1
  captured_report_id: <id>
  retaliation_author: <author>
  retaliation_vector: <vector>
  pressure_trace_or_absence: <trace_or_absence>
assigned_hearing:
  rite: storyteller.rite.appeal_retaliation_counterpressure_hearing.v1
  selected_counterpressure_mode: <mode>
  handler_or_absence: <handler_or_absence>
  shield_or_absence: <shield_or_absence>
  price_or_absence: <price_or_absence>
  future_reader: <reader>
result:
  event_seen_or_armed: storyteller.event.appeal_pressure_reversal.v1
  reversal_state_after: <state>
  counter_deltas: {}
  future_route_effect: <effect>
assertions:
  - entry_is_state_triggered
  - source_retaliation_is_preserved
  - retaliation_author_trace_slots_and_future_reader_visible
  - branch_outcomes_diverge
  - success_has_relief_cost_and_future_gate
  - failed_counterpressure_hardens_retaliation
  - downstream_reader_consumes_result
  - no_fixed_turn_trigger

Non-goals

• Not governance, dashboard, or metric methodology.
• Not a generic faction-reputation layer.
• Not a second attempt to cleanly redo a failed appeal.
• Not a raw count expansion.
• Not a fixed turn, fixed day, or chapter-phase trigger.
• Not valid if retaliation disappears without trace, cost, and future reader consequence.