dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003:mo-003c

This is an old revision of the document!


MO-003c — Common Infrastructure Baseline

Crucible SHALL use the same identified version of the Infrastructure Baseline for each selected Deployment Platform.

This requirement derives from:

The Original Requirement states:

The system SHALL provide cloud-agnostic deployment capabilities.[C3]

MO-003c preserves the portion of the Original Requirement that requires a common Infrastructure Baseline across the selected Deployment Platforms.

The separate requirements derived from MO-003 address:

The Original Requirement does not identify the infrastructure requirements that remain common across Cloud Providers or Deployment Platforms.

The phrase cloud-agnostic deployment capabilities does not identify:

  • The common Infrastructure Baseline
  • The version of the Infrastructure Baseline
  • The Deployment Platforms to which the Infrastructure Baseline applies
  • The distinction between baseline requirements and platform-specific implementation details
  • The criteria used to determine whether the same Infrastructure Baseline was applied to each deployment

MO-003c:

  • Identifies the Infrastructure Baseline as the common source of infrastructure requirements
  • Requires use of the same identified Infrastructure Baseline version across the selected Deployment Platforms
  • Prevents a change of target Deployment Platform from implicitly changing the common infrastructure requirements
  • Separates common Infrastructure Baseline use from cross-platform deployment, common Crucible Description use, and provider-specific dependency limitation

A common Infrastructure Baseline establishes consistent infrastructure requirements across multiple Deployment Platforms.

The Infrastructure Baseline defines the required infrastructure characteristics independently of the provider-specific mechanisms used to realize those characteristics.

Using the same identified version supports:

  • Consistent infrastructure requirements
  • Controlled comparison of deployment results
  • Change control
  • Cross-platform evaluation
  • Detection of platform-specific changes to common baseline requirements
  • Reuse across supported Deployment Platforms

The requirement uses an identified version rather than the unqualified word same. The identifier and version establish the specific Infrastructure Baseline applied to each deployment.

Provider-specific implementations can realize the common Infrastructure Baseline through different platform mechanisms. Those mechanisms do not change the requirements established by the identified Infrastructure Baseline.

This requirement does not require use of the same Crucible Description. MO-003b establishes that requirement.

Verification confirms that:

  1. Two or more selected Deployment Platforms are identified
  2. Each deployment uses an Infrastructure Baseline with the same identifier
  3. Each deployment uses the same identified version of the Infrastructure Baseline
  4. The Infrastructure Baseline defines common infrastructure requirements
  5. Changing the selected Deployment Platform does not require modification of the identified Infrastructure Baseline version
  6. Platform-specific implementation mechanisms do not alter the requirements established by the Infrastructure Baseline
  7. The deployment records identify the Infrastructure Baseline identifier and version used for each Deployment Platform

Verification includes:

  • Infrastructure Baseline inspection
  • Infrastructure Baseline identifier comparison
  • Infrastructure Baseline version comparison
  • Artifact Representation comparison
  • Cryptographic digest inspection
  • Platform-independent information inspection
  • Platform-specific information inspection
  • Cross-platform deployment tests
  • Resulting Infrastructure Environment comparison
  • Deployment-record inspection
  • Provenance inspection
  • Traceability inspection
  • Evidence inspection

The verification record identifies:

  1. The selected Deployment Platforms
  2. The Infrastructure Baseline identifier
  3. The Infrastructure Baseline version
  4. The applicable Infrastructure Baseline Artifact Representation
  5. The cryptographic digest of the applicable Artifact Representation
  6. The common infrastructure requirements
  7. The platform-specific implementation mechanisms used for each Deployment Platform
  8. The deployment result for each Deployment Platform
  9. The resulting Infrastructure Environment for each Deployment Platform
  10. Any detected modification to the Infrastructure Baseline
  11. The observed result
  12. The generated Evidence

Phase 1 and subsequent phases

Not Assessed

Implementation status requires verification that deployments to the selected Deployment Platforms use the same identified version of the Infrastructure Baseline.

Draft

This requirement derives from MO-003 in the Crucible System Requirements Specification, Version 1.1 Draft.


This requirement page should retain the stable requirement identifier MO-003c.

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

Changes to the Statement SHALL preserve the common Infrastructure Baseline intent derived from MO-003.

The applicable deployment records should identify:

  • The Infrastructure Baseline identifier
  • The Infrastructure Baseline version
  • The applicable Artifact Representation
  • The cryptographic digest
  • The selected Deployment Platform
  • The applicable Provider Implementation
  • The platform-specific implementation mechanisms used for the deployment
  • The deployment result
  • The resulting Infrastructure Environment
  • The supporting Evidence

Material 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-003:mo-003c#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-003/mo-003c.1784561264.txt.gz
  • Last modified: 2026/07/20 08:27
  • by nick_dido