Data Portability Rule¶

Exit-right rule — instantiates Network Effect Governance

Requires that a participant can export their own data — and, where it applies, their reputation and connections — in a usable, machine-readable format, so leaving costs no more than the network's value honestly justifies.

A Data Portability Rule establishes the right and the format obligation to take your accumulated value with you when you leave. A network becomes sticky partly because it holds your history — your transactions, your content, your ratings, your connections — and that accumulation can be either honest value or a hostage. The rule draws the line: whatever you contributed or earned must be exportable in a usable, machine-readable form, so that switching costs reflect what the network is genuinely worth rather than an artificial wall built from your own data. Its defining move is to preserve the departing participant's accumulated value at the moment of exit — the difference between legitimate stickiness and coercive lock-in.

Example¶

A retail-bank customer wants to move to a competitor but a decade of transaction history, standing orders, and payee lists lives inside the old bank's app. Under a data portability rule the bank must hand that data over in a defined, machine-readable format within a set window — not as a scanned statement, but as structured records the new bank can ingest. The customer's accumulated financial history follows them, and the switch turns on which bank is better rather than on who is holding the ledger, in the spirit of the data-portability right in modern privacy law.^[1]

How it works¶

Define the exportable dataset. Draw the boundary of "your" data — clearly your inputs, and, where it applies, the derived records (ratings, reputation) that carry your value.
Mandate a usable format. A documented, machine-readable, ideally standardized format the receiving system can actually consume — not a technically-compliant dump.
Set delivery terms. A method and a timeframe, so the right is exercised in days rather than negotiated indefinitely.
Scope relational data. Where reputation or connections are part of the value, specify whether and how they transfer, since these are the hardest and most lock-in-relevant to move.

Tuning parameters¶

Dataset scope — raw inputs only, or the derived and inferred data too; the derived data is usually what actually creates the switching cost.
Format standardization — a bespoke export versus an industry-standard schema the destination can read without custom work.
Delivery latency — how fast the export must be produced; slow delivery quietly re-imposes the lock-in the rule was meant to remove.
Reputation and graph inclusion — whether earned standing and connections travel, and under what consent and privacy constraints.
One-off vs continuous — a single export on request versus standing programmatic access.

When it helps, and when it misleads¶

Its strength is that it converts a theoretical exit into a real option, which disciplines lock-in even for participants who never leave: the credible threat is enough. Its failure mode is malicious compliance — a conformant export that is unusable (a giant unstructured file), or one that returns raw inputs while withholding the derived data that held the real value, so the right is satisfied and the captivity survives. Portability of data without portability of identity or reputation still traps people who built their standing on the network. The discipline is to require a documented, re-importable format and to scope the dataset by what actually creates switching cost, not by what is cheapest to hand over.

How it implements the components¶

portability_and_exit_path — the export-and-reuse right in a usable format is precisely this component: it makes leaving more than theoretical.
network_value_invariant — by carrying the participant's accumulated value out intact (relationship continuity and reputation where appropriate), it preserves what remains valuable to them, so exit doesn't destroy it.

It states what must be exportable; it does not build the tools that move it — that's Switching Support Tooling — nor provide live cross-vendor interfaces (that's Interoperability Mandate), nor measure whether participants are captive (that's Competition or Antitrust Remedy).

Instantiates: Network Effect Governance — it supplies the exit-governance that keeps network value from curdling into lock-in.
Sibling mechanisms: Switching Support Tooling · Interoperability Mandate · Competition or Antitrust Remedy · Open Standard · Service-Level Commitment

Notes¶

A portability right without tooling is often dead on arrival: it names what must be exportable, but a participant still has to actually move it. Switching Support Tooling is what turns this right into a path someone walks — the two are designed to be paired, one setting the obligation and the other reducing the effort.