SC-04: Rule Evaluation Investigation
| Field | Value |
|---|---|
| Scenario ID | PER-003-SC-04 |
| Context / Trigger | An operator from a state DOT contractor contacts David to report that their flight authorization request was denied, but they believe they meet all requirements. The operator has a valid Part 107 certificate, TSA background check, and organizational affiliation with the state DOT. David needs to determine whether the denial was correct or reflects a rule misconfiguration. |
Narrative
David searches for the operator’s authorization request in the authority dashboard. He locates the request and opens the detailed rule evaluation log. The system shows that the request was evaluated against 14 applicable rules: 13 passed, and 1 failed. The failing rule is a geographic rule that requires “County Infrastructure Access Permit” for flights within the water facility boundary.
David checks the operator’s attribute profile: they have “State DOT Contractor” affiliation but not the specific county permit. The denial was technically correct — the rule is working as designed. However, David recognizes that state DOT contractors working on county water infrastructure should qualify.
He creates a rule modification request to add “State DOT Contractor” as an accepted attribute for the water facility rule, routes it through the internal approval workflow, and informs the operator that the rule will be updated.
In the interim, David manually approves the operator’s request using his Authorizer role, documenting the justification. The system logs his override decision for audit purposes.
Traceability
| Linked End Goals | Review and resolve pending requests within SLA. Verify rules work correctly. |
| Linked Capabilities | Rule Evaluation Audit Trail (UERQ-SYS-1481), Operator Attribute Query, Rule Version Control (UERQ-SYS-1494). |
| Safety Relevance | Yes: the investigation reveals a rule gap. If not addressed, legitimate state DOT contractor operations near water infrastructure would continue to be blocked. |