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 the behavior Crucible performsInfrastructure does not identify the managed subject as an Infrastructure BaselineAsset does not use the defined concept ArtifactReusable does not identify the selection, application, or minimum reuse conditionsVersion-controlled combines identification, revision management, preservation, retrieval, and change control without identifying the required behaviorsThe Original Requirement does not identify how each Infrastructure Baseline is uniquely identifiedThe Original Requirement does not identify how revisions of an Infrastructure Baseline are distinguishedThe Original Requirement does not require selection of an approved Infrastructure Baseline for an Infrastructure DeploymentThe Original Requirement does not identify the minimum number of Infrastructure Deployments required to demonstrate reuseThe Original Requirement does not prohibit modification of approved Infrastructure Baseline content during reuseThe Original Requirement does not require each Infrastructure Deployment to identify the Infrastructure Baseline revision usedThe Original Requirement combines Artifact management, identification, Version Control, selection, reuse, immutability, and deployment traceability within one compound normative statementThese obligations can pass or fail independentlyThe Original Requirement does not provide independently identifiable statements for verification and traceabilityThe previously normalized Statement also combined:

Management of each Infrastructure Baseline as an ArtifactUnique identificationVersion ControlSelection for Infrastructure DeploymentReuse across multiple Infrastructure DeploymentsPreservation of approved baseline contentTraceability from each Infrastructure Deployment to the applied Infrastructure Baseline revisionThese obligations can pass or fail independently.

The Original Requirement therefore requires decomposition into independently identifiable normative requirements.

The decomposition preserves MO-005 as the stable parent requirement identifier. Each replacement requirement receives a lettered identifier and a separate requirement page.

Proposed Statements

The Original Requirement is replaced by the following independently identifiable normative requirements:

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