Public Recap Capture / 公开回顾捕获线

Public Recap Capture is a pressure storyline for the moment a scarred crisis result must be summarized on air.

The current green surface is dense with durable scars: private promises can be scoped, bodies can be delayed at live-floor bottlenecks, notice can be partial, power can be prioritized, metrics can be compressed, and continuity copies can be held in contempt. The next weak seam is not another right, carrier, or desk. It is the public sentence that says what happened.

The dramatic question is:

When the official recap speaks, does it preserve the scar, split the readers, correct the public memory, or let the clean version become broadcast reality?

Bound content pack

This storyline binds:

• 公开回顾捕获机制;
• 公开回顾账本;
• 公开回顾定性;
• 回顾捕获默认.

Why this is the strongest next gap

Recent content can prove that a resolution was not clean. But Storyteller also needs to prove that the public-facing recap cannot erase that uncleanliness.

Without this storyline:

• 私约违背线 can protect private scope, then a recap can accidentally call the material public consent.
• 直播现场通行瓶颈线 can protect one flow and defer another, then a recap can say everyone exited safely.
• 容量告知送达队列线 can track partial service, then a recap can say everyone was told.
• 应急供电优先线 can privilege one powered branch, then a recap can call the whole dome resilient.
• 经营压缩台 can show a sacrificed metric, then a recap can turn it into clean yield.
• 连续性后用藐视线 can limit a continuity copy, then a recap can make it canon for every reader.
• 播出实在漂移审计 can identify contradiction, then a recap can file it as stability.

This line makes the recap itself playable: a card, a rite, a default, and future route readers.

State-triggered entry

Open this storyline only when all of the following are visible:

entry_state_required:
  trigger_kind: state_pressure
  source_resolution_present: true
  source_resolution_has_relief: true
  source_resolution_has_scar: true
  public_recap_claim_present: true
  harmed_reader_or_explicit_absence_visible: true
  beneficiary_of_clean_wording_visible_or_explicit_absence: true
  proof_anchor_visible_or_explicit_absence: true
  future_reader_or_route_consumes_recap_state: true
  player_can_qualify_split_correct_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_dashboard_or_lens_health_trigger: true

The line fails if it opens from a fixed turn, fixed day/week, chapter quota, raw recap count, dashboard state, lens health, or generic post-episode PR phase.

Storyline spine

Beat 1 — A scarred result needs public words

A prior branch has both relief and scar. Something got saved, but not cleanly: a promise stayed private, a door stayed one-way, a queue remained unserved, a metric was sacrificed, a continuity copy remained scoped, or a contradiction survived.

The producer receives 公开回顾账本.

Beat 2 — The recap has a beneficiary and a harmed reader

The proposed recap wording benefits someone: sponsor, management, producer license, archive, public stability, route claimant, character, or broadcast reality.

The same wording harms or excludes someone else: public, lawful desk, sponsor, archive, access-caption class, fan oxygen queue, confidant character, route asset, or future audience.

Both sides must be named. A vague PR tradeoff is not enough.

Beat 3 — The proof anchor is tested

The recap can cite a public receipt, caption log, oxygen queue log, power ledger, promise row, metric report, edit checksum, lawful seal, or explicit absence.

If the proof anchor is absent, the recap may still air, but the absence must become part of the route state.

Beat 4 — The player qualifies the public memory

Run 公开回顾定性.

The player may qualify the scar, split reader wording, publish a correction, make public contrition, quarantine the recap, accept sponsor-clean wording, or let silent clean default fire.

Beat 5 — Broadcast reality remembers the wording

Future readers consume the recap state:

• Broadcast Reality treats aired wording as a reality pressure.
• Route Assets and Custody reads whether route assets are clean, split, or recovery-only.
• 无障碍字幕集体线 reads whether access harm was erased.
• 无障碍字幕信赖线 reads whether people relied on the recap.
• 播出容量责任级联线 reads false closure.
• 结局伤痕账本线 reads unresolved false public memory.

Branch map

Branch	Immediate relief	Cost/scar	Future state
Qualify scar	recap remains usable and truthful enough	sponsor, management, or audience confidence falls	scoped public proof; future reader accepts with scar
Split reader recap	incompatible public/lawful/sponsor/route readers can proceed separately	contradiction pressure, edit debt, handler burden	split-reader route handling required
Publish correction	false clean claim is amended	public distrust, correction pressure, producer-license heat	correction slot or addendum required before reuse
Public contrition recap	harmed public or character gets visible repair	sponsor stop-loss, management pressure, archive debt	public repair route opens; sponsor route narrows
Quarantine recap	false public memory is blocked	black-screen, schedule, fan, or route pressure rises	recap cannot be future proof until service/proof catches up
Sponsor clean recap	immediate sponsor and slot stability improve	public distrust, access harm, character breach, or drift rises	sponsor-only memory; public/lawful route costlier
Silent clean default	fastest narrator reduces immediate burden	hidden scar hardens	recap capture, correction required, recovery-only, or ending scar

Counter contract

Every non-default branch must mutate:

counter_deltas_required:
  relief: at_least_one
  cost: at_least_one
  future_reader_or_route_effect: at_least_one

Expected surfaces include public_receipt_legitimacy, public_receipt_distrust, broadcast_reality_drift, recap_capture, sponsor_stop_loss_pressure, management_pressure, producer_license_pressure, correction_pressure, caption_reliance, fan_oxygen_resentment, confidant_trust, route_asset_integrity, future_reader_acceptance, and ending_scar_pressure.

Missability and recovery

The storyline is missed when a future route consumes public_recapped, officially_explained, audience_informed, safe_exit, everyone_notified, resilience_confirmed, clean_yield, or canon_continuity without creating or reading a recap row.

Missed states include false_public_memory, recap_captured, private_consent_breach, access_or_oxygen_erasure, false_clean_yield, continuity_overwrite, drift_hardened, reader_hostile, route_blocked, and recovery_only.

Recovery is allowed only through visible cost: correction slot, public addendum, re-service, access-caption certificate, oxygen review, private apology and substitute proof, split-reader recap, route quarantine, or ending scar.

Replay evidence expectation

storyline_id: storyteller.storyline.public_recap_capture.v1
session_id: lens-public-recap-capture-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  source_resolution_id: <id>
  source_resolution_has_relief: true
  source_resolution_has_scar: true
  public_recap_claim_present: true
  harmed_reader_or_explicit_absence_visible: true
  future_reader_or_route_consumes_recap_state: true
  no_fixed_turn_trigger: true
offered:
  card: storyteller.card.public_recap_ledger.v1
  rite: storyteller.rite.public_recap_qualification.v1
branch_result:
  selected_posture: qualify_scar | split_reader_recap | publish_correction | public_contrition_recap | quarantine_recap | sponsor_clean_recap | silent_clean_default
  recap_state_after: qualified | split | corrected | public_contrition | quarantined | sponsor_clean | captured | breached | recovery_only
  harmed_reader_state_after: <state>
  beneficiary_state_after: <state>
  future_reader_effect: <effect>
  counter_deltas:
    relief: []
    cost: []
    future: []
default_branch:
  event_seen_or_armed: storyteller.event.recap_capture_default.v1 | explicit_absence
  default_narrator: <narrator or explicit_absence>
assertions:
  - entry_is_state_triggered
  - source_relief_and_scar_are_visible
  - recap_claim_and_omitted_scar_are_visible
  - harmed_reader_and_beneficiary_are_visible
  - proof_anchor_visible_or_explicit_absence
  - branches_diverge_by_reader_and_future_effect
  - default_capture_is_durable
  - no_universal_clean_recap
  - no_fixed_turn_day_week_raw_count_dashboard_or_lens_health_trigger

Non-goals

• Not a generic PR scene.
• Not a governance page.
• Not raw content scaling.
• Not a replacement for any source storyline.
• Not valid unless public wording changes future playable state.
• Not valid if the recap makes every reader accept the same clean history.