MO-005f — Approved Infrastructure Baseline Preservation

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:

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.

Preserving approved Infrastructure Baseline content supports:

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

This requirement does not prohibit 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 define the Version Control process used to create a new revision. MO-005c addresses Revision Control.

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

This requirement does not define the Infrastructure Deployment record that identifies the revision used. MO-005g addresses that Traceability.

Applies To

This requirement applies to:

Approved Infrastructure Baseline revisionsInfrastructure Baseline contentArtifactsArtifact identifiersRevision identifiersApproval recordsRevision-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 identifies the approved revisionThe approved revision content remains unchanged during reuseEach detected content change produces a distinct revisionThe original approved revision remains retrievable after creation of a subsequent revisionDeployment-specific parameters remain external to the approved revision contentDeployment-specific parameters do not alter the approved revision contentThe verification record preserves Traceability among the approved revision, approval record, reuse events, deployment-specific parameters, subsequent revisions, and preservation result

Referenced By

The following pages reference this requirement:

Delivery Phase

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

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 actorAn approved Infrastructure Baseline revision as the protected subjectProhibition of modification to approved revision content during reuseCreation of a distinct revision when controlled content changesSeparation of deployment-specific parameters from approved Infrastructure Baseline contentThe preservation record should identify:

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