Requirements for data portability are documented and approved and a viable exit plan established; a risk assessment grades the criticality of data and processes to scope portability and exit planning; architectural standards state how solutions move data and processing away from one provider, either to another provider or back on-premises; data portability plans are created, tested and approved; and an exit plan for each provider is created, tested and approved. Contracts give the right to obtain a copy of data on demand and have the provider's copies deleted with confirmation; standards favour open formats, provider-neutral transfer tools, bulk snapshot export and industry-standard interfaces, and flag proprietary components that would need rebuilding; plans cover privacy and security in transit, consent and legal constraints, metadata migration, reconciliation of completeness, and alignment with continuity and recovery plans, with test results persisted and approved.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.