Facility Extraction Permit Docket / 设施撤离许可案卷

Facility Extraction Permit Docket records the exact scope of a room, corridor, ward, archive, stage, sponsor, fan-gate, or cutroom extraction.

Create or refresh this docket before a future reader can cite an extraction permit as proof of access, encounter availability, route asset custody, archive movement, lawful service, public receipt, or broadcast reality.

Docket Required

docket_required:
  source_facility_row:
    row_id: <stable row id>
    source_surface: facility_access_lockdown | encounter_availability | ward_hold | live_floor | archive_counter | fan_gate | cutroom_lock | sponsor_booth | equivalent
    room_state_before: restricted | contested | sealed | watched | rerouted | burned | claimed | explicit_absence
  extraction_subject: person | proof_object | route_asset | ward_patient | archive_copy | fan_witness | broadcast_source | explicit_absence
  permit_holder_or_absence: handler | inspector | archive_clerk | ward_authority | sponsor_proxy | public_delegate | service_runner | explicit_absence
  origin_node: <room or explicit_absence>
  destination_node: <room or explicit_absence>
  route_edge_or_missing_route: <edge or explicit_absence>
  permitted_scope: named_room | named_edge | escorted_subject | ward_only | archive_only | public_only | lawful_only | sponsor_only | service_corridor_only | recovery_only | equivalent
  excluded_reader_or_room_or_absence: <reader room claimant or explicit_absence>
  escort_or_proof_bridge_or_absence: permit_stamp | escort_witness | lawful_seal | public_receipt | service_corridor_note | ward_log | archive_scan | explicit_absence
  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: certified_named_scope | split_scope_required | service_reroute_costlier | sealed_lawful_or_ward_only | public_only_addendum_required | blocked_or_recovery_only | false_clean_extraction
  future_reader_or_route_effect: <effect>

Invalid Shortcuts

This card is not satisfied by:

• room_open;
• permit_granted;
• access_ok;
• subject_extracted;
• escort_done;
• a high-status handler without origin, destination, route edge, scope, and excluded reader;
• a service corridor note reused as lawful, public, sponsor, archive, and encounter access.

Branch Payload

permit_resolution:
  selected_posture: <posture>
  relief_any:
    - subject_extracted | proof_seizure_down | ward_harm_down | archive_copy_preserved | public_visibility_up | equivalent
  cost_any:
    - inspection_heat_up | escort_debt_up | service_corridor_heat_up | runner_risk_up | proof_contamination_up | witness_exposure_up | equivalent
  future_effect_any:
    - certified_named_scope | split_scope_required | public_addendum_required | lawful_annex_required | route_costlier | recovery_only | equivalent

At least one relief, one cost, and one future effect must be present.