Maturity Notice Routing / 到期告知分流

Maturity Notice Routing is the management rite that decides how a mature 稳定化责任票据 becomes callable through a concrete 到期告知牒.

The rite exists because a ticket can be correct and still become too abstract. When sponsor, inspector, archive, fan public, lawful reader, callback reader, route claimant, or production asks to call the debt, the player must choose how the notice is served, which claimant receives the first legible surface, who carries the slip, and what scar remains for readers who were not served first.

Offer conditions

Offer this rite when all are true:

offer_state:
  trigger_kind: state_pressure
  maturity_notice_slip_present: true
  source_ticket_present: true
  source_ticket_has_maturity_trigger: true
  calling_claimant_present: true
  omitted_or_deferred_claimant_present_or_explicit_absence: true
  notice_carrier_or_explicit_absence_visible: true
  proof_of_service_possible_or_explicit_absence: true
  at_least_two_reader_surfaces_can_diverge: true
  future_route_or_reader_effect_possible: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

The rite is not offered from time passage, chapter count, crisis count, dashboard health, or generic debt. A mature ticket and service-risk row must already exist.

Inputs

assignment_required:
  slip: storyteller.card.maturity_notice_slip.v1
  source_ticket: storyteller.card.stabilization_liability_ticket.v1
  ticket_id: <stable ticket id>
  maturity_trigger: <trigger>
  calling_claimant: sponsor | inspector | archive | editor | fan_public | artist | witness | pirate | route_claimant | public_audience | lawful_reader | owed_reader | excluded_reader | equivalent
  omitted_or_deferred_claimant: <claimant or explicit_absence>
  selected_route: lawful_service | sponsor_service | archive_escrow | public_or_fan_notice | proxy_runner_service | split_notice | production_hold | suppress_or_false_service
  notice_carrier: lawful_notice | sponsor_desk | archive_clerk | fan_public_receipt | pirate_relay | proxy_runner | production_hold | route_asset | explicit_absence | equivalent
  proof_of_service: signed_slip | archive_stamp | sponsor_countercopy | public_receipt | fan_queue_receipt | pirate_timestamp | lawful_annex | edit_checksum | oral_witness | explicit_absence | equivalent
  handler_or_absence: producer | shen_luo | yu_lan | han_yanshuang | baiya | archive_clerk | public_witness | fan_delegate | proxy_runner | explicit_absence | equivalent
  reader_to_protect: <reader or route surface>
  reader_left_unserved_or_deferred: <reader or explicit_absence>

Optional supports:

support_optional:
  service_cost: money | favor_debt | handler_time | sponsor_concession | inspection_heat | public_exposure | fan_refund_reserve | route_delay | production_lane | none
  service_cover: lawful_annex | public_oath | fan_queue_receipt | archive_quarantine | sponsor_countercopy | pirate_timestamp | production_exception | none
  carrier_protection: staff_protection | legal_cover | public_credit | escort | anonymity | pay | none

A route is invalid if it records only served, notified, paid, audit_ok, or sponsor_acknowledged.

Branches

Branch A — Lawful service

The player serves inspector, lawful reader, owed reader, or archive-facing claimant through a lawful annex, white-glove acknowledgement, proof rehearing, or archive stamp.

branch: lawful_service
notice_state_after: lawful_served
relief_any:
  - admissibility_up
  - false_service_risk_down
  - lawful_reader_confidence_up
cost_any:
  - inspection_heat_up
  - bureau_favor_debt_up
  - sponsor_stop_loss_pressure_up
  - route_delay_up
future_effect_any:
  - lawful_only
  - accepted_with_notice_debt
  - public_addendum_required

Branch B — Sponsor service

The player lets sponsor, stop-loss desk, or naming-rights countercopy receive first service.

branch: sponsor_service
notice_state_after: sponsor_served
relief_any:
  - sponsor_stop_loss_pressure_down
  - commercial_package_pressure_down
  - immediate_management_pressure_down
cost_any:
  - contract_capture_up
  - public_notice_distrust_up
  - fan_oxygen_resentment_up
  - lawful_reader_hostility_up
future_effect_any:
  - sponsor_only
  - unwind_required_if_reused
  - lawful_or_public_reader_challenge_armed

Branch C — Archive escrow

The player places the slip with archive or route-asset custody until competing claimants can be served without false cleanliness.

branch: archive_escrow
notice_state_after: escrowed
relief_any:
  - source_trace_preserved
  - false_service_risk_down
  - route_asset_capture_down
cost_any:
  - archive_debt_up
  - schedule_pressure_up
  - sponsor_pressure_up
future_effect_any:
  - archive_only
  - split_required
  - recovery_only_until_release

Branch D — Public or fan notice

The player makes the service surface public through fan oxygen receipt, public oath, pirate timestamp, witness receipt, or public callback answer.

branch: public_or_fan_notice
notice_state_after: public_served | fan_served
relief_any:
  - public_receipt_legitimacy_up
  - private_capture_blocked
  - fan_refund_accountability_up
cost_any:
  - witness_exposure_up
  - sponsor_stop_loss_pressure_up
  - fan_refund_trigger_armed
  - inspection_heat_up
future_effect_any:
  - public_only
  - fan_audit_required
  - lawful_bridge_required

Branch E — Proxy runner service

The player assigns a human carrier, handler, or route asset to deliver the slip and make the service proof durable.

branch: proxy_runner_service
notice_state_after: served
relief_any:
  - route_access_up
  - proof_of_service_legibility_up
  - claimant_collision_contained
cost_any:
  - proxy_protection_debt_up
  - runner_risk_up
  - payroll_leak_up
  - hostile_proxy_risk_armed
future_effect_any:
  - route_unlocked_with_human_scar
  - proxy_posture_required
  - route_asset_notice_runner_possible

Branch F — Split notice

The player admits that no single service is clean and creates separate service surfaces for incompatible readers.

branch: split_notice
notice_state_after: split_served
relief_any:
  - selected_reader_unblocked
  - service_order_dispute_contained
cost_any:
  - source_ambiguity_up
  - handler_burden_up
  - future_correction_cost_up
future_effect_any:
  - split_required
  - sponsor_only_or_lawful_only
  - public_addendum_required

Branch G — Production hold

Production carries the notice temporarily because serving it would make a worse faction capture immediate.

branch: production_hold
notice_state_after: production_hold
relief_any:
  - faction_capture_delayed
  - immediate_source_use_kept
cost_any:
  - handler_fatigue_up
  - production_lane_scar_up
  - black_screen_pressure_up
  - unserved_notice_risk_up
future_effect_any:
  - future_source_use_costlier
  - production_triage_required

Branch H — Suppress or false-service default

The player hides the slip, serves the wrong claimant as if service were universal, erases the omitted claimant, coerces the carrier, or lets a desk file first without proof.

branch: suppress_or_false_service
notice_state_after: suppressed | unserved | false_served | recovery_only
emitted_or_armed_event: storyteller.event.unserved_maturity_notice.v1
relief_any:
  - immediate_assignment_burden_down
  - sponsor_or_management_pressure_may_drop
cost_any:
  - claimant_hostility_up
  - public_notice_distrust_up
  - false_service_risk_up
  - route_blocked
future_effect_any:
  - recovery_only
  - hostile_claimant_branch_armed
  - stabilization_debt_recall_continues

Resolution contract

Every branch must write a before/after row:

notice_before:
  slip_id: <slip>
  source_ticket_id: <ticket>
  notice_state: drafted | disputed | escrowed | unserved | explicit_absence
  calling_claimant: <claimant>
  omitted_or_deferred_claimant: <claimant or explicit_absence>
  notice_carrier: <carrier or explicit_absence>
  future_route_effect: <effect>
notice_after:
  notice_state_after: served | split_served | escrowed | public_served | fan_served | lawful_served | sponsor_served | production_hold | suppressed | unserved | false_served | recovery_only
  proof_of_service: <surface or explicit_absence>
  carrier_after: <carrier or explicit_absence>
  reader_to_protect: <reader>
  reader_left_unserved_or_deferred: <reader or explicit_absence>
  future_route_effect_after: <effect>
counter_deltas:
  relief: [<at least one>]
  cost: [<at least one>]
  future: [<at least one>]

The rite fails if all readers accept one notice as clean, if carrier state is not recorded, if omitted claimant is hidden, or if successful service carries no cost.

Runtime binding

The runtime rite is a one-shot, exact-slot review. It requires all seven assigned cards in hand, rejects substituted cards and missing choices, and exposes eight stable option IDs. Each option carries five parseable counter effects and five matching counterDeltas. Only option 0 recruits 苏牒; option 7 alone arms the unserved-notice default.

Non-goals

• Not a fixed servicing phase.
• Not a general notification rite.
• Not a replacement for 稳定化责任交接. The handoff assigns carrier; this rite proves how the mature call is served.
• Not a duplicate of claimant briefing order; this rite is about enforceable service and proof after ticket maturity.
• Not a duplicate of stale dispatch recall; this rite is about a liability notice, not a stale instruction.
• Not valid without source ticket, claimant split, carrier/proof surface, branch cost, and future route mutation.