Exit and Interoperability Rule¶
Document — instantiates Malleability Window Governance
Requires portability, migration paths, or alternative access so stakeholders are not trapped before consequences are known.
The Exit and Interoperability Rule is a binding clause written into procurement or adoption contracts requiring that, from day one, a system support portability (standard data export), interoperability (open, documented interfaces), and a defined migration or alternative-access path. It is a document, not an instrument: its job is to make exit contractually and technically available before anyone knows whether they will need it, so that stakeholders keep a real way out during the window when consequences are still unknown. It says nothing about whether lock-in is actually accruing and nothing about when reversal becomes infeasible — it simply guarantees, in writing and by design, that the door was built and kept unlocked.
Example¶
A school district is adopting a learning-management platform for 40,000 students. Before signing, it writes an exit-and-interoperability rule into the contract: student records must be exportable on demand in an open, documented standard; the gradebook and roster interfaces must be open and versioned; and the district must run a tested migration drill each year, moving a live sample of data to a second, unrelated platform. Eighteen months later, when the incumbent vendor proposes a steep renewal price, the district can credibly threaten to leave — not because it wants to, but because portability was contractually guaranteed and, crucially, drilled, so the alternative is real rather than notional. The rule preserved a bargaining position that a normal contract would have quietly surrendered.
How it works¶
- Front-loads exit into the acquisition document. Portability, open interfaces, and a migration path are contract preconditions, not features requested later.
- Specifies formats, interfaces, and owners. "Exportable" is pinned to a named open standard; the migration path names who executes it and to where.
- Mandates drills, not just clauses. A periodic, tested migration proves the exit works instead of merely asserting it.
- Ties renewal to continued compliance. Losing portability is grounds to withhold payment or renewal.
Tuning parameters¶
- Strictness of standard — a named open standard versus "some export capability." Stricter guarantees real portability but narrows the vendor field and raises price.
- Drill cadence — how often migration is actually tested. Frequent drills keep exit real but cost staff time and vendor cooperation.
- Scope — data portability only, or full functional migration. Broader scope preserves a more complete exit but is far harder to specify and enforce.
- Enforcement teeth — advisory clause versus payment-withholding. Harder teeth make the rule bite but complicate the commercial relationship.
When it helps, and when it misleads¶
Its strength is keeping a genuine exit — a real alternative to depend on — alive through the period when consequences are still unknown, which is exactly when option value is highest. Its failure mode is symbolic exit: a portability clause that is never drilled, so migration is permitted on paper but impossible in practice. Data-portability rights in law show the same trap — a right to move one's data means little without the tooling and formats to actually move it[n1] — which is why the rule mandates drills, not just entitlements. A classic misuse is accepting a proprietary "export" format that is technically compliant but practically unusable. The guarding discipline is to fund and run the migration drill on a real sample, treating an undrilled exit as no exit.
How it implements the components¶
interoperability_and_exit_requirement— the core clause: open export formats, documented open interfaces, and a named, tested migration or alternative-access path.option_preservation_buffer— the preserved fallback the rule keeps alive: a second vendor or manual path that stays viable because portability was guaranteed and drilled.
It builds and guarantees the exit but does not watch whether dependency is rising — the running lock_in_cost_monitor is Deployment Impact Dashboard's — nor forecast when the exit becomes infeasible, which is rollback_and_redesign_pathway's executability test in Reversibility Horizon Review.
Related¶
- Instantiates: Malleability Window Governance — the rule is how the archetype's "reversibility before scale" invariant is written into contracts.
- Sibling mechanisms: Adaptive Stage-Gate Protocol · Collingridge Curve Workshop · Deployment Impact Dashboard · Pause or Moratorium Trigger Protocol · Post-Pilot Lock-In Audit · Regulatory or Operational Sandbox · Reversibility Horizon Review · Stakeholder Harm Reporting Channel · Sunset Clause with Renewal Hearing
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Exit and Interoperability Rule operates as a standing rule, threshold, contractual commitment, or policy constraint governing future conduct because it requires portability, migration paths, or alternative access so stakeholders are not trapped before consequences are known.
Independent corroboration: The frozen evidence defines Exit and Interoperability Rule as 'Requires portability, migration paths, or alternative access so stakeholders are not trapped before consequences are known', so its operative form is Rule, Policy & Commitment.
Nearest alternative: Representation, Specification & Plan — Portability and migration requirements are binding acquisition and renewal constraints, while the document is their specification.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Ethics of Technology & AI Governance
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Mandated portability and exit to prevent technological lock-in is characteristic contemporary platform and technology governance.
Related originating lineages:
- Computer Science & Software Engineering — Open standards and interoperability engineering materially supply the technical migration mechanism.
- Law & Governance — Competition, consumer-protection, and data-portability law materially supply enforceable exit rights.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Independent reviewer agreement; medium confidence.
Notes¶
[n1] The right to data portability under the EU's GDPR (Article 20) entitles people to receive their data in a "structured, commonly used and machine-readable format." It is a real illustration of the rule's core lesson: a portability right is only as real as the formats and tooling that make moving actually feasible — which is why this mechanism mandates drills, not just entitlements. ↩