SC-03: New Rule Creation
| Field | Value |
|---|---|
| Scenario ID | PER-003-SC-03 |
| Context / Trigger | The county board has passed a new ordinance requiring all commercial drone flights within 1 nautical mile of county-owned critical water infrastructure to be operated by entities with a valid county water utility access agreement. David must translate this policy into an enforceable system rule. |
Narrative
David meets with his Legal Liaison to confirm the ordinance’s scope and his GIS Specialist to define the geographic boundaries around each water facility. The GIS Specialist prepares boundary polygons in GeoJSON format and uploads them through the self-service geometry ingestion interface [UERQ-SYS-1496]. The boundaries pass geometric validation [UERQ-SYS-1560].
David opens the rule creation interface. He creates a new rule: category “required”; geographic scope limited to the uploaded water facility boundaries; condition: operator must hold a “County Water Utility Access Agreement” attribute (a custom tenant-defined attribute in the IAM Service, UERQ-SYS-1909). He sets the rule to “automated” so that operators with the attribute get auto-approved and those without are routed to manual review.
Before activating, David uses the rule testing interface to evaluate the new rule against last month’s authorization requests. The system shows: 4 requests would have been auto-approved (operators with the attribute), 7 would have been routed to manual review, and 2 would have been auto-denied (operators with revoked attributes). David reviews the results and confirms they match his expectations.
He schedules the rule to activate on the ordinance’s effective date [UERQ-SYS-1479] and sets up a conflict detection check [UERQ-SYS-1495] to verify no existing rules produce contradictory outcomes for the same area. No conflicts are found. The rule enters scheduled status.
Traceability
| Linked End Goals | Define and publish a complete set of airspace rules within one business day. Verify that a new rule works correctly by testing it against sample scenarios before activation. |
| Linked Capabilities | Self-Service Rule Creation (UERQ-SYS-1484), Geometry Ingestion (UERQ-SYS-1496), Rule Activation Scheduling (UERQ-SYS-1479), Rule Conflict Detection (UERQ-SYS-1495), ABAC Rule Evaluation (UERQ-SYS-1483), Rule Version Control (UERQ-SYS-1494). |
| Safety Relevance | Yes: a misconfigured rule could silently grant access to critical water infrastructure. Testing the rule before activation is a safety verification step. |