Caption Translation Appeal Custody / 字幕译本申诉保管

Caption Translation Appeal Custody begins when a sponsor-edited caption translation is being reused as if it were the clean audience record for an artist’s public apology clip.

The current caption mesh already has Caption Translation Waiver Mismatch, Caption Latency Debt, Access Caption Reliance, and Caption Proof Carrier Handoff. The missing observable seam is appeal custody: after a translation has become a receipt, who authored it, which phrase is disputed, who read the mistranslation, and which future route will consume the corrected or uncorrected record?

Playable Question

When a later appeal panel, public recap, route asset gate, or archive index wants to cite a caption translation as public truth, does production certify a narrow correction, publish a bilingual receipt, quarantine the sponsor translation, route-scar the clip, bargain for a localization delay, or let a mistranslation default harden?

Every answer must name:

  • source caption row;
  • translator or explicit absence;
  • disputed phrase;
  • proof anchor or explicit absence;
  • harmed reader or explicit absence;
  • future reader or route;
  • selected translation posture;
  • translation state after;
  • public receipt state after;
  • future route effect.

Entry

Open this storyline only from live state pressure:

entry_state:
  trigger_kind: state_pressure
  source_caption_row_visible: true
  translator_or_absence_visible: true
  disputed_phrase_visible: true
  harmed_reader_visible_or_explicit_absence: true
  future_reader_or_route_consumes_translation_state: true
  player_can_certify_publish_quarantine_route_scar_bargain_or_default: true
  non_neutral_default_exists: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_phase_trigger: true
  no_raw_caption_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

Invalid entry sources include fixed turn count, raw caption count, generic localization work, dashboard state, or a clean caption_translated flag.

Bound Content

Branches

BranchImmediate reliefCost or scarFuture state
certify_narrow_captioncorrected row can be cited inside named scopesponsor heat risesappeal panel accepts scoped caption receipt
publish_bilingual_receiptpublic delegate can see source line and sponsor lineproducer license pressure risespublic recap unlocks counterclaim
quarantine_sponsor_translationsponsor caption cannot be reused as clean truthroute asset waitsarchive index requires translator name
route_asset_scar_captionroute can continue without erasing translation debtfuture route pays caption scarroute gate reads caption scar
bargain_for_localization_delaydeadline pressure falls temporarilylawful appeal and sponsor bargain debt riseappeal panel reopens delay cost
mistranslation_defaultfastest desk treats sponsor caption as clean recordfalse-clean translation scar hardensappeal panel reopens with translation penalty

Every constructive branch must mutate one relief surface, one cost surface, and one future reader or route effect. No branch may produce universal clean translation for public, lawful, sponsor, archive, route asset, and broadcast-reality readers at once.

Failure State

If later play cites the sponsor caption while source row, translator, disputed phrase, harmed reader, or future route effect is hidden, Mistranslation Default fires or arms.

The default must leave enough scar for later recovery through bilingual receipt, translator naming, route-asset addendum, lawful appeal, public recap correction, or sponsor-license pressure.

Non-Goals

Not a generic localization backlog, typo fix, accessibility task, caption count gate, or duplicate of caption translation waiver. This storyline only opens when a caption translation is being spent as public truth by a later reader.