Contradiction Analysis

1. Object of study

The Domain studies normative incompatibility, overlapping applicability, authority, priority, and the operational conditions that make conflict consequential

The principal objects of study are obligations, prohibitions, permissions, powers, definitions, classifications, conditions, exceptions, priorities, remedies, and consequences expressed by two or more rules. Analysis examines whether the rules govern the same or intersecting subjects, actions, objects, facts, times, places, systems, or decisions and whether their required states can coexist.

Contradictions may be direct, such as one rule requiring an action that another prohibits in the same circumstances. They may be indirect, where separate requirements consume the same limited resource, impose incompatible deadlines, require mutually exclusive classifications, or depend upon definitions that cannot both be true. They may be vertical, involving higher and lower authority; horizontal, involving rules of comparable authority; temporal, involving transition or supersession; or cross-representational, where policy text and software enforce different outcomes.

The Domain also studies apparent contradiction. Ambiguous language, omitted context, inaccurate classification, stale versions, invalid scope assumptions, hidden exceptions, and broken traceability can create conflict findings that disappear under disciplined analysis. Distinguishing genuine contradiction from an evidentiary or interpretive defect is a core responsibility.

Contradiction can exist at several levels at once. A textual pair may be reconcilable in theory while operational constraints make joint compliance impossible; conversely, two systems may produce different results because one implements the rule incorrectly rather than because the authoritative rules conflict. The unit of analysis may therefore be a proposition, a rule pair, a dependency chain, a decision pathway, or a complete operating scenario. Selecting the wrong unit can either hide a material contradiction or inflate a local implementation defect into a claim about the entire rule system.

2. Purpose within Rules Integrity

Contradiction Analysis prevents institutions from imposing duties or outcomes that cannot be reconciled in practice or justified through authority

When contradictory rules remain active, governed people may be punished regardless of which rule they follow, operators may develop inconsistent local workarounds, automated systems may select one requirement without authority, and institutions may produce arbitrary outcomes. Conflict can also conceal accountability: each owner points to a valid rule while no one owns the incompatibility created by their interaction.

The Domain provides a repeatable way to move from suspicion to a supported finding. It clarifies the circumstances of overlap, the exact propositions in conflict, the authority and priority of each rule, the affected populations and implementations, and the consequences of leaving the conflict unresolved. This supports drafting, validation, operations, incident response, change, and assurance.

Contradiction Analysis also preserves legitimate pluralism. Complex institutions often contain rules that balance competing interests rather than eliminate all tension. The purpose is not to force artificial uniformity. It is to determine when coexistence is possible, when a priority or exception resolves the matter, when discretion is authorized, and when the rule system fails to provide a legitimate path through incompatible demands.

3. Boundaries

Contradiction is distinct from ambiguity, duplication, policy disagreement, exception, dependency, and implementation error

Ambiguity exists when a rule supports more than one plausible interpretation; contradiction exists when applicable interpreted requirements cannot be jointly satisfied or produce incompatible normative states. Ambiguity can cause apparent contradiction, and contradiction analysis may expose ambiguity, but the defects are not identical.

Duplication repeats a requirement and may create maintenance risk without immediate incompatibility. Policy disagreement concerns competing preferences or purposes before they become operative rules. An exception authorizes a defined departure from a general rule and may resolve what otherwise appears contradictory. A dependency makes one rule rely upon another; only some dependency failures create contradiction. An implementation error occurs when a procedure or system fails to represent the authoritative rule, even if the source rules are internally consistent.

The Domain identifies and characterizes conflict but does not independently decide the political, legal, ethical, or institutional choice required to resolve it. Rule Governance determines authority and decision rights. Rule Design evaluates the intervention. Rule Semantics supports interpretation. Exception Engineering structures legitimate departures. Rule Assurance determines what confidence is justified after remediation.

4. Principal questions

The recurring questions test applicability, semantic opposition, satisfiability, authority, exception, priority, and consequence

• Do the rules apply to the same or overlapping subjects, actions, objects, circumstances, jurisdictions, and periods?
• What obligations, permissions, prohibitions, powers, classifications, conditions, and consequences does each rule actually express?
• Can all applicable requirements be satisfied together in at least one legitimate state, or are they mutually exclusive?
• Does one rule create an exception, qualification, delegation, precedence rule, or authorized discretion that resolves the appearance of conflict?
• What authority, hierarchy, effective date, specificity, or conflict-of-laws principle governs priority?
• Is the conflict present in authoritative rules, introduced during representation, or created by operational practice?
• Which people, decisions, systems, contracts, processes, rights, duties, or outcomes are affected?
• How frequently do the conflicting conditions arise, and what is the severity if they do?
• What evidence supports the finding, and which assumptions or interpretations remain contested?
• What interim control and permanent resolution are authorized, proportionate, and traceable?

5. Methods of inquiry and practice

Analysis proceeds through candidate discovery, semantic normalization, scope intersection, satisfiability testing, authority review, and consequence assessment

Candidate discovery may begin with review, complaints, incidents, version comparison, cross-reference analysis, shared terminology, overlapping classifications, dependency graphs, or automated detection. Candidate generation should favor recall appropriate to consequence, but a candidate is not a contradiction finding. Similar words can express compatible rules, and different words can express incompatible requirements.

Semantic normalization identifies the subject, modality, action or state, object, conditions, exceptions, temporal scope, jurisdiction, authority, consequence, and relevant definitions of each rule. Practitioners record interpretive uncertainty rather than selecting a convenient reading. Where rules exist in several languages or representations, the comparison must establish which versions are authoritative and whether transformations preserve meaning.

Scope-intersection analysis determines whether the rules can apply simultaneously. It compares populations, facts, thresholds, dates, locations, products, decisions, and system states. If the intersection is empty, the pair is not operationally contradictory under the tested interpretation. If overlap exists, satisfiability analysis asks whether a compliant action or outcome can meet all applicable requirements. Scenario tables, decision tables, constraint models, formal logic, simulation, and expert review may all be appropriate.

Authority analysis examines hierarchy, delegation, specificity, recency, jurisdiction, contractual priority, and explicit conflict rules. An apparent contradiction may be resolved by a valid exception or priority rule, but the resolution should be accessible to implementers and governed people. A conflict that is legally resolvable yet operationally invisible remains a Rule Integrity concern.

Consequence assessment evaluates frequency, affected populations, rights, safety, financial exposure, administrative burden, decision inconsistency, implementation cost, and reversibility. Findings are classified by confidence and severity, linked to evidence, assigned to authorized owners, and tracked through interim control, remediation, validation, and closure.

6. Evidence and records

A contradiction finding requires authoritative versions, explicit interpretations, tested overlap, and evidence of consequence

Core evidence includes the complete rule texts or controlled representations, authority and hierarchy records, definitions, effective dates, applicability criteria, exceptions, amendments, supersession, interpretations, and provenance. The analysis should identify the exact provisions and semantic propositions in question rather than citing whole documents generically.

Operational evidence may include procedures, forms, training, system logic, configuration, test cases, decision records, exception and override logs, incidents, complaints, appeals, audit findings, and observed outcomes. Such evidence helps determine whether conflict is theoretical, recurring, localized, or introduced during implementation.

The contradiction record should preserve candidate source, analysts, methods, scenarios, assumptions, interpretations considered, overlap determination, satisfiability result, authority analysis, uncertainty, severity, affected dependencies, interim measures, decision owner, resolution, validation, and closure basis. If experts disagree, the competing analyses and authority for final disposition should remain visible.

Absence of observed incidents is not proof of compatibility. People may avoid one obligation, conceal noncompliance, or never encounter the overlap during the observed period. Conversely, inconsistent outcomes do not prove source contradiction; they may arise from ambiguity, discretion, data quality, implementation defects, or unequal enforcement. Evidence must support the specific claim being made.

7. Expected outputs

The Domain produces supported conflict findings, overlap models, consequence assessments, and controlled resolution records

• candidate contradiction inventories with provenance and review status;
• normalized semantic comparisons of the relevant rules;
• applicability-intersection maps and scenario matrices;
• satisfiability findings showing whether joint compliance is possible and under which conditions;
• authority, hierarchy, priority, exception, and supersession analyses;
• classification of direct, indirect, vertical, horizontal, temporal, or cross-representational conflict;
• confidence and severity assessments linked to evidence and affected populations;
• interim control recommendations such as escalation, suspension, notice, manual review, or bounded exception;
• remediation options covering interpretation, clarification, amendment, repeal, architectural change, or implementation correction;
• validated closure records preserving the decision, authority, residual conflict, and monitoring obligation.

8. Relationship to lifecycle stages

Contradiction risk begins with design choices and continues through operation, change, transition, and retirement

9. Relationship to other Domains

Contradiction Analysis depends upon semantics, authority, exception, dependency, architecture, and traceability

Rule Semantics supplies the propositions, conditions, modality, and interpretive context needed for comparison. Rule Governance and Rule Lifecycle Management identify authority, ownership, effective state, and decision rights. Traceability provides source, version, rationale, implementation, and historical evidence. Without those foundations, conflict analysis can compare the wrong rules or wrong meanings.

Exception Engineering distinguishes authorized departure from unresolved incompatibility. Dependency Analysis identifies indirect conflicts transmitted through definitions, data, resources, and external conditions. Rule Architecture reveals structural concentrations and interfaces where independently coherent rule modules collide. Change Impact Analysis identifies the consequences and remediation scope of resolution.

Rule Quality treats contradiction as one important dimension among many. Rule Integrity Metrics may measure candidate volume, unresolved severity, age, recurrence, or coverage, but counts do not substitute for substantive analysis. Rule Analytics can identify patterns of conflict and operational effect. Rule Assurance evaluates whether conflict controls and remediation evidence justify confidence.

10. Failure patterns

Poor contradiction practice produces false positives, hidden conflicts, arbitrary priority, and remediation that creates new incompatibility

• keyword differences are treated as conflict without testing whether the rules apply simultaneously;
• similar language is assumed compatible even though definitions, modality, thresholds, or consequences differ;
• an exception is inferred from custom or convenience without authoritative conditions and approval;
• a higher-level rule is declared controlling without examining delegation, jurisdiction, specificity, or effective date;
• only formal texts are compared while procedures or software impose incompatible operational outcomes;
• automated tools label candidates as contradictions without expert validation or accessible reasoning;
• conflict is resolved locally through undocumented workarounds that shift burden or create unequal treatment;
• one rule is amended without evaluating dependencies, transition periods, historical cases, and other representations;
• severity is based on frequency alone, ignoring rare conflicts involving fundamental rights, safety, or irreversible harm;
• closure records state that the conflict was fixed without re-testing scenarios and operational implementations.

11. Institutional responsibilities

Conflict must have an owner with authority to coordinate across the boundaries that produced it

Rule designers and authors should identify known interactions and test proposed requirements against the existing rule environment. Rule engineers should preserve semantic distinctions and create executable or reviewable conflict tests where appropriate. Legal, policy, regulatory, technical, and subject-matter experts provide interpretation and authority analysis. Operational teams report circumstances in which joint compliance becomes impossible or produces harmful inconsistency.

Governance bodies assign responsibility, determine priority, approve interim controls, and authorize amendment, exception, suspension, or retirement. Owners of separate rules must participate even when no single unit caused the conflict. A cross-boundary contradiction cannot be resolved credibly by allowing each owner to defend only its own rule.

Independent reviewers challenge scope assumptions, preferred interpretations, severity ratings, and claims that a conflict has been resolved. Affected people should have routes to report contradictory demands and obtain timely guidance without bearing the risk of institutional indecision. Records stewards preserve the finding, authority, resolution, and historical applicability.

12. Open research questions

The Domain requires research on scalable detection, defeasible rules, distributed authority, indirect conflict, and empirical consequence

• Which semantic representations support contradiction detection across natural language, formal rules, procedures, and software without erasing context?
• How should defeasible obligations, standards, presumptions, priorities, and balancing tests be modeled?
• What methods distinguish genuine contradiction from legitimate discretion and plural institutional purposes?
• How can candidate discovery scale across large rule systems while preserving explainability and controlling false positives?
• How should indirect conflicts involving resources, timing, data, and cumulative obligations be identified and classified?
• What evidence predicts when textual contradiction will become operational harm?
• How can contradiction analysis operate across jurisdictions and languages with different authority and interpretive traditions?
• Which governance structures resolve cross-organizational conflicts without concentrating authority or suppressing legitimate contestation?

Related Education

Foundational chapters supporting the Contradiction Analysis Domain

The Education series introduces semantics, context, authority, traceability, contradiction, ambiguity, and governance. The Domain turns those foundations into a systematic conflict-analysis practice.

Related Scope stages

The Domain prevents, detects, controls, and resolves incompatibility throughout the lifecycle

Concluding principle

No institution should impose incompatible demands without making the conflict, priority, authority, and path to resolution explicit