Public Recap Liability Split / 公开回顾责任拆分机制

Public Recap Liability Split prevents one accepted recap line from becoming clean public memory, clean liability discharge, and clean route proof at the same time.

The mechanism is state-triggered. It opens only when a recap claim is about to be consumed as release, settlement proof, sponsor makegood satisfaction, liability discharge, ending scar closure, or route unlock.

Mechanic promise

A passing implementation proves:

• recap claim and source scar are visible;
• release seeker and exposed claimant are visible or explicitly absent;
• public memory state and liability release state are separate;
• collateral, carveout, proof, or explicit absence is recorded;
• future route consumption reads the release state;
• default false release mutates future play;
• no fixed turn, day/week, raw count, dashboard, or lens-health trigger exists.

Entry model

entry_state:
  trigger_kind: state_pressure
  recap_claim_present: true
  recap_claim_would_be_used_as_release_or_route_proof: true
  source_scar_or_explicit_absence_visible: true
  release_seeker_visible: true
  exposed_claimant_or_reader_visible_or_explicit_absence: true
  liability_surface_visible_or_explicit_absence: true
  collateral_or_carveout_visible_or_explicit_absence: true
  future_reader_or_route_consumes_release_state: true
  player_can_split_underwrite_carveout_contrit_quarantine_clean_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_recap_count_trigger: true
  no_raw_liability_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

State row

公开回顾责任案卷 records:

recap_liability_row:
  recap_claim_id: <stable id>
  recap_surface: public_recap | sponsor_safe_package | correction_slot | emergency_explainer | public_contrition | management_recap | equivalent
  recap_claim_text_or_code: <claim code>
  source_scar_or_absence: <scar or explicit_absence>
  proposed_release_use: sponsor_release | liability_discharge | route_unlock | makegood_satisfaction | settlement_proof | ending_scar_closure | equivalent
  release_seeker: sponsor | archive | inspector | management | producer_license | editor | public_delegate | route_claimant | character_proxy | equivalent
  exposed_claimant_or_reader: fan_oxygen_queue | access_caption_class | harmed_artist | witness_carrier | archive_claimant | sponsor_counterparty | public_audience | lawful_body | route_asset | explicit_absence | equivalent
  liability_surface_or_absence: public_receipt | sponsor_escrow | lawful_seal | fan_oxygen | correction_slot | route_asset | proof_anchor | ending_scar | explicit_absence
  collateral_or_carveout_or_absence: <collateral carveout proof bridge or explicit_absence>
  handler_or_absence: <actor or explicit_absence>
  future_reader_or_route: <reader route ending scar or explicit_absence>

Resolution model

回顾责任分配听证 must select one allocation posture:

• split_public_and_release;
• underwrite_release;
• claimant_carveout;
• public_contrition_allocation;
• quarantine_release_use;
• sponsor_clean_release;
• false_universal_default.

Each posture must write distinct public memory state, liability release state, exposed claimant state, and future route effect.

Default model

回顾责任释放默认 fires or arms when:

• a recap is used as universal release without allocation;
• the source scar is omitted;
• the release seeker is hidden;
• exposed claimant or explicit absence is missing;
• collateral, carveout, or proof absence is hidden;
• a future route consumes the recap as clean release.

The default produces false_universal_release, omitted_claimant, sponsor_only_release, lawful_only_release, public_memory_poisoned, collateral_unfunded, appeal_required, route_blocked, ending_scar, or recovery_only.

Integration rules

• With 公开回顾捕获机制, this mechanism consumes recap state rather than rewriting it.
• With 派系责任承保机制, this mechanism consumes collateral and call-trigger state rather than replacing underwriting.
• With 赞助补偿库存机制, sponsor clean release must still name replacement inventory or explicit absence.
• With Broadcast Reality, aired release wording becomes pressure but not universal discharge unless allocation passes.
• With Route Assets and Custody, route assets may become split-required, claimant-carved, sponsor-only, quarantined, appeal-bound, or recovery-only.

Failure states

The mechanism fails if it allows:

• public recap acceptance to imply liability release;
• liability release to imply public repair;
• sponsor release to erase access, fan oxygen, artist, witness, or route-asset claimants;
• lawful-only release to become public memory;
• collateral absence to be hidden;
• future route unlock without release-state consumption;
• fixed turn, fixed day/week, raw recap count, raw liability count, dashboard, or lens-health trigger.