Appeal Stay Afteruse / 申诉暂缓后用机制

Appeal Stay Afteruse is the mechanism that prevents a temporary stay from becoming universal clean permission.

The existing mesh already supports appeal residue, appeal retaliation, archive enforcement, broadcast legality conversion, and management compression. Those systems can prove that a controversy was paused, held, narrowed, or appealed. The uncovered danger is afteruse: a later desk can cite we have a stay as if the disputed route, proof, broadcast, sponsor package, public recap, or metric had won on the merits.

This mechanism makes that citation playable and costly.

Design problem

A stay is useful because it preserves a route, claimant, proof, or reply path while a harder question remains unresolved. If the implementation lets sponsor, management, archive, legal, public recap, or broadcast reality consume the stay as clean authority, then every appeal becomes an exploit: pause enforcement now, launder the pause as permission later.

The mechanism therefore separates three states:

1. the stay exists;
2. the stay scope permits a narrow act;
3. the merits or route truth remain unresolved unless a later branch pays for resolution.

State-triggered entry

Open this mechanism only when all required state exists:

entry_state_required:
  trigger_kind: state_pressure
  source_appeal_or_stay_present: true
  source_stay_scope_visible: true
  afteruse_request_present: true
  afteruse_request_claims_clean_permission_or_equivalent: true
  beneficiary_of_clean_stay_visible_or_explicit_absence: true
  harmed_or_deferred_reader_visible_or_explicit_absence: true
  merits_unresolved_or_explicitly_narrowed: true
  future_reader_or_route_consumes_stay_state: true
  player_can_scope_merits_notice_annex_escrow_restrict_quarantine_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_appeal_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Valid source stays include:

• appeal residue that preserves a claim but does not decide it;
• retaliation counterpressure that pauses punishment but does not prove safety;
• archive enforcement hold that preserves proof but does not release it cleanly;
• broadcast legality pause that prevents unlawful conversion but does not create legality;
• claimant collision hold that prevents erasure but does not select the owner;
• oxygen clawback stay that protects a breath promise but does not settle sponsor priority;
• equivalent temporary non-enforcement posture.

Core objects

• 申诉暂缓后用案卷 records the source stay, afteruse request, clean claim, beneficiary, harmed reader, proof anchor, minimum condition, and future reader.
• 申诉暂缓后用复核 resolves the request through scoped tag, merits hearing, public notice, lawful annex, escrow, sponsor restriction, quarantine, or default.
• 暂缓令越权默认 fires or arms when a stay is consumed as merits, release, legality, public truth, or clean metric.

State machine

states:
  - stay_afteruse_requested
  - stay_scope_visible
  - scoped_stay_carried
  - merits_hearing_required
  - public_notice_required
  - lawful_annex_required
  - proof_or_asset_escrowed
  - sponsor_afteruse_restricted
  - afteruse_quarantined
  - stay_overread
  - management_false_clean
  - sponsor_only_afteruse
  - archive_premature_release
  - legality_overclaim
  - public_false_clean
  - contradiction_pending
  - recovery_only_afteruse

The source appeal row is never erased by this mechanism. A branch changes whether later readers may consume it and at what cost.

Branch contract

Every non-default branch must mutate at least three surfaces:

• one relief surface;
• one cost surface;
• one future reader, route, asset, legality, public, management, or claimant effect.

Branch families:

Branch	Relief	Cost	Future effect
Carry scoped stay tag	route continues without lying	public/lawful/sponsor notice debt	accepted with tag, costlier, merits still required
Force merits hearing	false clean use blocked	schedule/sponsor/handler pressure	hearing required, route delayed
Publish public notice	public recap cannot claim vindication	distrust, inspection heat, sponsor retaliation	public-only, correction-cost, contradiction pending
Attach lawful annex	lawful/archive reader can consume the stay safely	archive debt, bureau debt, public delay	lawful-only, annex required
Escrow proof or route asset	false release blocked	route pressure, archive debt, schedule pressure	escrow required, costlier, lawful after review
Restrict sponsor afteruse	slot/sponsor pressure falls	contract capture, public distrust, future correction	sponsor-only, unwind required
Quarantine afteruse	stay laundering blocked	route block, schedule pressure, management pressure	blocked, substitute required, recovery-only
Overreach default	immediate desk relief may occur	stay becomes false-clean claim	sponsor-only, public false clean, legality overclaim, blocked, recovery-only

No branch may turn a stay into universal clean authority across sponsor, lawful, archive, public, claimant, route asset, management, and broadcast reality readers.

Reader distinctions

Reader	What they may accept	What they must not accept
Sponsor	scoped use, restricted package, temporary pressure relief	merits win, public consent, route truth
Lawful/archive	annexed stay, escrow, proof hold	public legitimacy, final ownership, clean release
Public/fan	notice that enforcement paused	vindication, apology completion, oxygen waiver
Claimant	preserved reply path or hold	loss of remedy, preclusion, owner selection
Management	qualified metric, pending status	clean KPI, closed liability, clean schedule efficiency
Broadcast reality	visible contradiction or scoped tag	aired stay as historical innocence

Failure modes

The mechanism fails if any are true:

• a stay is treated as a final ruling;
• afteruse has no docket;
• stay scope is absent or hidden;
• beneficiary of the clean stay is hidden;
• harmed or deferred reader is hidden without explicit costly absence;
• merits state disappears;
• sponsor, management, archive, legal desk, public recap, or route claimant can cite the stay cleanly for all readers;
• default only raises generic heat without false clean claim and future route effect;
• entry is driven by fixed turn, day, week, chapter, raw appeal count, dashboard state, or lens health.

Replay evidence shape

mechanic: storyteller.mechanic.appeal_stay_afteruse.v1
session_id: lens-appeal-stay-afteruse-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  source_appeal_or_stay_present: true
  source_stay_scope_visible: true
  afteruse_request_present: true
  merits_unresolved_or_explicitly_narrowed: true
  future_reader_or_route_consumes_stay_state: true
  no_fixed_turn_trigger: true
docket:
  card: storyteller.card.appeal_stay_afteruse_docket.v1
  source_stay_kind: <kind>
  requested_future_use: <use>
  clean_claim: <claim>
  beneficiary_of_clean_stay: <actor or explicit_absence>
  harmed_or_deferred_reader: <reader or explicit_absence>
hearing:
  rite: storyteller.rite.appeal_stay_afteruse_review.v1
  selected_posture: carry_scoped_stay_tag | force_merits_hearing | publish_public_stay_notice | attach_lawful_annex | escrow_route_asset_or_proof | restrict_sponsor_afteruse | quarantine_afteruse | let_overreach_default
outcome:
  event: storyteller.event.stay_order_overreach_default.v1 | none_if_valid
  stay_state_after: <state>
  merits_state_after: <state>
  future_reader_or_route_effect: <effect>
  counter_deltas:
    relief: []
    cost: []
    future: []
assertions:
  - source_stay_preserved
  - stay_scope_not_merits
  - afteruse_request_visible
  - beneficiary_and_harmed_reader_visible_or_explicit_absent
  - branches_diverge_by_reader_scope_and_future_effect
  - overreach_default_is_durable
  - no_universal_clean_stay
  - no_fixed_turn_day_week_raw_count_dashboard_or_lens_health_trigger

Non-goals

• Not a new appeal verdict.
• Not a generic legal system.
• Not a cooldown or timer.
• Not a replacement for appeal residue, appeal retaliation, archive enforcement, broadcast legality, or management compression.
• Not valid unless future route acceptance changes.