MO-005f — Approved Baseline Immutability

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

Statement

Crucible SHALL NOT modify the content of an approved Infrastructure Baseline revision during reuse.

Derived From

This requirement derives from:

The Original Requirement states:

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

MO-005f preserves the controlled-reuse intent of the Original Requirement by prohibiting modification of approved Infrastructure Baseline content during reuse.

The separate requirements derived from MO-005 address:

Assessment

The Original Requirement describes infrastructure as reusable and version controlled but does not identify how approved content remains controlled during reuse.

Without an explicit immutability constraint, reuse could permit:

Direct modification of an approved revisionSilent replacement of approved contentDeployment-specific changes within the approved revisionModification without creation of a new revisionLoss of the content associated with the approval recordLoss of reproducibility across Infrastructure DeploymentsThe phrase reusable and version-controlled asset does not identify:

The content protected from modificationThe approval state that activates the protectionThe period during which the protection appliesThe distinction between modifying an approved revision and creating a new revisionThe treatment of deployment-specific parametersThe Evidence required to demonstrate preservation of approved contentMO-005f:

Identifies Crucible as the responsible actorIdentifies an approved Infrastructure Baseline revision as the protected subjectStates the prohibited behavior directly through SHALL NOTLimits the prohibition to modification of approved revision content during reuseDistinguishes approved baseline content from deployment-specific parameter valuesSeparates immutability from Version Control, selection, reuse, and deployment traceability

Rationale

An approved Infrastructure Baseline revision represents a controlled configuration accepted for use.

Modification of the approved revision during reuse would prevent an evaluator from determining whether multiple Infrastructure Deployments used the same controlled baseline.

Approved baseline immutability supports:

Preservation of the approved configurationReproducibility across Infrastructure DeploymentsReliable comparison of deployment resultsAccurate approval recordsControlled change managementRecovery of previously approved configurationsPreservation of ProvenanceMaintenance of TraceabilityGeneration of auditable EvidenceA required change to approved Infrastructure Baseline content results in creation of a new revision through the applicable Version Control process. The new revision remains distinct from the approved revision from which it derives.

This requirement does not prohibit the use of deployment-specific parameters when those parameters remain external to the approved Infrastructure Baseline revision and do not alter its controlled content.

This requirement does not establish the Version Control process used to create a new revision. MO-005c establishes Version Control.

This requirement does not establish the minimum reuse threshold. MO-005e establishes Infrastructure Baseline reuse.

This requirement does not require an Infrastructure Deployment to record the revision used. MO-005g establishes deployment traceability.

Applies To

This requirement applies to:

Approved Infrastructure Baseline revisionsInfrastructure Baseline contentArtifactsArtifact identifiersRevision identifiersApproval recordsVersion Control recordsChange recordsSelection recordsReuse recordsDeployment-specific parametersInfrastructure DeploymentsArtifact repositoriesArtifact catalog recordsEvidenceProvenanceTraceability

Verification

Verification confirms that:

The approved Infrastructure Baseline revision is identifiedThe content associated with the approved revision is identifiedThe approval record applies to the identified revisionThe approved revision content remains unchanged during reuseEach detected content change results in a distinct revisionThe original approved revision remains retrievable after creation of a subsequent revisionDeployment-specific parameters do not alter the approved revision contentThe generated Evidence demonstrates preservation of the approved revision contentVerification includes:

Infrastructure Baseline inspectionArtifact identifier inspectionRevision identifier inspectionApproval-record inspectionApproved-content inspectionContent-integrity inspectionContent comparison before and after reuseArtifact digest comparisonVersion Control history inspectionNew-revision creation testingPrior-revision retrieval testingDeployment-parameter inspectionInfrastructure Deployment comparisonEvidence inspectionProvenance inspectionTraceability inspectionThe verification record identifies:

The Infrastructure BaselineThe stable Artifact identifierThe approved revision identifierThe approval statusThe approved content or content referenceThe content-integrity value before reuseThe content-integrity value after reuseEach Infrastructure Deployment involved in the reuse evaluationEach deployment-specific parameter appliedEach detected content differenceEach new revision created from the approved revisionThe prior-revision retrieval resultEach 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 preserves the content of an approved Infrastructure Baseline revision during reuse.

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

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

Changes to the Statement should preserve the approved Infrastructure Baseline immutability intent derived from MO-005.

The immutability record should identify:

The stable Infrastructure Baseline Artifact identifierThe approved revision identifierThe approval statusThe approved content or content referenceThe applicable content-integrity valueEach Infrastructure Deployment involved in reuseThe deployment-specific parameters appliedEach subsequent revision derived from the approved revisionThe 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-005f#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.