Normative Conflict

The principle that higher authority prevails. A constitutional provision overrides a statute; a statute overrides an administrative regulation; a federal law may preempt a state law under the supremacy clause. This creates a normative hierarchy where the source of law determines its weight.

• Example: A state privacy statute conflicts with a federal privacy act. The federal act prevails.
• Implementation: Requires a structured authority graph where each norm carries a rank or precedence level.
• Edge case: Conflicts between norms of equal rank (e.g., two constitutional provisions) require other resolution principles.

The principle that specific law derogates from general law (lex specialis derogat legi generali). A rule governing a narrow, particular situation overrides a broadly applicable rule, even if the general rule is later in time.

• Example: A general contract law provision on damages conflicts with a specific statute on construction contract damages. The construction-specific statute applies.
• Implementation: Requires semantic specificity scoring—measuring the narrowness of a norm's antecedent conditions.
• Challenge: Determining specificity is computationally non-trivial and may require ontological reasoning about the domain of each rule.

The principle that later law prevails over earlier law (lex posterior derogat legi priori). When two norms of equal authority conflict, the more recently enacted provision is presumed to reflect the current legislative intent.

• Example: A 2020 statute amends a 2015 statute on the same subject. The 2020 text governs.
• Implementation: Requires temporal metadata—effective dates, amendment dates, and repeal dates—for every norm in the knowledge base.
• Limitation: Lex posterior typically yields to lex specialis; a later general law does not override an earlier specific law unless explicitly stated.

Before resolution, conflicts must be identified. A normative conflict exists when two applicable norms prescribe incompatible deontic operators (obligation vs. prohibition) or incompatible actions (pay vs. withhold payment) under the same triggering conditions.

• Explicit conflict: Norm A obligates X; Norm B prohibits X.
• Implicit conflict: Compliance with one norm necessarily violates another due to resource constraints or logical impossibility.
• Technique: Deontic constraint satisfaction problems (CSPs) and answer set programming (ASP) can formally detect unsatisfiable normative sets.

In practice, resolution principles are defeasible—they can be overridden by stronger counter-arguments. A lex specialis argument may be defeated by showing the specific rule was not intended to apply to the instant case. This requires argumentation frameworks rather than rigid rule chaining.

• Model: Defeasible Logic Programming (DeLP) constructs dialectical trees where resolution principles are presumptive rules that can be rebutted.
• Example: Lex specialis favors a specific regulation, but a constitutional challenge defeats it via lex superior.
• Output: A justified conclusion with a traceable argument chain, not just a binary result.

Building a computable hierarchy requires mapping legal sources to a partial order. Constitutions > treaties > statutes > regulations > judicial precedent > administrative guidance. Within each level, temporal and specificity ordering applies.

• Data model: A directed acyclic graph (DAG) where nodes are norms and edges represent 'has-authority-over' relations.
• Dynamic updates: New judicial decisions can reorder the hierarchy by striking down regulations or interpreting statutes narrowly.
• Jurisdictional variation: The hierarchy differs across legal systems; a common law system weights precedent differently than a civil law system.

The structured ordering of legal norms by authority, providing the foundational resolution strategy for normative conflict. When two rules contradict, the hierarchy determines precedence.

• Lex Superior: The higher authority prevails (constitution over statute).
• Lex Specialis: The more specific rule overrides the general.
• Lex Posterior: The later-enacted law supersedes the earlier.

A non-monotonic extension of deontic logic that allows conclusions to be retracted in the presence of new information. This is essential for modeling how legal rules admit exceptions and how prima facie obligations can be defeated by countervailing norms.

• Handles exceptions without rewriting the base rule.
• Prevents logical explosion from contradictions.
• Models the argumentative nature of legal reasoning.

A conditional obligation that arises when a primary duty has been violated. CTD structures represent the normative fallback rules that govern non-ideal compliance situations, which are the primary source of real-world normative conflicts.

• Example: 'You ought not to breach a contract. If you do breach, you ought to pay damages.'
• Standard Deontic Logic (SDL) famously fails to model these without paradox.

A classic deontic logic puzzle demonstrating that Standard Deontic Logic (SDL) cannot consistently represent contrary-to-duty obligations without deriving logical contradictions. It illustrates why naive formalization of conflicting norms fails.

• Exposes the temporal dimension of obligations.
• Motivates the need for temporal or defeasible deontic logics.
• A benchmark test for any normative reasoning engine.

A computational argumentation framework that combines logic programming with defeasible reasoning to resolve conflicting normative conclusions through dialectical analysis. Arguments for and against an obligation are constructed and compared.

• Resolves conflict via argument defeat, not static hierarchy.
• Provides explicit warrants for conclusions.
• Suitable for adversarial legal reasoning systems.

A formalization of normative reasoning as a set of variables and deontic constraints, solved by finding assignments that satisfy all applicable obligations and prohibitions without conflict. When no solution exists, the CSP is over-constrained, indicating an irresolvable normative conflict.

• Detects inconsistency in regulatory codes.
• Used in compliance-by-design architectures.
• Enables algorithmic identification of conflicting permit requirements.