Contradictions

1. Defining contradiction

Contradiction is incompatibility within the same relevant case

This definition contains an important limitation: the rules must govern the same relevant case. “Employees must wear identification inside the secure facility” and “employees must not display identification in public” are not contradictory when location distinguishes their scope.

Contradiction can concern conduct, authority, timing, thresholds, definitions, evidence, consequences, or implementation. It may be explicit in text or emerge only when rules are combined.

Formal logic treats contradiction as the joint assertion of a proposition and its negation. Rule systems require a broader practical analysis because normative statements include obligation, permission, prohibition, exceptions, temporal conditions, and hierarchy.¹

2. Genuine and apparent contradictions

Rules that look inconsistent may become coherent after context is restored

An apparent contradiction is a conflict that disappears when the full rule system is considered. The rules may govern different populations, times, jurisdictions, objects, risk levels, or procedural stages. A priority rule or explicit exception may already determine which expression controls.

A genuine contradiction remains after those distinctions are examined. The same actor, under the same material conditions, would be required to produce incompatible results or would face mutually exclusive obligations.

Treating every difference as contradiction creates noise. Treating every difference as harmless variation conceals risk. The discipline lies in proving whether the overlap is real.

3. Direct contradictions

One rule requires what another rule prohibits

Direct contradictions are the clearest form. One rule obligates an action while another forbids the same action under the same relevant conditions.

Examples include:

• “The analyst must disclose the report to the regulator” and “The analyst must not disclose the report to any external party”;
• “The system must retain audit records for seven years” and “The system must delete all records after five years”;
• “The employee must approve the transaction” and “The employee must not participate in approval when a conflict exists,” where the same case also requires that employee's approval and no alternative approver is available.

Direct contradiction should be distinguished from an obligation paired with a permission. “Must disclose” and “may disclose” are not always logically incompatible, because the obligation satisfies the permission. They may still indicate inconsistent drafting or authority, but the actor can comply with both.

4. Conditional contradictions

Rules conflict only when particular conditions overlap

Conditional contradictions are more difficult because each rule appears coherent independently. The conflict emerges only for a subset of cases.

Suppose one rule requires enhanced review for every transaction involving a foreign official. Another rule permits automatic processing for transactions under $5,000. A transaction under $5,000 involving a foreign official satisfies both conditions. If automatic processing excludes enhanced review, the rules contradict for that intersection.

Detection requires analysis of condition combinations, not only sentence comparison. Decision tables and test cases are often more effective than prose review for exposing overlap.

5. Temporal contradictions

Rules may require incompatible action because they use different clocks, deadlines, or effective periods

Temporal contradictions include incompatible deadlines, sequencing, retention periods, notice windows, effective dates, and recurrence.

Examples include:

• a contract requires notice within five calendar days while policy allows ten business days;
• a rule requires approval before execution while another workflow permits approval after execution;
• a retention rule requires preservation for seven years while a deletion rule requires destruction after five;
• two versions are simultaneously marked effective for the same population.

Some temporal differences can be reconciled by satisfying the earlier deadline or longer retention period. But that approach is not always lawful or operationally sound. Earlier disclosure may violate confidentiality. Longer retention may violate a deletion obligation. The stricter-looking result is not automatically the correct one.

6. Threshold contradictions

Different boundaries can classify the same case differently

Threshold contradictions arise when rules use incompatible amounts, percentages, scores, ages, durations, or qualitative levels to control the same decision.

One rule may require board approval at $1 million while another reserves board approval for amounts above $2 million and assigns the lower range elsewhere. A system may define “high risk” as a score of 70 while policy defines it as 80.

Not every stricter threshold is contradictory. A lower internal review threshold may supplement an external minimum. Contradiction exists when the thresholds assign incompatible authority, rights, consequences, or classifications in the same range.

Threshold analysis should control comparison operators, units, aggregation, currency, measurement sources, rounding, and boundary inclusion.

7. Scope contradictions

Rules can conflict over who or what is governed

Scope contradictions occur when one rule includes a category that another excludes, or when responsibilities overlap without a coherent allocation.

Examples include:

• one policy covers contractors while another states that contractors are excluded from the same control;
• two departments are each assigned exclusive ownership of the same approval;
• a global rule applies to all subsidiaries while a local rule declares the entity outside the enterprise policy;
• a procedure treats a system as in scope while the governing inventory treats it as out of scope.

Scope contradictions can produce both duplication and gaps. When two actors are exclusively responsible, each may wait for the other. When two rules exclude the same case through different boundaries, no rule may govern.

8. Authority contradictions

Rules may conflict because different authorities claim control over the same decision

Authority contradictions arise when rule sources assign incompatible powers, duties, or priorities. A local rule may authorize conduct that enterprise policy prohibits. A policy may assign an exception to one officer while a contract reserves the decision to another party.

Resolution requires more than comparing wording. The institution must determine which authority is superior, which is specific, whether delegation exists, and whether either rule exceeds its source.

An unauthorized rule may create operational conflict without creating a valid normative conflict. The correct response may be withdrawal of the unauthorized rule rather than substantive compromise.

9. Self-contradictions

A single rule or provision can defeat itself

Self-contradiction occurs when one rule contains incompatible commands, conditions, definitions, or consequences.

A policy may state that every exception requires prior approval, then authorize retroactive emergency approval without distinguishing the emergency path. A rule may require immediate reporting but prohibit reporting until an investigation is complete. A definition may include and exclude the same category through nested clauses.

Self-contradiction can also arise through impossible condition structure. A rule may apply only when a case is both classified and unclassified, or require an actor to approve a decision from which that actor is prohibited from participating.

Because all elements appear under one heading, self-contradictions are often overlooked during document-level review.

10. Exception-created contradictions

An exception can create conflict when its relationship to the general rule is incomplete

Exceptions are supposed to determine when the general rule yields. They create contradiction when their scope, authority, priority, or effect is unclear.

Common failures include:

• the exception permits conduct that a superior rule still prohibits;
• two exceptions apply to the same case and direct different results;
• the exception removes an obligation but leaves a dependent deadline active;
• the exception is copied without the compensating control that made it acceptable;
• the general rule is amended but the exception retains obsolete conditions.

Exception analysis should treat the exception as a rule with its own authority, actor, conditions, effect, duration, evidence, and relationship to the general rule.

11. Stricter and weaker rules

Difference in strictness is not sufficient proof of contradiction

One of the most common analytical errors is to label every stricter rule a contradiction. An internal policy may require review at a lower threshold than law. A contract may impose a longer retention period than general policy. A safety standard may exceed the regulatory minimum.

These differences may be cumulative rather than incompatible. The actor can satisfy both by meeting the stricter requirement.

A true contradiction arises when:

• the stricter rule prohibits conduct that superior authority affirmatively requires or protects;
• the stricter rule exceeds the issuer's authority;
• the stricter rule makes compliance with another obligation impossible;
• the rules assign incompatible decision authority or consequence;
• the additional burden defeats a protected right or required outcome.

The proper classification may therefore be “stricter but compatible,” “weaker and noncompliant,” “subsumed,” or “genuinely contradictory.”

12. Semantic contradictions

Rules can contradict because they assign different meanings to the same term

Semantic contradictions arise when shared vocabulary, classifications, or modalities are inconsistent.

One rule may define “business day” to exclude local holidays while another uses the term to mean Monday through Friday. One policy may define “customer” to include former customers while another excludes them. A system may interpret “may” as permission while a report treats it as an obligation.

These contradictions can be more dangerous than direct textual conflict because the rules appear compatible until applied. Vocabulary governance, controlled definitions, and test cases are essential.

13. Implementation contradictions

The rule in operation may contradict the rule in authority

Implementation contradictions occur when procedures, forms, training, workflow, code, configuration, or human practice applies a materially different rule from the approved source.

Examples include:

• policy permits an exception but software offers no exception path;
• contract uses calendar days while workflow counts business days;
• procedure assigns approval to a role different from the policy owner;
• system logic blocks conduct that policy permits;
• training tells employees to ignore a rule that remains formally effective.

Implementation contradiction is not resolved merely by stating that the document controls. The operational behavior must be corrected, historical effects assessed, and traceability restored.

14. Contradiction detection

Detection requires comparison across meaning, context, authority, and implementation

Keyword matching can identify candidate conflicts, but reliable detection requires structured comparison.

Detection should operate across documents and system layers. Contradictions often exist between policy and procedure, law and contract, contract and workflow, enterprise rule and local configuration, or approved rule and informal practice.

Candidate detection should be separated from final determination. Automated tools may surface likely conflicts; accountable human review should confirm context, authority, and materiality.

15. Classification and materiality

Not all contradictions create the same degree of institutional risk

Classification supports governance by distinguishing contradictions that require immediate intervention from those that can be documented and reviewed through ordinary change processes.

Materiality may consider:

• authority level;
• legal, safety, financial, ethical, or rights impact;
• number of affected decisions or actors;
• whether compliance with both is impossible;
• whether a protected right or mandatory obligation is at stake;
• whether a valid priority rule already resolves the conflict;
• whether the contradiction is operationally active;
• whether evidence and reversibility exist.

Classification should not substitute for reasoning. A label must be supported by a recorded comparison of authority, scope, conditions, and consequences.

16. Resolution methods

Contradictions should be resolved by restoring coherent authority and meaning

Resolution may involve:

• applying an existing hierarchy or priority rule;
• clarifying scope, definitions, or timing;
• amending or withdrawing the lower rule;
• revising both rules to preserve their legitimate purposes;
• creating a lawful exception or reconciliation path;
• renegotiating contract terms;
• seeking authoritative legal or regulatory interpretation;
• correcting implementation while preserving the approved rule;
• suspending application until the conflict is resolved.

Resolution should identify the controlling authority, affected versions, implementation changes, historical cases, communication, tests, and effective date. Editing one document is insufficient when the contradiction has propagated into systems and decisions.

17. Visible unresolved contradictions

Some contradictions cannot be resolved immediately, but they should never disappear from view

Legal interpretation may be pending. Contract amendment may require negotiation. Multiple authorities may disagree. An operational workaround may be necessary while a system is changed. In such cases, forcing a premature resolution may be less responsible than preserving the contradiction openly.

An unresolved contradiction record should identify:

• the conflicting rules and exact provisions;
• the overlapping case;
• authority and materiality analysis;
• interim decision or control;
• affected populations and systems;
• owner and escalation authority;
• review date and resolution dependency;
• evidence of decisions made under the interim position.

Visibility is an integrity control. It prevents temporary ambiguity from becoming invisible institutional practice.

18. Governance and escalation

Contradiction governance should separate detection, determination, and decision authority

The person or system that detects a contradiction may not have authority to resolve it. A governance model should distinguish:

• candidate detection;
• semantic and contextual analysis;
• authority determination;
• materiality classification;
• interim operational control;
• formal resolution authority;
• implementation and verification;
• closure and historical preservation.

High-materiality contradictions may justify blocking adoption or implementation. Others may proceed with documented acceptance, compensating controls, or visible unresolved status. The correct governance rule depends on authority, risk, feasibility, and institutional mandate.

19. Common failure cases

Contradictions persist when institutions compare documents instead of rule systems

20. Contradiction review

Twenty questions for contradiction integrity

1. 01

   Candidate rules

   Which exact rule expressions or implementations appear incompatible?

2. 02

   Actor

   Do the rules govern the same actor, role, entity, or system?

3. 03

   Action

   Do they direct the same action, opposite actions, or mutually exclusive outcomes?

4. 04

   Modality

   Are the statements obligations, permissions, prohibitions, recommendations, or rights?

5. 05

   Conditions

   Do their activation conditions overlap in at least one realistic case?

6. 06

   Scope

   Do they govern the same subject, population, jurisdiction, location, and system?

7. 07

   Time

   Are both rules effective for the same event or decision period?

8. 08

   Definitions

   Do shared terms carry the same meaning?

9. 09

   Thresholds

   Are units, operators, aggregation, and boundary inclusion aligned?

10. 10

    Authority

    What valid source created each rule?

11. 11

    Priority

    Does superiority, specificity, chronology, or express exception resolve the conflict?

12. 12

    Joint satisfaction

    Can an actor comply with both without defeating either rule's purpose?

13. 13

    Strictness

    Is the difference merely stricter, or does it create true incompatibility?

14. 14

    Implementation

    Does procedure, system, training, or practice contradict the approved rule?

15. 15

    Materiality

    What rights, safety, legal, financial, operational, or ethical interests are affected?

16. 16

    Frequency

    How many real or foreseeable cases fall within the overlap?

17. 17

    Interim control

    What governs while resolution is pending?

18. 18

    Resolution authority

    Who has power to clarify, amend, waive, suspend, or withdraw the relevant rule?

19. 19

    Propagation

    Which documents, systems, tests, training, and historical decisions are affected?

20. 20

    Closure evidence

    Can the institution prove that the contradiction was resolved across every relevant layer?

21. Worked examples

Distinguishing contradiction from legitimate difference

Conclusion

Contradiction analysis is the discipline of proving incompatibility

Rules differ for many legitimate reasons. They may arise from different authority, govern different populations, apply at different times, impose cumulative controls, or establish specialized treatment for narrower cases.

A genuine contradiction exists only when the same relevant case remains governed by incompatible rules after authority, scope, conditions, time, definitions, exceptions, and priority are considered.

Detecting contradiction is therefore not enough. Institutions must classify materiality, establish interim control, identify resolution authority, propagate corrections through implementation, and preserve unresolved conflicts visibly when immediate resolution is not possible.