Normative Conflict Type Classification

A collision where two mandatory rules demand mutually exclusive actions, creating a deontic dilemma. The agent is obligated to perform both A and not-A simultaneously.

• Example: Contract A requires delivery by Friday; Contract B prohibits shipment until Monday.
• Resolution: Typically requires a preference ordering (e.g., lex specialis or lex posterior) to determine which obligation survives.
• Formalization: OA ∧ O¬A leads to a logical inconsistency in Standard Deontic Logic.

The strongest form of normative collision, where one rule mandates an action and another explicitly forbids it. This is a direct antinomy.

• Example: A data retention law obligates storage for 7 years; a privacy regulation prohibits keeping data beyond 3 years.
• Resolution: Often resolved via normative hierarchy (lex superior), where the higher authority's rule preempts the lower.
• Key Distinction: Unlike obligation-obligation conflicts, this involves a direct clash of deontic operators (O vs F).

A collision where a rule explicitly permits an action that another rule forbids. This creates normative uncertainty rather than a strict logical paradox.

• Example: A zoning ordinance permits commercial use; a restrictive covenant prohibits it.
• Resolution: The permissive norm is often treated as an exception that carves out a limited space from the general prohibition, implementing lex specialis.
• Formalization: PA ∧ FA is not a direct logical contradiction in all deontic systems but represents a practical collision.

A secondary obligation that activates only upon the violation of a primary duty. This models remedial norms and is a classic challenge for deontic logic.

• Example: A contract states 'You must not disclose data' (primary), but 'If you disclose, you must notify within 24 hours' (contrary-to-duty).
• Resolution: Requires non-monotonic logic to handle the dynamic activation of the secondary obligation without collapsing into inconsistency.
• Significance: Essential for modeling real-world compliance where breaches trigger new obligations.

A weak or apparent conflict where two rules grant permission for mutually exclusive actions. The agent has discretion but cannot exercise both.

• Example: A license permits exclusive use of a resource; a second license permits the same to another party.
• Resolution: This is not a logical conflict in deontic logic (both permissions can coexist), but a practical resource collision requiring a priority rule or temporal ordering.
• Classification: Often filtered out during strict deontic conflict detection but flagged for practical reasoning.

The identification of a missing rule where a normative system is silent on a required scenario. This is not a conflict but a critical classification output.

• Example: A contract specifies penalties for late delivery but is silent on non-delivery.
• Resolution: Triggers default rule application or flags the gap for human review, as no algorithmic reconciliation is possible without a rule to apply.
• Importance: Distinguishing a gap from a conflict prevents the system from incorrectly applying a conflict resolution heuristic where no rule exists.

The algorithmic process of identifying direct logical collisions between obligations, permissions, and prohibitions within a normative corpus. This is the prerequisite step to classification, scanning for patterns like a mandatory rule (Obligatory A) and a prohibitive rule (Forbidden A) existing simultaneously. Effective detection relies on parsing deontic modalities and comparing their scopes of application to flag irreconcilable commands before resolution logic is invoked.

A structured representation, often a two-dimensional array, that maps all possible pairwise interactions between deontic modalities to their predefined resolution outcomes. For example, an Obligation-Prohibition collision might default to prohibition, while a Permission-Prohibition collision yields a prohibition. This matrix serves as a deterministic lookup table for the classification system, encoding the legal system's policy for handling specific conflict types without requiring complex inference each time.

A fundamental principle of legal interpretation stating that a law governing a specific subject matter overrides a general law. In computational terms, this is the primary resolution pathway for a classified conflict where one rule is a subtype of another. The system must algorithmically verify that the scope of Rule A is a proper subset of Rule B, then apply the specific rule to the overlapping facts while preserving the general rule for all other cases.

A hierarchical conflict rule specifying that a law from a higher authority overrides a conflicting law from a lower authority. This is essential for resolving conflicts between, for instance, a federal statute and a state regulation. The classification system must tag each rule with its authority level in a normative hierarchy graph, allowing the resolution engine to immediately discard the inferior rule when a direct conflict with a superior rule is detected.

A deontic logic construct specifying what an agent is obligated to do after violating a primary obligation. This represents a complex, secondary conflict type: the collision between a violated ideal rule and the real-world state. Classification must distinguish this from a direct rule-rule conflict, as the resolution pathway involves activating a secondary, remedial obligation (e.g., 'pay a late fee') rather than simply choosing one rule over another.

A computational method for resolving normative conflicts by identifying the largest subset of non-contradictory rules from an inconsistent rule base. When multiple conflicts are classified within a single corpus, simple pairwise resolution may be insufficient. The MCS approach computes a conflict-free subset that retains the maximum number of valid rules, often guided by preference orderings like lex superior or lex posterior to select between multiple possible consistent subsets.