MO-005c — Infrastructure Baseline Revision Control

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

Statement

Crucible SHALL maintain each Infrastructure Baseline under Version Control.

Derived From

This requirement derives from:

The Original Requirement states:

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

MO-005c preserves the portion of the Original Requirement that requires infrastructure to be version controlled by identifying the controlled subject as an Infrastructure Baseline.

The separate requirements derived from MO-005 address:

Rationale

Version Control preserves the revision history of an Infrastructure Baseline.

A version-controlled Infrastructure Baseline can maintain:

A stable Artifact identifierA distinct identifier for each revisionThe content associated with each revisionThe relationship between successive revisionsThe date and time associated with each revisionThe actor or process responsible for each revisionThe reason for each revisionThe approval status of each revisionThe Provenance associated with each revisionThe Traceability relationships associated with each revisionVersion Control supports:

Retrieval of a specific Infrastructure Baseline revisionComparison of Infrastructure Baseline revisionsIdentification of changes between revisionsReproduction of an Infrastructure Deployment from a selected revisionPreservation of approved revisionsCreation of a new revision when Infrastructure Baseline content changesRecovery from an unintended changeAuditability of Infrastructure Baseline evolutionThe stable Artifact identifier identifies the Infrastructure Baseline across revisions. A revision identifier distinguishes one controlled state of the Infrastructure Baseline from another.

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

This requirement does not prohibit modification of an approved revision. MO-005f addresses preservation of approved Infrastructure Baseline revisions.

This requirement does not require an Infrastructure Deployment to record the revision used. MO-005g addresses that Traceability.

Applies To

This requirement applies to:

Artifact identifiersRevision identifiersRevision historiesRevision relationshipsChange recordsApproval recordsArtifact repositoriesArtifact catalog recordsEvidenceProvenanceTraceability

Verification

Verification confirms that:

Each Infrastructure Baseline is maintained within a Version Control mechanismEach controlled revision is distinguishable from every other revision of the same Infrastructure BaselineEach revision remains associated with the stable Artifact identifier of the Infrastructure BaselineThe content associated with each revision is retrievableThe relationship between successive revisions is recordedThe changes between two revisions can be identifiedA prior revision can be retrieved without replacing or altering another revisionEach revision record identifies the actor or process responsible for the revisionEach revision record identifies the reason for the revisionThe verification record preserves Provenance and Traceability for the revision history

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-005c.

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 actorThe Infrastructure Baseline as the controlled subjectVersion Control as the required management mechanismPreservation and retrieval of distinguishable Infrastructure Baseline revisionsThe Version Control record should identify:

The stable Infrastructure Baseline Artifact identifierThe revision identifierThe predecessor revisionThe revision date and timeThe actor or process responsible for the revisionThe revision descriptionThe reason for the revisionThe approval statusThe 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-005c#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.