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

Public Recap Liability Split opens when an official recap, sponsor-safe summary, emergency explainer, or management recap is about to double as a liability release.

公开回顾捕获线 already asks whether a scarred result can be spoken cleanly. 派系责任承保 already asks who guarantees future harm. This storyline covers the intersection: a recap can be truthful enough for the public while still being too thin to release liability, and a liability release can be lawful enough while still poisoning public memory.

Primary playable question

When one recap sentence is asked to stabilize audience memory, release a sponsor or faction from liability, and unlock a future route, does the producer split those uses, underwrite the release, attach a claimant carveout, publish contrition, quarantine the recap, accept sponsor clean release, or let false universal release harden?

A valid answer must name:

• the recap claim;
• the source scar or explicit absence;
• the party seeking release;
• the claimant or reader still exposed;
• the collateral, carveout, or explicit absence;
• the future route or reader that will consume the release state.

State-triggered entry

Open this storyline only from live state pressure:

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

The line fails if it opens from a fixed episode step, generic post-show PR, sponsor mood, raw recap count, raw liability count, dashboard state, or lens health.

Bound content pack

• 公开回顾责任拆分机制 defines the split between public memory, release, collateral, claimant carveout, and future route consumption.
• 公开回顾责任案卷 records recap wording, release seeker, exposed claimant, source scar, collateral, and future reader.
• 回顾责任分配听证 assigns who gets released, who stays exposed, and which proof or collateral travels.
• 回顾责任释放默认 fires when a recap is treated as universal release without allocation.

Storyline spine

Beat 1 — A recap gains legal weight

A public recap, captioned explainer, sponsor-safe package, public apology, correction slot, or emergency broadcast is accepted by at least one reader. Another desk then tries to use the same wording as release, settlement proof, sponsor makegood satisfaction, route unlock, liability discharge, or ending scar closure.

The recap cannot be only flavor. It must be about to change future access.

Beat 2 — The release seeker and exposed claimant diverge

The release seeker may be sponsor, archive, inspector, management, producer license, editor, public delegate, route claimant, or character proxy.

The exposed claimant may be fan oxygen queue, access-caption class, harmed artist, witness carrier, archive claimant, sponsor counterparty, public audience, lawful body, route asset, or explicit absence.

Both sides must be visible. If there is no claimant, the docket records explicit absence rather than silently making release universal.

Beat 3 — Liability is allocated

Run 回顾责任分配听证 before the future route consumes the recap as clean release.

The hearing requires recap claim, source scar, release seeker, exposed claimant, liability surface, proof anchor, collateral or carveout, handler, and selected allocation posture.

Beat 4 — Public truth and release truth split

The branch result must distinguish public memory from liability state. A recap can be publicly usable but not release-ready; release can be lawful-only; sponsor release can be paid but public repair remains open; a claimant carveout can keep a route alive while leaving a future hearing armed.

Beat 5 — Default creates false universal release

If allocation is skipped, 回顾责任释放默认 records the false release, the omitted claimant, and the future route mutation. The default cannot be only reputation loss.

Branch map

Branch	Relief	Cost	Future route effect
Split public and release	public recap remains usable	handler burden, contradiction pressure	future route reads public proof and release proof separately
Underwrite release	release seeker gets limited discharge	collateral, inspection heat, sponsor or public debt	route accepts release only while cover remains callable
Claimant carveout	exposed claimant stays answerable	release is narrower; schedule or legal pressure rises	claimant route, appeal, or refund path remains open
Public contrition allocation	public trust or harmed party repair improves	sponsor stop-loss, management, or license pressure rises	public repair route opens; clean release blocked
Quarantine release use	false discharge is blocked	route delay and makegood pressure rise	recap cannot unlock route until proof or collateral catches up
Sponsor clean release	sponsor pressure falls quickly	public distrust, claimant hostility, contract capture	sponsor-only release; public/lawful route costlier
False universal default	immediate burden may fall	omitted claimant, false discharge, ending scar	route blocked, hostile, recovery-only, or appeal-bound

Counter contract

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

counter_surfaces:
  relief:
    - public_recap_legibility
    - sponsor_stop_loss_pressure
    - route_unlock_pressure
    - liability_discharge_clarity
    - claimant_answerability
  cost:
    - handler_burden
    - contradiction_pressure
    - inspection_heat
    - management_pressure
    - contract_capture
    - public_receipt_distrust
    - collateral_call_risk
  future:
    - split_release_required
    - callable_cover_required
    - claimant_carveout_open
    - public_repair_route_open
    - recap_release_quarantined
    - sponsor_only_release
    - recovery_only

Character and faction hooks

• Shen Luo can broker sponsor clean release or limited release, but contract capture and future public distrust rise.
• 韩砚霜 can require lawful-only release and audit collateral, but bureau debt and inspection heat rise.
• 郁蓝 can force public contrition or claimant carveout when a recap erases public harm.
• Baiya can checksum split public proof from release proof, but edit debt and source ambiguity rise.
• 赞助补偿库存线 can feed replacement-inventory pressure into sponsor clean release.
• 无障碍字幕信赖线 can become the exposed claimant when access users relied on a clean recap.

Missability and recovery

This storyline is missed when implementation:

• treats a recap as universal liability release;
• records public memory but not release seeker;
• records release seeker but not exposed claimant or explicit absence;
• lets sponsor release satisfy public repair without cost;
• lets lawful release satisfy public memory without split reader state;
• unlocks a future route without reading collateral, carveout, or quarantine state;
• triggers from fixed turn, fixed day/week, raw recap count, raw liability count, dashboard state, or lens health.

Recovery is allowed only with visible scar: late claimant carveout, public addendum, lawful annex, sponsor unwind, collateral call, split-reader table, route quarantine, correction slot, ending scar, or recovery-only release.

Replay evidence expectation

storyline_id: storyteller.storyline.public_recap_liability_split.v1
session_id: lens-public-recap-liability-split-v1-<timestamp>
seed: <deterministic-seed>
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
  future_reader_or_route_consumes_release_state: true
  no_fixed_turn_trigger: true
offered:
  card: storyteller.card.public_recap_liability_docket.v1
  rite: storyteller.rite.recap_liability_allocation_hearing.v1
branch_result:
  selected_allocation: split_public_and_release | underwrite_release | claimant_carveout | public_contrition_allocation | quarantine_release_use | sponsor_clean_release | false_universal_default
  public_memory_state_after: <state>
  liability_release_state_after: <state>
  exposed_claimant_state_after: <state>
  future_route_effect: <effect>
  counter_deltas:
    relief: []
    cost: []
    future: []
default_branch:
  event_seen_or_armed: storyteller.event.recap_liability_release_default.v1
  false_release_author: <actor>
  omitted_claimant_or_reader: <actor or explicit_absence>
  recovery_scar: <scar>
assertions:
  - entry_is_state_triggered
  - recap_release_and_source_scar_are_visible
  - release_seeker_and_exposed_claimant_are_visible
  - collateral_or_carveout_is_visible_or_explicit_absence
  - public_memory_and_liability_release_can_diverge
  - default_false_universal_release_is_durable
  - no_fixed_turn_day_week_raw_count_dashboard_or_lens_health_trigger

Non-goals

• Not another generic recap scene.
• Not an abstract legal settlement.
• Not a sponsor copy clearance step before recap exists.
• Not a replacement for public recap capture or liability underwriting.
• Not valid unless release state changes future playable routes, readers, claims, or recovery cost.