C.3.9 Baseline Composition and Workspace

Go to Crucible Functional Requirements

The Baseline Composition and Workspace requirements define how Crucible consumes Image Layer and Infrastructure Baseline repositories within a checked-out workspace, composes one or more selected Baselines with optional application source, processes predeployment and postdeployment steps, and operates without interactive input.

Together, these requirements establish controlled Baseline Composition, Baseline Selection, and Baseline Reuse within a CI/CD Pipeline workspace.

Contents

Notes for Editors

The individual requirement pages should retain the stable identifiers FR-BAS-001 through FR-BAS-004.

Individual requirement pages are leaf nodes and should not include a trailing :start in their namespaces.

The Source Statement on each requirement page should preserve the original wording from the controlling System Requirements Specification.

Normalized Statements should use direct, testable behavior and should identify the selected Baseline repositories, applicable Revisions, workspace inputs, composition operation, and required result.

A composition containing only Image Layer Baselines, Infrastructure Baselines, or both should remain valid when application source does not apply.

Verification criteria should test only the behavior stated in the normalized Statement and should not introduce additional normative obligations.

Incoming Traceability should use the wiki Backlinks function rather than a manually maintained list.

To reference a requirement Statement from another wiki page, insert:

{{section><namespace>#Statement&noheader&nofooter&noeditbtn}}

Replace <namespace> with the namespace of the requirement leaf page.

The section name following # SHALL match the section heading verbatim on the requirement page.

Do not rename a requirement page after an external citation unless a redirect or move plan is in place.

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