MO-005

Go to Mission Objectives

Statement

Crucible SHALL maintain each Infrastructure Baseline as a uniquely identified, version-controlled Artifact that can be selected and applied to more than one Infrastructure Deployment without modifying the approved baseline content.

Source Statement

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

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 system does not use the defined system nameEstablish does not identify the lifecycle behavior that Crucible performsInfrastructure does not identify whether the requirement applies to an Infrastructure Baseline, deployed infrastructure, infrastructure configuration, or another infrastructure representationReusable does not identify the number of uses, permitted variation, selection criteria, or conditions under which reuse occursVersion-controlled does not identify the required revision identifier, revision history, repository record, or relationship between revisionsAsset does not identify the information, configuration, provenance, and lifecycle records that constitute the managed assetThe source statement does not distinguish modification of an approved baseline from selection and reuse of that baselineThe normalized Statement replaces establish with maintain, identifies the managed Infrastructure Baseline, and defines reuse as application to more than one Infrastructure Deployment without modifying the approved baseline content.

Rationale

Infrastructure definitions that exist only as deployment-specific scripts or manually maintained configurations cannot be reliably reused, compared, governed, or reproduced.

Crucible treats each Infrastructure Baseline as a managed Artifact with:

A stable identifierA revision identifierA revision historyDefined source contentProvenanceApproval statusSelection criteriaRelationships to preceding and succeeding revisionsRelationships to the Infrastructure Deployments that use the baselineThis treatment permits multiple deployments to use the same approved baseline while preserving the distinction between:

Reusing an approved baselineCreating a new baseline revisionApplying platform specific parametersRecording deployment-specific stateVersion Control preserves the baseline history and supports comparison, rollback, audit, Reproducibility, and Traceability throughout the Operational Lifecycle.

Applies To

This requirement applies to:

Verification

Verification SHALL confirm that each tested Infrastructure Baseline has a unique identifierVerification SHALL confirm that each tested Infrastructure Baseline has a revision identifierVerification SHALL confirm that the applicable Version Control system preserves the content associated with each baseline revisionVerification SHALL confirm that the applicable Version Control system preserves the relationship between successive baseline revisionsVerification SHALL confirm that the same approved Infrastructure Baseline can be selected for more than one Infrastructure DeploymentVerification SHALL confirm that reuse of the approved Infrastructure Baseline does not modify the approved baseline contentVerification SHALL confirm that changes to approved baseline content create a separately identified revisionVerification SHALL confirm that each tested Infrastructure Deployment records the identifier and revision of the selected Infrastructure BaselineVerification SHALL confirm that platform specific parameters remain distinguishable from the approved baseline contentVerification SHALL confirm that the baseline record preserves the applicable ProvenanceVerification SHALL confirm that an authorized user can retrieve a prior baseline revisionVerification SHALL confirm that an authorized user can compare two baseline revisionsVerification SHALL confirm that baseline reuse and revision records preserve TraceabilityVerification may include:

Baseline identifier inspectionRevision identifier inspectionRepository history inspectionBaseline content comparisonRevision comparisonRepeated deployment testsCross platform deployment testsBaseline selection testsBaseline immutability testsProvenance record inspectionDeployment record inspectionPrior revision retrieval testsEnd-to-end CI/CD Pipeline testsThe verification record SHALL identify:

The tested Infrastructure BaselineThe baseline identifierThe baseline revision identifierThe baseline source locationThe baseline approval statusThe preceding revisionThe succeeding revision, when applicableThe tested Infrastructure DeploymentsThe platform specific parametersThe content comparison resultThe revision comparison resultThe applicable ProvenanceThe observed resultsThe generated Evidence

Outgoing Traceability

This requirement is realized by:

This requirement also relates to:

Referenced By

The wiki Backlinks function provides the current list of pages that reference `MO-005`.

Incoming traceability should be derived dynamically from backlinks rather than maintained as a duplicate manual list.

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.

ConOps Relationship

The Crucible Concept of Operations describes Baseline Composition as the use of versioned Image Layer and Infrastructure Baseline repositories alongside consumer source within a CI/CD Pipeline workspace.

The Phase 1 workflow:

Selects the required baseline repositoriesRetrieves the identified baseline revisionsComposes the selected baselines within the workspaceApplies the selected Infrastructure BaselineRecords the source revision identifiersPerforms Infrastructure DeploymentPreserves deployment history and ProvenanceThe 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 Infrastructure Baselines are uniquely identified, version controlled, reusable across multiple deployments, 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`.

Changes to the Statement SHALL preserve the approved intent of the source requirement.

Material changes should receive review and should update the related outbound traceability, verification criteria, acceptance criteria, and source records.

The Source Statement should preserve the original wording from the controlling System Requirements Specification.

Incoming traceability should use the wiki Backlinks function rather than a manually maintained list.

Do not rename this page once it has been cited externally unless a redirect or move plan is in place.

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