FR-IMG-002 — Build Container Images

Go to Crucible Image Management Requirements

Statement

Crucible SHALL build a container image.

Source Statement

The system shall build container images.

Source

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

Assessment

The source statement expresses a direct functional behavior but requires terminology and normative-language normalization.

The following Specification Discipline and Authoring findings apply:

The system does not use the defined system nameshall does not follow the established uppercase normative conventionThe source statement does not identify a particular container-image format, target platform, build tool, or build methodThe source statement does not require image signing, image verification, image promotion, compliance assessment, publication, or deploymentThe normalized Statement:

Replaces The system with CrucibleUses the direct and testable verb buildIdentifies a container image as the required resultPreserves the implementation independence of the source requirementRetains one primary required behaviorThe normalized Statement does not add requirements for container-image content, format, signing, verification, promotion, compliance, publication, distribution, or deployment. Separate requirements define those obligations.

Rationale

A Container Image packages the files, software, configuration, and metadata required to instantiate a containerized workload.

Building container images through Crucible allows the Image Management workflow to produce image Artifacts for later verification, signing, promotion, transfer, publication, and deployment.

Container Image building contributes to:

Repeatable image creationControlled image contentConsistent workload instantiationAutomated build workflowsReproducibilityProvenanceTraceabilityThe build operation may consume:

A Crucible DescriptionOne or more Image LayersA selected BaselineApplication filesSoftware packagesRuntime contentConfiguration valuesBuild instructionsOther Controlled InputsThe applicable architecture and lower-level requirements determine which inputs apply to a particular container-image build.

Applies To

This requirement applies to:

Container-image buildsContainer-image build inputsContainer-image build outputsImage LayersBaselinesCrucible DescriptionsBuild toolsBuild workflowsContainer runtimesContainer registriesCI/CD Pipelines

Verification

Verification SHALL confirm that Crucible executes a container-image buildVerification SHALL confirm that the build produces a container imageVerification may include:

Container-image build testingBuild-output inspectionContainer-image Artifact inspectionBuild-log inspectionContainer-runtime instantiation testingAutomated CI/CD Pipeline testingThe verification record SHALL identify:

The tested container-image buildThe resulting container 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-002.

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 build controlled image Artifacts used by platform and application workflows.

FR-IMG-002 establishes the required container-image build behavior within that workflow.

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

Delivery Phase

Phase 1

Implementation Status

Not Assessed

Implementation status requires verification that Crucible builds a container 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-002.

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 container image.

Requirements for image composition, hardening, signing, verification, promotion, compliance assessment, publication, 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-002#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.