Appeal Residue Routing / 申诉残留分流线

Appeal Residue Routing is the pressure-system storyline for a scarred appeal result after the player has won enough for the result to matter, but before future readers spend it as if it were clean.

A successful 指标捕获申诉线 or 申诉报复反压线 can leave behind a limited credit: public correction, lawful stay, sponsor release, crew scar, quote reprice, route counterseal, split metric, or trustee note. This storyline makes that credit playable.

The promise is simple: the residue of a paid appeal is useful, but it is not a universal clean key.

Why this expansion is high-value

The current corpus is strong at local appeal and retaliation:

• 指标捕获申诉线 makes a captured false-clean report appealable and costly.
• 申诉报复反压线 turns retaliation against an appeal into assignable counterpressure.
• 裁定读者冲突线 prevents an existing source row from satisfying incompatible readers.
• 伤痕汇流台线 prevents a scarred stabilizer from becoming clean after several histories converge.

The missing product gap is the in-between state: a single appeal/counterpressure result can now be cited by multiple future systems. If not routed, that residue becomes invisible free cleanup. This storyline forces the player to spend, escrow, split, burn, or default it.

State-triggered entry

Open this storyline when all conditions below are true:

1. a scarred appeal or counterpressure result exists and is preserved;
2. the result has relief, cost, and a future reader or route effect;
3. the result creates a residue credit with limited scope;
4. at least one future reader can consume the residue;
5. duplicate or out-of-scope use is possible;
6. the player can assign a primary reader, handler, proof/seal, price, or explicit absence;
7. no entry condition depends on fixed turn count, day interval, chapter quota, raw content count, raw scar count, dashboard state, or lens health.

Content pack

Mechanism

• 申诉残留分流机制 defines residue credit, routing entry, assignment slots, branch contract, duplication default, counters, and replay evidence.

Card

• 申诉残留账本 records the source result, residue type, residue scope, spend limit, possible readers, primary reader, excluded readers, handler, proof/seal, price, and future effect.

Rite

• 申诉残留分流听证 resolves license routing, public table routing, lawful conversion, sponsor release, route asset counterseal, split-metric escrow, burn/retirement, or duplicate/no answer.

Event

• 残留信用复用默认 fires or is armed when a residue is double-spent, hidden from a primary reader, flattened into a clean key, or used without required discoverability.

Storyline spine

Beat 1 — A scarred appeal result becomes valuable

A branch from appeal or counterpressure creates a result that future systems want to cite.

Examples:

• public correction makes a hidden debt legible;
• lawful stay pauses a producer-license harm;
• sponsor release weakens private retaliation but preserves a confession scar;
• quote reprice detaches a false number from a captured report;
• route counterseal protects an asset but makes it unavailable;
• split metric lets one reader proceed while another reader surcharges.

Beat 2 — The residue ledger opens

Create 申诉残留账本. The ledger must show:

• source result id;
• source report or retaliation ledger id;
• residue id;
• residue type;
• scope and spend limit;
• eligible readers;
• duplicate or scope-breach risk;
• assignment slots.

Beat 3 — The producer routes the residue

Run 申诉残留分流听证. The player chooses whether the residue goes to license review, public table, lawful conversion, sponsor release, route counterseal, split-metric escrow, burn/retirement, or default/no answer.

The rite must record primary reader, excluded or delayed readers, handler, proof/seal, price or burn cost, and future effect.

Beat 4 — A future reader consumes the routed residue

At least one future system must consume the result:

• Producer License and Pressure reads a routed license note or surcharge;
• 公开悔过账本机制 reads a public scar or addendum;
• 更正档期竞拍机制 prices follow-up correction;
• 播出合法性转轨机制 reads lawful use or stay;
• Route Assets and Custody reads counterseal, quarantine, or release state;
• Broadcast Reality stores split, burned, duplicated, or captured residue.

Beat 5 — Duplicate use defaults or feeds later scars

If the residue is reused as a clean key, 残留信用复用默认 records the capturing reader and harmed/excluded reader.

A duplicated or overclaimed residue can later become a scarred stabilizer for 伤痕汇流台线, but this storyline handles the first routing problem before convergence.

Branch map

Branch	Immediate relief	Cost/scar	Future state
Route to license review	license harm narrows or stay opens	inspection, public table, or bureau cost rises	producer-license note, stay, surcharge, or review
Route to public table	public legitimacy and hidden-debt legibility improve	sponsor, witness, fan oxygen, or panic cost rises	public-table-required; accepted with scar
Route to lawful conversion	lawful use or liability narrowing improves	delay, archive debt, bureau debt, or inspection heat rises	lawful-only, stay-bound, public route costlier
Route to sponsor release	private retaliation or stop-loss pressure weakens	contract capture, public distrust, future blackmail	release record, confession scar, public surcharge
Route to route asset counterseal	asset custody/integrity improves	quarantine, release cost, route pressure, inspection	counterseal required, protected but unavailable, recovery-only
Escrow for split metric	scoped acceptance becomes possible	ambiguity, handler burden, correction pressure	split-required, surcharge, contradiction pending
Retire or burn residue	duplicate risk and false-clean hardening fall	current route loses the credit	substitute required, costlier, recovery-only
Duplicate or no answer	no true relief	duplication default, reader capture, false-clean hardening	blocked, split-required, producer-license review, recovery-only

Missability and recovery

This storyline is missed when implementation:

• lets a scarred appeal result become a universal clean key;
• lets one-use residue satisfy multiple future readers without split annotation or surcharge;
• omits source result id, residue id, scope, spend limit, primary reader, handler, proof/seal, or price;
• lets sponsor release erase discoverability;
• uses a split metric as universal acceptance;
• treats burn/retirement as flavor rather than route cost;
• triggers from fixed turn, day interval, chapter quota, raw content count, or lens health.

Recovery is allowed only through a visible new surface: public addendum, lawful stay, sponsor release record, correction slot, route counterseal, split annotation, burned residue, fresh appeal, or recovery-only path.

Replay evidence expectation

storyline_id: storyteller.storyline.appeal_residue_routing.v1
session_id: lens-appeal-residue-routing-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  source_result_present: true
  residue_credit_created: true
  possible_consumer_present: true
  duplicate_or_scope_breach_risk_present: true
  no_fixed_turn_trigger: true
source_result:
  source_result_id: <id>
  source_report_or_ledger_id: <id>
  source_state_after: <state>
residue:
  ledger: storyteller.card.appeal_residue_ledger.v1
  residue_id: <id>
  residue_type: <type>
  residue_scope: <scope>
  spend_limit: <limit>
offered:
  rite: storyteller.rite.appeal_residue_routing_hearing.v1
branch_result:
  selected_routing_mode: <mode>
  primary_reader_or_absence: <reader or explicit_absence>
  excluded_or_delayed_readers: []
  residue_state_after: <state>
  emitted_event: storyteller.event.residue_credit_duplication_default.v1 | none_if_valid
  future_route_effect: <effect>
  counter_deltas:
    relief: []
    cost: []
    future: []
assertions:
  source_result_preserved: true
  residue_scope_and_spend_limit_visible: true
  routing_assignments_explicit: true
  no_universal_clean_key: true
  duplicate_or_scope_breach_defaults: true
  downstream_reader_consumes_result: true

Non-goals

• Not raw content-count growth.
• Not a generic success aftermath scene.
• Not a clean reward card.
• Not a second appeal retry.
• Not a replacement for appeal, counterpressure, reader collision, scar convergence, public contrition, correction slots, legality conversion, or route asset custody.
• Not valid unless a limited appeal residue is routed, escrowed, burned, or defaulted with future consequences.