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

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-005g [2026/07/20 08:54] – created nick_didodido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005g [2026/07/30 05:27] (current) – [Delivery Phase] nick_dido
Line 1: Line 1:
-====== MO-005g — Baseline Revision Deployment Traceability ======+====== MO-005g — Infrastructure Deployment Baseline Traceability ======
  
 [[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 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-005g preserves the traceability necessary to demonstrate reuse of a version-controlled Infrastructure Baseline by requiring each Infrastructure Deployment to identify the specific Infrastructure Baseline revision used.+MO-005g preserves the Traceability needed to demonstrate reuse of a version-controlled Infrastructure Baseline by requiring each Infrastructure Deployment to identify the specific Infrastructure Baseline revision used.
  
 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-005d|MO-005d — Infrastructure Baseline Selection]]+  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005d|MO-005d — Approved Infrastructure Baseline Selection]]
   * [[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]]
- +
-===== Assessment ===== +
- +
-The Original Requirement describes infrastructure as reusable and version controlled but does not require an Infrastructure Deployment to identify the specific Infrastructure Baseline revision used. +
- +
-Without this relationship, an evaluator cannot reliably determine: +
- +
-  * Which Infrastructure Baseline produced an Infrastructure Deployment +
-  * Which revision of the Infrastructure Baseline applied +
-  * Whether two Infrastructure Deployments reused the same revision +
-  * Whether an approved revision or another revision applied +
-  * Whether a later deployment used a superseded revision +
-  * Whether deployment results remain reproducible +
-  * Whether the deployment record preserves adequate Provenance and Traceability +
- +
-The phrase **reusable and version-controlled asset** does not identify: +
- +
-  * The deployment record that preserves the relationship +
-  * The stable Artifact identifier of the Infrastructure Baseline +
-  * The revision identifier of the applied baseline +
-  * The Infrastructure Deployment associated with the baseline revision +
-  * The point at which the relationship is recorded +
-  * The treatment of failed or incomplete deployments +
-  * The Evidence required to demonstrate the relationship +
- +
-MO-005g: +
- +
-  * Identifies [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor +
-  * Identifies each Infrastructure Deployment as the traceability subject +
-  * Identifies the stable Artifact identifier and revision identifier as the required baseline reference +
-  * Establishes a direct relationship between an Infrastructure Deployment and the Infrastructure Baseline revision used +
-  * Separates deployment traceability from Artifact management, identification, Version Control, selection, reuse, and immutability+
  
 ===== Rationale ===== ===== Rationale =====
Line 64: Line 32:
 An Infrastructure Deployment represents a realized infrastructure instance produced from a selected Infrastructure Baseline revision. An Infrastructure Deployment represents a realized infrastructure instance produced from a selected Infrastructure Baseline revision.
  
-Recording the stable Artifact identifier and revision identifier enables an evaluator to determine exactly which controlled Infrastructure Baseline state Crucible used for the deployment.+Recording the stable Artifact identifier and revision identifier enables an evaluator to determine the controlled Infrastructure Baseline state used for the deployment.
  
-Baseline revision deployment traceability supports:+Infrastructure Deployment Baseline Traceability supports:
  
-  * Identification of the source baseline for each Infrastructure Deployment+  * Identification of the source Infrastructure Baseline for each Infrastructure Deployment
   * Confirmation that multiple Infrastructure Deployments reused the same revision   * Confirmation that multiple Infrastructure Deployments reused the same revision
   * Reproduction of an Infrastructure Deployment   * Reproduction of an Infrastructure Deployment
Line 74: Line 42:
   * Comparison of deployments created from different revisions   * Comparison of deployments created from different revisions
   * Detection of deployments created from superseded or unapproved revisions   * Detection of deployments created from superseded or unapproved revisions
-  * Evaluation of baseline changes across deployment history+  * Evaluation of Infrastructure Baseline changes across deployment history
   * Preservation of [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]   * 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]]   * 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 stable Artifact identifier identifies the Infrastructure Baseline across its revision history. The revision identifier identifies the controlled Infrastructure Baseline state used for the Infrastructure Deployment. The stable Artifact identifier identifies the Infrastructure Baseline across its revision history. The revision identifier identifies the controlled Infrastructure Baseline state used for the Infrastructure Deployment.
  
-The recorded relationship remains applicable when deployment-specific parameters produce permitted differences between Infrastructure Deployments. The baseline reference identifies the controlled baseline revision, while the deployment record separately identifies the parameters applied to the deployment.+Deployment-specific parameters may produce permitted differences between Infrastructure Deployments. The Infrastructure Baseline reference identifies the controlled revision, while the deployment record separately identifies the deployment-specific parameters.
  
-This requirement does not assign the stable Artifact identifier. MO-005b establishes Infrastructure Baseline identification.+This requirement does not assign the stable Artifact identifier. MO-005b addresses Infrastructure Baseline identification.
  
-This requirement does not establish Version Control for Infrastructure Baseline revisions. MO-005c establishes Version Control.+This requirement does not establish Revision Control for Infrastructure Baseline revisions. MO-005c addresses Revision Control.
  
-This requirement does not require reuse of the same revision across multiple Infrastructure Deployments. MO-005e establishes reuse.+This requirement does not require reuse of the same revision across multiple Infrastructure Deployments. MO-005e addresses Infrastructure Baseline reuse.
  
 ===== Applies To ===== ===== Applies To =====
Line 105: Line 72:
   * Deployment-specific parameters   * Deployment-specific parameters
   * Artifact catalog records   * Artifact catalog records
-  * Artifact repositories +  * Artifact repository records 
-  * Version Control records+  * Revision-control records
   * [[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 115: Line 82:
 Verification confirms that: Verification confirms that:
  
-  - Each Infrastructure Deployment has an associated deployment record +  - Each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] has an associated deployment record 
-  - The deployment record identifies the Infrastructure Baseline used +  - The deployment record identifies the [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] used 
-  - The deployment record contains the stable Artifact identifier of the Infrastructure Baseline+  - The deployment record contains the stable [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] identifier of the Infrastructure Baseline
   - The deployment record contains the revision identifier of the Infrastructure Baseline revision used   - The deployment record contains the revision identifier of the Infrastructure Baseline revision used
-  - The recorded Artifact identifier resolves to the applicable Infrastructure Baseline +  - The recorded Artifact identifier resolves to the identified Infrastructure Baseline 
-  - The recorded revision identifier resolves to the controlled revision used for the deployment+  - The recorded revision identifier resolves to the controlled revision used for the Infrastructure Deployment
   - The recorded relationship remains associated with the Infrastructure Deployment   - The recorded relationship remains associated with the Infrastructure Deployment
-  - The deployment record preserves the required Evidence, Provenance, and Traceability+  - Failed or incomplete Infrastructure Deployments retain the Infrastructure Baseline Artifact identifier and revision identifier selected for execution 
 +  - The verification record preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among the Infrastructure Deployment, deployment record, Infrastructure Baseline, revision, selection record, deployment-specific parameters, and deployment result
  
-Verification includes:+===== Referenced By =====
  
-  * Infrastructure Deployment inspection +The following pages reference this requirement:
-  * Deployment-record inspection +
-  * Infrastructure Baseline inspection +
-  * Artifact identifier inspection +
-  * Revision identifier inspection +
-  * Artifact catalog inspection +
-  * Artifact repository inspection +
-  * Version Control record inspection +
-  * Baseline-selection record inspection +
-  * Identifier-resolution testing +
-  * Cross-deployment record comparison +
-  * Evidence inspection +
-  * Provenance inspection +
-  * Traceability inspection+
  
-The verification record identifies:+{{backlinks>.#dido:02-crusible}}
  
-  - The Infrastructure Deployment +===== Delivery Phase =====
-  - The associated deployment record +
-  - The Infrastructure Baseline +
-  - The stable Artifact identifier +
-  - The applied revision identifier +
-  - The Artifact catalog record +
-  - The Version Control record +
-  - The baseline-selection record +
-  - The identifier-resolution result +
-  - The applicable deployment-specific parameters +
-  - Each missing, invalid, or conflicting baseline reference +
-  - 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 records the Artifact identifier and revision identifier of the Infrastructure Baseline used by 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-005g 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>Define the deployment record that preserves the relationship between an Infrastructure Deployment and the Infrastructure Baseline revision used.</todo>
  
-===== Delivery Phase =====+<todo>Define when Crucible records the Infrastructure Baseline Artifact identifier and revision identifier.</todo>
  
-Phase 1 and subsequent phases+<todo>Define the identifier-resolution mechanism used to resolve the recorded Artifact identifier and revision identifier.</todo>
  
-===== Implementation Status =====+<todo>Define the treatment of failed, incomplete, interrupted, and repeated Infrastructure Deployments.</todo>
  
-Not Assessed+<todo>Define the behavior required when the recorded Artifact identifier or revision identifier cannot be resolved.</todo>
  
-Implementation status requires verification that the current [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] implementation records the Artifact identifier and revision identifier of the Infrastructure Baseline used by each Infrastructure Deployment. +<todo>Define the deployment-specific parameters that the deployment record must preserve separately from the Infrastructure Baseline reference.</todo>
- +
-===== Requirement Status ===== +
- +
-Draft +
- +
-This requirement derives from MO-005 in the Crucible System Requirements Specification, Version 1.1 Draft.+
  
 ---- ----
Line 202: Line 134:
 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 relationship between each Infrastructure Deployment and the specific Infrastructure Baseline revision used.+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 
 +  * Each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] as the Traceability subject 
 +  * The stable Infrastructure Baseline Artifact identifier 
 +  * The Infrastructure Baseline revision identifier 
 +  * The relationship between the Infrastructure Deployment and the specific Infrastructure Baseline revision used
  
 The deployment record should identify: The deployment record should identify:
Line 214: Line 154:
   * The operational environment   * The operational environment
   * The Deployment Platform   * The Deployment Platform
-  * The applicable deployment-specific parameters+  * The deployment-specific parameters
   * The deployment result   * The deployment result
-  * 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-005g.1784562896.txt.gz
  • Last modified: 2026/07/20 08:54
  • by nick_dido