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

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-005f [2026/07/20 08:53] – created nick_didodido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005f [2026/07/30 05:27] (current) – [Delivery Phase] nick_dido
Line 1: Line 1:
-====== MO-005f — Approved Baseline Immutability ======+====== MO-005f — Approved Infrastructure Baseline Preservation ======
  
 [[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 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-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 and version controlled but does not identify how approved content remains controlled during reuse. +
- +
-Without an explicit immutability constraint, reuse could permit: +
- +
-  * Direct modification of an approved revision +
-  * Silent replacement of approved content +
-  * Deployment-specific changes within the approved revision +
-  * Modification without creation of a new revision +
-  * Loss of the content associated with the approval record +
-  * Loss of reproducibility across Infrastructure Deployments +
- +
-The phrase **reusable and version-controlled asset** does not identify: +
- +
-  * The content protected from modification +
-  * The approval state that activates the protection +
-  * The period during which the protection applies +
-  * The distinction between modifying an approved revision and creating a new revision +
-  * The treatment of deployment-specific parameters +
-  * The Evidence required to demonstrate preservation of approved content +
- +
-MO-005f: +
- +
-  * Identifies [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor +
-  * Identifies an approved Infrastructure Baseline revision as the protected subject +
-  * States the prohibited behavior directly through **SHALL NOT** +
-  * Limits the prohibition to modification of approved revision content during reuse +
-  * Distinguishes approved baseline content from deployment-specific parameter values +
-  * Separates immutability from Version Control, selection, reuse, and deployment traceability+
  
 ===== Rationale ===== ===== Rationale =====
Line 65: Line 34:
 Modification of the approved revision during reuse would prevent an evaluator from determining whether multiple Infrastructure Deployments used the same controlled baseline. Modification of the approved revision during reuse would prevent an evaluator from determining whether multiple Infrastructure Deployments used the same controlled baseline.
  
-Approved baseline immutability supports:+Preserving approved Infrastructure Baseline content supports:
  
   * Preservation of the approved configuration   * Preservation of the approved configuration
Line 73: Line 42:
   * Controlled change management   * Controlled change management
   * Recovery of previously approved configurations   * Recovery of previously approved configurations
-  * 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]]+
  
-A required change to approved Infrastructure Baseline content results in creation of a new revision through the applicable Version Control process. The new revision remains distinct from the approved revision from which it derives.+A required change to approved Infrastructure Baseline content creates a new revision through the Version Control process. The new revision remains distinct from the approved revision from which it derives.
  
-This requirement does not prohibit the use of deployment-specific parameters when those parameters remain external to the approved Infrastructure Baseline revision and do not alter its controlled content.+This requirement does not prohibit deployment-specific parameters when those parameters remain external to the approved Infrastructure Baseline revision and do not alter its controlled content.
  
-This requirement does not establish the Version Control process used to create a new revision. MO-005c establishes Version Control.+This requirement does not define the Version Control process used to create a new revision. MO-005c addresses Revision Control.
  
-This requirement does not establish the minimum reuse threshold. MO-005e establishes Infrastructure Baseline reuse.+This requirement does not establish the minimum reuse threshold. MO-005e addresses Infrastructure Baseline reuse.
  
-This requirement does not require an Infrastructure Deployment to record the revision used. MO-005g establishes deployment traceability.+This requirement does not define the Infrastructure Deployment record that identifies the revision used. MO-005g addresses that Traceability.
  
 ===== Applies To ===== ===== Applies To =====
Line 99: Line 67:
   * Revision identifiers   * Revision identifiers
   * Approval records   * Approval records
-  * Version Control records+  * Revision-control records
   * Change records   * Change records
   * Selection records   * Selection records
Line 115: Line 83:
 Verification confirms that: Verification confirms that:
  
-  - The approved Infrastructure Baseline revision is identified+  - The approved [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] revision is identified
   - The content associated with the approved revision is identified   - The content associated with the approved revision is identified
-  - The approval record applies to the identified revision+  - The approval record identifies the approved revision
   - The approved revision content remains unchanged during reuse   - The approved revision content remains unchanged during reuse
-  - Each detected content change results in a distinct revision+  - Each detected content change produces a distinct revision
   - The original approved revision remains retrievable after creation of a subsequent revision   - The original approved revision remains retrievable after creation of a subsequent revision
 +  - Deployment-specific parameters remain external to the approved revision content
   - Deployment-specific parameters do not alter the approved revision content   - Deployment-specific parameters do not alter the approved revision content
-  - The generated Evidence demonstrates preservation of the approved revision content+  - The verification record preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among the approved revision, approval record, reuse events, deployment-specific parameters, subsequent revisions, and preservation result
  
-Verification includes:+===== Referenced By =====
  
-  * Infrastructure Baseline inspection +The following pages reference this requirement:
-  * Artifact identifier inspection +
-  * Revision identifier inspection +
-  * Approval-record inspection +
-  * Approved-content inspection +
-  * Content-integrity inspection +
-  * Content comparison before and after reuse +
-  * Artifact digest comparison +
-  * Version Control history inspection +
-  * New-revision creation testing +
-  * Prior-revision retrieval testing +
-  * Deployment-parameter inspection +
-  * Infrastructure Deployment comparison +
-  * Evidence inspection +
-  * Provenance inspection +
-  * Traceability inspection+
  
-The verification record identifies:+{{backlinks>.#dido:02-crusible}}
  
-  - The Infrastructure Baseline +===== Delivery Phase =====
-  - The stable Artifact identifier +
-  - The approved revision identifier +
-  - The approval status +
-  - The approved content or content reference +
-  - The content-integrity value before reuse +
-  - The content-integrity value after reuse +
-  - Each Infrastructure Deployment involved in the reuse evaluation +
-  - Each deployment-specific parameter applied +
-  - Each detected content difference +
-  - Each new revision created from the approved revision +
-  - The prior-revision retrieval result +
-  - 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 preserves the content of each approved Infrastructure Baseline revision during reuse.</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-005f 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 content included within an approved Infrastructure Baseline revision.</todo>
  
-===== Delivery Phase =====+<todo>Define the integrity mechanism used to determine whether approved Infrastructure Baseline content has changed.</todo>
  
-Phase 1 and subsequent phases+<todo>Define the deployment-specific parameters that remain external to the approved Infrastructure Baseline revision.</todo>
  
-===== Implementation Status =====+<todo>Define the behavior required when Crucible detects an attempted modification of approved Infrastructure Baseline content.</todo>
  
-Not Assessed+<todo>Define the process used to create a new revision when approved Infrastructure Baseline content requires a change.</todo>
  
-Implementation status requires verification that the current [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] implementation preserves the content of an approved Infrastructure Baseline revision during reuse. +<todo>Define the retention period and retrieval requirements for approved Infrastructure Baseline revisions.</todo>
- +
-===== Requirement Status ===== +
- +
-Draft +
- +
-This requirement derives from MO-005 in the Crucible System Requirements Specification, Version 1.1 Draft.+
  
 ---- ----
Line 205: Line 135:
 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 approved Infrastructure Baseline immutability 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 protected subject 
 +  * Prohibition of modification to approved revision content during reuse 
 +  * Creation of a distinct revision when controlled content changes 
 +  * Separation of deployment-specific parameters from approved Infrastructure Baseline content
  
-The immutability record should identify:+The preservation record should identify:
  
   * The stable Infrastructure Baseline Artifact identifier   * The stable Infrastructure Baseline Artifact identifier
Line 213: Line 151:
   * The approval status   * The approval status
   * The approved content or content reference   * The approved content or content reference
-  * The applicable content-integrity value+  * The content-integrity value
   * Each Infrastructure Deployment involved in reuse   * Each Infrastructure Deployment involved in reuse
-  * The deployment-specific parameters applied+  * The deployment-specific parameters
   * Each subsequent revision derived from the approved revision   * Each subsequent revision derived from the approved revision
-  * 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-005f.1784562821.txt.gz
  • Last modified: 2026/07/20 08:53
  • by nick_dido