Resolve contradictions at the principle level once — re-adjudicating at each tactical decision multiplies decision cost

Why This Is a Rule

When two values or commitments conflict, you can resolve the conflict once at the principle level or repeatedly at every tactical decision where the conflict surfaces. If "speed" and "quality" conflict in your engineering organization, resolving it at the principle level ("we optimize for quality up to the point where release cadence exceeds 2 weeks") gives every downstream decision a clear precedent. Leaving it unresolved at the principle level means every feature decision, every code review, every sprint planning meeting re-litigates the speed/quality trade-off from scratch.

This is decision amortization: the cognitive cost of resolving a contradiction once at the strategic level is paid once and applied many times. The cost of re-adjudicating at the tactical level is paid at every decision point, accumulating linearly with the number of decisions. For a contradiction that surfaces weekly, principle-level resolution saves 50+ redundant decision cycles per year.

The abstraction hierarchy matters. Tactical resolution ("we'll prioritize quality for this feature") doesn't prevent the same debate next week for the next feature. Strategic resolution ("our principle is X") provides a default that applies unless specific circumstances warrant an exception — which is itself a faster decision than the full re-adjudication.

When This Fires

• When the same trade-off debate keeps recurring in team meetings or personal decisions
• When you notice decision fatigue concentrated around the same set of competing values
• When a contradiction is consuming tactical decision bandwidth rather than being resolved once
• During organizational design when establishing decision-making principles

Common Failure Mode

Resolving contradictions tactically and assuming the resolution holds: "We chose speed over quality for the last release, so we've resolved this." You haven't — you've made one tactical decision. The contradiction persists and will demand re-adjudication at the next decision point. Only principle-level resolution creates a reusable default.

The Protocol

(1) When you notice the same trade-off recurring across multiple tactical decisions, flag it as a principle-level contradiction. (2) Escalate the resolution to the appropriate level: personal principles, team operating agreements, or organizational strategy. (3) Articulate the principle as a clear, general statement with scope conditions: "When X and Y conflict, we prioritize X unless [specific exception conditions]." (4) Document and communicate the principle so downstream decision-makers can apply it without re-adjudicating. (5) Periodically review the principle — strategic context changes, and what was the right resolution last year may need updating.