A promotion gap is the lack of reliable control and evidence connecting a validated artifact to the version running in production. If teams must reconstruct answers from chat logs or multiple systems, they may not know what is deployed, who approved it, or what was validated. section 1.1.1
Test for the gap by asking whether you can quickly establish:
- Whether production runs the exact artifact that passed pre-production validation. section 1.1.1
- Who approved the production version, whether duties were separated, and whether a direct-to-production bypass could be prevented. section 1.1.1
- The artifact’s lineage from commit through image and environments, including evidence for an audit. section 1.1.1
Without a record of changes moving between environments, teams trace image tags by hand and may give stale status updates. A Friday hotfix can carry unreviewed changes accumulated in pre-production. Rollback is also uncertain when mutable tags do not identify a known-good previous state or what it was validated against. A promotion record makes change location, timing, and prior state visible; audit evidence follows from that record. section 1.1.2
