MO-005g — Infrastructure Deployment Baseline 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 needed 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:

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 the controlled Infrastructure Baseline state used for the deployment.

Infrastructure Deployment Baseline Traceability supports:

Identification of the source Infrastructure 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 Infrastructure Baseline changes across deployment historyPreservation of ProvenanceMaintenance of TraceabilityThe 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.

Deployment-specific parameters may produce permitted differences between Infrastructure Deployments. The Infrastructure Baseline reference identifies the controlled revision, while the deployment record separately identifies the deployment-specific parameters.

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

This requirement does not establish Revision Control for Infrastructure Baseline revisions. MO-005c addresses Revision Control.

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

Applies To

This requirement applies to:

Infrastructure Baseline revisionsInfrastructure DeploymentsArtifact identifiersRevision identifiersDeployment recordsSelection recordsApproval recordsReuse recordsDeployment-specific parametersArtifact catalog recordsArtifact repository recordsRevision-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 identified Infrastructure BaselineThe recorded revision identifier resolves to the controlled revision used for the Infrastructure DeploymentThe recorded relationship remains associated with the Infrastructure DeploymentFailed or incomplete Infrastructure Deployments retain the Infrastructure Baseline Artifact identifier and revision identifier selected for executionThe verification record preserves Traceability among the Infrastructure Deployment, deployment record, Infrastructure Baseline, revision, selection record, deployment-specific parameters, and deployment result

Referenced By

The following pages reference this requirement:

Delivery Phase

Implemented and Verified.

Implementation Status

Requirement Status

Issues

The following unresolved issues affect this requirement:

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.

The parent MO-005 page is a non-leaf page and retains a trailing :start in its namespace.

Changes to the Statement should preserve:

as the responsible actorEach Infrastructure Deployment as the Traceability subjectThe stable Infrastructure Baseline Artifact identifierThe Infrastructure Baseline revision identifierThe relationship between the Infrastructure Deployment and the specific Infrastructure Baseline revision usedThe 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 deployment-specific parametersThe deployment resultThe associated ProvenanceThe associated TraceabilityMaterial changes should receive review and should update the verification criteria, source records, and Issues section.

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.