MO-005g — Baseline Revision Deployment Traceability

Go to MO-005 — Reusable and Version-Controlled Infrastructure Baselines

Statement

Crucible SHALL record the Artifact identifier and revision identifier of the Infrastructure Baseline used by each Infrastructure Deployment.

Derived From

This requirement derives from:

The Original Requirement states:

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

MO-005g preserves the traceability necessary to demonstrate reuse of a version-controlled Infrastructure Baseline by requiring each Infrastructure Deployment to identify the specific Infrastructure Baseline revision used.

The separate requirements derived from MO-005 address:

Assessment

The Original Requirement describes infrastructure as reusable and version controlled but does not require an Infrastructure Deployment to identify the specific Infrastructure Baseline revision used.

Without this relationship, an evaluator cannot reliably determine:

Which Infrastructure Baseline produced an Infrastructure DeploymentWhich revision of the Infrastructure Baseline appliedWhether two Infrastructure Deployments reused the same revisionWhether an approved revision or another revision appliedWhether a later deployment used a superseded revisionWhether deployment results remain reproducibleWhether the deployment record preserves adequate Provenance and TraceabilityThe phrase reusable and version-controlled asset does not identify:

The deployment record that preserves the relationshipThe stable Artifact identifier of the Infrastructure BaselineThe revision identifier of the applied baselineThe Infrastructure Deployment associated with the baseline revisionThe point at which the relationship is recordedThe treatment of failed or incomplete deploymentsThe Evidence required to demonstrate the relationshipMO-005g:

Identifies Crucible as the responsible actorIdentifies each Infrastructure Deployment as the traceability subjectIdentifies the stable Artifact identifier and revision identifier as the required baseline referenceEstablishes a direct relationship between an Infrastructure Deployment and the Infrastructure Baseline revision usedSeparates deployment traceability from Artifact management, identification, Version Control, selection, reuse, and immutability

Rationale

An Infrastructure Deployment represents a realized infrastructure instance produced from a selected Infrastructure Baseline revision.

Recording the stable Artifact identifier and revision identifier enables an evaluator to determine exactly which controlled Infrastructure Baseline state Crucible used for the deployment.

Baseline revision deployment traceability supports:

Identification of the source baseline for each Infrastructure DeploymentConfirmation that multiple Infrastructure Deployments reused the same revisionReproduction of an Infrastructure DeploymentComparison of deployments created from the same revisionComparison of deployments created from different revisionsDetection of deployments created from superseded or unapproved revisionsEvaluation of baseline changes across deployment historyPreservation of ProvenanceMaintenance of TraceabilityGeneration of auditable EvidenceThe stable Artifact identifier identifies the Infrastructure Baseline across its revision history. The revision identifier identifies the controlled Infrastructure Baseline state used for the Infrastructure Deployment.

The recorded relationship remains applicable when deployment-specific parameters produce permitted differences between Infrastructure Deployments. The baseline reference identifies the controlled baseline revision, while the deployment record separately identifies the parameters applied to the deployment.

This requirement does not assign the stable Artifact identifier. MO-005b establishes Infrastructure Baseline identification.

This requirement does not establish Version Control for Infrastructure Baseline revisions. MO-005c establishes Version Control.

This requirement does not require reuse of the same revision across multiple Infrastructure Deployments. MO-005e establishes reuse.

Applies To

This requirement applies to:

Infrastructure Baseline revisionsInfrastructure DeploymentsArtifact identifiersRevision identifiersDeployment recordsSelection recordsApproval recordsReuse recordsDeployment-specific parametersArtifact catalog recordsArtifact repositoriesVersion Control recordsEvidenceProvenanceTraceability

Verification

Verification confirms that:

Each Infrastructure Deployment has an associated deployment recordThe deployment record identifies the Infrastructure Baseline usedThe deployment record contains the stable Artifact identifier of the Infrastructure BaselineThe deployment record contains the revision identifier of the Infrastructure Baseline revision usedThe recorded Artifact identifier resolves to the applicable Infrastructure BaselineThe recorded revision identifier resolves to the controlled revision used for the deploymentThe recorded relationship remains associated with the Infrastructure DeploymentThe deployment record preserves the required Evidence, Provenance, and TraceabilityVerification includes:

Infrastructure Deployment inspectionDeployment-record inspectionInfrastructure Baseline inspectionArtifact identifier inspectionRevision identifier inspectionArtifact catalog inspectionArtifact repository inspectionVersion Control record inspectionBaseline-selection record inspectionIdentifier-resolution testingCross-deployment record comparisonEvidence inspectionProvenance inspectionTraceability inspectionThe verification record identifies:

The Infrastructure DeploymentThe associated deployment recordThe Infrastructure BaselineThe stable Artifact identifierThe applied revision identifierThe Artifact catalog recordThe Version Control recordThe baseline-selection recordThe identifier-resolution resultThe applicable deployment-specific parametersEach missing, invalid, or conflicting baseline referenceEach identified failure or exceptionThe observed resultThe generated Evidence

Requirements Realized By

This requirement is realized by:

Related Architecture Sections

Referenced By

The following pages reference this requirement:

Delivery Phase

Phase 1 and subsequent phases

Implementation Status

Not Assessed

Implementation status requires verification that the current Crucible implementation records the Artifact identifier and revision identifier of the Infrastructure Baseline used by each Infrastructure Deployment.

Requirement Status

Draft

This requirement derives from MO-005 in the Crucible System Requirements Specification, Version 1.1 Draft.

Notes for Editors

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

This page is a leaf requirement page and omits a trailing :start from its namespace.

Changes to the Statement should preserve the relationship between each Infrastructure Deployment and the specific Infrastructure Baseline revision used.

The deployment record should identify:

The Infrastructure Deployment identifierThe stable Infrastructure Baseline Artifact identifierThe applied revision identifierThe approval status of the applied revisionThe baseline-selection recordThe deployment date and timeThe operational environmentThe Deployment PlatformThe applicable deployment-specific parametersThe deployment resultThe associated ProvenanceThe associated TraceabilityThe supporting EvidenceMaterial changes should receive review and should update the related verification criteria, requirements realization, related architecture sections, and source records.

To reference this requirement Statement from another wiki page, insert:

{{section>dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005g#Statement&noheader&nofooter&noeditbtn}}

Do not rename this page after an external citation unless a redirect or move plan is in place.

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