Recap Syndication Drift / 回顾分发漂移线

Recap Syndication Drift is the non-character pressure storyline for what happens after a public recap has already been written and a smaller fragment starts to travel.

公开回顾捕获线 decides whether the official recap preserves a scar. 陆纷切条分发跑腿线 makes the human cutter recruitable, protectable, capturable, and missable. This storyline binds the system-level consequence: a future reader must not consume a clip, quote strip, sponsor package, mirror teaser, caption extract, fan cut, archive preview, or route bridge as if it carried the full recap proof.

Bound content pack

This storyline binds:

• 回顾分发漂移机制;
• 回顾分发条;
• 回顾分发复核;
• 洁净切条分发默认.

Why this is the next pressure gap

The current mesh can prove many upstream truths:

• an official recap can be scarred, split, corrected, quarantined, or captured;
• a caption reader can rely on an accessible surface;
• a mirror feed can have different territorial scope;
• a sponsor can demand clean makegood inventory;
• a continuity copy can be scoped after use;
• a service row can be delivered to someone who lacks current authority.

The remaining gap is proof laundering by fragment. A short fragment can be technically real while missing the source scar, proof anchor, omitted-reader warning, caption dependency, mirror scope, operator state, or future-use restriction. The player should be able to use fragments, but every future route must know whether it is reading full recap proof, a bounded excerpt, or a false clean substitute.

Dramatic question

When a scarred public recap becomes a smaller proof object, does the fragment carry the scar, split by reader, require witness context, publish an addendum, stay quarantined, travel as sponsor/mirror-only, or become a false clean reality?

State-triggered entry

Open this storyline only when all required live state is visible:

entry_state_required:
  trigger_kind: state_pressure
  source_recap_row_present: true
  source_recap_state_visible: true
  source_recap_scar_or_explicit_absence_visible: true
  fragment_requested_or_circulating: true
  fragment_destination_visible: true
  proof_caption_mirror_or_service_boundary_visible_or_explicit_absence: true
  beneficiary_of_clean_fragment_visible_or_explicit_absence: true
  harmed_or_omitted_reader_visible_or_explicit_absence: true
  operator_state_or_explicit_absence_visible: true
  future_reader_or_route_consumes_fragment_state: true
  player_can_carry_split_witness_addendum_quarantine_restrict_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_clip_count_trigger: true
  no_raw_share_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

The storyline fails if it opens from a calendar cadence, chapter quota, raw clip count, raw share count, generic PR pressure, dashboard state, lens health, or a future route that never reads the fragment state.

Storyline spine

Beat 1 — The recap stops being a whole document

A source recap row exists. It may be qualified, split, corrected, public-contrition, quarantined, sponsor-clean, captured, breached, or recovery-only. A downstream desk asks for a smaller object: clip, quote strip, sponsor package, mirror teaser, caption extract, fan cut, archive preview, emergency explainer, or route bridge.

The player receives or updates 回顾分发条.

fragment_intake:
  source_recap_id: <stable recap row>
  source_recap_state: <state>
  source_scar: <scar or explicit_absence>
  proof_anchor_or_absence: <proof or explicit_absence>
  fragment_id: <stable fragment>
  fragment_kind: <kind>
  destination_surface: <surface>
  boundary_state: caption | mirror | service | sponsor | route | public | archive | fan | explicit_absence
  beneficiary_of_clean_fragment: <actor or explicit_absence>
  harmed_or_omitted_reader: <reader or explicit_absence>
  future_reader_or_route: <reader route asset or explicit_absence>

Beat 2 — The lost context becomes playable

The game must show what the fragment lost or carried:

• scar tag;
• proof anchor;
• caption/adaptation context;
• mirror-right or territorial scope;
• service-recipient authority boundary;
• omitted-reader warning;
• operator state;
• future-use restriction.

Absence is allowed only when it is explicit and priced.

Beat 3 — The player reviews the fragment before reliance

Run 回顾分发复核.

Valid postures:

1. carry scar tag;
2. split by reader;
3. require caption witness;
4. publish addendum;
5. quarantine fragment;
6. restrict as sponsor-only or mirror-only;
7. accept false-clean default.

A named operator such as Clip Syndication Runner may improve the fragment state, but no operator can make the fragment universal proof.

Beat 4 — Reader-specific reliance mutates route state

A resolved branch must mutate at least one relief surface, one cost surface, and one future route surface.

Valid future effects include:

• accepted_with_scar;
• split_required;
• caption_witness_required;
• public_addendum_required;
• service_recheck_required;
• sponsor_only;
• mirror_only;
• public_audit_required;
• route_blocked;
• costlier;
• hostile;
• recovery_only.

Beat 5 — False-clean syndication becomes durable

If a fragment is consumed as full recap proof without reading 回顾分发条, 洁净切条分发默认 fires or arms. The event must name the source recap or its absence, the fragment, failed requirement, narrator, beneficiary, harmed reader, operator state, false claim, and future route effect.

Branch map

Branch	Immediate relief	Cost/scar	Future state
Carry scar tag	fragment can circulate without lying	sponsor discomfort, public attention to scar	accepted-with-scar, bounded reuse
Split by reader	public/lawful/sponsor/mirror/caption/route readers avoid overwriting each other	contradiction pressure, edit debt, handler burden	split-required, sponsor-only, mirror-only, caption-only
Require caption witness	caption readers get source-matched context	witness exposure, delay, sponsor pressure	caption-witness-required, correction if reused without witness
Publish addendum	missing scar or proof absence becomes visible	public distrust, license heat, sponsor pressure	public-audit-required, addendum-before-reuse
Quarantine fragment	route contamination and false clean proof are blocked	schedule, fan, sponsor, and route pressure rise	quarantined, recovery-only if ignored
Restrict sponsor/mirror cut	sponsor or mirror continuity improves	public/access/fan harm or mirror contempt rises	sponsor-only, mirror-only, service-recheck-required
False-clean default	immediate management burden drops	false clean clip hardens; harmed reader becomes hostile	correction, caption witness, blocked, costlier, hostile, recovery-only

Counter contract

counter_deltas_required:
  relief: at_least_one
  cost: at_least_one
  future_reader_or_route_effect: at_least_one
candidate_surfaces:
  - clip_legibility
  - scar_tag_integrity
  - false_clean_clip
  - caption_reliance
  - access_harm_erasure
  - fan_oxygen_resentment
  - sponsor_stop_loss_pressure
  - public_receipt_legitimacy
  - public_receipt_distrust
  - mirror_relay_contempt
  - service_authority_conflict
  - broadcast_reality_drift
  - route_asset_integrity
  - operator_capture_risk
  - future_reader_acceptance
  - correction_pressure
  - recovery_only_pressure

Missability and recovery

The storyline is missed when a sponsor package, mirror teaser, caption extract, fan cut, archive preview, quote strip, emergency explainer, or route bridge is consumed without a fragment row.

Missed states include:

• false_clean_clip;
• caption_context_lost;
• sponsor_clean_fragment;
• mirror_scope_lie;
• service_authority_overread;
• access_or_oxygen_erasure;
• route_asset_unreliable;
• hostile_clip_operator;
• recovery_only.

Recovery is allowed only with visible cost: reattach scar tag, publish addendum, split reader fragments, produce caption witness, recheck service authority, quarantine old fragment, protect/recruit the fragment operator, or accept sponsor-only, mirror-only, costlier, hostile, or recovery-only future use.

Replay/session evidence shape

storyline_id: storyteller.storyline.recap_syndication_drift.v1
session_id: lens-recap-syndication-drift-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  source_recap_row_present: true
  source_recap_state_visible: true
  source_recap_scar_or_explicit_absence_visible: true
  fragment_requested_or_circulating: true
  fragment_destination_visible: true
  future_reader_or_route_consumes_fragment_state: true
  no_fixed_turn_trigger: true
offered:
  card: storyteller.card.recap_syndication_slip.v1
  rite: storyteller.rite.recap_syndication_review.v1
branch_result:
  selected_posture: carry_scar_tag | split_by_reader | require_caption_witness | publish_addendum | quarantine_fragment | restrict_sponsor_or_mirror_cut | default_false_clean
  fragment_state_after: scar_tagged | split_tagged | caption_witness_required | addendum_required | quarantined | sponsor_only | mirror_only | false_clean | disputed | recovery_only
  harmed_reader_state_after: <state or explicit_absence>
  beneficiary_state_after: <state or explicit_absence>
  operator_state_after: <state or explicit_absence>
  future_reader_effect: <effect>
  counter_deltas:
    relief: []
    cost: []
    future: []
default_branch:
  event_seen_or_armed: storyteller.event.clean_clip_syndication_default.v1 | explicit_absence
  failed_requirement: <requirement or explicit_absence>
assertions:
  - entry_is_state_triggered
  - source_recap_and_fragment_are_visible
  - scar_tag_or_explicit_absence_is_visible
  - proof_caption_mirror_or_service_boundary_is_visible_or_explicit_absent
  - beneficiary_and_harmed_reader_are_visible_or_explicit_absent
  - future_reader_consumes_fragment_state
  - branch_results_diverge_by_reader_scope_and_future_effect
  - false_clean_default_is_durable
  - no_universal_clean_fragment
  - no_fixed_turn_day_week_raw_count_dashboard_or_lens_health_trigger

Non-goals

• Not a generic marketing scene.
• Not a share-count system.
• Not a governance page.
• Not a replacement for 公开回顾捕获线.
• Not a replacement for 陆纷切条分发跑腿线.
• Not valid if a fragment becomes universal proof for every reader.