MO-005f — Approved Infrastructure Baseline Preservation

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

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

This requirement derives from:

• MO-005 — Reusable and Version-Controlled Infrastructure Baselines

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:

• MO-005a — Infrastructure Baseline Artifact Management
• MO-005b — Infrastructure Baseline Identification
• MO-005c — Infrastructure Baseline Revision Control
• MO-005d — Approved Infrastructure Baseline Selection
• MO-005e — Infrastructure Baseline Reuse
• MO-005g — Infrastructure Deployment Baseline Traceability

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 configuration
• Reproducibility across Infrastructure Deployments
• Reliable comparison of deployment results
• Accurate approval records
• Controlled change management
• Recovery of previously approved configurations
• Preservation of Provenance
• Maintenance of Traceability

A 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.

This requirement applies to:

• Crucible
• Infrastructure Baselines
• Approved Infrastructure Baseline revisions
• Infrastructure Baseline content
• Artifacts
• Artifact identifiers
• Revision identifiers
• Approval records
• Revision-control records
• Change records
• Selection records
• Reuse records
• Deployment-specific parameters
• Infrastructure Deployments
• Artifact repositories
• Artifact catalog records
• Evidence
• Provenance
• Traceability

Verification confirms that:

1. The approved Infrastructure Baseline revision is identified
2. The content associated with the approved revision is identified
3. The approval record identifies the approved revision
4. The approved revision content remains unchanged during reuse
5. Each detected content change produces a distinct revision
6. The original approved revision remains retrievable after creation of a subsequent revision
7. Deployment-specific parameters remain external to the approved revision content
8. Deployment-specific parameters do not alter the approved revision content
9. The verification record preserves Traceability among the approved revision, approval record, reuse events, deployment-specific parameters, subsequent revisions, and preservation result

The following pages reference this requirement:

Implemented and Verified.

Assess whether the current Crucible implementation preserves the content of each approved Infrastructure Baseline revision during reuse.

Review and accept MO-005f as a proposed derived requirement created from the evaluation and decomposition of MO-005 in the Crucible System Requirements Specification, Version 1.1 Draft.

The following unresolved issues affect this requirement:

Define the content included within an approved Infrastructure Baseline revision.

Define the integrity mechanism used to determine whether approved Infrastructure Baseline content has changed.

Define the deployment-specific parameters that remain external to the approved Infrastructure Baseline revision.

Define the behavior required when Crucible detects an attempted modification of approved Infrastructure Baseline content.

Define the process used to create a new revision when approved Infrastructure Baseline content requires a change.

Define the retention period and retrieval requirements for approved Infrastructure Baseline revisions.

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:

• Crucible as the responsible actor
• An approved Infrastructure Baseline revision as the protected subject
• Prohibition of modification to approved revision content during reuse
• Creation of a distinct revision when controlled content changes
• Separation of deployment-specific parameters from approved Infrastructure Baseline content

The preservation record should identify:

• The stable Infrastructure Baseline Artifact identifier
• The approved revision identifier
• The approval status
• The approved content or content reference
• The content-integrity value
• Each Infrastructure Deployment involved in reuse
• The deployment-specific parameters
• Each subsequent revision derived from the approved revision
• The associated Provenance
• The associated Traceability

Material 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.