5.1 Select and Compose Baselines [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 5.1 Select and Compose Baselines ======

[[dido:02-crusible:05-operational-concept:start|Go to 5. Operational Concept]]

[[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_composition|Baseline Composition]] selects identified and version-controlled [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]] and makes their content available within a controlled workspace for the selected [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]] activity.

A composition can include:

  * Application source
  * One or more [[dido:99_annexes:annex-b-terms-and-definitions:i:image_layer|Image Layers]]
  * One or more [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baselines]]
  * A combination of application source, Image Layers, and Infrastructure Baselines

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 =====

Baseline selection identifies the Baselines needed to produce the intended result.

The selection identifies:

  * Each Baseline
  * The selected Baseline revision
  * The Baseline source location
  * The role of the Baseline in the composition
  * The approval status required for its use
  * The selected lifecycle activity
  * Any applicable [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_parameter|Platform Specific Parameters]]

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.

===== Workspace Composition =====

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:

  * Application source, when included
  * Selected Image Layers
  * Selected Infrastructure Baselines
  * Applicable [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible_description|Crucible Descriptions]]
  * Required configuration and parameters
  * Inputs required by the selected lifecycle activity

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 =====

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 [[dido:02-crusible:05-operational-concept:05-02-construct-images|5.2 Construct Images]].

===== Infrastructure Baselines =====

Infrastructure Baselines describe reusable deployment content and lifecycle activities associated with an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|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.

===== Composition Result =====

The composition result identifies the complete set of selected inputs made available for the lifecycle activity.

The result records:

  * The composition identifier
  * Each selected Baseline identifier
  * Each selected Baseline revision
  * Each source location
  * The included application source revision, when applicable
  * The applicable Crucible Description
  * The applicable Platform Specific Parameters
  * The selected lifecycle activity
  * The composition result
  * The associated [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
  * The associated [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
  * The generated [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]

The composition result provides controlled inputs for subsequent image construction, dependency capture, compliance assessment, deployment, validation, and lifecycle-record preservation activities.

===== Requirements Addressed =====

^ Requirement ^ Statement ^
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-09-baseline-composition-and-workspace:fr-bas-001]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-09-baseline-composition-and-workspace:fr-bas-001#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-09-baseline-composition-and-workspace:fr-bas-002]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-09-baseline-composition-and-workspace:fr-bas-002#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-09-baseline-composition-and-workspace:fr-bas-003]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-09-baseline-composition-and-workspace:fr-bas-003#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-09-baseline-composition-and-workspace:fr-bas-004]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-09-baseline-composition-and-workspace:fr-bas-004#Statement&noheader&nofooter&noeditbtn}} |

The linked leaf requirement pages remain the canonical sources.

----

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