Baseline Composition

Go up to Terms and Definitions

Discussion

Baseline Composition combines two or more controlled 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 Image Baseline, Infrastructure Baseline, provisioning source, application source, and 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 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 Red Hat Enterprise Linux (RHEL) 9 Image Baseline, a Kubernetes Infrastructure Baseline, a STIG Compliance Baseline, and an application repository into the configuration used for a deployment.

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