====== 5. Operational Concept ======

[[dido:02-crusible:start|Go to Crucible]]

The operational concept describes how [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] applies its approved capabilities as a coordinated lifecycle.

The lifecycle begins with the selection and composition of approved [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]] and continues through image construction, [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency_capture|Dependency Capture]], [[dido:99_annexes:annex-b-terms-and-definitions:c:compliance_assessment|Compliance Assessment]], deployment, validation, and preservation of [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] and lifecycle records.

The activities described in this section form a logical operational sequence. An implementation can execute some activities separately, repeat an activity, or omit an activity when the selected lifecycle operation and applicable requirements do not require it.

Each activity uses identified inputs, produces recorded outputs, and preserves the [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] needed to relate the intended result to the environment, image, assessment result, or other artifact produced.

The pages in this section describe only capabilities supported by approved leaf requirements in [[dido:02-crusible:99-annexes:annex-c-requirements:start|Annex C: Requirements]]. Each child page identifies the applicable leaf requirements and displays their canonical Statements through transclusion.

===== Contents =====

{{indexmenu>dido:02-crusible:05-operational-concept#1|js navbar nocookie maxjs#2 id#crucible_operational_concept_nav}}

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>