Ruling Reader Collision / 裁定读者冲突

Ruling Reader Collision is the mechanism for a valid ruling, served row, public receipt, or enforcement load row that is read by more than one future reader and cannot satisfy all readers at once.

The existing enforcement-load surface asks whether a result can be reused by a future reader. The drift audit asks what happens when public reality contradicts proof. This mechanism fills the bridge between them: the same source row may be legally valid, publicly persuasive, sponsor-safe, artist-safe, and route-asset-safe in different ways, but those recognitions can be mutually exclusive.

The player is not asked to re-litigate the ruling. The player is asked to choose which reader gets recognition, which reader receives a scoped or scarred version, and which reader becomes hostile, blocked, public-only, lawful-only, sponsor-only, or recovery-only.

Entry condition

Open this mechanism only from state pressure. A valid entry has all fields below:

entry_state:
  trigger_kind: state_pressure
  source_ruling_or_equivalent_row_present: true
  source_history_preserved: true
  at_least_two_future_readers_present: true
  readers_have_incompatible_acceptance_rules: true
  one_reader_is_bound_to_broadcast_or_public_reality: true
  one_reader_is_bound_to_law_archive_sponsor_artist_or_route_asset: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true

Valid source rows include archive enforcement, attachment compliance, enforcement mandate, public receipt, proof-burden shift, settlement relief, broadcast legality conversion, artist refusal boundary, route asset custody hold, sponsor carve-out, fan oxygen audit, or a hardened double-reality docket.

Reader types

A reader is any live system, faction, card, rite, route, or character surface that tries to consume the source row.

Common readers:

  • lawful_reader — inspector, white-glove, archive bureau, admissibility seal, enforcement mandate.
  • public_reader — fan oxygen public, unauthorized historian, witness receipt, pirate relay, audience stability.
  • sponsor_reader — stop-loss desk, naming rights, relief package, contract containment.
  • artist_boundary_reader — refusal receipt, living body, memorial voice, performer safety boundary.
  • editor_reader — cutroom, black-box checksum, continuity patch, source tape.
  • management_reader — compression desk, producer license, triage board, budget or slot report.
  • route_asset_reader — custody carrier, permit, proof object, follower, witness, route unlock.
  • claimant_reader — claimant floor row, settlement claimant, adverse coalition, duplicate receipt holder.

Collision row schema

Each collision row must name both the shared source and the incompatible reader demands.

collision_row:
  row_id: <stable-row-id>
  source_ruling_or_row: <source id>
  source_state_before: served | public_receipt | load_row | drift_docket | settlement | mandate | equivalent
  readers:
    - reader_id: <reader-a>
      reader_type: lawful_reader | public_reader | sponsor_reader | artist_boundary_reader | editor_reader | management_reader | route_asset_reader | claimant_reader
      wants: accept_as_universal | accept_public_only | accept_lawful_only | suppress_public_use | preserve_boundary | seize_asset | clear_report | unlock_route | equivalent
      minimum_required_surface: legal | public | sponsor | artist_boundary | editor_proof | management_report | custody_chain | claimant_notice
    - reader_id: <reader-b>
      reader_type: <type>
      wants: <incompatible demand>
      minimum_required_surface: <surface>
  incompatibility: public_vs_lawful | sponsor_vs_public | artist_boundary_vs_route_unlock | editor_patch_vs_archive_truth | management_clean_vs_claimant_notice | custody_chain_vs_public_receipt | equivalent
  recognition_surface_selected: none | lawful_priority | public_priority | sponsor_priority | artist_boundary_priority | editor_priority | management_priority | route_asset_priority | split_table | quarantine
  reader_states_after: []
  default_if_unresolved: loudest_reader_captures | false_universal_key | double_reader_hardens | route_asset_seized | claimant_floor_hostile | black_screen_pressure | equivalent

Branch families

Lawful priority

The player lets the inspector, archive, or legal mandate define the recognized reading.

Required effect:

  • one lawful, archive, proof, or custody risk improves;
  • public, sponsor, artist, route asset, or claimant pressure worsens;
  • at least one non-lawful reader becomes public_only, narrowed, hostile, blocked, or recovery_only.

Public priority

The player lets the fan public, historian, witness, or public receipt define the reading.

Required effect:

  • public receipt legitimacy, audience stability, fan oxygen balance, or private-capture resistance improves;
  • inspection heat, sponsor pressure, archive debt, witness exposure, or legal admissibility worsens;
  • at least one lawful or sponsor reader becomes public_only, contested, or audit_required.

The player lets sponsor packaging, stop-loss, naming rights, or private settlement define the reading.

Required effect:

  • sponsor stop-loss, budget, slot report, or immediate management pressure improves;
  • contract capture, public distrust, fan oxygen resentment, artist-boundary risk, or delayed inspection heat worsens;
  • at least one public or artist reader becomes captured, hostile, blocked, or recovery_only.

Artist-boundary priority

The player lets refusal, living body, memorial voice, safety boundary, or consent receipt define the reading.

Required effect:

  • artist harm, voice integrity risk, witness harm, or boundary breach risk improves;
  • route unlock, sponsor promise, public grief, fan oxygen expectation, management pressure, or archive completeness worsens;
  • at least one route or sponsor reader becomes narrowed, blocked, or lawful_only.

Split recognition table

The player scopes the ruling differently for different readers.

Required effect:

  • at least two readers receive different durable acceptance states;
  • ambiguity, archive debt, inspection heat, public distrust, or future correction cost worsens;
  • the table cannot mark every reader as cleanly accepted.

Quarantine source

The player prevents any reader from citing the row until proof, boundary, or custody improves.

Required effect:

  • false service, drift, boundary breach, or fraud risk improves;
  • the current route is delayed, blocked, or recovery-only;
  • future release requires public, lawful, artist, sponsor, or route-asset cost.

Default capture

The player hides, underfills, falsely serves, or leaves the collision unassigned.

Required effect:

  • a named reader captures the source first;
  • another reader becomes hostile, blocked, or harder to satisfy;
  • future use of the source is no longer neutral.

Counter contract

A collision resolution must mutate at least three surfaces:

  • one recognition_relief surface;
  • one recognition_cost surface;
  • one future_reader_or_route_effect.

Primary counters and durable states:

  • reader_collision
  • future_route_acceptance
  • enforcement_load
  • reality_drift
  • continuity_hazard
  • inspection_heat
  • bureau_favor_debt
  • archive_signature_legitimacy
  • archive_debt
  • public_receipt_legitimacy
  • public_receipt_distrust
  • fan_oxygen_resentment
  • sponsor_stop_loss_pressure
  • contract_capture
  • artist_refusal_respected
  • voice_integrity_risk
  • edit_debt
  • source_ambiguity
  • route_asset_pressure
  • claimant_hostility
  • management_pressure
  • black_screen_slots

Integration rules

  • With Ruling Enforcement Load, this mechanism is used when one load row has multiple incompatible future readers.
  • With 播出实在漂移审计, this mechanism is used when a public version and a proof/custody reader both cite the same source differently.
  • With Route Assets and Custody, a route asset may become posted, captured, false-owned, or recovery-only depending on which reader is recognized.
  • With 派系责任承保, any chosen reader can later underwrite the damage it pushed onto an excluded reader.

Failure conditions

The mechanism fails if any of these are true:

  • a valid ruling becomes a universal key for all readers;
  • the source ruling is re-litigated or erased instead of preserved;
  • only one reader is present;
  • readers are named but have no incompatible demands;
  • branch choice only changes flavor text;
  • sponsor, law, archive, edit, public proof, or producer authority satisfies every reader without cost;
  • default has no named capturing reader;
  • recovery erases the scar;
  • entry uses fixed turn count, fixed day count, fixed week framing, dashboard health, or raw content volume.

Replay evidence shape

mechanic: storyteller.mechanic.ruling_reader_collision.v1
session_id: lens-ruling-reader-collision-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  source_ruling_or_row: <id>
  source_history_preserved: true
  readers_min: 2
  incompatible_acceptance_rules: true
  no_fixed_turn_trigger: true
collision_row:
  row_id: <row>
  readers: []
  incompatibility: <kind>
branch_result:
  recognition_surface_selected: lawful_priority | public_priority | sponsor_priority | artist_boundary_priority | split_table | quarantine | default_capture
  reader_states_after: []
  relief: []
  cost: []
  future_effect: []
assertions:
  - entry_is_state_triggered
  - source_preserved
  - multiple_readers_visible
  - incompatibility_visible
  - branch_has_relief_cost_and_future_effect
  - no_universal_clean_acceptance

Non-goals

  • Not a new trial.
  • Not a generic faction vote.
  • Not a governance page.
  • Not filler volume.
  • Not a fixed aftermath phase.
  • Not a universal reconciliation layer.
  • Not valid unless future reader states diverge.