Facility Extraction Permit Receipt / 设施撤离许可回执线

Facility Extraction Permit Receipt is the storyline for the moment a person, proof object, route asset, ward patient, archive copy, fan witness, or broadcast source leaves a contested room under a permit that later readers may try to treat as clean building-wide access.

Facility Access Lockdown already proves that rooms and corridors can be sealed, watched, claimed, rerouted, or broken. Encounter Availability Routing already proves that an access choice changes who can still be met. The uncovered seam is the permit receipt between them: after an extraction succeeds, the game must preserve what the permit actually allowed, who carried it, which room or edge it covered, who was excluded, and what future reader can cite it.

Playable Question

When a facility extraction permit is issued, does the producer certify a narrow extraction, split escort scope, route through a service corridor, seal the permit for ward or archive use, publish a public receipt, refuse the permit, or let a false-clean extraction default harden?

The answer must name:

• source facility row;
• permit holder or explicit absence;
• extracted subject or proof;
• origin node and destination node;
• route edge or missing route;
• permitted room scope;
• excluded room, reader, or claimant;
• escort, proof bridge, or explicit absence;
• selected posture;
• future route effect.

Gap Diagnosis

Without this storyline, implementation can:

• extract a route asset through one corridor and let later play treat the permit as facility-wide access;
• move a witness from a ward room without naming the ward reader who lost control;
• let sponsor, archive, public, lawful, editor, fan, and floor readers cite the same permit;
• convert a service-corridor rescue into clean encounter availability;
• hide whether the permit was certified, split, public-only, lawful-only, ward-sealed, or recovery-only.

The permit is not the same as the map. It is a scoped receipt created by one access decision and consumed by later route, encounter, archive, lawful, public, sponsor, or broadcast-reality readers.

State-Triggered Entry

Open this storyline when an extraction permit is about to affect future access:

entry_state_required:
  trigger_kind: state_pressure
  source_facility_row_present: true
  extraction_subject_visible: true
  origin_node_visible: true
  destination_node_visible: true
  route_edge_or_missing_route_visible: true
  permit_holder_visible_or_explicit_absence: true
  permitted_scope_visible: true
  excluded_reader_or_room_visible_or_explicit_absence: true
  future_reader_consumes_permit_state: true
  player_can_certify_split_reroute_seal_publish_refuse_or_default: true
  no_fixed_turn_trigger: true
  no_fixed_day_or_week_trigger: true
  no_raw_room_count_trigger: true
  no_dashboard_or_lens_health_trigger: true

The entry may happen after a lockdown, encounter window, ward hold, live-floor pull, archive counter claim, sponsor bridge, cutroom lock, or fan gate surge. Timing can explain pressure, but the trigger is the state of a scoped extraction permit.

Bound Content Pack

• 设施撤离许可回执机制 defines permit rows, scope states, branch contract, and false-clean default.
• 设施撤离许可案卷 records holder, subject, nodes, edge, scope, excluded reader, proof bridge, posture, and future effect.
• 设施撤离许可复核 resolves certify, split, reroute, seal, publish, refuse, or default branches.
• 伪清洁撤离默认 records hidden or overbroad permit use.
• Facility Extraction Permit Receipt Lens observes the implementation contract.

Storyline Spine

Beat 1 - The extraction row appears

A room, corridor, ward, stage threshold, archive counter, fan gate, sponsor booth, cutroom, or service passage has produced a permit. Create or refresh Facility Extraction Permit Docket before later play consumes that permit.

Beat 2 - Scope becomes visible

The docket names origin node, destination node, route edge, permit holder, extracted subject, permitted scope, excluded reader or room, and proof bridge or explicit absence.

Beat 3 - Review prices the extraction

Run Facility Extraction Permit Review. The player chooses a permit posture and accepts relief, cost, and future reader effect.

Beat 4 - Future play reads the permit

Later encounter availability, route asset custody, archive enforcement, public receipt, lawful annex, sponsor access, editor checksum, ward discharge, floor crew, or broadcast-reality surfaces must consume permit_state_after, not a generic extracted flag.

Beat 5 - False-clean extraction defaults

If a permit is hidden, overbroad, wrong-reader, wrong-route, or consumed without excluded-reader scope, False Facility Extraction Default records the false clean claim and scars the future reader.

Branch Map

Branch	Immediate relief	Cost/scar	Future state
Certify narrow extraction	subject/proof reaches destination	inspection heat or escort debt rises	certified_named_scope
Split escort scope	two readers receive separate permit truths	schedule and handler burden rise	split_scope_required
Service-corridor reroute	seizure or lock is bypassed	runner risk and proof contamination rise	service_reroute_costlier
Ward/archive seal	harm or false public use falls	public or sponsor route narrows	sealed_lawful_or_ward_only
Publish public receipt	sponsor or hidden room claim weakens	witness exposure and facility heat rise	public_only_addendum_required
Refuse permit	false-clean access is blocked	encounter or route delays	blocked_or_recovery_only
False extraction default	immediate access may seem open	wrong reader captures scope	false_clean_extraction

No branch may turn a corridor, ward, archive, sponsor, editor, public, lawful, or floor permit into universal clean facility access.

Missability And Recovery

This storyline is missed when implementation:

• stores only permit_granted, room_open, extracted, or access_ok;
• omits origin, destination, route edge, holder, excluded reader, or permitted scope;
• treats sponsor escort as public access or public receipt as lawful access;
• treats service-corridor movement as clean encounter availability;
• lets a future reader consume the permit without reading the extraction scope;
• opens from fixed turn, day/week cadence, raw room count, dashboard state, or lens health.

Recovery requires visible scar: add a public addendum, lawful annex, ward seal, escort testimony, service-corridor receipt, room-collision hearing, substitute carrier, encounter recovery, or route-asset quarantine.

Replay Evidence Expectation

storyline_id: storyteller.storyline.facility_extraction_permit_receipt.v1
session_id: lens-facility-extraction-permit-receipt-v1-<timestamp>
seed: <deterministic-seed>
entry_state:
  trigger_kind: state_pressure
  source_facility_row_present: true
  extraction_subject_visible: true
  origin_node_visible: true
  destination_node_visible: true
  permitted_scope_visible: true
  future_reader_consumes_permit_state: true
  no_fixed_turn_trigger: true
offered:
  card: storyteller.card.facility_extraction_permit_docket.v1
  rite: storyteller.rite.facility_extraction_permit_review.v1
branch_result:
  selected_posture: certify_narrow_extraction | split_escort_scope | service_corridor_reroute | ward_archive_seal | publish_public_receipt | refuse_permit | false_extraction_default
  permit_state_after: <state>
  future_reader_or_route_effect: <effect>
  event_seen_or_armed: storyteller.event.false_facility_extraction_default.v1 | none
  counter_deltas:
    relief: []
    cost: []
    future: []

Non-goals

• Not a replacement for facility access lockdown.
• Not a replacement for encounter availability routing.
• Not a general movement system.
• Not a fixed-timer extraction scene.
• Not valid if the only observable result is room_open, permit_granted, or access_ok.