Puts new and changed services and features into users' hands; a release means a group of CIs, or a version of one service or other CI, made available in this way. In traditional settings, releases follow a plan and schedule agreed with customers, with pilots and reviews. In Agile and DevOps settings, deployment and release are kept apart: small, frequent releases use blue/green environments or feature flags, so functionality is deployed first and switched on for users through configuration, and release management still makes sure that user guides, training, release notes, documentation, support scripts and known errors are all ready. Strategy and the portfolio supply policies, guidance and timelines; improvements are released through the same route; content and pace suit customer and user needs; services become available in a controlled way during transition; component changes are bundled into releases; and delivery is given what it needs to restore service.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.