FR-IMG-001 — Build Virtual Machine Images

Go to Crucible Image Management Requirements

Statement

Crucible SHALL build a Machine Image.

Source Statement

The system shall build virtual machine images.

Source

Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-IMG-001.

Assessment

The source statement expresses a direct functional behavior but requires normalization of terminology.

The following Specification, Discipline, and Authoring findings apply:

The system does not use the defined system nameshall does not follow the established uppercase normative conventionvirtual machine images does not use the defined Machine Image termThe source statement does not identify a particular image format, target platform, build tool, or build methodThe source statement does not require image signing, image verification, image promotion, compliance assessment, or deploymentThe normalized Statement:

Replaces The system with CrucibleUses the direct and testable verb buildReplaces virtual machine images with the defined Machine Image termPreserves the implementation independence of the source requirementRetains one primary required behaviorThe normalized Statement does not add requirements for the contents, format, signing, verification, promotion, compliance, or deployment of the resulting Machine Image. Separate requirements define those obligations.

Rationale

A Machine Image captures the software, configuration, and other image content required to instantiate a virtual machine.

Building Machine Images through Crucible allows the Image Management workflow to create image Artifacts for later verification, signing, promotion, distribution, and deployment.

Machine Image building contributes to:

Repeatable image creationControlled image contentConsistent virtual machine instantiationAutomated image workflowsReproducibilityProvenanceTraceabilityThe build operation may consume:

A Crucible DescriptionOne or more Image LayersA selected BaselineConfiguration valuesSoftware packagesOperating-system contentBuild scriptsOther controlled input ArtifactsThe applicable architecture and lower-level requirements determine which inputs apply to a particular Machine Image build.

Applies To

This requirement applies to:

Machine Image buildsMachine Image build inputsMachine Image build outputsImage LayersBaselinesCrucible DescriptionsBuild toolsBuild workflowsVirtual machine platformsCI/CD Pipelines

Verification

Verification SHALL confirm that Crucible executes a Machine Image buildVerification SHALL confirm that the build produces a Machine ImageVerification may include:

Machine Image build testingBuild-output inspectionMachine Image artifact inspectionBuild-log inspectionAutomated CI/CD Pipeline testingThe verification record SHALL identify:

The tested Machine Image buildThe resulting Machine ImageThe build resultThe observed outputThe generated Evidence

Outgoing Traceability

This requirement realizes:

This requirement relates to:

Referenced By

The wiki Backlinks function provides the current list of pages that reference FR-IMG-001.

Incoming Traceability should be derived dynamically from backlinks rather than maintained as a duplicate manual list.

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 in which a CI/CD Pipeline invokes Crucible to compose selected inputs and build a hardened Machine Image.

FR-IMG-001 establishes the required Machine Image build behavior within that workflow.

Requirements governing image composition, hardening, signing, verification, promotion, compliance, and deployment define separate behavior associated with the resulting Machine Image.

Delivery Phase

Phase 1

Implementation Status

Not Assessed

Implementation status requires verification that Crucible builds a Machine Image.

Requirement Status

Draft

The source System Requirements Specification identifies Version 1.1 as a draft.

Notes for Editors

This requirement page should retain the stable requirement identifier FR-IMG-001.

Changes to the Statement SHALL preserve the approved intent of the source requirement.

The Source Statement should preserve the original wording from the controlling System Requirements Specification.

The Statement should remain limited to building a Machine Image.

Requirements for image composition, hardening, signing, verification, promotion, compliance assessment, distribution, and deployment should remain in their applicable requirement pages.

Verification criteria should test only the behavior stated in the normalized Statement and should not introduce additional normative obligations.

Incoming Traceability should use the wiki Backlinks function rather than a manually maintained list.

To reference this requirement Statement from another wiki page, insert:

{{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-02-image-management:fr-img-001#Statement&noheader&nofooter&noeditbtn}}

Do not rename this page after an external citation unless a redirect or move plan is in place.

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.