dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-02-image-management:fr-img-006

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-02-image-management:fr-img-006 [2026/07/20 07:08] – ↷ Links adapted because of a move operation nick_didodido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-02-image-management:fr-img-006 [2026/07/30 05:42] (current) – nick_dido
Line 5: Line 5:
 ===== Statement ===== ===== Statement =====
  
-[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL promote an identified [[dido:99_annexes:annex-b-terms-and-definitions:i:image|Image]] from one defined promotion state to another after the Image satisfies the applicable transition criteria.+[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL perform [[dido:99_annexes:annex-b-terms-and-definitions:i:image_promotion|Image Promotion]] for an identified [[dido:99_annexes:annex-b-terms-and-definitions:i:image|Image]] after the Image satisfies the applicable transition criteria.
  
-===== Source Statement =====+===== Derived From =====
  
-> [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL perform [[dido:99_annexes:annex-b-terms-and-definitions:i:image_promotion|Image Promotion]] for an identified [[dido:99_annexes:annex-b-terms-and-definitions:i:image|Image]] after the Image satisfies the applicable transition criteria.+This requirement derives from:
  
-===== Source =====+  * Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-IMG-006
  
-Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-IMG-006.+The Original Requirement states:
  
-===== Assessment =====+> //[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL perform [[dido:99_annexes:annex-b-terms-and-definitions:i:image_promotion|Image Promotion]] for an identified [[dido:99_annexes:annex-b-terms-and-definitions:i:image|Image]] after the Image satisfies the applicable transition criteria.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]
  
-The source statement expresses the approved intent but does not provide a fully testable formulation.+The Original Requirement already identifies:
  
-The following Specification Discipline and Authoring findings apply:+  * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor 
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:i:image_promotion|Image Promotion]] as the required behavior 
 +  * An identified [[dido:99_annexes:annex-b-terms-and-definitions:i:image|Image]] as the subject 
 +  * Satisfaction of the applicable transition criteria as the condition for promotion
  
-  * **The system** does not use the defined system name +No substantive normalization is required.
-  * **shall** does not follow the established uppercase normative convention +
-  * **Support** is a weak verb that does not identify the required behavior +
-  * **Image promotion workflows** does not identify the Image being promoted +
-  * The source statement does not identify the states between which promotion occurs +
-  * The source statement does not identify the conditions governing a promotion transition +
-  * The source statement does not identify an observable promotion result +
-  * The source statement does not prescribe a particular state model, repository, release process, or implementation technology +
- +
-The normalized Statement: +
- +
-  * Replaces **The system** with [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] +
-  * Replaces **support** with the direct behavior **promote** +
-  * Identifies an Image as the subject of promotion +
-  * Identifies movement between defined promotion states +
-  * Requires satisfaction of applicable transition criteria before promotion +
-  * Retains one primary required behavior +
-  * Preserves implementation independence +
- +
-The normalized Statement does not prescribe the names or number of promotion states. The applicable promotion workflow defines those states and their transition criteria.+
  
 ===== Rationale ===== ===== Rationale =====
  
-Image promotion controls the progression of an identified [[dido:99_annexes:annex-b-terms-and-definitions:i:image|Image]] through defined states associated with evaluation, approval, release, distribution, or deployment.+[[dido:99_annexes:annex-b-terms-and-definitions:i:image_promotion|Image Promotion]] controls the progression of an identified [[dido:99_annexes:annex-b-terms-and-definitions:i:image|Image]] after the Image satisfies the criteria governing the applicable transition.
  
-Example promotion states may include:+The transition criteria determine whether the Image is eligible for promotion. Separate requirements, policies, or workflows define those criteria.
  
-  * Built +This requirement does not independently prescribe:
-  * Evaluated +
-  * Signed +
-  * Verified +
-  * Approved +
-  * Staged +
-  * Released +
-  * Available for deployment +
-  * Retired+
  
-The applicable workflow determines which states apply and which transitions are permitted. +  * Promotion states 
- +  * Signing criteria 
-Transition criteria may include: +  * Verification criteria 
- +  * Vulnerability-assessment criteria 
-  * Successful build completion +  * Compliance criteria 
-  * Successful digital-signature verification +  * Approval criteria 
-  * Successful vulnerability assessment +  * Publication criteria 
-  * Successful compliance assessment +  * Deployment criteria
-  * Required test results +
-  * Required approval +
-  * Required [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] +
-  * Compatibility with a target environment +
-  * Satisfaction of applicable release conditions +
- +
-FR-IMG-006 does not independently require any particular signing, testing, scanning, compliance, or approval criterion. The applicable lower-level requirement or promotion policy establishes each criterion. +
- +
-Controlled Image promotion contributes to: +
- +
-  * Prevention of unauthorized Image use +
-  * Consistent release decisions +
-  * Controlled Image distribution +
-  * Controlled Image deployment +
-  * Image-state visibility +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:a:auditability|Auditability]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]+
  
 ===== Applies To ===== ===== Applies To =====
Line 90: Line 48:
  
   * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]   * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
 +  * [[dido:99_annexes:annex-b-terms-and-definitions:i:image_promotion|Image Promotion]]
   * [[dido:99_annexes:annex-b-terms-and-definitions:i:image|Images]]   * [[dido:99_annexes:annex-b-terms-and-definitions:i:image|Images]]
-  * [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Images]] 
-  * [[dido:99_annexes:annex-b-terms-and-definitions:c:container_image|Container Images]] 
-  * Image identifiers 
-  * Image promotion states 
-  * Promotion-state transitions 
   * Transition criteria   * Transition criteria
-  * Image promotion workflows 
-  * Image repositories 
-  * Image release workflows 
-  * Image deployment workflows 
-  * [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipelines]] 
  
 ===== Verification ===== ===== Verification =====
  
-  - Verification SHALL confirm that the applicable Image promotion workflow defines at least two promotion states +Verification confirms that:
-  - Verification SHALL confirm that the applicable Image promotion workflow defines the permitted transition between the tested promotion states +
-  - Verification SHALL confirm that the tested transition identifies applicable transition criteria +
-  - Verification SHALL confirm that [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] promotes the identified [[dido:99_annexes:annex-b-terms-and-definitions:i:image|Image]] when the Image satisfies the applicable transition criteria +
-  - Verification SHALL confirm that Crucible does not perform the tested promotion transition when the Image does not satisfy the applicable transition criteria +
-  - Verification SHALL confirm that Crucible records the resulting promotion state+
  
-Verification may include: +  - An identified [[dido:99_annexes:annex-b-terms-and-definitions:i:image|Image]] is selected for promotion 
- +  - The applicable transition criteria are identified for the tested Image Promotion 
-  * Machine Image promotion testing +  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] performs Image Promotion after the identified Image satisfies the applicable transition criteria 
-  * Container Image promotion testing +  - Crucible does not perform the tested Image Promotion before the identified Image satisfies the applicable transition criteria 
-  * Successful-transition testing +  - The result of the tested Image Promotion can be determined
-  * Failed-transition testing +
-  * Transition-criteria inspection +
-  * Image-state inspection +
-  * Promotion-record inspection +
-  * Image-repository inspection +
-  * Promotion-log inspection +
-  * Automated [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]] testing +
- +
-The verification record SHALL identify: +
- +
-  - The promoted Image +
-  - The Image identifier +
-  - The initial promotion state +
-  - The requested promotion state +
-  - The applicable transition criteria +
-  - The observed criteria results +
-  - The promotion decision +
-  - The resulting promotion state +
-  - The promotion result +
-  - The generated [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] +
- +
-===== Outgoing Traceability ===== +
- +
-This requirement realizes: +
- +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-001:start|MO-001]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005|MO-005]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006|MO-006]] +
- +
-This requirement relates to: +
- +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-02-image-management:fr-img-001|FR-IMG-001 — Build Virtual Machine Images]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-02-image-management:fr-img-002|FR-IMG-002 — Build Container Images]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-02-image-management:fr-img-003|FR-IMG-003 — Immutable Infrastructure Workflows]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-02-image-management:fr-img-004|FR-IMG-004 — Image Signing]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-02-image-management:fr-img-005|FR-IMG-005 — Image Verification]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:start|C.3.3 Deployment Orchestration]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-06-compliance-management:start|C.3.6 Compliance Management]] +
-  * [[dido:02-crusible:06-machine-images-and-image-layers:start|6. Machine Images and Image Layers]] +
-  * [[dido:02-crusible:09-compliance-and-security:start|9. Compliance and Security]] +
-  * [[dido:02-crusible:10-reproducibility-provenance-and-traceability:start|10. Reproducibility, Provenance, and Traceability]]+
  
 ===== Referenced By ===== ===== Referenced By =====
  
-The wiki Backlinks function provides the current list of pages that reference ''FR-IMG-006''.+The following pages reference this requirement:
  
-Incoming [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] should be derived dynamically from backlinks rather than maintained as a duplicate manual list. +{{backlinks>.#dido:02-crusible}}
- +
-Backlinks identify incoming references but do not define the semantics of each relationship. Referencing pages should identify whether the relationship represents realization, refinement, verification, dependency, or another defined traceability relationship. +
- +
-===== ConOps Relationship ===== +
- +
-The Crucible Concept of Operations describes a Phase 1 workflow that builds, evaluates, and deploys controlled Image [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]] through an automated [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]]. +
- +
-FR-IMG-006 establishes the required behavior for progressing an identified Image between defined promotion states after satisfaction of the applicable transition criteria. +
- +
-Requirements governing Image building, signing, verification, compliance assessment, publication, transfer, and deployment define the behavior or conditions associated with particular promotion transitions. +
- +
-===== Delivery Phase ===== +
- +
-Phase 1+
  
 ===== Implementation Status ===== ===== Implementation Status =====
  
-Not Assessed +Implemented and Verified
- +
-Implementation status requires verification that [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] promotes an identified [[dido:99_annexes:annex-b-terms-and-definitions:i:image|Image]] from one defined promotion state to another after the Image satisfies the applicable transition criteria.+
  
 ===== Requirement Status ===== ===== Requirement Status =====
  
-Draft +<todo>Review and approve FR-IMG-006 as a leaf requirement.</todo>
- +
-The source System Requirements Specification identifies Version 1.1 as a draft.+
  
 ---- ----
-===== Notes for Editors =====+===== Issues =====
  
-This requirement page should retain the stable requirement identifier ''FR-IMG-006''.+<todo>Determine whether separate requirements or policies define the applicable Image Promotion transition criteria.</todo>
  
-Changes to the Statement SHALL preserve the approved intent of the source requirement.+<todo>Determine whether separate requirements govern preservation of the Image Promotion result.</todo>
  
-The Source Statement should preserve the original wording from the controlling System Requirements Specification.+---- 
 +===== Notes for Editors =====
  
-The Statement should remain limited to promotion of an identified Image between defined promotion states after satisfaction of applicable transition criteria.+This requirement page retains the stable requirement identifier ''FR-IMG-006''.
  
-The applicable workflow or lower-level requirements should define the promotion states and transition criteria without adding those details to this requirement unless the controlling source changes.+This page is a leaf requirement page and omits a trailing '':start'' from its namespace.
  
-Verification criteria should test only the behavior stated in the normalized Statement and should not introduce additional normative obligations.+The Statement reproduces the approved source behavior without introducing a specific promotion-state model.
  
-Incoming Traceability should use the wiki Backlinks function rather than a manually maintained list.+Do not add particular promotion states, signing criteria, verification criteria, vulnerability-assessment criteria, compliance criteria, approval criteria, publication criteria, or deployment criteria unless the controlling requirement changes through an approved requirements process.
  
 To reference this requirement Statement from another wiki page, insert: To reference this requirement Statement from another wiki page, insert:
Line 213: Line 99:
 {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-02-image-management:fr-img-006#Statement&noheader&nofooter&noeditbtn}} {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-02-image-management:fr-img-006#Statement&noheader&nofooter&noeditbtn}}
 </code> </code>
- 
-Do not rename this page after an external citation unless a redirect or move plan is in place. 
  
 ---- ----
  • dido/02-crusible/99-annexes/annex-c-requirements/03-functional-requirements/03-02-image-management/fr-img-006.1784556501.txt.gz
  • Last modified: 2026/07/20 07:08
  • by nick_dido