C.3.9 Baseline Composition and Workspace

Go to Crucible Functional Requirements

The Baseline Composition and Workspace requirements define how Crucible consumes Baseline Repositories containing Image Layers and Infrastructure Baselines within a 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

Requirement Status

Issues

Notes for Editors

This page is a non-leaf requirement page and therefore retains a trailing :start in its namespace.

The namespace for this page is:

dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-09-baseline-composition-and-workspace:start

Use the following controlling Terms and Definitions entries:

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

Individual requirement pages are leaf nodes nested beneath the Baseline Composition and Workspace namespace and omit a trailing :start.

The Derived From section on each leaf requirement page preserves the original wording from the controlling System Requirements Specification.

Normalized Statements use direct, testable behavior and identify selected Baseline Repositories, applicable Revisions, Workspace inputs, composition operations, and required results only when the controlling source establishes that information.

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

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

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

Each leaf requirement page includes its actual namespace in the DokuWiki section-transclusion example.

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.