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

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:start [2026/07/20 08:43] – ↷ Page moved and renamed from dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005 to dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:start nick_didodido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:start [2026/07/22 12:20] (current) – nick_dido
Line 1: Line 1:
-====== MO-005 — Reusable and Version-Controlled Infrastructure ======+====== MO-005 — Reusable and Version-Controlled Infrastructure Baselines ======
  
 [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:start|Go to Mission Objectives]] [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:start|Go to Mission Objectives]]
  
-===== Statement =====+===== Original Requirement =====
  
-[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL maintain each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] as a uniquely identified, [[dido:99_annexes:annex-b-terms-and-definitions:v:version_control|version-controlled]] [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] that can be selected and applied to two or more [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployments]] without modifying the approved baseline content.+> //The system SHALL establish infrastructure as a reusable and version-controlled asset.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]
  
-===== Source Statement =====+===== Assessment of Original Requirement =====
  
-> The system SHALL establish infrastructure as a reusable and version-controlled asset. +The Original Requirement preserves the approved mission objective but does not express independently testable normative statements.
- +
-===== Source ===== +
- +
-Crucible System Requirements Specification, Version 1.1 Draft, Mission Objectives, MO-005. +
- +
-===== Assessment ===== +
- +
-The source statement expresses the approved mission objective but does not provide a fully testable formulation.+
  
 The following Specification Discipline and Authoring findings apply: The following Specification Discipline and Authoring findings apply:
  
-  * **The system** does not use the defined system name +  * **The system** does not use the defined system name [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] 
-  * **Establish** does not identify the lifecycle behavior that [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] performs +  * **Establish** is a weak verb that does not identify an observable behavior performed by Crucible 
-  * **Infrastructure** does not identify whether the requirement applies to an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]], deployed infrastructure, infrastructure configuration, or another infrastructure representation +  * **Infrastructure** does not identify the managed subject as an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] 
-  * **Reusable** does not identify the minimum number of uses, permitted variation, selection criteria, or conditions under which reuse occurs +  * **Asset** does not use the defined concept [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] 
-  * **Version-controlled** does not identify the required revision identifier, revision history, repository record, or relationship between revisions +  * **Reusable** does not identify the required reuse behavior 
-  * **Asset** does not identify the managed [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]], its [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact_catalog_record|Artifact Catalog Record]], or the information required to govern the Artifact throughout its lifecycle +  * **Version-controlled** combines several independently testable behaviors without identifying them separately
-  * The source statement does not distinguish modification of an approved baseline from selection and reuse of that baseline +
-  * The source statement does not require a deployment to record the baseline identifier and revision that it uses+
  
-The normalized Statement replaces **establish** with **maintain**, identifies the managed [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]], defines reuse as application to two or more deployments, and prohibits reuse from modifying approved baseline content.+The Original Requirement does not identify:
  
-===== Rationale =====+  * How Crucible manages an Infrastructure Baseline as an Artifact 
 +  * How Crucible uniquely identifies each Infrastructure Baseline 
 +  * How Crucible distinguishes Infrastructure Baseline revisions 
 +  * How an approved Infrastructure Baseline revision is selected for an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] 
 +  * The minimum number of Infrastructure Deployments required to demonstrate reuse 
 +  * Whether approved Infrastructure Baseline content may change during reuse 
 +  * How each Infrastructure Deployment identifies the Infrastructure Baseline revision used
  
-Infrastructure definitions that exist only as deployment-specific scripts or manually maintained configurations cannot be reliably reused, compared, governed, or reproduced.+The Original Requirement therefore requires:
  
-[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] treats each [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] as a managed [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] and maintains an [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact_catalog_record|Artifact Catalog Record]] for the Infrastructure Baseline.+  * Replacement of **the system** with the defined system name [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] 
 +  * Replacement of **establish** with observable Crucible behavior 
 +  * Identification of the managed subject as an Infrastructure Baseline 
 +  * Management of each Infrastructure Baseline as an Artifact 
 +  * Unique identification of each Infrastructure Baseline 
 +  * Identification and preservation of Infrastructure Baseline revisions 
 +  * Selection of an approved Infrastructure Baseline revision for Infrastructure Deployment 
 +  * Reuse of an Infrastructure Baseline revision across multiple Infrastructure Deployments 
 +  * Preservation of approved Infrastructure Baseline content during reuse 
 +  * Traceability from each Infrastructure Deployment to the Infrastructure Baseline revision used 
 +  * Confirmation that the derived requirements collectively preserve the complete intent of MO-005
  
-The Artifact Catalog Record describes the Infrastructure Baseline and its managed lifecycle information, including:+The decomposition preserves ''MO-005'' as the stable parent requirement identifier. Each proposed replacement requirement receives a lettered identifier and a separate leaf requirement page.
  
-  * The stable Artifact identifier +===== Proposed Statements =====
-  * The applicable revision identifier +
-  * The revision history +
-  * The defined source content +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] +
-  * Approval status +
-  * Selection criteria +
-  * Relationships to preceding and succeeding revisions +
-  * Relationships to the [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployments]] that use the baseline+
  
-This treatment permits multiple deployments to use the same approved baseline while preserving the distinction between:+The Original Requirement is decomposed into the following proposed replacement requirements:
  
-  * Reusing an approved baseline +{{indexmenu>dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005#1|js navbar nocookie maxjs#1 id#crucible_mo_005_requirements_nav}}
-  * Creating a new baseline revision +
-  * Applying [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_parameter|Platform Specific Parameters]] +
-  * Recording deployment-specific state +
-  * Recording locally authorized configuration changes+
  
-[[dido:99_annexes:annex-b-terms-and-definitions:v:version_control|Version Control]] preserves baseline content and revision history. The Artifact Catalog Record preserves the managed information and relationships associated with each baseline revision.+===== Requirement Status =====
  
-Together, Version Control and the Artifact Catalog Record support comparison, rollback, [[dido:99_annexes:annex-b-terms-and-definitions:a:auditability|Auditability]], [[dido:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducibility]], and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] throughout the [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]].+<todo>Review and approve the proposed decomposition of MO-005 into independently testable Infrastructure Baseline management, identification, revision-control, selection, reuse, preservation, and Traceability requirements.</todo>
  
-A deployment record identifies the exact Infrastructure Baseline revision used for an environment and references the applicable Artifact Catalog Record. This relationship allows an organization to determine which environments use a baseline revision and which deployments may require review when that baseline changes.+<todo>Determine whether MO-005a through MO-005g collectively supersede MO-005.</todo>
  
-===== Applies To =====+<todo>If MO-005a through MO-005g are accepted as the complete replacement for MO-005, mark MO-005 as superseded and preserve this page as the parent Traceability record.</todo>
  
-This requirement applies to:+---- 
 +===== Issues =====
  
-  * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] +The following unresolved issues affect the decomposition of MO-005:
-  * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible_description|Crucible Descriptions]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_composition|Baseline Composition]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baselines]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployments]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact_catalog_record|Artifact Catalog Records]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact_catalog|Artifact Catalog]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:v:version_control|Version Control]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:r:revision|Revisions]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:r:revision_history|Revision History]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_approval|Baseline Approval]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_selection|Baseline Selection]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_reuse|Baseline Reuse]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_immutability|Baseline Immutability]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_parameter|Platform Specific Parameters]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration_management|Configuration Management]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducibility]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:a:auditability|Auditability]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipelines]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_lifecycle|Operational Lifecycle]]+
  
-===== Verification =====+<todo>Define the Artifact-management requirements that apply to an Infrastructure Baseline.</todo>
  
-  - Verification SHALL confirm that each tested [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] has an [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact_catalog_record|Artifact Catalog Record]] +<todo>Define the identifier assigned to each Infrastructure Baseline and the authority responsible for assigning it.</todo>
-  - Verification SHALL confirm that each tested Artifact Catalog Record identifies the Infrastructure Baseline using a unique Artifact identifier +
-  - Verification SHALL confirm that each tested Artifact Catalog Record identifies the applicable baseline revision +
-  - Verification SHALL confirm that the applicable [[dido:99_annexes:annex-b-terms-and-definitions:v:version_control|Version Control]] system preserves the content associated with each baseline revision +
-  - Verification SHALL confirm that the Artifact Catalog Record preserves the relationships between successive baseline revisions +
-  - Verification SHALL confirm that the Artifact Catalog Record identifies the source and author of each tested baseline revision +
-  - Verification SHALL confirm that the Artifact Catalog Record identifies the approval status of each tested baseline revision +
-  - Verification SHALL confirm that the same approved Infrastructure Baseline can be selected for two or more [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployments]] +
-  - Verification SHALL confirm that reuse of an approved Infrastructure Baseline does not modify the approved baseline content +
-  - Verification SHALL confirm that a change to approved baseline content creates a separately identified revision +
-  - Verification SHALL confirm that each tested Infrastructure Deployment records the Artifact identifier and revision identifier of the selected Infrastructure Baseline +
-  - Verification SHALL confirm that each tested Infrastructure Deployment references the applicable Artifact Catalog Record +
-  - Verification SHALL confirm that [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_parameter|Platform Specific Parameters]] remain distinguishable from the approved baseline content +
-  - Verification SHALL confirm that deployment-specific state remains distinguishable from the approved baseline content +
-  - Verification SHALL confirm that each tested Artifact Catalog Record preserves the applicable [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] +
-  - Verification SHALL confirm that an authorized user can retrieve a prior baseline revision +
-  - Verification SHALL confirm that an authorized user can compare two baseline revisions +
-  - Verification SHALL confirm that the Artifact Catalog Record preserves [[dido:99_annexes:annex-b-terms-and-definitions:a:auditability|Auditability]] and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] for baseline reuse and revision+
  
-Verification may include:+<todo>Define the revision identifier, revision sequence, and change-control rules for Infrastructure Baselines.</todo>
  
-  * Artifact Catalog Record inspection +<todo>Define the approval authority and approval status required before an Infrastructure Baseline revision may be selected for Infrastructure Deployment.</todo>
-  * Artifact identifier inspection +
-  * Revision identifier inspection +
-  * Repository history inspection +
-  * Baseline approval inspection +
-  * Baseline content comparison +
-  * Revision comparison +
-  * Repeated deployment tests +
-  * Cross-platform deployment tests +
-  * Baseline selection tests +
-  * Baseline reuse tests +
-  * Baseline immutability tests +
-  * Platform Specific Parameter inspection +
-  * Deployment-specific state inspection +
-  * Provenance inspection +
-  * Deployment record inspection +
-  * Prior revision retrieval tests +
-  * End-to-end [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]] tests+
  
-The verification record SHALL identify:+<todo>Define the minimum number of Infrastructure Deployments required to demonstrate Infrastructure Baseline reuse.</todo>
  
-  - The tested [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] +<todo>Define whether reuse requires identical Controlled Inputs other than deployment-specific parameters.</todo>
-  - The applicable [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact_catalog_record|Artifact Catalog Record]] +
-  - The Artifact identifier +
-  - The baseline revision identifier +
-  - The baseline source location +
-  - The baseline approval status +
-  - The baseline author +
-  - The preceding revision +
-  - The succeeding revision, when applicable +
-  - The tested [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployments]] +
-  - The Platform Specific Parameters +
-  - The deployment-specific state +
-  - The content comparison result +
-  - The revision comparison result +
-  - The applicable [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] +
-  - The observed results +
-  - The generated [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]+
  
-===== Outgoing Traceability =====+<todo>Define the behavior required when a change to an approved Infrastructure Baseline is necessary.</todo>
  
-This requirement is realized by:+<todo>Define the Traceability record that associates each Infrastructure Deployment with the Infrastructure Baseline identifier and revision used.</todo>
  
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001|OR-001 — Operational Roles]] +<todo>Determine whether MO-005a through MO-005g provide complete coverage of the approved intent of MO-005.</todo>
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-002|OR-002 — Deployment Environments]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-003|OR-003 — Classified and Unclassified Environments]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-004|OR-004 — Concurrent Environment Management]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-005|OR-005 — Distributed Environment Management]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-01-configuration-management:start|FR-CFG-001 through FR-CFG-005]] +
-  * [[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-08-devsecops-integration:start|FR-DSO-001 through FR-DSO-006]] +
-  * [[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]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:09-maintainability-requirements:start|MAINT-001 through MAINT-005]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:10-data-management-requirements:start|DATA-001 through DATA-005]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:13-key-value-proposition-requirements:kvp-003|KVP-003 — Improve deployment repeatability]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:13-key-value-proposition-requirements:kvp-005|KVP-005 — Reduce configuration drift]]+
  
-KVP identifies a Key Value Proposition requirement.+---- 
 +===== Notes for Editors =====
  
-This requirement also relates to:+This page should retain the stable parent requirement identifier ''MO-005''.
  
-  * [[dido:02-crusible:05-descriptions-composition-and-baselines:start|5. Descriptions, Composition, and Baselines]] +This page is a non-leaf requirement page and retains a trailing '':start'' in its namespace.
-  * [[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 =====+The child requirements are leaf requirement pages and omit a trailing '':start'' from their namespaces.
  
-The wiki Backlinks function provides the current list of pages that reference ''MO-005''.+The explicit child-page links should remain while the proposed decomposition is being developed. After the child pages have been created and finalized, the explicit links may be removed because the ''indexmenu'' displays the child requirement pages contained within the MO-005 namespace.
  
-Incoming traceability should be derived dynamically from backlinks rather than maintained as a duplicate manual list.+This page preserves:
  
-Backlinks identify incoming references but do not define the semantics of each relationship. Referencing pages should identify whether the relationship represents realization, refinement, verification, dependency, or another defined traceability relationship. +  * The Original Requirement 
- +  * The assessment of the Original Requirement 
-===== ConOps Relationship ===== +  * The reason for decomposition 
- +  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] to the proposed replacement requirements 
-The Crucible Concept of Operations describes [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline_composition|Baseline Composition]] as the use of versioned Image Layer and [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] repositories alongside consumer source within a [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]] workspace. +  * The unresolved cross-cutting issues affecting the decomposition 
- +  * The supersession decision
-The Phase 1 workflow: +
- +
-  * Selects the required baseline repositories +
-  * Retrieves the identified baseline revisions +
-  * Composes the selected baselines within the workspace +
-  * Applies the selected Infrastructure Baseline +
-  * Applies the required Platform Specific Parameters +
-  * Records the source revision identifiers +
-  * Performs [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] +
-  * Records the baseline identifier and revision used by the deployment +
-  * Preserves deployment history and [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] +
- +
-The ConOps permits a composition to contain application source, Image Layers, Infrastructure Baselines, or a combination of these inputs. A composition that contains only Image Layers or Infrastructure Baselines remains valid. +
- +
-This operational model treats an Infrastructure Baseline as a reusable and versioned deployment input rather than a deployment-specific script or manually recreated configuration. +
- +
-===== Delivery Phase ===== +
- +
-Phase 1 and subsequent phases +
- +
-===== Implementation Status ===== +
- +
-Not Assessed +
- +
-Implementation status requires verification that approved [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baselines]] are uniquely identified, version controlled, reusable across two or more deployments, described by Artifact Catalog Records, and traceable to the deployments that use them. +
- +
-===== Requirement Status ===== +
- +
-Draft +
- +
-The source System Requirements Specification identifies Version 1.1 as a draft. +
- +
----- +
-===== Notes for Editors =====+
  
-This requirement page should retain the stable requirement identifier ''MO-005''.+The derived requirements should distinguish:
  
-Changes to the Statement SHALL preserve the approved intent of the source requirement.+  * Management of an Infrastructure Baseline as an Artifact 
 +  * Identification of an Infrastructure Baseline 
 +  * Identification and control of Infrastructure Baseline revisions 
 +  * Approval and selection of an Infrastructure Baseline revision 
 +  * Reuse of an Infrastructure Baseline revision 
 +  * Preservation of approved Infrastructure Baseline content 
 +  * Traceability from an Infrastructure Deployment to the Infrastructure Baseline revision used
  
-Material changes should receive review and should update the related outbound traceability, verification criteria, baseline governance, acceptance criteria, and source records.+Reuse does not mean modification of an approved Infrastructure Baseline revision. A required change should produce a new controlled revision rather than alter the approved revision already used by prior Infrastructure Deployments.
  
-The Source Statement should preserve the original wording from the controlling System Requirements Specification.+Infrastructure Baseline identification and Infrastructure Baseline revision identification are separate concerns. The baseline identifier identifies the managed baseline, while the revision identifier distinguishes one controlled state of that baseline from another.
  
-Incoming traceability should use the wiki Backlinks function rather than a manually maintained list.+The Original Requirement should not be marked as superseded until the requirement owner:
  
-To reference this requirement Statement from another wiki page, insert:+  * Approves the proposed decomposition 
 +  * Approves the child requirements 
 +  * Defines the Infrastructure Baseline identification and revision-control rules 
 +  * Defines the approval and selection process 
 +  * Defines the minimum reuse condition 
 +  * Defines the preservation and change-control rules 
 +  * Defines the required Infrastructure Deployment Traceability record 
 +  * Confirms that the child requirements collectively preserve the complete approved intent of MO-005 
 +  * Confirms that no additional child requirements are required
  
-<code dokuwiki> +After supersession, this page should remain as the parent Traceability record and should continue to preserve the Original Requirement and its assessment.
-{{section>dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005#Statement&noheader&nofooter&noeditbtn}} +
-</code>+
  
-Do not rename this page after an external citation unless a redirect or move plan is in place.+Material changes to the decomposition should update the child requirements, Requirement Status, Issues, and Traceability records.
  
 ---- ----
  • dido/02-crusible/99-annexes/annex-c-requirements/01-mission-objectives/mo-005/start.1784562196.txt.gz
  • Last modified: 2026/07/20 08:43
  • by nick_dido