Public Recap Ledger / 公开回顾账本

Public Recap Ledger is a route-bearing card for the official recap, 上期提要, emergency explainer, or sponsor-safe continuity strip that summarizes a prior crisis result for the public.

The card exists because Storyteller’s core rule is not only that broadcast changes reality. The wording that recaps a scar can become the reality later readers inherit. A protected disclosure, bottlenecked exit, scoped notice, private promise, or costly management win must not become a clean public truth just because the recap said it was clean.

This is not a copywriting flavor card. The row is valid only when the recap wording can change future route access, public proof, broadcast-reality drift, sponsor capture, correction pressure, character availability, or ending scars.

Card role

The ledger records the difference between what actually happened and what the public recap is about to make legible.

A valid row must show:

public_recap_row:
  recap_id: <stable id>
  source_resolution_id: <prior branch route asset hearing or event id>
  source_surface: confidant_promise | live_floor_egress | capacity_notice | emergency_power | management_compression | continuity_afteruse | broadcast_reality_drift | route_asset | equivalent
  factual_scar: private_scope | deferred_flow | unserved_notice | power_priority_loss | sacrificed_metric | contempt_risk | drift_contradiction | route_asset_split | equivalent
  recap_claim: clean_success | qualified_success | partial_failure | public_apology | sponsor_safe_story | lawful_notice | silent_omission | equivalent
  omitted_or_softened_scar: <scar or explicit_absence>
  recap_narrator: producer | sponsor | management | archive | fan_delegate | editor | inspector | character | broadcast_reality | equivalent
  beneficiary_of_clean_wording: sponsor | management | producer_license | archive | public_stability | route_claimant | character | equivalent | explicit_absence
  harmed_reader: public | lawful | sponsor | archive | access_caption_class | fan_oxygen_queue | confidant_character | route_asset | future_audience | equivalent
  proof_anchor_or_absence: public_receipt | caption_log | oxygen_queue_log | power_ledger | promise_row | metric_report | edit_checksum | lawful_seal | explicit_absence
  future_reader_or_route: <route reader slot ending scar or explicit_absence>
  recap_state: pending | qualified | split | corrected | sponsor_clean | public_contrition | quarantined | captured | breached | recovery_only

The row fails as content if it only says public opinion improved, audience understands, recap aired, PR handled, or sponsor approved.

Source surfaces

A row may be created from any prior resolution whose scar could be erased by public wording:

• 私约违背线 when private trust is recapped as public consent;
• 直播现场通行瓶颈线 when a protected/deferred flow is recapped as universal safe exit;
• 容量告知送达队列线 when partial service is recapped as everyone having been told;
• 应急供电优先线 when one powered branch is recapped as general resilience;
• 经营压缩台 when a sacrificed metric is recapped as clean yield;
• 连续性后用藐视线 when a scoped continuity copy is recapped as reusable canon;
• 播出实在漂移审计 when contradiction is recapped as stability.

Branch states

recap_states:
  qualified:
    meaning: recap states relief and scar together; future readers can proceed with scope
  split:
    meaning: public, lawful, sponsor, and route readers receive separate wording and cannot treat one as universal
  corrected:
    meaning: a prior clean claim is amended with visible cost
  sponsor_clean:
    meaning: sponsor accepts the public story while other readers inherit distrust or capture
  public_contrition:
    meaning: recap admits harm and opens public repair at sponsor or management cost
  quarantined:
    meaning: recap is withheld or narrowed until proof or notice catches up
  captured:
    meaning: the fastest narrator turns the scar into a false clean public memory
  breached:
    meaning: private, lawful, access, oxygen, or route boundary is violated by the recap
  recovery_only:
    meaning: future use requires correction slot, apology, re-service, public addendum, or ending scar

Counter contract

Every resolved row must mutate at least one relief, one cost, and one future reader or route effect.

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.

Non-goals

• Not a generic PR beat.
• Not a social-media mood counter.
• Not a governance or dashboard page.
• Not a way to overwrite the source resolution.
• Not valid unless the recap wording can change future playable state.
• Not valid if a clean recap becomes universal acceptance across public, lawful, sponsor, archive, character, route, and broadcast-reality readers.