====== MO-005d — Approved Infrastructure Baseline Selection ====== [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:start|Go to MO-005 — Reusable and Version-Controlled Infrastructure Baselines]] ===== Statement ===== [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL select an approved [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] revision for each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]]. ===== Derived From ===== This requirement derives from: * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:start|MO-005 — Reusable and Version-Controlled Infrastructure Baselines]] The Original Requirement states: > //The system SHALL establish infrastructure as a reusable and version-controlled asset.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]] MO-005d preserves the selection behavior required to reuse a controlled Infrastructure Baseline by requiring Crucible to select an approved Infrastructure Baseline revision for each Infrastructure Deployment. The separate requirements derived from MO-005 address: * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005a|MO-005a — Infrastructure Baseline Artifact Management]] * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005b|MO-005b — Infrastructure Baseline Identification]] * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005c|MO-005c — Infrastructure Baseline Revision Control]] * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005e|MO-005e — Infrastructure Baseline Reuse]] * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005f|MO-005f — Approved Infrastructure Baseline Preservation]] * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005g|MO-005g — Infrastructure Deployment Baseline Traceability]] ===== Rationale ===== Selection identifies the approved Infrastructure Baseline revision that governs a specific Infrastructure Deployment. Selecting an approved revision before deployment supports: * Deliberate use of a controlled Infrastructure Baseline * Prevention of accidental use of a draft, withdrawn, or superseded revision * Reproducible Infrastructure Deployments * Comparison of Infrastructure Deployments created from different revisions * Controlled promotion of Infrastructure Baseline revisions * Association of deployment inputs with an approved configuration * Preservation of [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] * Maintenance of [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] The Infrastructure Baseline identifier identifies the managed baseline. The revision identifier distinguishes the selected controlled state of that baseline. This requirement does not require reuse of the selected revision across multiple Infrastructure Deployments. MO-005e addresses reuse. This requirement does not permit modification of the selected approved revision. MO-005f addresses preservation. This requirement does not define the deployment record that identifies the selected revision. MO-005g addresses that Traceability. ===== Applies To ===== This requirement applies to: * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baselines]] * Infrastructure Baseline revisions * Approved Infrastructure Baseline revisions * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployments]] * Artifact identifiers * Revision identifiers * Approval records * Selection records * Deployment requests * Deployment parameters * Deployment Platforms * Operational environments * Security profiles * Compliance profiles * Policy constraints * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] ===== Verification ===== Verification confirms that: - Each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] is identified - The candidate [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] is identified - The candidate Infrastructure Baseline revision is identified - The selected revision has an approved status - The approval covers the intended Infrastructure Deployment context - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] selects the approved revision - Crucible does not select an unapproved revision - Crucible does not select a withdrawn revision - Crucible does not select a superseded revision unless the controlling approval explicitly permits its use - The selection result identifies the Infrastructure Baseline Artifact identifier and revision identifier - The verification record preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among the Infrastructure Deployment, Infrastructure Baseline, selected revision, approval record, and selection result ===== Referenced By ===== The following pages reference this requirement: {{backlinks>.#dido:02-crusible}} ===== Delivery Phase ===== Implemented and Verified. ===== Implementation Status ===== Assess whether the current Crucible implementation selects an approved Infrastructure Baseline revision for each Infrastructure Deployment. ===== Requirement Status ===== Review and accept MO-005d as a proposed derived requirement created from the evaluation and decomposition of MO-005 in the Crucible System Requirements Specification, Version 1.1 Draft. ---- ===== Issues ===== The following unresolved issues affect this requirement: Identify the authority that approves Infrastructure Baseline revisions. Define the approval statuses that permit selection of an Infrastructure Baseline revision. Define the Infrastructure Deployment context covered by an approval. Define the selection criteria used when more than one approved Infrastructure Baseline revision is available. Define the behavior required when no approved Infrastructure Baseline revision satisfies the deployment context. Define whether and under what conditions a superseded Infrastructure Baseline revision may be selected. ---- ===== Notes for Editors ===== This requirement page should retain the stable requirement identifier ''MO-005d''. This page is a leaf requirement page and omits a trailing '':start'' from its namespace. The parent MO-005 page is a non-leaf page and retains a trailing '':start'' in its namespace. Changes to the Statement should preserve: * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor * An approved [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] revision as the selected object * An [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] as the selection context * Selection of one approved revision for each Infrastructure Deployment The selection record should identify: * The Infrastructure Deployment * The stable Infrastructure Baseline Artifact identifier * The selected revision identifier * The approval status * The approval scope * The selection date and time * The actor or process responsible for the selection * The operational environment * The Deployment Platform * The policy and compliance constraints * The associated [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] * The associated [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] Material changes should receive review and should update the verification criteria, source records, and Issues section. To reference this requirement Statement from another wiki page, insert: {{section>dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005d#Statement&noheader&nofooter&noeditbtn}} Do not rename this page after an external citation unless a redirect or move plan is in place. ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.