====== C.3.9 Baseline Composition and Workspace ======

[[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:start|Go to Crucible Functional Requirements]]

The [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_composition|Baseline Composition]] and [[dido:99_annexes:annex-b-terms-and-definitions:w:workspace|Workspace]] [[dido:99_annexes:annex-b-terms-and-definitions:f:functional_requirement|requirements]] define how [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] consumes [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_repository|Baseline Repositories]] containing [[dido:99_annexes:annex-b-terms-and-definitions:i:image_layer|Image Layers]] and [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baselines]] within a Workspace, composes one or more selected [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]] with optional application source, processes predeployment and postdeployment steps, and operates without interactive input.

Together, these requirements establish controlled Baseline Composition, [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_selection|Baseline Selection]], and [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_reuse|Baseline Reuse]] within a [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]] Workspace.

===== Contents =====

{{indexmenu>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-09-baseline-composition-and-workspace#1|js navbar nocookie maxjs#1 id#crucible_baseline_composition_workspace_requirements_nav}}

===== Requirement Status =====

<todo>Review and approve the Baseline Composition and Workspace requirement set.</todo>

<todo>Review and approve FR-BAS-001 through FR-BAS-004 as leaf requirements.</todo>

----
===== Issues =====

<todo>Confirm that FR-BAS-001 distinguishes consumption of Baseline Repositories from Baseline Selection and Baseline Composition.</todo>

<todo>Confirm that FR-BAS-003 separates predeployment and postdeployment behavior when those activities require independent verification.</todo>

<todo>Confirm that FR-BAS-004 defines observable noninteractive behavior without adding requirements for a particular automation platform.</todo>

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

  * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_composition|Baseline Composition]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_repository|Baseline Repository]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_reuse|Baseline Reuse]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_selection|Baseline Selection]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:w:workspace|Workspace]]

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 [[dido:99_annexes:annex-b-terms-and-definitions:r:revision|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 [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|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.

----

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