public:99_annexes:annex-b-terms-and-definitions:b:baseline_composition

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:99_annexes:annex-b-terms-and-definitions:b:baseline_composition [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:b:baseline_composition [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Baseline Composition ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +Baseline Composition combines two or more controlled [[public:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]] or baseline elements into a defined configuration for a build, deployment, assessment, or operational purpose.
 +
 +The composition identifies the participating baselines, their resolved revisions, their relationships, applicable precedence rules, and any compatibility constraints.
 +
 +Within Crucible, Baseline Composition may combine an [[public:99_annexes:annex-b-terms-and-definitions:i:image_baseline|Image Baseline]], [[public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]], provisioning source, application source, and [[public:99_annexes:annex-b-terms-and-definitions:c:compliance_baseline|Compliance Baseline]] within a controlled pipeline workspace.
 +
 +Baseline Composition allows the participating baselines to evolve independently while preserving an explicit record of the versions selected for a particular result.
 +
 +===== Definition =====
 +
 +//combination of two or more controlled [[public:99_annexes:annex-b-terms-and-definitions:b:baseline|baselines]] or baseline elements into a defined configuration for a build, deployment, assessment, or operational purpose//
 +
 +===== Source =====
 +
 +Generalized from configuration management, systems integration, software composition, and baseline-management usage and specialized for the Crucible architecture and operational model.
 +
 +===== Note =====
 +
 +Baseline Composition does not merge the identities of the participating baselines. Each Baseline retains its identity, revision history, and change authority.
 +
 +A composition may contain only image or infrastructure baselines and need not include application source.
 +
 +===== Example =====
 +
 +A Crucible Description composes a hardened [[public:99_annexes:annex-b-terms-and-definitions:r:rhel]] 9 Image Baseline, a Kubernetes Infrastructure Baseline, a STIG Compliance Baseline, and an application repository into the configuration used for a deployment.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>