Skip to content

Enterprise release orchestration

Trigger

Multiple products/platforms/suppliers must release into a shared business/technology environment and need one dependency, readiness and go/no-go process.

Intended outcome

The integrated release is sequenced, independently readiness-checked, authorised, executed by technical owners, validated and closed with measurable release performance.

Workflow steps and gates

Step Accountable role Activity Handover Gate
1 Enterprise Release Manager builds integrated release scope/calendar and identifies cross-system dependencies/blackouts integrated release calendar All material releases and blackout/business constraints are represented
2 Architecture Repository and Modelling Lead validates technical/service dependency graph and critical sequencing constraints release dependency register No critical dependency is missing an owner or sequence
3 Organisational Change and Adoption Manager validates communications/training/adoption/business readiness for affected cohorts business readiness Affected business cohorts have executable readiness actions/evidence
4 Data Migration and Cutover Lead validates cutover sequence, data reconciliation, checkpoints and abort criteria cutover readiness Cutover and data reconciliation are rehearsed/evidenced for critical transitions
5 SIAM Manager validates supplier staffing, dependencies, handoffs and escalation readiness supplier readiness No critical supplier dependency is relying on informal availability
6 Release Engineer validates technical release artefacts, provenance and executable rollback technical/rollback readiness Release artefacts are traceable and rollback is exercised/feasible
7 Secure Delivery / DevSecOps Architect checks that release provenance, pipeline controls, policy-as-code and software supply-chain evidence conform to the approved secure-delivery architecture secure delivery readiness evidence Critical secure-delivery controls and provenance are evidenced; deviations are owned, time-bound and visible to independent release assurance
8 Release Quality Gatekeeper independently checks mandatory release criteria and evidence release gate assurance Producer cannot waive its own failed critical gate
9 Enterprise Release Manager issues delegated integrated go/no-go or routes decision to higher authority go/no-go decision Decision cites evidence, waivers, residual risk and abort triggers
10 Release Engineer executes the authorised technical release through controlled pipelines release execution evidence Executed artefacts/plan match what was approved
11 Site Reliability Engineer monitors agreed technical/service signals and triggers reversal if thresholds breach technical post-release validation Rollback/reversal triggers are acted on, not debated after breach
12 IT Service Owner confirms business/service outcome and closes or escalates residual issues release acceptance Closure states outcome, impact, residual issues and owners

Running this workflow: operator and implementer boundary

In Claude Code or Codex CLI, use the prompt in the next section (or adapt it to your programme): it is a provider conversation request, not a shell program named after this workflow. You supply the source materials, actual owners, gate acceptance and any authorisation for changing real systems. The provider agent interprets the registered workflow stages and role contracts, calls supported tools if allowed, and returns explicit evidence and blockers. Stage completion in the diagram or metadata is not proof of a successful external tool call, an approved exception or a released system.

For consequential decisions explicitly start /layered (Claude) or $workflow-layered (Codex); this version does not force every direct/natural-language workflow invocation into Fabric. Human L0 authority remains separate, with Codex requiring the actual human to run any protected authority command in a trusted terminal. See the interaction model, layered engagement and human authority.

How to use this workflow

A practical prompt pattern is:

Apply the enterprise-release-orchestration workflow to this situation. For each step, identify the current state, accountable role, required evidence, hand-over artefact, gate status and unresolved blocker. Do not skip a gate merely because the implementation is technically complete.

Operational interpretation

The workflow is most useful when the team keeps each hand-over explicit. The system can help generate or review the artefacts, but the accountable role and approval decision remain organisational responsibilities.