MO-005 — Reusable and Version-Controlled Infrastructure Baselines

Go to Mission Objectives

Original Requirement

The system SHALL establish infrastructure as a reusable and version-controlled asset.[C1]

Assessment of Original Requirement

The Original Requirement preserves the approved mission objective but does not express independently testable normative statements.

The following Specification Discipline and Authoring findings apply:

The system does not use the defined system name CrucibleEstablish is a weak verb that does not identify an observable behavior performed by CrucibleInfrastructure does not identify the managed subject as an Infrastructure BaselineAsset does not use the defined concept ArtifactReusable does not identify the required reuse behaviorVersion-controlled combines several independently testable behaviors without identifying them separatelyThe Original Requirement does not identify:

How Crucible manages an Infrastructure Baseline as an ArtifactHow Crucible uniquely identifies each Infrastructure BaselineHow Crucible distinguishes Infrastructure Baseline revisionsHow an approved Infrastructure Baseline revision is selected for an Infrastructure DeploymentThe minimum number of Infrastructure Deployments required to demonstrate reuseWhether approved Infrastructure Baseline content may change during reuseHow each Infrastructure Deployment identifies the Infrastructure Baseline revision usedThe Original Requirement therefore requires:

Replacement of the system with the defined system name CrucibleReplacement of establish with observable Crucible behaviorIdentification of the managed subject as an Infrastructure BaselineManagement of each Infrastructure Baseline as an ArtifactUnique identification of each Infrastructure BaselineIdentification and preservation of Infrastructure Baseline revisionsSelection of an approved Infrastructure Baseline revision for Infrastructure DeploymentReuse of an Infrastructure Baseline revision across multiple Infrastructure DeploymentsPreservation of approved Infrastructure Baseline content during reuseTraceability from each Infrastructure Deployment to the Infrastructure Baseline revision usedConfirmation that the derived requirements collectively preserve the complete intent of MO-005The decomposition preserves MO-005 as the stable parent requirement identifier. Each proposed replacement requirement receives a lettered identifier and a separate leaf requirement page.

Proposed Statements

The Original Requirement is decomposed into the following proposed replacement requirements:

Requirement Status

Issues

The following unresolved issues affect the decomposition of MO-005:

Notes for Editors

This page should retain the stable parent requirement identifier MO-005.

This page is a non-leaf requirement page and retains a trailing :start in its namespace.

The child requirements are leaf requirement pages and omit a trailing :start from their namespaces.

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.

This page preserves:

The Original RequirementThe assessment of the Original RequirementThe reason for decompositionTraceability to the proposed replacement requirementsThe unresolved cross-cutting issues affecting the decompositionThe supersession decisionThe derived requirements should distinguish:

Management of an Infrastructure Baseline as an ArtifactIdentification of an Infrastructure BaselineIdentification and control of Infrastructure Baseline revisionsApproval and selection of an Infrastructure Baseline revisionReuse of an Infrastructure Baseline revisionPreservation of approved Infrastructure Baseline contentTraceability from an Infrastructure Deployment to the Infrastructure Baseline revision usedReuse 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.

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.

The Original Requirement should not be marked as superseded until the requirement owner:

Approves the proposed decompositionApproves the child requirementsDefines the Infrastructure Baseline identification and revision-control rulesDefines the approval and selection processDefines the minimum reuse conditionDefines the preservation and change-control rulesDefines the required Infrastructure Deployment Traceability recordConfirms that the child requirements collectively preserve the complete approved intent of MO-005Confirms that no additional child requirements are requiredAfter supersession, this page should remain as the parent Traceability record and should continue to preserve the Original Requirement and its assessment.

Material changes to the decomposition should update the child requirements, Requirement Status, Issues, and Traceability records.

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.