Caption Proof Carrier Handoff / 字幕证明承载交接线

Caption Proof Carrier Handoff is the pressure storyline for the moment after a caption row has already become proof and a later desk tries to move that proof onto a new carrier.

The existing mesh can already ask whether the caption is a witness, whether an access reader relied on it, whether it arrived late, and whether a translated waiver is too broad. This line tests the next seam: who carries the caption proof when it leaves its source surface, and what reader loses scope if that carrier is treated as clean for everyone?

State-triggered entry

Open this storyline only when all conditions are true:

entry_state:
  trigger_kind: state_pressure
  source_caption_proof_row_present: true
  handoff_surface_visible: true
  carrier_or_explicit_absence_visible: true
  reader_scope_visible: true
  proof_bridge_or_explicit_absence_visible: true
  attempted_future_use_visible: true
  future_reader_consumes_carrier_state: true
  player_can_assign_public_lawful_archive_sponsor_operator_split_quarantine_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_caption_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

The storyline must not open from a raw number of captions, a generic proof audit, a schedule beat, dashboard state, lens health, or the fact that a caption page exists. A later reader must be about to consume the handoff.

Why this is a missing surface

Caption systems currently create strong local truth:

Those systems still leave a delivery gap. A caption proof row can be handed to a public bulletin, lawful annex, archive checksum, sponsor package, edit desk, route asset, or operator witness. If the handoff does not name the carrier and scope, the implementation can accidentally turn caption proof exists into all future readers can cite it.

If the carrier is unchanged but a later caption version or broadcast cut cites the old timing receipt, route the pressure into Caption Delay Afteruse Receipt. This line remains about who carries proof; that line is about whether named timing proof survives a version or cut delta.

Content pack

Storyline spine

Beat 1 — A caption proof row wants to travel

The source caption proof already exists. It may come from caption witness custody, access caption reliance, caption latency repair, translation waiver review, lawful transcript, public recap, archive checksum, or operator relay.

This beat does not ask whether the caption was correct. It asks what object or person is carrying it forward.

Beat 2 — Handoff surface appears

Create Caption Proof Carrier Docket. The row must name:

  • source caption proof row;
  • source caption state;
  • handoff surface;
  • carrier or explicit absence;
  • reader scope;
  • proof bridge or explicit absence;
  • attempted future use;
  • future reader or route.

Valid handoff surfaces include public bulletin, access notice, lawful annex, archive checksum, sponsor report, edit lane, route asset packet, fan relay, inspector memo, and operator witness record.

Beat 3 — Pressure actor tries to file the carrier as clean

At least one pressure actor wants the handoff to be enough:

  • sponsor wants the caption proof to count as reach;
  • lawful reader wants the caption proof annexed without public scope;
  • archive wants a checksum without re-opening access harm;
  • editor wants caption proof to cover a cut;
  • public desk wants a notice to satisfy all readers;
  • route claimant wants the proof packet to unlock a route asset;
  • management wants the handoff to close a metric.

Beat 4 — Review assigns the handoff

Run Caption Proof Carrier Review. The player chooses whether the carrier becomes public, lawful, archive-bound, sponsor-scoped, operator-protected, split, quarantined, or defaulted.

Every valid branch must preserve relief, cost, carrier state after, and future reader or route effect.

Beat 5 — Later consumption reads carrier state

The later route must read the handoff result:

  • public access route accepts proof but keeps sponsor dispute open;
  • lawful route narrows use and leaves public notice debt;
  • archive route preserves checksum but delays route unlock;
  • sponsor route counts reach with an access scar;
  • operator route opens because the carrier had to be protected;
  • split route requires two future readers;
  • quarantine blocks the future use;
  • default hardens false carrier state and arms recovery-only consequences.

Branch map

BranchImmediate reliefCost/scarFuture state
public_access_handoffpublic/access reader receives a named carriersponsor pressure, lawful heat, operator exposurepublic route accepted with access scar
lawful_annex_handofflegal trace preservedpublic notice debt, archive delay, access distrustlawful-only or notice-required route
archive_checksum_handoffchecksum and row order survivefuture route delay, source ambiguity, archive debtchecksum-required or blocked-until-review
sponsor_scope_handoffsponsor reach or makegood narrows pressureaccess reader scar, public distrust, route costsponsor-only or disputed-reach route
operator_protection_handoffoperator is not the hidden carrierhandler burden, witness exposure, edit debtoperator witness or protected-carrier route
split_carrier_handoffmultiple readers keep scoped proofcontradiction pending, upkeep cost, route forksplit-required route
quarantine_carrierfalse universal carrier blockedroute delay, recovery pressure, claimant hostilityblocked or recovery-only
false_caption_carrier_defaultfastest desk closes the rowhidden reader, false proof carrier, future scarhostile, contradiction-pending, or recovery-only

Character and route hooks

  • Redaction Stenographer can protect the caption operator or become the exposed carrier.
  • 楼刻字幕切换员线 can reveal which caption row was routed first, but this storyline still requires a handoff carrier and future reader.
  • 韩砚霜 can demand lawful annex scope when archive or inspector proof is cited.
  • 郁蓝 can insist that public proof and sponsor reach are different carriers.
  • Baiya can provide checksum support while increasing edit debt.

Missability and recovery

The storyline is missed when implementation:

  • stores only caption proof accepted;
  • lets public bulletin, lawful annex, sponsor report, archive checksum, edit lane, or route packet inherit one carrier without scope;
  • hides the harmed reader or omitted reader;
  • makes the caption operator the silent carrier;
  • lets proof bridge, carrier, and future reader collapse into one boolean;
  • opens from fixed time, raw caption count, dashboard state, or lens health.

Recovery is allowed only with visible scar: late public notice, lawful annex correction, archive checksum repair, sponsor unwind, operator protection, split-carrier addendum, quarantine receipt, blocked route, hostile reader, or recovery-only state.

Replay evidence expectation

storyline_id: storyteller.storyline.caption_proof_carrier_handoff.v1
session_id: lens-caption-proof-carrier-handoff-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  source_caption_proof_row_present: true
  handoff_surface_visible: true
  carrier_or_explicit_absence_visible: true
  reader_scope_visible: true
  proof_bridge_or_explicit_absence_visible: true
  attempted_future_use_visible: true
  future_reader_consumes_carrier_state: true
offered:
  - card.caption_proof_carrier_docket
  - rite.caption_proof_carrier_review
branch_result:
  selected_posture: <branch>
  carrier_state_after: <state>
  harmed_or_omitted_reader: <reader or explicit_absence>
  future_reader_or_route_effect: <effect>
  event_seen_or_armed: storyteller.event.false_caption_carrier_default.v1 | none
assertions:
  - caption_proof_does_not_create_universal_carrier
  - carrier_scope_and_future_reader_are_visible
  - false_carrier_default_is_durable