Contradiction Resolver

Layer 1 · Principles

• Frameworks are tools, not truths. When they clash, the human chooses. No framework is universally correct. Each optimizes for something specific and sometimes those somethings conflict. Pretending one framework is always right produces worse outcomes than accepting that context determines the winner.
• A named trade-off beats an unconscious contradiction every time. Most stuck decisions are actually unnamed contradictions. You know something is off but cannot articulate what. Naming the specific conflict turns paralysis into a choice. The choice might still be hard, but now it can be made.
• The resolution itself becomes reusable knowledge. Each ruling is a precedent. Over time, your documented resolutions become a personal framework hierarchy that prevents re-fighting the same conflict. The log is more valuable than any single ruling.

Layer 2 · Systematic Approach

Four-step resolution protocol

1. Identify the exact contradiction. Write the two opposing recommendations side by side. One sentence each. If you cannot state them cleanly in parallel, the contradiction may be imagined; re-read the frameworks' actual outputs before continuing.
2. Name the core trade-off. For each framework, identify what it is optimizing for. Speed vs. accuracy. Resilience vs. leverage. Short-term clarity vs. long-term flexibility. The trade-off is usually a pair of values that are both good but in tension.
3. Choose the hierarchy for this context. Which value wins here, and why? The why matters. 'Because speed matters more for this specific decision under current constraints' is a real reason. 'Because I feel like it' is not, and the ruling won't survive review.
4. Document the ruling. Record the decision in a personal framework hierarchy log. Include: what the contradiction was, what you chose, the reason, and whether this ruling is specific to this context or general. Over time these rulings form your personal decision constitution.

Layer 3 · Force Multipliers

• Framework hierarchy as compounding asset Every ruling adds to your personal hierarchy. After a year of use, you have a documented set of precedents that resolve most recurring contradictions automatically. New users of your framework library can read your hierarchy and absorb your judgment without having to re-derive it. For teams or individuals with 10+ frameworks in active use, a hierarchy log typically eliminates most recurring contradictions within six months, freeing up decision capacity for novel conflicts.
• Contradictions become learning moments Treating framework conflict as information rather than a bug reframes the experience entirely. The contradiction is telling you something important about the boundary conditions of both frameworks. That information is usually more valuable than the decision the framework is being asked to make.
• Unlocks framework libraries at scale Below about five frameworks, contradictions are rare enough to resolve ad hoc. Above that, conflicts compound and unmanaged libraries produce decision paralysis. This framework is the load-bearing protocol that lets a library grow past the ad-hoc ceiling.

Layer 4 · Success Metrics

Leading indicators

• Every run produces a side-by-side statement of the two recommendations.
• The core trade-off is named in terms of values, not just actions.
• The ruling is documented with its reasoning.

Lagging indicators

• Recurring contradictions decrease over months of use as precedents accumulate.
• Decision paralysis on multi-framework sessions drops measurably.

Failure modes

• Premature resolution
• Universal precedent

Do not use when

• Only one framework is actually firing. Before running, confirm both frameworks really apply.
• The frameworks agree on the action but disagree on the reasoning. That is not a contradiction; that is a bonus.

Layer 5 · Implementation

Required to start

• Two frameworks that have both fired and produced different recommendations.
• Eight to twelve uninterrupted minutes.
• A place to record the ruling for future reference.

Works best with

• An existing hierarchy log where previous rulings live.
• A second person to review the ruling before it gets filed.

You are done when

• Side-by-side statement of the two conflicting recommendations.
• A named trade-off in terms of values.
• A ruling with a written reason.
• The ruling filed in your hierarchy log.

Where to use it

• Personal framework library maintenance When your own library of thinking tools has grown past five or six frameworks and conflicts are starting to emerge, this becomes the weekly or monthly discipline that keeps the library coherent.
• Team decision-making When team members champion different frameworks on the same problem. The protocol surfaces that the disagreement is about values, not facts, which usually changes the conversation.
• Stalled progress debugging When a project or decision has been stuck for days with no clear cause, there is often a hidden framework contradiction underneath. This framework surfaces it.