dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005d

Differences

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

Link to this comparison view

Next revision		 Previous revision
dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005d [2026/07/20 08:50] – created nick_didodido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005d [2026/07/30 05:26] (current) – [Delivery Phase] nick_dido
Line 1: Line 1:
-====== MO-005d — Infrastructure Baseline Selection ======+====== 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]] [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:start|Go to MO-005 — Reusable and Version-Controlled Infrastructure Baselines]]
Line 5: Line 5:
 ===== Statement ===== ===== Statement =====
  
-[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL permit selection of an approved [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] revision for an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]].+[[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 ===== ===== Derived From =====
Line 17: Line 17:
 > //The system SHALL establish infrastructure as a reusable and version-controlled asset.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]] > //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 permit selection of an approved Infrastructure Baseline revision for an Infrastructure Deployment.+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: The separate requirements derived from MO-005 address:
Line 23: Line 23:
   * [[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-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-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 Version Control]]+  * [[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-005e|MO-005e — Infrastructure Baseline Reuse]]
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005f|MO-005f — Approved Baseline Immutability]] +  * [[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 — Baseline Revision Deployment Traceability]] +  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005g|MO-005g — Infrastructure Deployment Baseline Traceability]]
- +
-===== Assessment ===== +
- +
-The Original Requirement describes infrastructure as reusable but does not identify the selection behavior required before reuse or deployment. +
- +
-The phrase **reusable asset** does not identify: +
- +
-  * The object selected +
-  * The revision selected +
-  * The approval condition applicable to the selected revision +
-  * The Infrastructure Deployment for which the revision is selected +
-  * The actor or process initiating the selection +
-  * The criteria used to determine whether the selected revision applies +
-  * The behavior required when a revision is not approved +
-  * The Evidence required to demonstrate selection +
- +
-MO-005d: +
- +
-  * Identifies [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor +
-  * Identifies an approved Infrastructure Baseline revision as the selected object +
-  * Identifies an Infrastructure Deployment as the selection context +
-  * Distinguishes selection from application and reuse +
-  * Separates selection from Artifact management, identification, Version Control, immutability, and deployment traceability+
  
 ===== Rationale ===== ===== Rationale =====
  
-Selection identifies the approved Infrastructure Baseline revision that applies to a specific Infrastructure Deployment.+Selection identifies the approved Infrastructure Baseline revision that governs a specific Infrastructure Deployment.
  
-Selecting a revision before deployment supports:+Selecting an approved revision before deployment supports:
  
-  * Deliberate use of an approved baseline +  * Deliberate use of a controlled Infrastructure Baseline 
-  * Prevention of accidental use of a draft or superseded revision+  * Prevention of accidental use of a draft, withdrawn, or superseded revision
   * Reproducible Infrastructure Deployments   * Reproducible Infrastructure Deployments
   * Comparison of Infrastructure Deployments created from different revisions   * Comparison of Infrastructure Deployments created from different revisions
   * Controlled promotion of Infrastructure Baseline revisions   * Controlled promotion of Infrastructure Baseline revisions
   * Association of deployment inputs with an approved configuration   * Association of deployment inputs with an approved configuration
-  * Preservation of Provenance +  * Preservation of [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] 
-  * Maintenance of Traceability +  * Maintenance of [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
-  * Generation of auditable [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] +
- +
-The selection can depend on: +
- +
-  * Deployment purpose +
-  * Deployment Platform +
-  * Operational environment +
-  * Security classification +
-  * Compliance profile +
-  * Applicable policy +
-  * Required Machine Images +
-  * Required dependencies +
-  * Deployment parameters +
-  * Approval status +
-  * Effective period+
  
 The Infrastructure Baseline identifier identifies the managed baseline. The revision identifier distinguishes the selected controlled state of that baseline. The Infrastructure Baseline identifier identifies the managed baseline. The revision identifier distinguishes the selected controlled state of that baseline.
  
-This requirement does not require application of the selected revision to multiple Infrastructure Deployments. MO-005e establishes reuse.+This requirement does not require reuse of the selected revision across multiple Infrastructure Deployments. MO-005e addresses reuse.
  
-This requirement does not prohibit modification of the selected approved revision. MO-005f establishes approved baseline immutability.+This requirement does not permit modification of the selected approved revision. MO-005f addresses preservation.
  
-This requirement does not require the Infrastructure Deployment record to preserve the selected identifiers. MO-005g establishes that requirement.+This requirement does not define the deployment record that identifies the selected revision. MO-005g addresses that Traceability.
  
 ===== Applies To ===== ===== Applies To =====
Line 109: Line 71:
   * Compliance profiles   * Compliance profiles
   * Policy constraints   * Policy constraints
-  * Artifact catalog records 
-  * Artifact repositories 
   * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]   * [[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:p:provenance|Provenance]]
Line 119: Line 79:
 Verification confirms that: Verification confirms that:
  
-  - The Infrastructure Deployment is identified +  - Each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] is identified 
-  - The candidate Infrastructure Baseline 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 candidate Infrastructure Baseline revision is identified
   - The selected revision has an approved status   - The selected revision has an approved status
-  - The approval applies to the intended Infrastructure Deployment context +  - The approval covers the intended Infrastructure Deployment context 
-  - Crucible permits selection of the approved revision +  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] selects the approved revision 
-  - Crucible does not present an unapproved revision as approved +  - Crucible does not select an unapproved revision 
-  - The selection result identifies the selected Artifact identifier and revision identifier +  - Crucible does not select a withdrawn revision 
-  - The selection record preserves the required Evidence, Provenance, and Traceability+  - 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
  
-Verification includes:+===== Referenced By =====
  
-  * Infrastructure Deployment inspection +The following pages reference this requirement:
-  * Infrastructure Baseline inspection +
-  * Artifact identifier inspection +
-  * Revision identifier inspection +
-  * Approval-record inspection +
-  * Approval-scope inspection +
-  * Artifact catalog inspection +
-  * Baseline-selection testing +
-  * Approved-revision selection testing +
-  * Unapproved-revision selection testing +
-  * Superseded-revision selection testing +
-  * Selection-record inspection +
-  * Evidence inspection +
-  * Provenance inspection +
-  * Traceability inspection+
  
-The verification record identifies:+{{backlinks>.#dido:02-crusible}}
  
-  - The Infrastructure Deployment +===== Delivery Phase =====
-  - The candidate Infrastructure Baseline +
-  - The stable Artifact identifier +
-  - The candidate revision identifier +
-  - The approval status of the candidate revision +
-  - The approval scope +
-  - The selected revision +
-  - The selection result +
-  - Each rejected candidate revision +
-  - The reason for each rejection +
-  - Each identified failure or exception +
-  - The observed result +
-  - The generated [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]+
  
-===== Requirements Realized By =====+Implemented and Verified.
  
-This requirement is realized by:+===== Implementation Status =====
  
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-01-configuration-management:start|FR-CFG-001 through FR-CFG-005]] +<todo>Assess whether the current Crucible implementation selects an approved Infrastructure Baseline revision for each Infrastructure Deployment.</todo>
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:start|FR-DEP-001 through FR-DEP-007]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-metadata-catalog-and-provenance:start|FR-MC-001 through FR-MC-005]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-09-baseline-composition-and-workspace:start|FR-BAS-001 through FR-BAS-004]]+
  
-===== Related Architecture Sections =====+===== Requirement Status =====
  
-  * [[dido:02-crusible:05-descriptions-composition-and-baselines:start|5. Descriptions, Composition, and Baselines]] +<todo>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.</todo>
-  * [[dido:02-crusible:07-infrastructure-and-deployment:start|7. Infrastructure and Deployment]] +
-  * [[dido:02-crusible:10-reproducibility-provenance-and-traceability:start|10. Reproducibility, Provenance, and Traceability]]+
  
-===== Referenced By =====+---- 
 +===== Issues =====
  
-The following pages reference this requirement:+The following unresolved issues affect this requirement:
  
-{{backlinks>.#dido:02-crusible}}+<todo>Identify the authority that approves Infrastructure Baseline revisions.</todo>
  
-===== Delivery Phase =====+<todo>Define the approval statuses that permit selection of an Infrastructure Baseline revision.</todo>
  
-Phase 1 and subsequent phases+<todo>Define the Infrastructure Deployment context covered by an approval.</todo>
  
-===== Implementation Status =====+<todo>Define the selection criteria used when more than one approved Infrastructure Baseline revision is available.</todo>
  
-Not Assessed+<todo>Define the behavior required when no approved Infrastructure Baseline revision satisfies the deployment context.</todo>
  
-Implementation status requires verification that the current [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] implementation permits selection of an approved Infrastructure Baseline revision for an Infrastructure Deployment. +<todo>Define whether and under what conditions a superseded Infrastructure Baseline revision may be selected.</todo>
- +
-===== Requirement Status ===== +
- +
-Draft +
- +
-This requirement derives from MO-005 in the Crucible System Requirements Specification, Version 1.1 Draft.+
  
 ---- ----
Line 207: Line 133:
 This page is a leaf requirement page and omits a trailing '':start'' from its namespace. This page is a leaf requirement page and omits a trailing '':start'' from its namespace.
  
-Changes to the Statement should preserve the Infrastructure Baseline selection intent derived from MO-005.+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 selection record should identify:
Line 218: Line 151:
   * The selection date and time   * The selection date and time
   * The actor or process responsible for the selection   * The actor or process responsible for the selection
-  * The applicable operational environment +  * The operational environment 
-  * The applicable Deployment Platform +  * The Deployment Platform 
-  * The applicable policy and compliance constraints +  * The policy and compliance constraints 
-  * The associated Provenance +  * The associated [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] 
-  * The associated Traceability +  * The associated [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
-  * The supporting Evidence+
  
-Material changes should receive review and should update the related verification criteria, requirements realization, related architecture sections, and source records.+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: To reference this requirement Statement from another wiki page, insert:
  • dido/02-crusible/99-annexes/annex-c-requirements/01-mission-objectives/mo-005/mo-005d.1784562618.txt.gz
  • Last modified: 2026/07/20 08:50
  • by nick_dido