1. Purpose of the gate
This gate opens Broad Deployment. It changes the step from something one supported project uses into something any eligible team can pick up, often without the close attention the first project received. That change is where many adoptions quietly lose their controls: documentation drifts away from the flow, users skip training because a colleague showed them, licences run short near a busy milestone, and the production environment differs in small ways from the one security approved.
The gate therefore checks four things that make the step safe to scale. The production flow release is under configuration control, so every team runs the same locked versions. User training exists and is a condition of access, not a suggestion. Licence and compute capacity are planned for the expected users. The production environment is approved by information security, not assumed to match the first project's.
Two decisions are frozen here. Rollout scope, taken at this gate, sets how widely the step is released and whether it is optional or the new default. Licence and capacity model, worked out as Broad Deployment is prepared, sets how capacity is bought and allocated.
10 more sections for registered members.