Continuity Afteruse Contempt / 连续性后用藐视线

Continuity Afteruse Contempt is a pressure storyline for the stage after a safe or official continuity version already exists, but later production discovers that the next route needs a source the official version previously suppressed.

The old win remains true: the safe version stabilized panic, the inspector seal held, the sponsor-named disaster kept the slot alive, the editor-safe cut reduced continuity hazard, or the split-canon compromise stopped immediate collapse. The new question is whether that official version can later cite the excluded source without becoming false.

Why this is the next useful expansion

The current mesh is strong at first-order continuity disputes:

• Seventh Dome Continuity Law establishes that only one official version can hold civic/legal force while unauthorized testimony remains playable pressure.
• Safe Continuity Version Fork verifies that a safe version can stabilize breach at visible cost while preserving the unauthorized fork.
• Continuity Version Dispute verifies that legal identity can be assigned across corporate, archive, split, disaster-name, or suppression branches.
• 播出实在漂移审计 catches contradiction after aired reality drifts.
• 播出合法性转轨线 prevents route assets from jumping channels for free.
• 裁定读者冲突线 prevents one source row from satisfying incompatible readers.

The remaining gap is afteruse contempt: once official reality has denied a source, later systems can accidentally cite that source as clean proof. This storyline makes the contradiction playable before it becomes invisible free continuity repair.

Primary playable question

When official continuity needs the memory it suppressed, does the producer:

• file a contradiction addendum;
• reopen continuity hearing;
• publish a public historian footnote;
• quarantine the source through black-box checksum;
• buy sponsor release or accept sponsor capture;
• split the reader note;
• quarantine or burn the citation;
• default by citing the suppressed source cleanly?

Every answer must alter future reader or route acceptance. It is not enough to change legal flavor.

State-triggered entry

Open this storyline when all are true:

1. an official continuity version exists: safe version, inspector-sealed version, sponsor-named version, editor-safe continuity, split canon, lawful-only version, public-only version, recovery-only version, or equivalent;
2. an excluded source exists or is explicitly absent: fan witness, public crack testimony, unauthorized memorial, pirate relay, black-box fragment, redacted hearing line, voice residue, public receipt, or equivalent;
3. a later use request wants that source for citation, replay, route unlock, correction, appeal, stabilization, sponsor packaging, memorial use, licensing, or recovery;
4. at least two reader families can disagree: official continuity, public memory, lawful reader, sponsor gate, editor checksum, route asset, correction slot, broadcast reality, artist boundary, fan public;
5. the player can choose a recognition surface, handler, liability carrier, proof bridge, quarantine, burn, or explicit absence;
6. the result can mutate future reader state, route availability, route cost, recovery state, contempt state, or asset freshness.

No trigger may depend on fixed turn count, arbitrary day/week interval, chapter quota, raw content count, raw lens count, dashboard state, or lens health.

Content pack

Mechanic

• 连续性后用藐视机制 defines official version state, excluded source state, later use request, reader divergence, branch contract, and replay evidence.

Card

• 连续性后用藐视案卷 records official version id, excluded source id, later use request, desired reader, harmed reader, contradiction reason, assignment slots, and contempt risk.

Rite

• 连续性后用藐视听证 resolves acknowledgement, reopening, public footnote, checksum quarantine, sponsor release/capture, split reader note, quarantine/burn, or default citation.

Event

• 被压制证词引证默认 fires or arms when the contradiction is cited cleanly.

Storyline spine

Beat 1 — Official continuity has already won something

The player has a useful version: a safe patch, inspector seal, sponsor-named disaster, editor-safe cut, split-canon compromise, lawful-only admission, public-only memory, or recovery-only scar.

This version is not retconned. The storyline starts because the version worked well enough to matter.

Beat 2 — The next route needs the excluded source

A later system asks for the source that the official version denied or narrowed.

Examples:

• a correction slot needs the redacted line;
• an appeal needs a public crack testimony;
• a sponsor package wants to quote public grief while still owning the disaster name;
• an editor-safe cut needs the raw black-box fragment to explain a route asset;
• a lawful route wants to cite a pirate relay;
• a voice-probate or memorial afteruse row needs a source that safe continuity previously suppressed.

Beat 3 — The contempt docket opens

Create 连续性后用藐视案卷. The docket must name both sides of the contradiction:

• the official version that excluded the source;
• the excluded source now requested;
• the actor requesting use;
• the desired reader;
• the harmed or excluded reader;
• the liability carrier after the choice;
• the branch or default risk.

Beat 4 — The hearing forces a recognition surface

Run 连续性后用藐视听证. The player chooses whether the contradiction is acknowledged, reopened, publicly footnoted, quarantined, packaged, split, burned, or hidden.

The rite must not allow a clean citation branch.

Beat 5 — Later readers inherit the scar

Future content consumes the result:

• official continuity accepts with addendum, narrows, reopens, or blocks;
• public memory accepts with footnote, distrusts, or becomes hostile;
• lawful reader accepts with cost, demands rehearing, or rejects;
• sponsor gate captures, releases with record, or becomes hostile;
• editor checksum accepts only as cut/source trace, not raw proof;
• route asset becomes official-only, public-only, sponsor-only, editor-safe, split-reader, quarantined, or recovery-only.

Branch map

Branch	Immediate relief	Cost/scar	Future state
Contradiction addendum	official or lawful route can cite with scar	official trust, archive debt, inspection heat, or public distrust worsens	addendum required; public or official reader surcharges
Reopen continuity hearing	contempt/false-clean risk drops	schedule delay, bureau debt, public fracture, route delay	lawful-only until ruling, split-canon possible, correction costlier
Public historian footnote	public memory and source visibility improve	inspector heat, sponsor pressure, exposure, fan resentment	public-only citation, official route costlier, historian reader accepts
Black-box checksum quarantine	source trace and continuity hazard improve	edit debt, ambiguity, archive debt, public distrust	editor-safe only, raw proof blocked, recovery-only until hearing
Sponsor release or capture	funded route or slot pressure improves	contract capture, public distrust, official trust loss, future blackmail	sponsor-only or release-record-required; public route hostile/costlier
Split reader note	one route progresses with scoped reader	handler burden, ambiguity, correction pressure, distrust	split-reader required; universal acceptance blocked
Quarantine or burn citation	contempt and false-clean risk drop	current route blocks or needs substitute	substitute source required; recovery-only; route delayed/costlier
Default citation	no upfront recognition cost	default event, false claim, reader split, hostile reader, recovery cost	contempt armed/hardened; correction or recovery required

Counter contract

Every non-default branch must mutate at least three counters or durable states: one relief, one cost, and one future reader/route/recovery effect.

Core counters and durable state families:

• continuity_authority
• continuity_contempt
• safe_version_integrity
• suppressed_testimony_visibility
• official_version_trust
• public_memory_trust
• lawful_admissibility
• archive_debt
• inspection_heat
• sponsor_stop_loss_pressure
• contract_capture
• edit_debt
• source_ambiguity
• public_receipt_legitimacy
• public_receipt_distrust
• fan_oxygen_resentment
• route_asset_pressure
• reader_collision
• future_recovery_cost

Missability and recovery

The storyline is missed or defaults when implementation:

• lets a safe version cite suppressed testimony as clean official history;
• lets a redacted line become clean proof without reopening or redaction log;
• lets sponsor naming use public grief without capture/release record;
• lets editor-safe continuity become raw source proof;
• flattens split canon into universal acceptance;
• hides desired reader, harmed reader, handler, liability carrier, or future effect;
• triggers from fixed turn count, day/week interval, raw content count, dashboard state, or lens health.

Recovery is allowed only through visible surfaces:

• contradiction addendum;
• reopened continuity hearing;
• public historian footnote;
• black-box checksum quarantine;
• sponsor release record or captured sponsor-only state;
• split-reader note;
• quarantine or burn citation;
• correction slot;
• recovery-only route asset.

Replay evidence expectation

storyline_id: storyteller.storyline.continuity_afteruse_contempt.v1
session_id: lens-continuity-afteruse-contempt-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  official_version_present: true
  excluded_source_present_or_explicit_absence: true
  later_use_request_present: true
  desired_reader_present: true
  excluded_or_harmed_reader_present_or_explicit_absence: true
  player_can_choose_recognition_surface: true
  future_route_or_reader_change_possible: true
  no_fixed_turn_trigger: true
offered:
  card: storyteller.card.continuity_afteruse_contempt_docket.v1
  rite: storyteller.rite.continuity_afteruse_contempt_hearing.v1
branch_runs:
  valid_branch:
    selected_branch: contradiction_addendum | reopen_continuity_hearing | public_historian_footnote | blackbox_checksum_quarantine | sponsor_release_or_capture | split_reader_note | quarantine_or_burn_citation
    official_version_state_before: <state>
    excluded_source_state_before: <state>
    official_version_state_after: <state>
    excluded_source_state_after: <state>
    desired_reader_state_after: <state>
    excluded_or_harmed_reader_state_after: <state>
    liability_carrier_after: <carrier>
    counter_deltas:
      relief: []
      cost: []
      future: []
  default_branch:
    event_seen_or_armed: storyteller.event.suppressed_testimony_citation_default.v1
    false_claim_created: <claim>
    future_route_effect: <effect>
assertions:
  - official_version_and_excluded_source_visible
  - later_use_request_visible
  - desired_and_harmed_readers_visible_or_explicitly_absent
  - no_clean_universal_citation
  - reader_states_diverge
  - default_is_durable
  - no_fixed_turn_trigger

Integration notes

• With 播出实在漂移审计, the contradiction can become drift evidence rather than hidden cleanup.
• With 播出合法性转轨线, a source may still need lawful, public, editor, sponsor, pirate, or recovery channel conversion after contempt is acknowledged.
• With 裁定读者冲突线, split reader notes become route restrictions rather than flavor.
• With 路线资产维护分诊线, the scarred citation can become a route asset that must be refreshed, quarantined, or burned later.

Non-goals

• Not a new first-use continuity dispute.
• Not a duplicate of memorial-rights contempt.
• Not a clean proof-conversion mechanism.
• Not a governance or dashboard page.
• Not a raw lens-count expansion.
• Not valid unless later reader or route acceptance changes.