Moves components into live use when they are new or changed, whether hardware, software, documentation, processes or anything else, and can also deploy into test or staging environments. It works hand in hand with release management and change control while remaining a practice in its own right (infrastructure provisioning included). Approaches include: phased deployment, covering one part of the environment at a time; continuous delivery, where components are integrated, tested and deployed as needed; big bang deployment to every target together where dependencies demand it; and pull deployment, where users fetch components from a controlled repository when they choose. Components are kept in a definitive media library or repository under tight access control and in secure environments. Improvements may call for deployments planned like any other; deployment is an essential part of design and transition; and in obtain/build, changes go out in increments, particularly where automated DevOps toolchains handle continuous integration, delivery and deployment.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.