Access Caption Reliance / 无障碍字幕信赖线

Access Caption Reliance is a pressure storyline for the moment after a caption has been treated as access, delivery proof, refund basis, management reach, lawful transcript, or route unlock.

The current mesh already makes captions custody-bearing through 字幕证词羁押线. It also prices oxygen clawback, sponsor makegood, management compression, and recall priority. The missing seam is the reliance aftershock: a caption can be correct enough for one reader while still becoming false access, false reach, or false route proof for another.

This storyline binds 无障碍字幕信赖机制, 无障碍字幕信赖案卷, 无障碍字幕信赖听证, and 无障碍字幕信赖默认.

Why this is the next useful expansion

Recent content made the source/caption split testable. That closes a proof gap, but opens a management gap. Once a caption has state, several desks can spend it:

  • access public relies on it to know what happened;
  • foreign-language public relies on it to enter the route at all;
  • sponsor counts it as delivered reach;
  • management counts it as audience-access KPI;
  • fan public uses it as oxygen refund evidence;
  • archive or inspector cites it as lawful transcript;
  • route asset readers treat it as a clean unlock;
  • caption operator becomes the quiet person blamed when the row collapses.

Without this storyline, a certified access caption could silently satisfy sponsor delivery, public access, fan oxygen, archive proof, and management metric at once. This line makes that impossible.

Primary playable question

When a reader relies on a caption, does the producer:

  • refund or correct for the access reader;
  • let sponsor count the caption as delivered reach;
  • put reliance into archive/lawful escrow;
  • protect the caption operator from silent liability;
  • split reliance across language/access tracks;
  • convert the claim into sponsor makegood, recovery inventory, or recall priority;
  • refuse reliance and record the dispute;
  • or let the fastest desk file a false access metric by default?

Every answer must name the relying reader, excluded/harmed reader, constrained surface, and future route effect.

State-triggered entry

Open this storyline only when all conditions are true:

entry_state:
  trigger_kind: state_pressure
  source_caption_row_or_explicit_absence_present: true
  caption_state_changes_access_meaning_delivery_or_route_use: true
  reliance_claim_present: true
  relying_reader_visible: true
  excluded_or_harmed_reader_visible_or_explicit_absence: true
  constrained_surface_visible_or_explicit_absence: true
  future_reader_or_route_consumes_reliance_state: true
  default_if_unworked_present: true
  player_can_refund_count_escrow_protect_split_convert_refuse_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

The storyline must not open from fixed turn count, fixed day/week interval, chapter quota, raw caption count, raw viewer count, dashboard state, lens health, or generic legal/accessibility review.

Content pack

Mechanic

Card

  • 无障碍字幕信赖案卷 records the source caption state, relying reader, reliance claim, excluded reader, pressure actor, constrained surface, proof, selected response, and future effect.

Rite

  • 无障碍字幕信赖听证 assigns refund/correction, sponsor reach, archive escrow, operator protection, split reliance, makegood conversion, refusal, or default.

Event

  • 无障碍字幕信赖默认 fires or arms when caption reliance is hidden, falsely cleaned, or filed first by sponsor, management, archive, fan public, inspector, editor, route claimant, or operator absence.

Storyline spine

Beat 1 — Caption state becomes reliance surface

A caption state exists or is explicitly absent. It may be certified access, sponsor-safe, split-language, archive-escrowed, fan-hardsubbed, false-caption, hostile-caption, or recovery-only.

The key is reliance, not correctness. A correct caption can still be misused as sponsor reach. A sponsor-safe caption can still deny access. A fan translation can still expose an operator. An archive caption can still block public access.

Beat 2 — A reader claims reliance

The relying reader must be named:

  • deaf access public;
  • foreign-language public;
  • fan public;
  • sponsor;
  • management;
  • inspector;
  • archive reader;
  • artist boundary;
  • route asset reader.

The reliance claim must say what the caption did: provided access, denied access, changed consent, changed refusal, proved sponsor reach, became management reach metric, became refund basis, became correction basis, or unlocked a route.

Beat 3 — Harmed reader and constrained surface appear

The row names the excluded/harmed reader and the constrained surface:

  • fan oxygen refund;
  • public correction slot;
  • sponsor makegood frame;
  • access caption operator;
  • archive caption escrow;
  • edit checksum lane;
  • producer license;
  • route asset access;
  • explicit absence.

The story fails if the settlement is generic money or generic reputation.

Beat 4 — Hearing chooses response

Run 无障碍字幕信赖听证. The producer chooses which reader is protected and which future route inherits cost.

The hearing must preserve proof or explicit absence, handler or explicit absence, constrained surface state, relying reader state, excluded reader state, and future effect.

Beat 5 — Reliance result is consumed

A later route consumes the result:

  • public access route is protected but oxygen refund audit opens;
  • sponsor reach is accepted with disputed access scar;
  • lawful caption rehearing blocks public/sponsor clean use;
  • operator witness route opens;
  • split caption canon requires future fork;
  • makegood or recall queue inherits the claim;
  • public-only, sponsor-only, lawful-only, blocked, or recovery-only route state becomes durable.

Branch map

BranchImmediate reliefCost/scarFuture state
Refund access readeraccess/public trust improvesfan oxygen refund, correction slot, sponsor pressure, inspection heatpublic access route protected; oxygen audit
Sponsor counts reachsponsor stop-loss or management pressure narrowsfalse access metric, access distrust, operator exposuresponsor reach disputed; metric scar
Archive escrow reviewfalse caption risk drops; lawful rehearing availablearchive debt, route delay, sponsor/public pressurelawful-only or blocked until recheck
Protect operator refusaloperator not silent liability sinkhandler burden, management pressure, proof gapoperator witness route or costlier route
Split caption reliancetwo readers receive scoped reliancetranslation drift, proof upkeep, edit/archival debtsplit required or contradiction pending
Convert to makegoodimmediate dispute paused by named surfacesponsor makegood inventory, recovery inventory, fan oxygen pressuremakegood converted; recall queue armed
Refuse reliancefalse reliance blockedaccess/sponsor/public hostility, inspection heatpublic-only, lawful appeal, blocked
Default selectsfast desk files firsthidden reader, false metric, future recovery costsponsor-only, public-only, lawful-only, blocked, recovery-only

Character and faction hooks

  • Redaction Stenographer can become protected operator, exposed operator, or hostile witness if a caption row is spent as clean access.
  • 郁蓝 can argue that public/fan reliance is not sponsor delivery.
  • 韩砚霜 can demand lawful caption rehearing when archive relies on a caption.
  • Shen Luo can broker sponsor reach conversion, but the result must retain access scar and future dispute.
  • Baiya can provide edit checksum support, increasing edit debt or source ambiguity.

Missability and recovery

The storyline is missed when implementation:

  • treats access as a clean boolean;
  • treats a caption as universal delivery proof;
  • lets sponsor/management count access reach without access reader receipt;
  • hides caption operator state;
  • hides excluded reader;
  • converts reliance into generic money;
  • creates no future route effect;
  • opens from fixed timing or raw counts.

Recovery is allowed only with a visible scar: access refund audit, lawful caption rehearing, operator witness protection, sponsor makegood conversion, public correction slot, split caption canon, recall queue, blocked route, or recovery-only state.

Replay evidence expectation

storyline_id: storyteller.storyline.access_caption_reliance.v1
session_id: lens-access-caption-reliance-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  source_caption_row_or_explicit_absence_present: true
  caption_state_changes_access_meaning_delivery_or_route_use: true
  reliance_claim_present: true
  relying_reader_visible: true
  excluded_or_harmed_reader_visible_or_explicit_absence: true
  constrained_surface_visible_or_explicit_absence: true
  future_reader_or_route_consumes_reliance_state: true
  no_fixed_turn_trigger: true
offered:
  card: storyteller.card.access_caption_reliance_docket.v1
  rite: storyteller.rite.access_caption_reliance_hearing.v1
branch_runs:
  constructive_branch:
    selected_response: refund_access_reader | sponsor_counts_reach | archive_escrow_review | protect_operator_refusal | split_caption_reliance | convert_to_makegood | refuse_reliance
    relying_reader_state_after: <state>
    excluded_or_harmed_reader_state_after: <different state>
    constrained_surface_state_after: <state>
    future_reader_effect: <effect>
    counter_deltas:
      relief: []
      cost: []
      future: []
  default_branch:
    event_seen_or_armed: storyteller.event.access_caption_reliance_default.v1
    default_actor: <actor>
    false_reliance_claim: <claim>
    hidden_or_excluded_reader: <reader>
    future_reader_effect: <effect>
assertions:
  - entry_is_state_triggered
  - source_caption_row_or_explicit_absence_visible
  - reliance_claim_and_relying_reader_visible
  - excluded_or_harmed_reader_visible
  - constrained_surface_visible
  - branch_outcomes_diverge
  - every_success_has_relief_cost_and_future_effect
  - default_names_actor_false_claim_hidden_reader_and_future_effect
  - future_reader_consumes_reliance_state
  - no_universal_clean_access_caption
  - no_fixed_turn_day_week_raw_count_dashboard_or_lens_health_trigger

Non-goals

  • Not raw content-count expansion.
  • Not a generic accessibility checklist.
  • Not localization QA.
  • Not caption custody again.
  • Not sponsor makegood or fan oxygen alone.
  • Not a fixed upkeep phase.
  • Not valid unless reliance changes future playable state.