MO-005g — Infrastructure Deployment Baseline Traceability

Crucible SHALL record the Artifact identifier and revision identifier of the Infrastructure Baseline used by each Infrastructure Deployment.

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:

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 Deployment
  • Confirmation that multiple Infrastructure Deployments reused the same revision
  • Reproduction of an Infrastructure Deployment
  • Comparison of deployments created from the same revision
  • Comparison of deployments created from different revisions
  • Detection of deployments created from superseded or unapproved revisions
  • Evaluation of Infrastructure Baseline changes across deployment history
  • Preservation of Provenance
  • Maintenance of Traceability

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

This requirement applies to:

Verification confirms that:

  1. Each Infrastructure Deployment has an associated deployment record
  2. The deployment record identifies the Infrastructure Baseline used
  3. The deployment record contains the stable Artifact identifier of the Infrastructure Baseline
  4. The deployment record contains the revision identifier of the Infrastructure Baseline revision used
  5. The recorded Artifact identifier resolves to the identified Infrastructure Baseline
  6. The recorded revision identifier resolves to the controlled revision used for the Infrastructure Deployment
  7. The recorded relationship remains associated with the Infrastructure Deployment
  8. Failed or incomplete Infrastructure Deployments retain the Infrastructure Baseline Artifact identifier and revision identifier selected for execution
  9. The verification record preserves Traceability among the Infrastructure Deployment, deployment record, Infrastructure Baseline, revision, selection record, deployment-specific parameters, and deployment result

Implemented and Verified.

Assess whether the current Crucible implementation records the Artifact identifier and revision identifier of the Infrastructure Baseline used by each Infrastructure Deployment.

Review and accept MO-005g 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 deployment record that preserves the relationship between an Infrastructure Deployment and the Infrastructure Baseline revision used.

Define when Crucible records the Infrastructure Baseline Artifact identifier and revision identifier.

Define the identifier-resolution mechanism used to resolve the recorded Artifact identifier and revision identifier.

Define the treatment of failed, incomplete, interrupted, and repeated Infrastructure Deployments.

Define the behavior required when the recorded Artifact identifier or revision identifier cannot be resolved.

Define the deployment-specific parameters that the deployment record must preserve separately from the Infrastructure Baseline reference.


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:

  • Crucible as the responsible actor
  • Each Infrastructure Deployment as the Traceability subject
  • The stable Infrastructure Baseline Artifact identifier
  • The Infrastructure Baseline revision identifier
  • The relationship between the Infrastructure Deployment and the specific Infrastructure Baseline revision used

The deployment record should identify:

  • The Infrastructure Deployment identifier
  • The stable Infrastructure Baseline Artifact identifier
  • The applied revision identifier
  • The approval status of the applied revision
  • The baseline-selection record
  • The deployment date and time
  • The operational environment
  • The Deployment Platform
  • The deployment-specific parameters
  • The deployment result
  • 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-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.

  • dido/02-crusible/99-annexes/annex-c-requirements/01-mission-objectives/mo-005/mo-005g.txt
  • Last modified: 2026/07/30 05:27
  • by nick_dido