Maturity Notice Service Order / 到期告知送达顺序线

Maturity Notice Service Order is the system-facing storyline for the moment a Stabilization Liability Ticket matures and more than one reader can claim the first enforceable notice.

Stabilization Liability Handoff already asks who carries a cost after scoped relief. Su Die Maturity Notice Runner proves the human courier route. This storyline owns the broader service-order problem: when the ticket is called, the game must prove who was served, who was omitted, who carried the proof, and which future reader inherits the scar.

Gap diagnosis

The current mesh can create liability tickets, assign proxy or production carriers, recall hidden debt, brief claimants, and route stale dispatches. The remaining seam is the first legible service surface after maturity.

Without this storyline, implementation can jump from ticket matured to debt called, or let sponsor, lawful, archive, public, fan, route-asset, and management readers all treat one notice as clean universal service. That is too clean. A mature ticket must pass through a visible Maturity Notice Slip before it becomes future authority.

Primary playable question

When a stabilization liability ticket matures, does the producer serve lawful first, serve sponsor first, escrow the slip with archive, publish fan or public notice, route it through a proxy runner, split service by reader, hold it in production, or suppress it into false service?

Every branch must name:

• source ticket and source scar;
• maturity trigger;
• calling claimant;
• omitted or deferred claimant, or explicit absence;
• notice carrier, or explicit absence;
• proof of service, or explicit absence;
• selected service route;
• notice state after;
• future route or reader effect.

State-triggered entry

Open this storyline only when a mature liability ticket is being called by live state pressure:

entry_state_required:
  trigger_kind: state_pressure
  source_ticket_present: true
  source_ticket_has_maturity_trigger: true
  source_ticket_handoff_state_present: true
  maturity_notice_slip_present_or_can_be_created: 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
  player_can_route_notice_or_record_default: 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

Valid maturity sources include sponsor stop-loss call, white-glove audit, archive admissibility review, fan refund, public receipt challenge, route asset release dispute, callback call, proof rehearing, checksum challenge, room collision, witness leak, blackout review, or manual review of a prior ticket.

Bound content pack

• Maturity Notice Routing defines service-order states, carrier rules, reader divergence, default conditions, and recovery.
• Maturity Notice Slip records the source ticket, maturity trigger, calling claimant, omitted claimant, notice carrier, proof, reader effects, and notice state after.
• Maturity Notice Routing resolves lawful, sponsor, archive, public, fan, proxy, split, production-hold, and false-service routes.
• Unserved Maturity Notice fires or arms when the slip is hidden, falsely served, carried by a captured surface, or reused as clean proof.
• Su Die Maturity Notice Runner remains the character-bound courier route.

Storyline spine

Beat 1 - Ticket matures into a service conflict

A ticket enters matured, recall_pending, disputed, public_bonded, proxy_carried, production_carried, underwritten, routed_to_recourse, or recovery_only. The source relief remains true, but it is no longer enough. A claimant, reader, refund table, archive desk, lawful table, sponsor desk, fan public, route asset, or production reader now asks to call the cost.

Beat 2 - Slip separates claimant state

Create or refresh Maturity Notice Slip.

The slip must keep these locks separate:

required_locks:
  source_ticket_lock:
    ticket_id: <stable ticket id>
    source_surface: <source surface>
    handoff_state_before: <state>
    scar_after_source: <scar>
    future_route_effect_before: <effect>
  maturity_lock:
    maturity_trigger: <trigger>
    calling_claimant: <claimant>
    omitted_or_deferred_claimant: <claimant or explicit_absence>
    first_service_requested_by: <claimant desk handler public surface or explicit_absence>
  carrier_lock:
    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
    carrier_state: unseen | visible | protected | recruited | retained | suppressed | captured | hostile | missed | false_served | unavailable | explicit_absence
  future_lock:
    notice_state_after: <state>
    future_route_effect_after: <effect>

The row fails if it stores only ticket_matured, notice_sent, claimant_notified, sponsor_called, or audit_started.

Beat 3 - Service order resolves before reuse

Run Maturity Notice Routing before a future reader can cite the ticket as clean service.

Valid service routes:

• lawful_service
• sponsor_service
• archive_escrow
• public_or_fan_notice
• proxy_runner_service
• split_notice
• production_hold
• suppress_or_false_service

Beat 4 - Future readers inherit the notice scar

At least one later route, refund, lawful annex, archive release, sponsor package, public statement, fan audit, route asset, or broadcast-reality reader must consume notice_state_after and future_route_effect_after.

If future play cites the ticket while service proof, carrier state, calling claimant, omitted claimant, or reader split is hidden, Unserved Maturity Notice must fire or remain armed.

Branch matrix

Branch	Immediate relief	Cost/scar	Future state
Lawful service	admissibility and false-service control improve	inspection heat, bureau debt, sponsor pressure, route delay	lawful-only or accepted with notice debt
Sponsor service	stop-loss or package pressure drops	contract capture, public distrust, fan resentment, lawful challenge	sponsor-only or unwind required
Archive escrow	source trace survives and false service is blocked	archive debt, schedule pressure, sponsor pressure	archive-only, split-required, or recovery-only until release
Public or fan notice	private capture is blocked	witness exposure, fan refund trigger, sponsor pressure, inspection heat	public-only, fan audit required, or lawful bridge required
Proxy runner service	service proof becomes durable through a carrier	proxy protection debt, runner risk, payroll leak	route unlocked with human scar or proxy posture required
Split notice	incompatible readers receive scoped service	source ambiguity, handler burden, future correction cost	split-required, public addendum, lawful-only, or sponsor-only
Production hold	immediate capture is delayed	handler fatigue, production lane scar, black-screen pressure	source use costlier or production triage required
Suppress or false service	short pressure may drop	claimant hostility, public distrust, route block, recall continues	hostile, blocked, recovery-only, or unserved default

No constructive branch may serve every sponsor, lawful, archive, public, fan, management, route asset, callback, and broadcast-reality reader at once.

Counter contract

Every resolved branch must mutate at least one relief surface, one cost surface, and one future route or reader surface.

Accepted relief surfaces include admissibility_up, false_service_risk_down, sponsor_stop_loss_pressure_down, source_trace_preserved, public_receipt_legitimacy_up, private_capture_blocked, proof_of_service_legibility_up, and selected_reader_unblocked.

Accepted cost surfaces include inspection_heat_up, bureau_favor_debt_up, contract_capture_up, public_notice_distrust_up, fan_oxygen_resentment_up, archive_debt_up, proxy_protection_debt_up, handler_burden_up, production_lane_scar_up, and claimant_hostility_up.

Accepted future states include lawful_only, sponsor_only, public_only, fan_audit_required, split_required, proxy_posture_required, production_triage_required, hostile, blocked, and recovery_only.

Missability and recovery

This storyline is missed when a mature ticket is called, reused, recalled, packaged, audited, refunded, or routed without a slip or explicit absence.

Missed states include:

• unserved_maturity_notice;
• false_service_claim;
• wrong_first_claimant;
• carrier_captured;
• omitted_claimant_hidden;
• proof_of_service_absent;
• suppress_notice;
• clean_reuse_without_service;
• recovery_only_notice_route.

Recovery must keep the scar visible: late lawful annex, corrective public receipt, split service, carrier rescue or replacement, archive escrow, fan refund with proof, sponsor-only acknowledgement, lawful-only acknowledgement, public-only acknowledgement, blocked route, or recovery-only route.

Non-goals

• Not a timer or upkeep phase.
• Not generic legal noncompliance.
• Not a duplicate of claimant briefing order; this is enforceable service after a ticket matures.
• Not a duplicate of stale dispatch recall; this is liability notice proof, not an old instruction.
• Not a clean route to erase stabilization liability.