Baseline Composition selects identified and version-controlled Baselines and makes their content available within a controlled workspace for the selected Operational Lifecycle activity.
A composition can include:
Application source is not required for every composition. A composition containing only Image Layers, Infrastructure Baselines, or both remains valid when those inputs satisfy the selected lifecycle activity.
Baseline selection identifies the Baselines needed to produce the intended result.
The selection identifies:
Crucible uses the identified revision rather than an unspecified or changing repository state. This allows the composition to be reproduced and related to the artifacts, deployments, assessments, and records produced from it.
Crucible places or makes the selected inputs available within a controlled workspace.
The workspace provides the execution context in which Crucible can locate and use:
The workspace can contain inputs retrieved from separate repositories. Co-location within the workspace does not merge their identities, histories, or governance.
Each selected Baseline remains independently identifiable and version controlled.
Image Layers describe reusable content and activities applied during image construction and hardening.
A composition can select one or more Image Layers according to the intended image, operating system, security criteria, and applicable lifecycle activity.
The selected Image Layers become controlled inputs to the image-construction activity described in 5.2 Construct Images.
Infrastructure Baselines describe reusable deployment content and lifecycle activities associated with an Infrastructure Environment.
An Infrastructure Baseline can include content used before, during, or after deployment. The applicable requirement and Baseline content determine the activities performed.
Crucible treats an Infrastructure Baseline as a reusable, versioned input rather than as a manually recreated or deployment-specific configuration.
The same approved Infrastructure Baseline revision can support more than one deployment when the applicable Deployment Targets, provider parameters, and acceptance criteria permit its reuse.
The composition result identifies the complete set of selected inputs made available for the lifecycle activity.
The result records:
The composition result provides controlled inputs for subsequent image construction, dependency capture, compliance assessment, deployment, validation, and lifecycle-record preservation activities.
| Requirement | Statement |
|---|---|
| FR-BAS-001 — Consume Baseline Repositories from a Workspace |
Crucible SHALL consume Baseline Repositories containing Image Layers or Infrastructure Baselines from a Workspace. |
| FR-BAS-002 — Compose Selected Baselines |
Crucible SHALL perform Baseline Composition using one or more selected Baselines and optional application source. |
| FR-BAS-003 — Process Predeployment and Postdeployment Steps |
Crucible SHALL process predeployment and postdeployment steps. |
| FR-BAS-004 — Perform Noninteractive Workspace Execution |
|
The linked leaf requirement pages remain the canonical sources.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.