Deontic Conflict Detection

The core mechanism identifies direct logical incompatibility between deontic operators. A collision occurs when a single subject is simultaneously obligated to perform an action and prohibited from performing that same action under identical circumstances. The system must parse the deontic modality (obligation, permission, prohibition) of each rule and check for logical contradiction. Key collision types include:

• Obligation-Prohibition Conflict: The strongest and most critical collision, where one rule mandates an action and another forbids it.
• Obligation-Obligation Conflict: Two mandatory duties that are practically impossible to fulfill simultaneously.
• Permissive-Prohibitive Conflict: A rule permitting an action that another rule explicitly forbids, creating legal uncertainty.

Conflict detection is not merely a surface-level keyword match. The system must perform deep semantic parsing to determine if two rules actually apply to the same factual scenario. This involves extracting and comparing the rule applicability conditions—the precise set of facts that trigger each rule. A conflict only exists if the scopes of the two rules overlap. For example, a general prohibition on 'vehicle entry' and a specific permission for 'emergency vehicle entry' only conflict if the system correctly identifies that an ambulance is a subset of 'vehicle.' Mismatched scopes lead to false positives.

Legal rules have temporal dimensions that must be factored into conflict analysis. A rule enacted later may intentionally override an earlier one (lex posterior), or two rules may have non-overlapping effective periods. The detection engine must extract effective dates, sunset clauses, and transitional provisions to build a temporal map. A conflict is only actionable if the two rules are simultaneously in force. Detecting a collision between a current statute and a repealed one is a false positive that must be filtered out.

Not all rule collisions are equal. The system must construct a normative hierarchy graph to weigh the authority of conflicting sources. A collision between a constitutional provision and a municipal ordinance is resolved by the lex superior principle before any other analysis. The detection engine tags each rule with its jurisdictional level and issuing authority. This metadata is critical for downstream conflict resolution, as a lower-authority rule that contradicts a higher one may be flagged as void ab initio rather than merely overridden.

A sophisticated detection capability identifies contrary-to-duty (CTD) structures—scenarios where a secondary obligation is triggered specifically by the violation of a primary obligation. For example: 'You must not damage property, but if you do, you must pay restitution.' The system must recognize that the duty to pay restitution does not conflict with the prohibition on damage; rather, it is conditionally dependent on its breach. Misclassifying CTD structures as standard conflicts leads to erroneous resolution attempts.

Once a collision is confirmed, the system assigns a conflict severity score to prioritize resolution. This heuristic function weighs multiple factors:

• Deontic collision type: Obligation-prohibition collisions score highest.
• Jurisdictional gap: Conflicts spanning sovereign legal systems score higher than intra-jurisdictional ones.
• Practical impact: Collisions affecting fundamental rights or high-value transactions are weighted more heavily.
• Resolution complexity: Conflicts requiring multi-step reconciliation protocols receive elevated scores. This scoring feeds into a normative coherence metric for the entire corpus.