The Principle
The interoperability principle defines the minimum conditions under which diverse organizations can cooperate productively without requiring assimilation. It is the enterprise-level distillation of OO's method: participants are not required to agree on everything — they are required to make their disagreements legible, their claims testable, and their exit terms clear.
The Three Requirements
Legible Disagreement
Participants must state their positions in terms that other participants can evaluate. This means: the claim is specified, the evidence is cited, the reasoning is traceable, and the conditions under which the claim would be revised are named. Disagreements that meet this standard can be resolved through method. Disagreements that do not meet it cannot be resolved at all — they can only be managed through power.
The standard does not require participants to share the same analytical framework. It requires that each framework be transparent enough that participants using different frameworks can identify where their analyses diverge — and evaluate whether the divergence is a matter of evidence, method, or values.
Testable Claims
Participants must commit to making claims that can, in principle, be verified or falsified. A participant that makes claims immune to testing — "our approach is superior because it aligns with our values" — has opted out of the methodological framework. The claim may be true. But it cannot be evaluated by other participants, which means it cannot serve as a basis for cooperative decision-making.
Testability does not require that every claim be immediately testable. It requires that the participant can specify what evidence would confirm or disconfirm the claim, and what timeline would be appropriate for evaluation. This is contextual certainty (2.2.1) applied to organizational claims.
Clear Exit
Participants must know the terms under which they can leave the cooperative arrangement — and those terms must not include penalties disproportionate to the benefits the participant received. Exit that is formally available but practically punitive is not meaningful exit. It is a structural vulnerability the interoperability principle is designed to rule out — not, by itself, proof that the arrangement has become coercive.
Clear exit requires three specifics: what happens to the departing participant's contributed data, what happens to their contractual obligations, and what (if any) transition period applies. These terms are published at the time of entry, not negotiated at the point of departure.
The Test
A cooperative arrangement that meets the interoperability principle permits diverse organizations to work together while maintaining the capacity for each to evaluate, challenge, and — if necessary — leave. It does not guarantee good outcomes. It guarantees that bad outcomes can be identified and corrected without requiring any single participant to surrender their judgment to the collective.
This is OO's method at its most demanding application: the commitment that reason, not power, governs the terms of cooperation — even when the participants disagree about nearly everything else.
Change Log
- 27 Aug 26 — Corrected a structural-coercion phrasing instance: recast "coercion with an option clause" as a structural vulnerability, not proof of coercion by itself.
- 18 Mar 26 — Standardized capitalization of the toolkit name "interoperability principle" throughout.
- 17 Mar 26 — Initial publication.