Stabilization Liability Ticket / 稳定化责任票据

Stabilization Liability Ticket is the durable card created when a broadcast, slot, callback, proof, public receipt, lawful annex, route asset, or staged reality remains usable only because somebody else is carrying the cost.

The card is the handoff object between source success and later liability play. It now accepts not only audience/drift stabilization, but also results from 播出合约回读线 and 回叫消费证明线.

It is not a money counter, generic debt flag, or global reputation track.

When this card appears

Create or update this card when all are true:

1. a source branch produced immediate relief, scoped acceptance, callback-bearing acceptance, public legibility, lawful use, route unlock, sponsor release, proof preservation, or recovery-only survival;
2. the source named a concrete object: slot row, readback docket, callback docket, relief row, proof object, public version, receipt, room, route asset, proxy row, fan oxygen pool, legal seal, or schedule lane;
3. at least one claimant was harmed, omitted, excluded, deferred, owed, or explicitly absent;
4. a carrier exists or its absence is explicitly recorded;
5. a maturity trigger can later call or challenge the cost;
6. the future route or reader effect remains visible.

Entry is state-driven. This card must never appear because a fixed numbered trigger, raw count, dashboard state, or lens-health state was reached.

Required ticket row

ticket_id: <stable id>
source:
  source_surface: broadcast_contract_readback | callback_consumption_proof | audience_stability_floor | broadcast_reality_drift_audit | public_receipt | sponsor_patch | edit_checksum | route_asset_custody | equivalent
  source_row_id: <row id or explicit_absence>
  source_session_id: <session id if inherited>
  source_seed: <seed if inherited>
  source_state_after: <source result state>
stabilized_or_scoped_object:
  object_id: <slot, proof object, receipt, room, route asset, callback relief row, public version, proxy row, fan oxygen pool, legal seal, or schedule lane>
  object_family: slot_scope | callback_relief | public_version | proof_object | public_receipt | facility_room | route_asset | proxy_row | fan_oxygen_pool | legal_seal | schedule_lane
  object_state_after: accepted_with_scope | accepted_with_callback | callback_required | public_only | lawful_only | sponsor_only | split_required | contradiction_pending | costlier | blocked | hostile | recovery_only | equivalent
relief_claimed:
  - <immediate relief gained>
liability_origin: contract_readback | callback_relief | sponsor_patch | editor_patch | inspector_seal | public_receipt | fan_bridge | pirate_bridge | release_stamp | facility_route | production_carry | split_copy | hidden_breach
beneficiary: producer | sponsor | inspector | archive | editor | fan_public | artist | witness | pirate | route_claimant | lawful_reader | public_reader | split
harmed_or_owed_claimant: sponsor | inspector | archive | editor | fan_public | artist | witness | pirate | route_claimant | public_audience | lawful_reader | excluded_reader | owed_reader | none
carrier: sponsor_escrow | inspector_surety | edit_checksum | public_bond | fan_refund | route_asset | proxy | handler_time | production_lane | facility_room | callback_carrier | proof_bridge | none
handoff_state: unassigned | escrowed | underwritten | routed_to_recourse | proxy_carried | production_carried | public_bonded | disputed | matured | recalled | recovery_only
maturity_trigger: contradiction | audit | sponsor_stop_loss | fan_refund | witness_leak | checksum_challenge | room_collision | release_challenge | callback_call | reader_challenge | proof_rehearing | blackout | manual_review
scar_after_source: <durable scar>
future_route_effect: unlocked_with_debt | costlier | public_only | lawful_only | sponsor_only | split_required | captured | hostile | blocked | recovery_only | recall_pending

A row is invalid if it only says the show was stabilized, the slot was accepted, the callback was handled, the audience calmed down, or liability increased. It must name the object, beneficiary, harmed or owed claimant, carrier, maturity trigger, handoff state, scar, and future effect.

Source-specific fields

From Broadcast Contract Readback

When created from 播出合约回读案卷, the ticket must preserve:

readback_payload:
  prior_contract_row: <row or explicit_absence>
  current_reader: <reader>
  scope_delta: <delta>
  readback_state_after: <state>
  original_excluded_or_harmed_reader: <reader or explicit_absence>
  original_proof_or_custody_anchor: <anchor or explicit_absence>
  future_route_effect: <effect>

Examples:

• an accepted public scope creates a public-bonded or production-carried ticket;
• an addendum creates lawful annex debt;
• split readers create contradiction maturity;
• proof rehearing creates inspector or archive carrier pressure;
• sponsor-only use creates contract capture and public resentment;
• recovery-only use creates no clean route unlock.

From Callback Consumption Proof

When created from 回叫消费案卷, the ticket must preserve:

callback_payload:
  source_relief_row: <row or explicit_absence>
  callback_state_after: <state>
  owed_reader_or_absence: <reader or explicit_absence>
  excluded_or_deferred_reader_or_absence: <reader or explicit_absence>
  callback_carrier_or_absence: <carrier or explicit_absence>
  proof_bridge_or_absence: <proof bridge or explicit_absence>
  future_reader_effect: <effect>

Examples:

• accepted-with-callback creates a ticket carried by handler, receipt, proxy, or production lane;
• attach-cost creates callback debt and owed-reader leverage;
• reader-scope conversion creates public-only, lawful-only, or sponsor-only effects;
• quarantine creates recovery-only or blocked future use;
• waiver creates named harm;
• false-clean laundering creates immediate recall risk.

Handoff states

• unassigned — relief exists but no downstream surface has accepted the cost.
• escrowed — sponsor, inspector, editor, public, fan, production, facility, route asset, callback carrier, or proof bridge temporarily holds the cost.
• underwritten — the cost has been transferred into 责任承保账本.
• routed_to_recourse — the cost can be called against a collectible target or release condition.
• proxy_carried — a human proxy is carrying the cost and may become recruitable, hostile, faction-bound, missing, or recovery-only.
• production_carried — production absorbs the cost as lane scar, handler fatigue, unstaffed crisis risk, route delay, or blackout pressure.
• public_bonded — public, fan, witness, pirate, or receipt layer accepts the cost and can later demand refund, correction, exposure, or answer.
• disputed — two claimants disagree over carrier, scope, callback debt, or future use.
• matured — the maturity trigger fired and a downstream rite or event must resolve the ticket.
• recalled — 稳定化债务召回 has been emitted or armed.
• recovery_only — repair remains possible, but clean use is blocked.

Play hooks

• A scoped readback result can create this ticket before the old contract row is cited by a new route.
• A callback-bearing relief result can create this ticket before relief is treated as closure.
• A successful public, drift, edit, audience, release, or facility branch can create this ticket instead of silently adding a counter.
• A ticket may route to underwriting when a guarantor and collateral exist.
• A ticket may route to recourse when a claimant can call the debt against an asset, slot, proof object, room, callback carrier, or proxy.
• A ticket may route to proxy posture when a person carries the version as signer, handler, witness, relay host, edit operator, manager bridge, or room key.
• A ticket may stay with production only if lane scar, handler fatigue, route delay, unstaffed risk, blackout pressure, or recovery-only state is recorded.

Miss and default

The card is missable when the player treats scoped readback, callback-bearing relief, or stabilization as a clean victory and assigns no carrier.

Miss outcomes include:

• stabilization_debt_recalled;
• readback_scope_challenged;
• callback_call_reopened;
• clean_patch_challenged;
• public_bond_refund_called;
• edit_checksum_reopened;
• proxy_carrier_break;
• production_lane_overdrawn;
• recourse_target_created;
• recovery_only_stabilization.

Miss is not passage-of-time punishment. It is triggered by a concrete contradiction, callback call, reader challenge, audit, breach, release dispute, proxy break, room collision, checksum challenge, refund demand, or explicit refusal to assign liability.

Evidence expectation

Any replay using this card should expose before/after ticket state:

ticket_evidence:
  ticket_id: <stable id>
  source_surface: <surface>
  source_row_id: <row>
  source_state_after: <state>
  object_id: <object>
  beneficiary: <beneficiary>
  harmed_or_owed_claimant: <claimant or explicit_absence>
  carrier_before: <carrier or none>
  carrier_after: <carrier or explicit_absence>
  maturity_trigger: <trigger>
  handoff_state_before: <state>
  handoff_state_after: <state>
  scar_after_source: <scar>
  future_route_effect_before: <effect>
  future_route_effect_after: <effect>
  session_id: <session>
  seed: <seed>