Stay Notice Relay / 暂缓告知转运机制

Stay Notice Relay is the mechanism that makes scoped stay notices travel to future readers as playable state.

It extends 申诉暂缓后用机制 without replacing it. Appeal stay afteruse defines what a stay can and cannot mean. This mechanic defines whether that scope was delivered, who carried it, who was omitted, and how misdelivery mutates future play.

Mechanic promise

A stay scope is not durable until a future reader consumes either:

• a scoped receipt;
• a public bulletin;
• a lawful annex;
• an archive receipt or escrow;
• a sponsor-only or management-only summary with scar;
• an explicit absence;
• or a misdelivery default.

The mechanic fails if stay reviewed automatically equals reader informed.

Entry contract

entry_state:
  trigger_kind: state_pressure
  source_stay_present: true
  source_stay_scope_visible_or_explicit_absence: true
  downstream_afteruse_reader_present: true
  downstream_reader_would_consume_stay: true
  served_or_omitted_reader_can_diverge: true
  carrier_or_explicit_absence_visible: true
  future_reader_or_route_effect_visible: true
  player_can_deliver_recruit_retain_publish_annex_escrow_capture_suppress_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_notice_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Valid source states include appeal stay, archive hold, legality pause, enforcement pause, retaliation hold, claimant hold, oxygen clawback stay, or equivalent. The mechanism does not open from a generic legal cleanup or from lens status.

Core state fields

stay_notice_relay_state:
  source_stay_row_id: <row id or explicit_absence>
  stay_scope_integrity: intact | narrowed | public_only | lawful_only | sponsor_only | management_summary | overread | missing | explicit_absence
  carrier_state: unseen | visible | protected | retained | recruited | public_exposed | lawful_bound | escrow_bound | captured | suppressed | hostile | missed | explicit_absence
  served_reader: <reader or explicit_absence>
  omitted_reader: <reader or explicit_absence>
  proof_state: receipt | public_bulletin | lawful_annex | archive_receipt | escrow | sponsor_summary | management_summary | verbal_only | explicit_absence
  future_reader_or_route_effect: accepted_with_stay_tag | public_only | lawful_only | annex_required | escrow_required | sponsor_only | management_false_clean | contradiction_pending | blocked | recovery_only | equivalent

Carrier states

Carrier state	Meaning	Future consequence
visible	courier or handler can carry scope but is not protected	capture or hostility risk remains
protected	scope can be served with receipt	cost rises; future reader accepts tag
retained	one delivery is bought or sheltered	follow-up cost and payroll leak remain
recruited	courier becomes narrow route asset	future relay available only with source row visible
public_exposed	notice is public and courier is visible	public legitimacy rises; retaliation risk rises
lawful_bound	service is tied to lawful annex	lawful-only use; public notice still needed
escrow_bound	archive holds proof of service	release delayed; archive debt rises
captured	sponsor/management/archive controls wording	sponsor-only or management false clean
suppressed	carrier or row is hidden	misdelivery default or overreach likely
hostile	courier can testify against false delivery	recovery possible at higher cost
missed	downstream reader consumed stay before relay	late notice, correction, or recovery-only route

Branch families

Protected scoped delivery

The player records a relay slip, protects the carrier, serves the intended reader, and keeps the does_not_decide clause visible.

Required mutation:

relief_any:
  - stay_scope_integrity_up
  - stay_overread_pressure_down
  - future_reader_acceptance_with_tag_up
cost_any:
  - handler_burden_up
  - sponsor_stop_loss_pressure_up
  - inspection_heat_up
future_effect_any:
  - accepted_with_stay_tag
  - public_notice_required
  - lawful_annex_required

Recruit or retain courier

The player spends protection, payroll, route credit, or public blame relief to keep the carrier usable.

Required mutation:

relief_any:
  - stay_notice_delivery_up
  - repeat_relay_capacity_up
cost_any:
  - payroll_leak_up
  - route_asset_pressure_up
  - handler_burden_up
future_effect_any:
  - future_stay_relay_available_with_source_row
  - follow_up_delivery_required

Public / lawful / archive split

The player accepts that public notice, lawful annex, and archive receipt are different readers.

Required mutation:

relief_any:
  - public_false_clean_blocked
  - lawful_reader_acceptance_up
  - archive_release_integrity_up
cost_any:
  - public_delay_up
  - lawful_annex_debt_up
  - archive_debt_up
future_effect_any:
  - public_only
  - lawful_only
  - annex_required
  - escrow_required

Capture or misdelivery

Sponsor, management, archive, production, or explicit absence consumes the notice before the scope travels.

Required mutation:

relief_any:
  - immediate_pressure_down
cost_any:
  - stay_scope_integrity_down
  - public_receipt_distrust_up
  - broadcast_legality_risk_up
future_effect_any:
  - sponsor_only
  - management_false_clean
  - public_false_clean
  - legality_overclaim
  - contradiction_pending
  - recovery_only

Counter contract

Every resolved relay must mutate at least three durable surfaces:

counter_deltas_required:
  relief: at_least_one
  cost: at_least_one
  future_reader_or_route_effect: at_least_one

Primary surfaces:

• stay_scope_integrity
• stay_notice_delivery
• stay_overread_pressure
• courier_capture_risk
• courier_hostility
• handler_burden
• payroll_leak
• public_receipt_legitimacy
• public_receipt_distrust
• lawful_annex_debt
• archive_debt
• sponsor_stop_loss_pressure
• contract_capture
• management_pressure
• broadcast_legality_risk
• broadcast_reality_drift
• route_asset_pressure
• future_recovery_cost

Integration rules

• With 申诉暂缓后用线, this mechanism begins only after a scoped stay or explicit absence exists.
• With 代理人姿态链, the courier can become recruited, retained, faction-bound, hostile, or missed.
• With 容量告知送达队列线, a notice queue can carry stay scope but cannot make absence equal delivery.
• With 赞助后用引证线, sponsor receipt can be sponsor-only unless public/lawful readers also receive scope.
• With 经营压缩台, a management summary cannot count as clean liability unless the stay scope and omitted reader remain visible.
• With 播出合法性转轨线, notice delivery can support lawful annex, but cannot turn non-enforcement into legality.

Replay evidence expectation

mechanic: storyteller.mechanic.stay_notice_relay.v1
session_id: lens-stay-notice-relay-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  source_stay_present: true
  downstream_afteruse_reader_present: true
  carrier_or_explicit_absence_visible: true
  no_fixed_turn_trigger: true
selected_slip: storyteller.card.stay_notice_relay_slip.v1
selected_delivery: <branch>
carrier_state_before: <state>
carrier_state_after: <state>
served_reader: <reader or explicit_absence>
omitted_reader: <reader or explicit_absence>
stay_state_after: <state>
future_reader_or_route_effect: <effect>
event_seen_or_armed: storyteller.event.stay_notice_misdelivery_default.v1 | explicit_absence
counter_deltas:
  relief: []
  cost: []
  future: []
assertions:
  - source_stay_scope_visible_or_explicit_absent
  - served_and_omitted_reader_visible_or_explicit_absent
  - courier_state_changes_or_explicit_absence_recorded
  - branches_diverge_by_reader_scope_and_future_effect
  - misdelivery_default_is_durable
  - no_universal_clean_stay
  - no_fixed_turn_day_week_raw_count_dashboard_or_lens_health_trigger

Non-goals

• Not a second appeal review.
• Not legal governance.
• Not a general courier queue.
• Not a generic recruitable NPC system.
• Not valid if delivery resolves locally without a future reader consuming the scar.