Differences

This shows you the differences between two versions of the page.

--- dido:99_annexes:annex-b-terms-and-definitions:i:image_promotion [2026/07/13 12:10] – created nick_dido
+++ dido:99_annexes:annex-b-terms-and-definitions:i:image_promotion [2026/07/17 08:48] (current) – nick_dido
@@ Line 1: / Line 1: @@
 ====== Image Promotion ======
-[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
+[[dido:99_annexes:annex-b-terms-and-definitions:start|Go to Terms and Definitions]]
 ===== Discussion =====
-Image Promotion is the controlled transition of a [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]] from one lifecycle status, usage scope, or operating context to another.
+Image Promotion is a controlled [[dido:99_annexes:annex-b-terms-and-definitions:l:lifecycle|Lifecycle]] transition that changes the promotion state of an identified [[dido:99_annexes:annex-b-terms-and-definitions:i:image|Image]] after the Image satisfies the applicable transition criteria.
-The transition may authorize the image for broader testing, staging, production deployment, a different organizational domain, or another approved environment.
+Image Promotion may progress an Image through states associated with:
-Image Promotion evaluates the applicable build records, test results, compliance findings, integrity information, provenance, approvals, and target-context requirements before changing the image status.
+  * Building
+  * Evaluation
+  * Testing
+  * [[dido:99_annexes:annex-b-terms-and-definitions:i:image_signing|Image Signing]]
+  * [[dido:99_annexes:annex-b-terms-and-definitions:d:digital_signature_verification|Digital Signature Verification]]
+  * Compliance assessment
+  * Approval
+  * Staging
+  * Release
+  * Publication
+  * Distribution
+  * Deployment authorization
+  * [[dido:99_annexes:annex-b-terms-and-definitions:r:retirement|Retirement]]
-The process changes the image's permitted use or governance status. It does not necessarily modify the image content.
+The applicable Image Promotion workflow defines:
+  * The promotion states
+  * The permitted transitions among promotion states
+  * The transition criteria
+  * The actor or process permitted to request a transition
+  * The actor or process permitted to authorize a transition
+  * The result of a successful transition
+  * The result of an unsuccessful transition
+  * The records and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] associated with the transition
+Transition criteria may include:
+  * Successful Image build
+  * Successful test execution
+  * Successful vulnerability assessment
+  * Successful compliance assessment
+  * A valid [[dido:99_annexes:annex-b-terms-and-definitions:d:digital_signature|Digital Signature]]
+  * Required approval
+  * Required Evidence
+  * Compatibility with a target environment
+  * Satisfaction of applicable release conditions
+Image Promotion differs from Image transfer:
+  * Image Promotion changes the promotion state of an Image
+  * Image transfer moves an Image between repositories, environments, or administrative domains
+Image Promotion differs from Image publication:
+  * Image Promotion authorizes or records a transition between promotion states
+  * Image publication makes an Image available through a repository or distribution mechanism
+Image Promotion differs from deployment:
+  * Image Promotion changes the status of an Image within its promotion Lifecycle
+  * Deployment uses an Image to instantiate or replace a computing subject
+An Image may be promoted without being deployed, and deployment may require the Image to occupy a specified promotion state.
 ===== Definition =====
-//controlled transition of a [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|machine image]] from one lifecycle status, usage scope, or operating context to another//
+//controlled [[dido:99_annexes:annex-b-terms-and-definitions:l:lifecycle|lifecycle]] transition that changes the promotion state of an identified [[dido:99_annexes:annex-b-terms-and-definitions:i:image|image]] after satisfaction of applicable transition criteria//
 ===== Source =====
-Generalized from release management, artefact management, software delivery, configuration management, and machine-image governance usage and specialized for the Crucible architecture and operational model.
+Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 ===== Note =====
-Image Promotion differs from copying or uploading an image. A transfer changes location or availability, while Image Promotion changes the image’s authorized status or permitted use.
+Image Promotion does not by itself define:
+  * The names or numbers of promotion states
+  * The order of all promotion states
+  * The transition criteria
+  * The approval authority
+  * The repository used to store the Image
+  * The mechanism used to record the promotion state
+  * The environments in which the Image may be deployed
+The applicable Image Promotion workflow or lower-level requirements define those details.
+Image Promotion should preserve, as applicable:
+  * The Image identifier
+  * The Image [[dido:99_annexes:annex-b-terms-and-definitions:r:revision|Revision]]
+  * The prior promotion state
+  * The resulting promotion state
+  * The applicable transition criteria
+  * The observed criteria results
+  * The requesting actor or process
+  * The authorizing actor or process
+  * The transition time
+  * The promotion result
+  * The resulting Evidence
+  * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
+  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
-A promoted image should retain the identity, integrity, information, evidence, and provenance associated with the evaluated image.
+Promotion of an Image does not modify the content of the Image. A content change produces a different Image or Image Revision, subject to its own evaluation and promotion.
 ===== Example =====
-After a [[dido:99_annexes:annex-b-terms-and-definitions:r:rhel]] p Hardened Image passes integration testing, compliance assessment, signature verification, and governance review, the organization promotes it from the test catalog to the production-approved catalog.
+A Container Image enters the **Built** promotion state after a successful build. After the Image passes required testing, compliance assessment, and Digital Signature Verification, an authorized workflow performs Image Promotion to the **Approved for Deployment** state.
 ----