Availability Reader Collision / 可用性读者冲突线

Availability Reader Collision is the pressure-system storyline for the moment after the game has already produced a scarred availability state and before future routes reuse it as if it were clean access.

The current corpus now has strong first-order surfaces:

• 遇见可用性分流线 makes named people and roles not always reachable.
• 档期抢占认领线 makes finite slots create winners, displaced claims, off-slot states, and recovery-only scars.
• 裁定读者冲突线 prevents rulings and source rows from becoming universal legal/public/sponsor keys.

The remaining gap is availability reuse. A target being reachable through one surface does not mean every future reader may cite that reachability. This storyline turns that reuse into playable management/RPG pressure.

Primary playable question

When a source row says a target, slot, or route asset is private_only, lawful_only, public_only, sponsor_only, relay_only, floor_locked, ward_held, delayed_with_receipt, substitute_only, missed, or recovery_only, which future reader may cite it, which reader is scoped or excluded, and what route now becomes costlier, hostile, blocked, captured, or recovery-only?

State-triggered entry

Open this storyline when all are true:

entry_state:
  trigger_kind: state_pressure
  source_availability_row_present: true
  source_availability_state_present: true
  source_history_preserved: true
  future_readers_min: 2
  readers_have_incompatible_access_demands: true
  one_reader_controls_route_or_encounter_progress: true
  player_can_scope_or_record_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_count_trigger: true

Valid source availability rows include:

• encounter availability rows;
• schedule preemption selected or displaced rows;
• live floor lock or overrun rows;
• recovery ward hold, discharge, or recovery-only rows;
• fan delegate mandate rows;
• facility lockdown rows;
• route asset availability rows;
• explicit absence rows.

Content pack

Mechanic

• 可用性读者冲突机制 defines source availability states, reader types, incompatibility kinds, branch families, defaults, counters, and replay evidence.

Card

• 可用性读者冲突案卷 records the source availability row, target or slot, future readers, incompatible demands, default capture, and future effect.

Rite

• 可用性读者冲突听证 resolves public, lawful, sponsor, split, quarantine, substitute, or default recognition.

Event

• 可用性读者冲突默认 fires or arms when an incompatible reader reuses availability without scope.

Storyline spine

Beat 1 — A scarred availability state asks to be reused

A later route, recruitment, public receipt, lawful filing, sponsor statement, ward release, floor plan, route asset unlock, correction slot, or archive handoff tries to cite a prior availability state.

The source history is preserved. The player does not re-run the original encounter or slot decision.

Beat 2 — Two future readers disagree

Create or refresh 可用性读者冲突案卷. It must name at least two readers and why the same availability state cannot satisfy them cleanly.

Examples:

• 韩砚霜 recognizes lawful access, but 郁蓝 needs public receipt.
• Shen Luo can open sponsor access, but the archive reader treats that as capture.
• Baiya can keep access private through edit custody, but fan delegate readers cannot treat it as public proof.
• 海盗频段童声 can reach a target by relay, but lawful readers see chain-of-custody poison.

Beat 3 — The player scopes recognition

Offer 可用性读者冲突听证. The player chooses public recognition, lawful recognition, sponsor recognition, split table, quarantine, substitute reader, or default capture.

The rite must record the selected recognition surface, primary reader, scoped or excluded reader, proof bridge or explicit absence, handler or explicit absence, state boundary, and future effect.

Beat 4 — Reader states diverge

The availability state remains history, but readers now disagree in play.

Valid reader states include:

• accepted_with_scope;
• accepted_with_public_addendum;
• accepted_lawful_only;
• accepted_public_only;
• sponsor_captured;
• neutrality_contested;
• proof_requires_disclosure;
• route_asset_narrowed;
• target_recovery_only;
• reader_hostile;
• reader_blocked;
• default_capture_armed.

Beat 5 — A future route consumes the scoped state

The storyline is not complete until a future reader consumes the result.

Acceptable future effects include:

• public route opens but lawful addendum is required;
• lawful route proceeds but public mandate fractures;
• sponsor route opens with capture;
• archive custody requires source disclosure;
• floor route blocks the encounter route;
• ward protection makes the target recovery-only;
• substitute route opens with weaker proof;
• hostile reader arms leak, appeal, counterproof, or recovery route.

Beat 6 — Default capture becomes a named narrator

If the player hides the reader conflict, 可用性读者冲突默认 names the capturing reader and excluded reader.

The loudest reader may be sponsor, inspector, public delegate, editor, pirate relay, archive clerk, floor captain, ward authority, route asset holder, or hostile target.

Branch map

Branch	Relief	Cost	Future reader / route effect
Public recognition	public receipt, fan visibility, anti-capture pressure	lawful addendum, inspection heat, witness exposure, sponsor pressure	accepted public-only; lawful route costlier
Lawful recognition	admissibility, proof chain, archive legibility	public distrust, bureau debt, fan mandate fracture, schedule pressure	accepted lawful-only; public addendum required
Sponsor recognition	stop-loss, slot pressure, management pressure fall	contract capture, public distrust, route asset pressure, future recovery cost	sponsor-captured; neutrality contested
Split table	two readers proceed with scope	ambiguity, handler burden, correction pressure, inspection heat	scoped acceptance; disclosure required
Quarantine	false availability reuse and breach risk fall	route blocks, sponsor pressure, missed encounter pressure	reader blocked; recovery-only or substitute required
Substitute reader	immediate route can continue	original target weakens, proof weaker, public legitimacy falls	substitute-only; original reader hostile
Default capture	immediate assignment burden falls	excluded reader hostility, false reuse, route pressure, recovery cost rise	default capture armed; hostile or recovery-only

Missability and recovery

The storyline is missed when implementation:

• lets one availability state satisfy every future reader;
• uses lawful-only access as public proof;
• uses public-only access as lawful custody;
• uses sponsor-only access as neutral access;
• uses private/editor access as public receipt;
• uses relay-only access as admissible chain;
• treats delayed-with-receipt as free availability;
• treats substitute-only as original target access;
• ignores ward-held or floor-locked state;
• hides the excluded reader;
• triggers from fixed turn, day, week, chapter, raw count, dashboard state, or lens health.

Recovery requires a visible scar:

• reopen the collision hearing;
• publish public addendum;
• file lawful addendum;
• unwind sponsor capture;
• disclose source or narrow proof;
• reroute through substitute with weaker effect;
• repair ward or floor breach;
• quarantine the availability state;
• accept recovery-only route.

Replay/session evidence shape

storyline_id: storyteller.storyline.availability_reader_collision.v1
session_id: lens-availability-reader-collision-v1-<timestamp>
seed: <deterministic seed>
entry_state:
  trigger_kind: state_pressure
  source_availability_row_present: true
  source_availability_state_present: true
  source_history_preserved: true
  future_readers_min: 2
  incompatible_access_demands: true
  no_fixed_turn_trigger: true
source:
  source_availability_row_id: <stable id>
  source_system: <system>
  source_availability_state: <state>
  target_or_slot: <target slot route asset or explicit_absence>
offered:
  card: storyteller.card.availability_reader_collision_docket.v1
  rite: storyteller.rite.availability_reader_collision_hearing.v1
collision_row:
  readers:
    - reader_id: <reader-a>
      reader_type: <type>
      minimum_acceptance_surface: <surface>
    - reader_id: <reader-b>
      reader_type: <type>
      minimum_acceptance_surface: <surface>
  incompatibility: <kind>
branch_runs:
  resolved_branch:
    selected_branch: recognize_public_surface | recognize_lawful_surface | recognize_sponsor_surface | split_reader_table | quarantine_availability | accept_substitute_reader
    primary_reader: <reader>
    scoped_or_excluded_reader: <reader>
    reader_states_after: []
    future_route_effect: <effect>
    counter_deltas:
      relief: []
      cost: []
      future: []
  default_branch:
    selected_branch: default_capture
    event_seen_or_armed: storyteller.event.availability_reader_collision_default.v1
    capturing_reader: <reader>
    excluded_or_harmed_reader: <reader>
    false_reuse_kind: <kind>
    future_route_effect: <effect>
assertions:
  - entry_is_state_triggered
  - source_availability_history_preserved
  - multiple_readers_visible
  - incompatible_access_demands_visible
  - reader_states_diverge
  - no_universal_availability_key
  - default_has_named_capturing_reader
  - excluded_reader_visible
  - future_reader_consumes_result
  - no_fixed_turn_trigger
  - no_fixed_day_or_week_trigger

Non-goals

• Not a turn-count trigger.
• Not a calendar cooldown.
• Not an encounter generator.
• Not a generic social relationship system.
• Not a new ruling or appeal.
• Not raw content-count expansion.
• Not valid if the same availability state becomes clean consensus for all readers.