Differences

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

--- dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-09-baseline-composition-and-workspace:start [2026/07/17 00:21] – created nick_dido
+++ dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-09-baseline-composition-and-workspace:start [2026/07/31 05:43] (current) – nick_dido
@@ Line 3: / Line 3: @@
 [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:start|Go to Crucible Functional Requirements]]
-The Baseline Composition and 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:i:image_layer|Image Layer]] and [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] repositories within a checked-out 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.
+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 [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_composition|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.
+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 =====
@@ Line 11: / Line 11: @@
 {{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 =====
-The individual requirement pages should retain the stable identifiers ''FR-BAS-001'' through ''FR-BAS-004''.
+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''
-Individual requirement pages are leaf nodes and should not include a trailing '':start'' in their namespaces.
+Use the following controlling Terms and Definitions entries:
-The Source Statement on each requirement page should preserve the original wording from the controlling System Requirements Specification.
+  * [[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]]
-Normalized Statements should use direct, testable behavior and should identify the selected [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] repositories, applicable [[dido:99_annexes:annex-b-terms-and-definitions:r:revision|Revisions]], workspace inputs, composition operation, and required result.
+The individual requirement pages retain the stable identifiers ''FR-BAS-001'' through ''FR-BAS-004''.
-A composition containing only Image Layer Baselines, Infrastructure Baselines, or both should remain valid when application source does not apply.
+Individual requirement pages are leaf nodes nested beneath the Baseline Composition and Workspace namespace and omit a trailing '':start''.
-Verification criteria should test only the behavior stated in the normalized Statement and should not introduce additional normative obligations.
+The Derived From section on each leaf requirement page preserves the original wording from the controlling System Requirements Specification.
-Incoming [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] should use the wiki Backlinks function rather than a manually maintained list.
+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.
-To reference a requirement Statement from another wiki page, insert:
+A composition containing only Image Layer Baselines, Infrastructure Baselines, or both remains valid when application source does not apply.
-<code dokuwiki>
+Verification criteria test only the behavior stated in the normalized Statement and do not introduce additional normative obligations.
-{{section><namespace>#Statement&noheader&nofooter&noeditbtn}}
-</code>
-Replace ''<namespace>'' with the namespace of the requirement leaf page.
+Incoming [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] uses the wiki Backlinks function rather than a manually maintained list.
-The section name following ''#'' SHALL match the section heading verbatim on the requirement page.
+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.