Task: Develop project porting and handoff to the owner
Develop project porting and handoff to the owner
Formulate a practical criterion for the absence of infrastructure lock-in: the project can be handed over to the owner or another team as a working system.
The Problem
The ability to download a repository is too weak a criterion for portability. A real project includes code, data, files, runtime, configuration, external dependencies, and knowledge required for operations.
If a client transfers a website to a service provider for maintenance, the service must not make the project's continued existence dependent on itself solely for customer retention.
What to Investigate
It is necessary to determine what must be available to the owner for a real exit: what artifacts, state, instructions, and accesses allow another specialist or agent to reproduce and continue maintaining the system.
At the same time, portability does not mean that any project must run on any hosting without changes. The criterion must distinguish normal technological dependencies from artificial vendor lock-in.
Related to project state, runtime, secrets and external dependencies, and backup/restore.