Maturity Notice Slip / 到期告知牒

Maturity Notice Slip is the small, assignable card created when a 稳定化责任票据 can be called by a claimant, reader, refund demand, audit, callback, release challenge, proof rehearing, or broadcast-reality contradiction.

The stabilization ticket says a cost exists. The notice slip says who can make that cost legally, publicly, commercially, or archivally real first.

It is not a generic debt reminder, calendar trigger, or countdown. It appears only from live state pressure when a ticket has a maturity trigger and at least one claimant, carrier, or omitted reader can change future play.

When this card appears

Create or update this card when all are true:

entry_state:
  trigger_kind: state_pressure
  source_ticket_present: true
  source_ticket_state: unassigned | escrowed | underwritten | routed_to_recourse | proxy_carried | production_carried | public_bonded | disputed | matured | recall_pending | recovery_only
  maturity_trigger_present: true
  calling_claimant_present: true
  omitted_or_deferred_claimant_present_or_explicit_absence: true
  carrier_or_service_absence_visible: true
  proof_of_service_surface_possible: 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

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, or manual review that reads a prior stabilization ticket.

Required row

maturity_notice_slip:
  slip_id: <stable id>
  source_ticket:
    ticket_id: <stable stabilization liability ticket id>
    source_surface: <source surface>
    source_row_id: <source row or explicit_absence>
    stabilized_or_scoped_object_id: <object>
    handoff_state_before: <state>
    carrier_before: <carrier or explicit_absence>
    scar_after_source: <scar>
    future_route_effect_before: <effect>
  maturity:
    maturity_trigger: sponsor_stop_loss | audit | fan_refund | release_challenge | callback_call | reader_challenge | proof_rehearing | checksum_challenge | room_collision | witness_leak | blackout | manual_review | equivalent
    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>
    first_service_requested_by: <claimant, desk, handler, public surface, or explicit_absence>
    service_order_risk: clean | disputed | claimant_first | sponsor_first | public_first | lawful_first | fan_first | false_service_risk | unserved
  carriage:
    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
  result:
    notice_state: drafted | served | split_served | escrowed | public_served | sponsor_served | lawful_served | fan_served | suppressed | unserved | false_served | recovery_only
    future_route_effect_after: unlocked_with_notice_debt | sponsor_only | lawful_only | public_only | fan_audit_required | split_required | costlier | hostile | blocked | recovery_only | recall_event_armed

A row is invalid if it only records ticket_matured, notice_sent, claimant_notified, sponsor_called, or audit_started. The card must name the source ticket, calling claimant, omitted or deferred claimant, carrier or absence, proof surface, service order risk, carrier state, and future route effect.

Play hooks

• A ticket routed through 稳定化责任交接线 can create this card when its maturity trigger is live.
• A proxy-carried ticket can create this card when a human carrier can be protected, recruited, suppressed, captured, or made hostile.
• A public-bonded or fan-bonded ticket can create this card when fans demand refund, correction, or proof of who was served first.
• A sponsor-only or lawful-only source can create this card when a different reader challenges the service order.
• A recovery-only ticket can still create this card if visible service would preserve the scar and prevent false clean closure.

Reader outcomes

A served notice must leave at least two readers in different states.

reader_state_examples:
  sponsor_reader: accepted_with_cost | sponsor_only | hostile | blocked | explicit_absence
  lawful_reader: lawful_only | accepted_with_notice | proof_rehearing_required | blocked | explicit_absence
  public_reader: public_only | distrustful | notice_receipt_legible | hostile | explicit_absence
  fan_oxygen_reader: refund_audit_required | fan_served | resentful | blocked | explicit_absence
  archive_reader: archive_stamp_required | escrowed | accepted_with_cost | blocked | explicit_absence
  production_reader: production_hold | handler_overdrawn | recovery_only | explicit_absence
  route_asset_reader: unlocked_with_notice_debt | split_required | captured | costlier | blocked | recovery_only

The card cannot make sponsor, lawful, archive, public, fan, management, route asset, callback, and broadcast-reality readers all accept the same ticket as clean truth.

Miss and default

The notice is missed when the mature ticket is reused or recalled without service proof, when the wrong claimant is served as if service were universal, when the carrier is hidden, when the omitted claimant is erased, or when production suppresses the slip with no future scar.

Miss outcomes include:

• unserved_maturity_notice;
• false_service_claim;
• claimant_hostility;
• fan_refund_without_proof;
• sponsor_only_service_hardens;
• lawful_reader_challenges_service;
• public_notice_distrust;
• route_asset_captured_by_notice_gap;
• recovery_only_notice_route.

Miss is never a passage-of-time punishment. It is triggered by a concrete call, audit, refund, challenge, rehearing, release dispute, or explicit refusal to serve.

Evidence expectation

notice_evidence:
  slip_id: <stable id>
  source_ticket_id: <ticket id>
  source_session_id: <session or explicit_absence>
  source_seed: <seed or explicit_absence>
  maturity_trigger: <trigger>
  calling_claimant: <claimant>
  omitted_or_deferred_claimant: <claimant or explicit_absence>
  notice_carrier_before: <carrier or explicit_absence>
  notice_carrier_after: <carrier or explicit_absence>
  proof_of_service: <surface or explicit_absence>
  notice_state_before: <state>
  notice_state_after: <state>
  future_route_effect_before: <effect>
  future_route_effect_after: <effect>
  counter_deltas:
    relief: []
    cost: []
    future: []

Runtime binding

The runtime slip is one of seven exact assignments to storyteller.rite.maturity_notice_routing.v1. The other assignments are the real inherited card.stabilization_liability_ticket, 苏牒, claimant split, carrier/proof bundle, future-reader table, and service-route sheet. Broad semantic substitutes no longer satisfy the rite.

Non-goals

• Not a fixed upkeep reminder.
• Not a new global law system.
• Not a generic mail or scheduling card.
• Not a duplicate of claimant briefing order; this card is about making a mature stabilization debt callable.
• Not a duplicate of stale dispatch recall; this card is about service proof for a liability ticket, not stopping an old local instruction.
• Not valid if service has no carrier, proof, omitted claimant, reader split, and future route consequence.