SC-01: Emergency TFR Response

Andi Lamprecht ·2026-05-11· 2 min read· Draft

Narrative

David accesses the authority dashboard from the county’s EOC, where he has relocated. He navigates to the rule management interface and selects “Create Emergency Rule.” The system presents a map-based boundary drawing tool. David draws a polygon around the fire perimeter plus a 2-nautical-mile buffer, using real-time fire location data from the county’s GIS feed.

He configures the rule: blanket denial for all operations except those with Operation Category “Emergency Services” or “Firefighting.” The rule is set to activate immediately with no end date (David will deactivate it manually when the fire is contained). He sets the rule to “required” category so it cannot be overridden by sub-authority standing approvals.

Before activating, the system runs a conflict check: it identifies 3 currently accepted authorizations within the new denial zone, all non-emergency. The system informs David and asks for confirmation. David confirms; the system activates the blanket denial, revokes the 3 conflicting authorizations (they are in Accepted state, not Activated, so preemption is permitted per UERQ-SYS-1476), and notifies the affected operators.

David verifies the rule is active by checking the jurisdiction status display. He sees the restricted zone highlighted on the map and confirms that the system is rejecting a test request from his Rule Analyst. He notifies the state DOT root authority of the restriction.