MO-005e — Infrastructure Baseline Reuse [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== MO-005e — Infrastructure Baseline Reuse ======

[[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:start|Go to MO-005 — Reusable and Version-Controlled Infrastructure Baselines]]

===== Statement =====

[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL apply the same approved [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] revision to two or more [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployments]].

===== Derived From =====

This requirement derives from:

  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:start|MO-005 — Reusable and Version-Controlled Infrastructure Baselines]]

The Original Requirement states:

> //The system SHALL establish infrastructure as a reusable and version-controlled asset.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]

MO-005e preserves the reuse intent of the Original Requirement by requiring [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] to apply the same approved Infrastructure Baseline revision to multiple Infrastructure Deployments.

The separate requirements derived from MO-005 address:

  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005a|MO-005a — Infrastructure Baseline Artifact Management]]
  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005b|MO-005b — Infrastructure Baseline Identification]]
  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005c|MO-005c — Infrastructure Baseline Revision Control]]
  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005d|MO-005d — Approved Infrastructure Baseline Selection]]
  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005f|MO-005f — Approved Infrastructure Baseline Preservation]]
  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005g|MO-005g — Infrastructure Deployment Baseline Traceability]]

===== Rationale =====

Reuse occurs when [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] applies the same approved Infrastructure Baseline revision to more than one Infrastructure Deployment.

The minimum threshold of two Infrastructure Deployments distinguishes demonstrated reuse from a single application of an Infrastructure Baseline revision.

Reuse supports:

  * Consistent infrastructure composition
  * Reduction of duplicated configuration effort
  * Repeatable deployment processes
  * Comparison of Infrastructure Deployments created from the same Infrastructure Baseline revision
  * Reproduction of previously deployed infrastructure
  * Controlled deployment across multiple operational environments
  * Controlled deployment across multiple Deployment Platforms
  * Preservation of approved infrastructure configurations
  * Preservation of [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
  * Maintenance of [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]

The Infrastructure Deployments may differ in deployment instance, location, operational environment, Deployment Platform, execution time, or intended use, provided that Crucible applies the same approved Infrastructure Baseline revision.

The resulting Infrastructure Environments need not be identical when permitted deployment-specific parameters or Provider Implementations produce controlled differences.

This requirement does not permit modification of the approved Infrastructure Baseline revision during reuse. MO-005f addresses preservation of approved revisions.

This requirement does not define the deployment record that identifies the applied Infrastructure Baseline revision. MO-005g addresses that Traceability.

===== Applies To =====

This requirement applies to:

  * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baselines]]
  * Approved Infrastructure Baseline revisions
  * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployments]]
  * Artifact identifiers
  * Revision identifiers
  * Approval records
  * Selection records
  * Deployment records
  * Deployment Platforms
  * Operational environments
  * Deployment-specific parameters
  * Provider Implementations
  * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]

===== Verification =====

Verification confirms that:

  - The approved [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] revision is identified
  - Two or more [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployments]] are identified
  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] applies the same approved Infrastructure Baseline revision to each identified Infrastructure Deployment
  - The Infrastructure Baseline Artifact identifier is the same for each identified Infrastructure Deployment
  - The Infrastructure Baseline revision identifier is the same for each identified Infrastructure Deployment
  - The approved Infrastructure Baseline content remains unchanged across the identified Infrastructure Deployments
  - Each Infrastructure Deployment completes with an identified result
  - Each permitted difference among the Infrastructure Deployments is attributable to identified deployment-specific parameters or Provider Implementations
  - The verification record preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among the approved Infrastructure Baseline revision, each Infrastructure Deployment, the deployment-specific parameters, the Provider Implementation, and the deployment result

===== Referenced By =====

The following pages reference this requirement:

{{backlinks>.#dido:02-crusible}}

===== Delivery Phase =====

Implemented and Verified.

===== Implementation Status =====

<todo>Assess whether the current Crucible implementation applies the same approved Infrastructure Baseline revision to two or more Infrastructure Deployments.</todo>

===== Requirement Status =====

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

----
===== Issues =====

The following unresolved issues affect this requirement:

<todo>Confirm that two Infrastructure Deployments provide the minimum sufficient demonstration of Infrastructure Baseline reuse.</todo>

<todo>Define the criteria used to determine that two Infrastructure Deployments apply the same Infrastructure Baseline revision.</todo>

<todo>Define the deployment-specific parameters that may differ without changing the reused Infrastructure Baseline revision.</todo>

<todo>Define the permitted differences among Infrastructure Environments produced from the same approved Infrastructure Baseline revision.</todo>

<todo>Define whether reuse across different Deployment Platforms or operational environments requires additional equivalence criteria.</todo>

----
===== Notes for Editors =====

This requirement page should retain the stable requirement identifier ''MO-005e''.

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:

  * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor
  * An approved [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] revision as the reused subject
  * Application of the same revision to two or more Infrastructure Deployments
  * Two Infrastructure Deployments as the minimum demonstrated reuse threshold

The reuse record should identify:

  * The stable Infrastructure Baseline Artifact identifier
  * The applied revision identifier
  * The approval status of the applied revision
  * Each Infrastructure Deployment
  * The application date and time
  * The operational environment
  * The Deployment Platform
  * The deployment-specific parameters
  * The Provider Implementation
  * The application result
  * The associated [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
  * The associated [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|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:

<code dokuwiki>
{{section>dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-005:mo-005e#Statement&noheader&nofooter&noeditbtn}}
</code>

Do not rename this page after an external citation unless a redirect or move plan is in place.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>