Encounter Availability Routing / 遇见可用性分流线

Encounter Availability Routing is a pressure-system storyline for the moment when the game must admit that a person is not always reachable. After the newest recovery-ward and fan-delegate work, Storyteller has strong pressure rows, but the next high-value gap is whether those rows change actual encounter access.

A producer can stabilize discharge, seat a delegate, win lawful access, move a floor crew, route through an editor, or accept sponsor relief. Each success should change which person can still be met, recruited, interviewed, protected, or used as route asset. This storyline turns that into playable management/RPG depth.

Playable promise

When a route needs a person, the game must surface encounter availability as a contested route asset. The player chooses a gate: private, lawful, public, sponsor, editor, relay, ward, floor, or substitute. The chosen gate must open or preserve one access path and cost another.

The result can make a person:

• available with cost;
• private-only;
• lawful-only;
• public-only;
• sponsor-only;
• relay-only;
• ward-held;
• floor-locked;
• substitute-only;
• missed;
• recovery-only.

Why this is the next useful expansion

The current corpus already supports:

• 代理人姿态链 for human carriers;
• 直播现场班组负荷线 for floor capacity;
• 复原病房出院压迫线 for care/custody pressure;
• 粉丝委任分裂线 for scoped public voice;
• Route Assets and Custody for route asset movement;
• Broadcast Reality for aired facts becoming world pressure.

The remaining gap is not another docket. It is a cross-reader that prevents every character from remaining available after those systems mutate the world. If a legal route, sponsor route, floor route, or ward route changes access, the future encounter reader must know.

State-triggered entry

Open this storyline when all of the following are true:

1. A future route, rite, proof, custody handoff, recruitment, testimony, apology, correction slot, discharge hold, or safety signoff needs a named person, NPC, role, or explicit absence.
2. At least two access gates are active or missing: schedule, legal, facility, public, sponsor, editor, ward, floor, relay, handler, or equivalent.
3. The source pressure already has preserved relief and cost from a prior branch.
4. Choosing one gate can make another encounter narrower, missed, substitute-only, or recovery-only.
5. A future reader consumes the encounter state.
6. Entry does not depend on fixed turn number, day/week interval, chapter quota, raw content count, or dashboard/lens-health state.

Content pack

Mechanism

• 遇见可用性分流机制 defines gates, availability states, branch families, default conditions, and replay evidence.

Card

• 遇见可用性账本 records the target, encounter need, source pressure, access gates, availability state, rival or lost encounter, state boundary, and future reader.

Rite

• 遇见窗口仲裁 resolves which gate is used and what encounter becomes narrower or lost.

Event

• 错过遇见默认 fires or arms when the game would otherwise leave a missed or scarred encounter silently available.

Storyline spine

Beat 1 — A route asks for a person

A proof, apology, ward hold, floor operation, correction slot, public delegate, lawful interview, archive handoff, or route asset requires a person. The target may be a character, NPC, role, or explicit absence.

Examples:

• Yu Lan is needed as receipt carrier, historian, or public witness;
• Shen Luo can arrange sponsor access that captures future wording;
• Han Yanshuang can make access lawful-only;
• Baiya can keep the meeting alive through edit custody;
• 海盗频段童声 can reach a target by relay while increasing lawful risk;
• Call-Sheet Captain can prove a target is floor-locked.

Beat 2 — Availability ledger appears

Create or refresh 遇见可用性账本. The row must name:

• target entity or explicit absence;
• encounter need;
• source pressure and preserved relief/cost;
• at least two access gates;
• current availability;
• rival or lost encounter;
• handler or explicit absence;
• state boundary;
• future reader or route.

Beat 3 — Gates conflict

At least two gate families should disagree. For example:

• schedule says the target is available, but facility access says escort required;
• legal route says lawful-only, but fan delegate route needs public witness;
• sponsor route can reach the person, but only with contract capture;
• editor route can hide the source, but public route loses proof;
• ward route protects the person, but discharge pressure demands action;
• floor route locks the person to a live operation.

Beat 4 — Arbitration chooses access

Offer 遇见窗口仲裁. The player chooses:

• reserve private meeting;
• seat lawful interview;
• broadcast public call;
• trade sponsor access;
• route through editor or relay;
• overload access by spending capacity;
• defer, substitute, or default.

Beat 5 — Future reader mutates

The selected branch must change both availability and route future. Valid future effects include:

• private_route_open_with_public_cost;
• lawful_route_open_public_addendum_required;
• public_route_open_with_retaliation;
• sponsor_route_open_with_capture;
• source_disclosure_required;
• split_public_lawful_routes;
• access_scar_armed;
• route_blocked_until_substitute;
• recovery_only.

Beat 6 — Miss/default becomes material

If the player treats access as clean, 错过遇见默认 fires or arms. The default must name the person or explicit absence, missing gate evidence, default actor, route effect, and recovery hook.

Branch matrix

Branch	Immediate relief	Cost/scar	Future state
Reserve private meeting	target protected, source safer, private route opens	public distrust, lawful addendum, handler fatigue	private route with disclosure cost
Seat lawful interview	admissibility and compliance rise	bureau debt, public route narrows, fan fracture	lawful-only / public addendum
Broadcast public call	public legitimacy and anti-capture pressure rise	witness exposure, inspection heat, relay risk	public-only / lawful appeal
Trade sponsor access	slot and stop-loss pressure fall	contract capture, public distrust, route asset capture	sponsor route with capture
Route through editor or relay	retaliation or access block falls	edit debt, source ambiguity, relay custody risk	source disclosure / split route
Overload access	contact happens despite capacity stress	crew load, blackout risk, ward/facility/handler scar	access scar / recovery route
Defer or substitute	immediate overload may fall	original target missed or weakened	substitute-only / recovery-only / blocked

Missability and recovery

The storyline is missed when the player:

• assumes a person remains globally available after choosing a gate;
• uses lawful access as public access;
• uses sponsor access as neutral access;
• uses private/editor route as public proof;
• spends ward, floor, facility, or handler capacity without scar;
• substitutes a person without weakening the future route;
• opens a future route without naming which encounter was narrowed or lost.

Recovery requires visible cost: substitute proxy, lawful appeal, public counter-receipt, sponsor unwind, source disclosure, ward repair, crew repair, facility extraction, apology hearing, or replacement route asset.

Replay evidence expectation

storyline_id: storyteller.storyline.encounter_availability_routing.v1
session_id: lens-storyteller-encounter-availability-routing-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  target_or_explicit_absence_present: true
  source_pressure_present: true
  access_gate_count_min: 2
  rival_or_lost_encounter_present: true
  future_reader_or_route_consumes_result: true
  no_fixed_turn_trigger: true
offered:
  card: storyteller.card.encounter_availability_ledger.v1
  rite: storyteller.rite.encounter_window_arbitration.v1
branch_runs:
  preserving_branch:
    selected_branch: reserve_private_meeting | seat_lawful_interview | broadcast_public_call | trade_sponsor_access | route_through_editor_or_relay
    opened_encounter: <target or route>
    narrowed_or_lost_encounter: <target route or explicit_absence>
    cost_state: <state>
    future_route_effect: <effect>
  miss_or_substitute_branch:
    selected_branch: overload_access | defer_substitute_or_default
    event_seen_or_armed: storyteller.event.missed_encounter_default.v1
    availability_after: missed | substitute_only | recovery_only | lawful_only | public_only | sponsor_only | relay_only | equivalent
    future_route_effect: <effect>
assertions:
  - entry_is_state_triggered
  - ledger_records_target_pressure_gates_rival_and_future_reader
  - rite_changes_availability_and_future_route
  - success_has_cost
  - missed_default_is_durable
  - no_fixed_turn_or_day_trigger

Non-goals

• Not raw content expansion.
• Not a social hub.
• Not a fixed-turn missed scene.
• Not a generic relationship system.
• Not a universal rescue mechanic.
• Not valid if one access gate cleanly opens every person, route, and future reader.