C.3.2 Image Management

Go to Crucible Functional Requirements

The Image Management requirements define how Crucible builds virtual Machine Images and container images, applies immutable infrastructure workflows, signs and verifies images, and promotes images through defined lifecycle states.

Together, these requirements establish controlled image creation and lifecycle behavior that contributes to image integrity, Reproducibility, Provenance, and Traceability.

Contents

Contents

Notes for Editors

The individual requirement pages should retain the stable identifiers FR-IMG-001 through FR-IMG-006.

Individual requirement pages are leaf nodes and should not include a trailing :start in their namespaces.

The Source Statement on each requirement page should preserve the original wording from the controlling System Requirements Specification.

Normalized Statements should use direct, testable behavior and should identify the applicable image Artifact, operation, and required result.

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 a requirement Statement from another wiki page, insert:

{{section><namespace>#Statement&noheader&nofooter&noeditbtn}}

Replace <namespace> with the namespace of the requirement leaf page.

The section name following # SHALL match the section heading verbatim on the requirement page.

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

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