False Facility Extraction Default / 伪清洁撤离默认

False Facility Extraction Default fires or arms when a facility extraction permit is consumed as clean access while its room, corridor, holder, scope, excluded reader, or proof bridge is hidden.

Default Payload

event: storyteller.event.false_facility_extraction_default.v1
trigger_kind: state_pressure
source_facility_row_or_absence: <row id or explicit_absence>
extraction_subject_or_absence: <subject or explicit_absence>
permit_holder_or_absence: <holder or explicit_absence>
origin_node_or_absence: <room or explicit_absence>
destination_node_or_absence: <room or explicit_absence>
route_edge_or_missing_route: <edge or explicit_absence>
hidden_or_overbroad_scope: named_room_missing | edge_missing | holder_missing | excluded_reader_hidden | wrong_reader | wrong_room | universal_access_claim | explicit_absence
default_actor: sponsor | inspector | archive | public_table | ward_authority | floor_crew | editor | management | route_asset | blackout_system | equivalent
false_clean_claim: permit_counts_as_universal_access | extraction_counts_as_clean_encounter | service_corridor_counts_as_lawful | sponsor_escort_counts_as_public | public_receipt_counts_as_lawful | equivalent
harmed_reader_or_route: <reader route claimant or explicit_absence>
permit_state_after: false_clean_extraction | wrong_reader_capture | public_only | lawful_only | sponsor_only | blocked | hostile | recovery_only | equivalent
future_reader_or_route_effect: route_costlier | encounter_recovery_required | lawful_annex_required | public_addendum_required | room_collision_required | recovery_only | equivalent
counter_deltas_min: 3

Fire Or Arm Conditions

• A future reader consumes an extraction without Facility Extraction Permit Docket.
• Origin, destination, route edge, permit holder, or extracted subject is absent without explicit absence.
• The excluded reader, excluded room, or claimant is hidden.
• A service-corridor, ward, sponsor, archive, lawful, public, editor, floor, or route-asset permit is filed as universal access.
• A route asset or encounter becomes available from access_ok rather than scoped permit state.
• Raw room count, dashboard state, or lens health declares the extraction clean.

Recovery Hooks

Recovery requires one of:

• public addendum;
• lawful annex;
• ward seal;
• archive scan;
• escort testimony;
• service-corridor receipt;
• room-collision review;
• encounter recovery;
• route-asset quarantine.

The default is invalid if it mutates only mood, reputation, or generic pressure. It must change permit state, harmed reader or route, and future reader effect.