Facility Access Routing / 设施通行派线

Facility Access Routing is the rite that resolves one update of 设施通行图. It makes the player assign a path, handler, and access proof before a person, receipt, voice copy, editor checksum, fan witness, oxygen support, or route asset can reach a contested room.

The rite is offered when the right crisis response is known but the room or passage is not safely reachable.

Rite slots

Slot	Required fill	Why it matters
map	facility-access-map or equivalent open map state	proves the room/route conflict is visible
origin_node	room/threshold where the person/proof currently sits	prevents teleporting route assets
target_node	room/threshold that must be reached or sealed	names the real place objective
edge_or_route	passage between origin and target, or explicit absence	shows which route is used, blocked, or missing
handler	character, route asset, runner, escort, legal/audit actor, public cover, or explicit absence	ties the route to RPG staffing
access_support	permit, proof, archive seal, oxygen support, sponsor language, public witness, black-box checksum, security escort, or explicit absence	pays or fails the access requirement
claimant_pressure	faction that benefits if the route is unresolved	creates non-neutral default pressure

The rite cannot pass with a famous handler alone. It must record route state and access support or explicit absence.

Allowed handlers and supports

Examples, not a closed list:

• Baiya can route through cutroom_blackbox, lock or certify edit state, and carry edit debt.
• Han Yanshuang can certify inspection-facing access or harden a lawful seal.
• Yu Lan can use public witness or historian presence to cross fan_oxygen_gate or challenge a default.
• Shen Luo can bridge sponsor access but risks contract capture.
• 交接链跑腿 can move through service_corridor_chain but risks exposure, debt, or missing stubs.
• Inspection Shadow Crew Permit can certify a watched path or be burned by seal break.

State-triggered offer

Offer the rite when all are true:

1. a map/card state exposes at least one restricted, contested, sealed, watched, rerouted, burned, or claimed node/edge;
2. a person, proof, card, rite, public queue, oxygen support, edit, broadcast option, or route asset depends on access to that node/edge;
3. at least one handler or access support is available or explicitly absent;
4. at least one claimant benefits if access remains unresolved;
5. the room state is not terminally resolved.

No fixed turn count or calendar count may be required.

Resolution branches

Branch A — Certify the path

The player assigns credible handler plus support to a restricted or watched route.

Expected outcome:

• route state becomes open, certified, or escort_only_open;
• target room becomes reachable for the linked crisis;
• one cost rises: inspection heat, public debt, sponsor capture, oxygen debt, schedule scar, or handler fatigue.

Branch B — Reroute through service access

The player moves through a service corridor or low-rank path instead of the official route.

Expected outcome:

• person/proof reaches or leaves the target;
• service_corridor_reroute appears;
• runner_risk, proof_contaminated, missing_stub, low_rank_staff_debt, or inspection_heat rises.

Branch C — Seal for protection

The player makes a room or edge inaccessible to protect a person, proof, oxygen room, fan queue, or broadcast source.

Expected outcome:

• seizure, injury, hostile edit, or crowd pressure drops;
• one future route, rite, public option, or schedule lane is blocked, delayed, or costlier;
• the seal owner and release condition are recorded.

Branch D — Break the seal

The player violates a seal to reach the target now.

Expected outcome:

• access is gained, partially gained, or fails loudly;
• seal_broken_on_camera, custody_gap, inspection_heat, security_injury, public_distrust, or black_screen_slots changes;
• future legal, archive, or public access becomes harder.

Branch E — Let room control default

The player does not assign credible route, handler, support, or delay.

Expected outcome:

• current claimant controls the room/edge;
• default can emit room seizure, auto-edit, false owner, sponsor language, fan-public version, route asset capture, or archive lock;
• future access is blocked, costlier, hostile, captured, or recovery-only.

Required result payload

rite: storyteller.rite.facility_access_routing.v1
map: storyteller.card.facility_access_map.v1
origin_node: <node_id>
target_node: <node_id>
edge_or_route: <edge_id_or_absent>
route_state_before: open | restricted | contested | sealed | rerouted | watched | burned | claimed
handler: <character_or_route_asset_or_explicit_absence>
access_support: <permit_or_proof_or_resource_or_explicit_absence>
claimant_pressure: archive | sponsor | inspector | fan_public | editor | security | blackout_system | route_asset | contradiction | none
branch: certify | reroute | seal | break_seal | default
outcome:
  route_state_after: open | certified | escort_only_open | rerouted | sealed | burned | claimed | defaulted
  target_room_effect: reachable | protected | blocked | costlier | captured | hostile | recovery_only
  counter_deltas: {}
  future_route_effects:
    unlocked: []
    blocked_or_costlier: []

Counter contract

The rite must mutate at least three counters or durable states when it resolves, including one relief and one cost.

Typical changes:

• facility_access_pressure: -1 on credible route, +1 on default or broken seal;
• room_seal_pressure: +1 when a seal is created or violated;
• service_corridor_heat: +1 on reroute;
• runner_risk: +1 when low-rank carrier bears access risk;
• inspection_heat: +1 on watched or broken access;
• custody_gap: +1 on contaminated or defaulted route;
• edit_debt, contract_capture, fan_oxygen_resentment, schedule_lane_scarred, or black_screen_slots: +1 based on route family.

Miss and failure

If a live map is ignored while a claimant can default a room, the next event must be able to resolve the room through default control. Skipping this rite is not a neutral wait.

Non-goals

• Not a movement minigame.
• Not a generic action point spend.
• Not a way to bypass 制作分诊台机制.
• Not satisfied unless origin, target, route state, handler/support, claimant, deltas, and future availability are recorded.