Facility Access Map / 设施通行图机制

Facility Access Map is the mechanism that binds Storyteller’s management-RPG pressure to physical rooms and passages. It prevents crises from resolving only through abstract ledgers by requiring access state, room claimant, route requirement, assignment, and default consequences whenever a person/proof/broadcast asset must physically cross the Seventh Dome.

The next highest-value gap after recent faction, liability, contrition, and triage work is not another ledger. It is the missing place layer: who can actually enter the cutroom, archive counter, fan gate, checkpoint, sponsor booth, service corridor, ward air room, or stage threshold when several factions need those rooms at once?

Mechanism entry

Open or refresh this mechanism when all of the following are true:

  1. a crisis depends on access to a physical node or passage from 第七穹顶设施通行图;
  2. the relevant node/edge is not safely open: it is restricted, contested, sealed, watched, rerouted, burned, claimed, or missing a route;
  3. a player assignment could still certify, reroute, seal, break, delay, or surrender room control;
  4. at least one faction benefits from unresolved room control;
  5. the room conflict can change future availability, custody, proof value, broadcast reality, public legitimacy, schedule pressure, or route-asset state.

This mechanism has no fixed numbered trigger. It opens from spatial contention and access risk.

Primary design problem

制作分诊台机制 can prove that two crises compete for the same operational lane. Route Assets and Custody can prove that a person or proof has a controllable state. But neither alone proves that a runner can physically cross a watched service corridor, that a black-box edit is trapped in the cutroom, or that the stage threshold is locked by a sponsor bridge.

Facility Access Map adds the physical consequence layer:

  • assigning the legal lane still fails if the checkpoint is sealed and no permit or oath is present;
  • saving a witness still fails if the ward air room is reachable only through a watched corridor;
  • publishing a public receipt still fails if the fan gate is crowd-blocked or sponsor-screened;
  • editing a contradiction still creates debt if the cutroom is black-box locked;
  • moving a route asset through staff space exposes the low-rank carrier instead of making the movement free.

Core object model

ObjectMeaningRequired observable field
facility_mapcurrent set of relevant room nodes and passage edgesnode states, edge states, claimants, required access, default actor
room_nodephysical place where person/proof/crowd/edit/broadcast option sitsnode id, access state, current claimant, occupants/assets
passage_edgepath between rooms or thresholdsedge id, from/to nodes, access state, risk tags
access_requirementwhat is needed to cross or control a node/edgepermit, handler, escort, proof, public cover, oxygen support, archive seal, sponsor language, or explicit absence
seal_orderfactional or safety lock on a node/edgeseal owner, reason, release condition, break consequence
room_claim_defaultwhat happens if the current claimant keeps access controldefault actor, durable state, future route effect

Room and edge states

A satisfying implementation must record at least one node and one edge when access matters.

StateMeaningRequired consequence
openthe route is usableassignment can proceed but still spends relevant resource
restrictedroute requires a named inputmissing input causes denial, delay, reroute, or event
contestedmultiple claimants can control the node/edgethe branch must choose, challenge, or default a claimant
sealedaccess is locked by authority or safety orderuse requires certify, reroute, break, or accept delay/default
reroutedofficial path is blocked and alternate path is usedraises service-corridor heat, runner risk, contamination, or public debt
watchedaccess creates visible evidence or witnessescovert use creates leak, audit heat, or hostile testimony
burnedprevious use damaged route availabilityfuture use is blocked, hostile, or costlier
claimedfaction holds control until challengedunresolved state defaults to that faction’s version

Branch contract

Branch A — Certify controlled access

The player assigns handler plus access support to a restricted/watched route.

Expected outcome:

  • route becomes certified, open, or escort-only;
  • linked crisis can proceed;
  • a cost rises: inspection heat, public debt, sponsor capture, runner exposure, oxygen debt, staff fatigue, or schedule scar.

Branch B — Reroute through low-rank space

The player uses service corridor, staff access, or unofficial handoff.

Expected outcome:

  • person/proof reaches target or escapes seizure;
  • route asset or low-rank carrier takes risk;
  • service_corridor_heat, runner_risk, proof_contaminated, missing_stub, or low_rank_staff_debt appears.

Branch C — Seal for protection

The player deliberately locks a room/edge to protect a person, proof, queue, ward, edit, or stage threshold.

Expected outcome:

  • immediate seizure, harm, leak, or public surge is reduced;
  • at least one future route, rite, public option, edit, or schedule lane is delayed, blocked, scarred, or costlier;
  • seal owner and release condition are durable.

Branch D — Break the seal

The player violates authority or safety access to reach the target now.

Expected outcome:

  • urgent access may succeed;
  • backlash appears through 房间封控撞锁 or equivalent;
  • future legal, archive, sponsor, security, public, or schedule access becomes harder.

Branch E — Let room control default

The player does not or cannot resolve access.

Expected outcome:

  • the current claimant narrates the room;
  • target becomes claimed, captured, hostile, locked, false-ownered, auto-edited, or black-screened;
  • recovery becomes costlier or narrower.

Required surfaces

Counters and durable states

A resolution must mutate at least three values, including one relief and one cost.

Primary values:

  • facility_access_pressure
  • room_seal_pressure
  • service_corridor_heat
  • runner_risk
  • inspection_heat
  • custody_gap
  • archive_debt
  • fan_oxygen_resentment
  • contract_capture
  • edit_debt
  • schedule_lane_scarred
  • black_screen_slots
  • public_distrust

Primary tags/states:

  • facility_map_open
  • route_certified
  • service_corridor_reroute
  • room_seal_active
  • seal_broken_on_camera
  • room_claim_defaulted
  • runner_exposed_by_reroute
  • stage_threshold_contested
  • cutroom_blackbox_locked
  • archive_counter_claimed
  • room_locked_recovery_only

Replay evidence contract

mechanic: storyteller.mechanic.facility_access_map.v1
source_state:
  map_state: map_open
  active_node:
    id: <node_id>
    state: restricted | contested | sealed | watched | burned | claimed
    claimant: archive | sponsor | inspector | fan_public | editor | security | route_asset | contradiction
    held_assets: []
  active_edge:
    id: <edge_id>
    from: <node_id>
    to: <node_id>
    state: open | restricted | contested | sealed | rerouted | watched | burned | claimed
  required_access:
    - permit | handler | escort | proof | public_cover | oxygen_support | archive_seal | sponsor_language | explicit_absence
assignment:
  branch: certify | reroute | seal | break_seal | default
  handler: <handler_or_absent>
  support: <support_or_absent>
result:
  route_state_after: <state>
  room_state_after: <state>
  counter_deltas: {}
  future_route_effects:
    unlocked: []
    blocked_or_costlier: []

Non-goals

  • Not a decorative place bible.
  • Not a universal movement system.
  • Not a fixed-turn phase.
  • Not a generic AP economy.
  • Not a governance or dashboard page.
  • Not a free workaround for triage, custody, proof, sponsor, inspection, witness, or route-asset pressure.
  • Not satisfied by page existence alone; room/edge state, claimant, assignment, deltas, and future access changes must be observable.